technical-review

Technical Review

When to Use

• Stage 3 of the full-stack workflow: after technology selection is complete and before program design.
• When the user requests review of the architecture, API contracts, or risk analysis.

Input

Read from the current iteration directory:

• Requirements document (requirements-{id}.md）
• Technology selection document (technology-selection-{id}.md）

Execution Points

1. Architectural Feasibility: Whether the technology selection can satisfy the functional and non-functional requirements in the requirements (performance, security, deployment).
2. API Contract Definition: List the paths, methods, request/response schemas, and status code conventions of the core interfaces.
3. Data Model: Core entities, fields, relationships, and index recommendations.
4. Risk List: Technical risks, dependency risks, and unconfirmed items, each with a recommended countermeasure.
5. Review Conclusion: Pass / Conditional pass (list mandatory corrections) / Fail (technology selection must be redone).

Supplementary Materials

• Complete example output:examples/sample-output.md — Demonstrates the complete structure and depth of a qualified review document
• Review reference:reference.md — Review dimension checklist, API design specifications, common risk types, conclusion criteria

Output

• Use templates/review-template.md to produce the review document for use by "Program Design".

Document and Status

• Output is written to docs/{current_iteration_id}/technical-review-{technical_review_id}.md。
• Before starting: call the history-manager skill's get-phase technical_review and check-file to confirm whether it has been completed.
• After completion: call the history-manager skill's set-phase technical_review {technical_review_id} to record and advance the status.