aet-req-design

Provide the requirements analysis specification and access to the project codebase as mandatory inputs. The skill runs a four-stage pipeline: codebase exploration, design with feasibility verification, template-based document generation, and an optional review stage, producing an SDD-style design specification.

Two mandatory inputs are required: the requirements analysis specification from the previous phase and access to the current project codebase. Optional inputs include codebase analysis documents, reference projects, domain materials, and existing design references.

The document includes design decisions, architecture change overviews with Mermaid diagrams, module change tables with frozen zones, feature impact mapping, core workflows, algorithm and data model design, interface contracts, and DFx strategy covering availability, performance, and security.

Yes, at High effort level a red-team feasibility verification is delegated to a subagent using a dedicated checklist covering facts, omissions, and practicality. Low and Medium effort levels skip this verification step.

Only the final review stage (A4) can be declined by the user. Stages A1 through A3 are strictly sequential, and the skill refuses to skip them because each stage depends on the completion of the previous one.

Generation requires running the assemble-template.mjs Node script with the req-design argument rather than reading template files directly. If workflow SOP files or template components are missing, the skill aborts and lists the files that must be provided.