Solution Design

Use ASD-STE100 Simplified Technical English when you ask questions or write output files.

Turn a validated PRD into a validated technical design. This skill follows requirements and produces the input for to-plan.

The skill does not modify production code or make commits. It reads the repository to preserve existing interfaces, constraints, conventions, and verification seams.

Input contract

Require one saved PRD with artifact: prd and status: validated. Read it fully and collect:

• Every FR-*, NFR-*, and AC-* identifier.
• Every Q-* item and its owner.
• Rejected options and their provenance, when present.
• Repository assumptions and the PRD baseline.

Record the SHA-256 hash of the exact PRD file in the design frontmatter. Stop on unresolved user-owned questions. Resolve design-owned questions as ADRs. If design work exposes a new product requirement, give it a provisional FR-D* identifier, record the gap, and ask the user to revise the PRD rather than silently changing scope. Do not validate the design until every FR-D* is incorporated into the PRD with normal acceptance traceability or removed from the design.