2.0 KiB
2.0 KiB
allowed-tools, argument-hint, description
| allowed-tools | argument-hint | description |
|---|---|---|
| Task(*), Read(*), Glob(*) | <directory> | Create technical design (tech-design.md) from requirements.md |
Execute technical design creation for the directory at: $ARGUMENTS
Prerequisites:
- requirements.md must exist in the directory (run
/create-specfirst if needed)
Step 0: Parse Arguments and Validate
- Extract directory path from $ARGUMENTS
- Verify that requirements.md exists in this directory (MANDATORY)
- Check if research.md exists in the same directory (OPTIONAL - for context on existing patterns)
- Check if scenarios.md exists in the same directory (OPTIONAL - for detailed test context)
Step 1: Launch software-architect Agent
Launch software-architect agent to create technical design:
- Read requirements.md from: [directory]/requirements.md (MANDATORY - contains acceptance criteria)
- Read research.md from: [directory]/research.md (OPTIONAL - if exists, use existing patterns and components)
- Read scenarios.md from: [directory]/scenarios.md (OPTIONAL - if exists, provides detailed test scenarios for design context)
- Output directory: [directory]
- Output filename: tech-design.md (not design.md)
- Task: Create tech-design.md with technical design covering ALL acceptance criteria in requirements.md. If research.md is provided, use existing patterns and components from the research. If scenarios.md is provided, use test scenarios to inform design decisions.
Step 2: If Design Options Presented
If the software-architect agent pauses to present multiple design alternatives:
- Review the design options with the user
- Present pros/cons and recommendation clearly
- Wait for user to select an option
- Once user selects, relaunch software-architect agent to complete tech-design.md with chosen option
Expected Output: ✅ tech-design.md with technical design in the directory
Next Steps: After tech-design.md is created, you can begin implementation using your preferred development approach.