What is amaa-design-lifecycle?

A process for managing design documents from an initial draft through review, approval, implementation, and archiving. It also defines how to revise a design when problems appear during development.

Use it to create and track design documents, submit them for review, prepare implementation handoffs, record progress, and handle redesigns.

It gives teams clear states and handoffs, reducing confusion about which designs are approved, being implemented, or need changes.

amaa-design-lifecycle — Skill for Claude Code by Emasoft

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add Emasoft/ai-maestro-architect-agent

Claude Code

/plugin install ai-maestro-architect-agent

Made for: Claude Code.

Or install ai-maestro-architect-agent, the plugin that ships this one along with the rest of its 27 skills, 4 commands, 5 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle/github.svg)](https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle)

Your own site

<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-design-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.01333
Opus 5	$0.00017	$0.00666
Sonnet 5	$0.00007	$0.00267
Haiku 4.5	$0.00003	$0.00133

Measured 10d ago against content hash c54dbbab327b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

amaa-design-lifecycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/amaa-design-lifecycle/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Lifecycle Skill

Overview

Manages the complete lifecycle of design documents: creation, review, approval, implementation tracking, and archival. Enforces valid state transitions (DRAFT->REVIEW->APPROVED->IMPLEMENTED->ARCHIVED, plus DEPRECATED/SUPERSEDED as terminal off-ramps) plus the redesign-loop re-entry edge IMPLEMENTED->REVIEW (so a design flaw surfaced mid-dev can be pulled back and revised), and generates handoff documents for implementers.

Checklist

Copy this checklist and track your progress:

Receive requirements via AMCOS (the team boundary)
Research APIs/technologies
Create design documents in docs_dev/design/
Generate design UUID and register in index with state DRAFT
Complete design and validate checklist
Submit for review (state: REVIEW)
Address review comments
Update state to APPROVED
Create handoff document for AMOA
Report completion to AMCOS
Track implementation progress
If a design flaw surfaces mid-dev (relayed by ORCH): run the redesign loop (IMPLEMENTED->REVIEW), revise or split/group, re-approve
Archive when complete (state: ARCHIVED)

Prerequisites

Write access to docs_dev/design/ directory for design documents
Design scripts available at ${CLAUDE_PLUGIN_ROOT}/scripts/amaa_design_*.py

Instructions

Receive requirements via AMCOS (the team boundary)
Research APIs/technologies and create design documents in docs_dev/design/
Generate design UUID and register in index with state DRAFT
Complete design, validate checklist, submit for review (state: REVIEW)
Address review comments, update state to APPROVED
Create handoff document for AMOA, report completion to AMCOS
Track implementation progress, archive when complete (state: ARCHIVED)

Reference Documents

Reference	Description
procedures.md	PROCEDURE 1: Create New Design, PROCEDURE 2: Submit for Review, PROCEDURE 3: Approve Design, PROCEDURE 4: Track Implementation, PROCEDURE 5: Complete and Archive
design-states.md	State Definitions + the redesign loop (mid-dev re-entry)
op-manage-state-transitions.md	When to Use, Prerequisites, Procedure, State Transition Rules, Checklist, Examples, Error Handling
op-accept-redesign-request.md	When to Use, Prerequisites, Procedure, Checklist, Related Operations, Related Templates
examples.md	Example 1: Design Real-Time Collaborative Editor, Example 2: Design Stripe Payment Integration, Example 3: Create and Submit Design for Review (Lifecycle), Example 4: Approve and Track Implementation (Lifecycle)
scripts.md	Script Reference
rule-14-enforcement.md	1 When handling user requirements in any workflow, 2 When detecting potential requirement deviations, 3 When a technical constraint conflicts with a requirement, 4 When documenting requirement compliance

Read the full file on GitHub · 113 lines

Files

What ships with it

24 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 113 lines · 34 tokens per session scan A c54dbbab327b

Subscribe to this mod's changes

amaa-design-lifecycle is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 1,333 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

amaa-design-lifecycle