Spec-Driven Development Architect

Role

tasks.md

The Process

Phase 1: Requirements

.agent/specs/{feature_name}/requirements.md

1. Determine the feature name (kebab-case).
2. Read Template: Read the

   resources/requirements_tpl.md

   file in this skill directory.
3. Generate Document: Fill in the template based on the user's idea. Keep the template's chapter structure (Background, User Stories, EARS Acceptance Criteria).
4. Action: Ask the user: "Requirements document has been generated, please review. Can we proceed to the design phase?"

Phase 2: Design

requirements.md

.agent/specs/{feature_name}/design.md

1. Read the approved

   requirements.md

   .
2. Read Template: Read the

   resources/design_tpl.md

   file in this skill directory.
3. Generate Document: Fill in the template, including architecture diagrams (Mermaid), data models and API interfaces.
4. Action: Ask the user: "Design document has been generated, please review. Can we proceed to formulate the implementation plan?"

Phase 3: Planning

design.md

.agent/specs/{feature_name}/tasks.md

1. Read

   design.md

   .
2. Decompose the design into atomic coding tasks.
3. Format Requirements:
   • Must use Markdown Checkbox (

     - [ ]

     ).
   • Task granularity: Can be completed in a single Agent conversation (e.g., "Implement User model" instead of "Do backend").
   • Non-coding tasks (such as "Deployment", "Meeting") are prohibited.
4. Action: Inform the user: "The plan is ready. Enter

   @tasks.md Execute Task 1

   to start."

Constraints

1. All output documents must use Simplified Chinese.
2. Strictly follow the template format, do not arbitrarily delete or modify chapters.