メニュー
This skill should be used when the user asks to "create a design document", "write technical specs", "document architecture", "generate SDD", "design the system", "API design", or when creating technical design documents from approved PRDs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sdd-template |
| description | This skill should be used when the user asks to "create a design document", "write technical specs", "document architecture", "generate SDD", "design the system", "API design", or when creating technical design documents from approved PRDs. |
| version | 0.1.0 |
Create comprehensive technical design documents following the Atlassian 8-section structure.
| Section | Purpose |
|---|---|
| 1. Introduction | Purpose, scope, definitions |
| 2. System Overview | High-level architecture |
| 3. Design Considerations | Assumptions, constraints, risks |
| 4. Architectural Strategies | Key decisions and alternatives |
| 5. System Architecture | Components, data flow, APIs, models |
| 6. Policies and Tactics | Security, error handling, logging |
| 7. Detailed Design | Component-level specifications |
| 8. Appendix | Diagrams, glossary |
## 1. Introduction
### 1.1 Purpose
[What this document covers and its intended audience]
### 1.2 Scope
[System boundaries - what's included and excluded]
### 1.3 Definitions and Acronyms
| Term | Definition |
|------|------------|
| [Term] | [Definition] |
### 1.4 References
- PRD: [link to PRD document]
- [Other relevant documents]
## 2. System Overview
### 2.1 System Context
[How this system fits into the broader architecture]
### 2.2 High-Level Architecture
[Architecture diagram description or ASCII diagram]
### 2.3 Key Components
- **Component A**: [Purpose and responsibility]
- **Component B**: [Purpose and responsibility]
## 3. Design Considerations
### 3.1 Assumptions
- [Assumption 1]
- [Assumption 2]
### 3.2 Constraints
- [Technical constraint]
- [Business constraint]
### 3.3 Dependencies
- [External system X]
- [Library Y version Z]
### 3.4 Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| [Risk] | High/Med/Low | [Strategy] |
## 4. Architectural Strategies
### 4.1 Strategy Selection
[Why this architecture was chosen over alternatives]
### 4.2 Alternatives Considered
| Option | Pros | Cons | Decision |
|--------|------|------|----------|
| [Option A] | [Pros] | [Cons] | Selected |
| [Option B] | [Pros] | [Cons] | Rejected |
### 4.3 Key Architectural Decisions
- **Decision 1**: [Decision and rationale]
- **Decision 2**: [Decision and rationale]
## 5. System Architecture
### 5.1 Component Diagram
[Description or ASCII representation]
### 5.2 Data Flow
[How data moves through the system]
### 5.3 API Design
#### 5.3.1 Endpoints
| Method | Path | Description |
|--------|------|-------------|
| POST | /api/resource | Create resource |
| GET | /api/resource/:id | Get resource |
#### 5.3.2 Request/Response Schemas
[TypeScript interfaces or JSON schemas]
### 5.4 Data Models
[Database schema with types and constraints]
## 6. Policies and Tactics
### 6.1 Security
- Authentication: [Strategy]
- Authorization: [Strategy]
- Data encryption: [At rest / in transit]
### 6.2 Error Handling
- [Error handling strategy]
- [Retry policies]
### 6.3 Logging and Monitoring
- [What to log]
- [Alerting thresholds]
### 6.4 Performance
- [Caching strategy]
- [Connection pooling]
## 7. Detailed Design
### 7.1 [Component A] Design
#### 7.1.1 Responsibilities
- [Responsibility 1]
- [Responsibility 2]
#### 7.1.2 Interface
[TypeScript interface or function signatures]
#### 7.1.3 Implementation Notes
[Specific implementation details, algorithms, or patterns]
## 8. Appendix
### 8.1 Sequence Diagrams
[For complex flows]
### 8.2 State Diagrams
[For stateful components]
### 8.3 Glossary
[Extended definitions]
Each design decision should trace to requirements:
### REQ-001 Implementation
**Requirement:** [Quote requirement]
**Design:** [How this design satisfies it]
**Verification:** [How to test it]
Before finalizing an SDD:
For detailed section guidance and examples, see references/sections.md.
This skill should be used when the user asks to "generate tasks", "create implementation plan", "break down feature", "write agent prompts", "decompose into tasks", "create work items", or when creating agent-ready task descriptions from PRD and SDD documents.
Verify the current task and output a completion marker. Use this to check if a task is complete and signal the stop hook to allow session exit.
This skill should be used when the user asks to "analyze the codebase", "understand the tech stack", "extract project patterns", "get codebase context", "what technologies are used", or when preparing context for planning documents, PRDs, or design documentation.
This skill should be used when the user asks to "create a PRD", "write requirements", "document a feature", "generate product spec", "define requirements", "write feature specifications", or when creating PRD documents from gathered requirements.
This skill should be used when the user asks to "research documentation", "find framework docs", "search for best practices", "look up API documentation", "find implementation patterns", "research how to implement", or when gathering external technical knowledge to inform planning or design decisions.