Agent skill
design-doc-generate
Generate design documents for Validate mode work items (Checkpoint 1). Required for high-complexity items.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/design-doc-generate
SKILL.md
<degrees_of_freedom> LOW — Follow the design doc structure precisely. Decisions must have rationale. </degrees_of_freedom>
<output_format>
| Decision | Choice | Rationale |
|----------|--------|-----------|
| ... | ... | ... |
</output_format>
<output_format>
| Risk | Impact | Mitigation |
|------|--------|------------|
| ... | ... | ... |
</output_format>
## Summary
{brief description}
## Key Decisions
{decisions table}
## Technical Approach
{component diagram, API contracts}
## Risks
{risks table}
## Implementation Checklist
{ordered steps}
---
This is Checkpoint 1 of Validate mode.
Approve design? [Y/n/edit]
</output>
</checkpoint>
Route to Builder for Checkpoint 2 (implementation plan)? [Y/n]
</output>
</check>
<check if="response == edit">
<ask>What changes are needed?</ask>
<action>Incorporate feedback</action>
<goto step="8"/>
</check>
<check if="response == n">
<output>Design rejected. What concerns need to be addressed?</output>
<action>Gather feedback, revise approach</action>
<goto step="3"/>
</check>
<output_artifacts>
| Artifact | Location | Template |
|---|---|---|
| Design Doc | .specs-fire/intents/{intent-id}/work-items/{id}-design.md |
./templates/design.md.hbs |
| </output_artifacts> |
<success_criteria> Work item analyzed for design decisions Key decisions documented with rationale Domain model defined (if applicable) Technical approach specified Risks identified with mitigations Implementation checklist created Design doc approved at checkpoint Design doc saved to correct location </success_criteria>
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?