design-doc
Create technical design documents for new features, systems, refactoring plans, API designs, and database schemas. Use when asked to write a design doc, TRD (technical requirements document), RFC, or system design document. Triggers on requests like "write a design doc for X", "design the Y feature", "create a technical spec", or "plan the architecture for Z".
How do I install this agent skill?
npx skills add https://github.com/diskd-ai/design-doc --skill design-docIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is a template-based guide for creating technical design documents. It contains no executable code, network operations, or sensitive data access patterns, and is entirely documentation-based.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerwarn
3/3 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Technical Design Document Skill
Create structured technical design documents that communicate system behavior, implementation approach, and acceptance criteria.
Workflow
- Gather context: Understand the feature/system scope, constraints, and goals
- Draft structure: Use template from
references/template.md - Fill sections: Work through each section, asking clarifying questions as needed
- Review: Ensure acceptance criteria are testable and implementation outline is actionable
Template
See references/template.md for the full template structure and section guidelines.
Core sections:
- Context and motivation: Problem statement, goals, non-goals
- Implementation considerations: Constraints and design principles
- High-level behavior: End-to-end system behavior
- Domain-specific sections: Adapt to feature type (discovery, validation, API, state, rendering)
- Error handling and UX: Error surfacing and recovery
- Future-proofing: Design for extensibility
- Implementation outline: Step-by-step approach
- Testing approach: Unit, integration, manual tests
- Acceptance criteria: Testable conditions for "done"
Writing Guidelines
- Use
---underlines for section headers (Setext style) - Write in present tense for behavior ("loads", "validates", "returns")
- Be specific: "max 100 chars" not "reasonable length"
- Include concrete examples where behavior varies
- Non-goals are as important as goals - prevent scope creep
- Acceptance criteria must be verifiable, not subjective
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/diskd-ai/design-doc/design-doc">View design-doc on skillZs</a>