@tudeorangbiasa/sdd-multiagent-opencode 0.1.4 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.opencode/agents/sdd-explorer.md +1 -2
- package/.opencode/agents/sdd-implementer.md +4 -5
- package/.opencode/agents/sdd-orchestrator.md +17 -127
- package/.opencode/agents/sdd-planner.md +5 -6
- package/.opencode/agents/sdd-reviewer.md +0 -1
- package/.opencode/agents/sdd-verifier.md +3 -4
- package/.opencode/commands/sdd-apply.md +83 -0
- package/.opencode/commands/sdd-explore.md +63 -0
- package/.opencode/commands/sdd-propose.md +116 -0
- package/.opencode/commands/sdd-ship.md +71 -0
- package/.opencode/plugins/sdd-register.js +22 -0
- package/.opencode/skills/sdd-audit/SKILL.md +5 -5
- package/.opencode/skills/sdd-implementation/SKILL.md +10 -12
- package/.opencode/skills/sdd-planning/SKILL.md +20 -29
- package/.opencode/skills/sdd-research/SKILL.md +5 -5
- package/.sdd/config.json +10 -10
- package/.sdd/templates/design-template.md +21 -0
- package/.sdd/templates/model-profile-template.json +20 -3
- package/.sdd/templates/progress-template.md +23 -0
- package/.sdd/templates/project-profile-template.json +2 -2
- package/.sdd/templates/proposal-template.md +22 -0
- package/.sdd/templates/reasoning-profile-template.json +4 -8
- package/.sdd/templates/spec-template.md +19 -0
- package/.sdd/templates/tasks-template.md +8 -0
- package/.sdd/templates/verification-template.md +17 -0
- package/GUIDE.md +128 -0
- package/README.md +259 -155
- package/bin/sdd-opencode.js +7 -9
- package/opencode.json +6 -14
- package/package.json +6 -4
- package/.opencode/commands/audit.md +0 -75
- package/.opencode/commands/brief.md +0 -190
- package/.opencode/commands/evolve.md +0 -87
- package/.opencode/commands/execute-parallel.md +0 -116
- package/.opencode/commands/execute-task.md +0 -81
- package/.opencode/commands/generate-prd.md +0 -82
- package/.opencode/commands/generate-rules.md +0 -67
- package/.opencode/commands/grill-me.md +0 -99
- package/.opencode/commands/implement.md +0 -149
- package/.opencode/commands/init-sdd.md +0 -141
- package/.opencode/commands/plan.md +0 -96
- package/.opencode/commands/refine.md +0 -115
- package/.opencode/commands/research.md +0 -194
- package/.opencode/commands/sdd-full-plan.md +0 -91
- package/.opencode/commands/specify.md +0 -124
- package/.opencode/commands/tasks.md +0 -110
- package/.opencode/commands/upgrade.md +0 -107
- package/.opencode/skills/sdd-evolve/SKILL.md +0 -95
- package/.sdd/templates/feature-brief-v2.md +0 -65
- package/.sdd/templates/plan-compact.md +0 -50
- package/.sdd/templates/research-compact.md +0 -114
- package/.sdd/templates/roadmap-template.json +0 -29
- package/.sdd/templates/roadmap-template.md +0 -66
- package/.sdd/templates/spec-compact.md +0 -71
- package/.sdd/templates/tasks-compact.md +0 -48
- package/.sdd/templates/todo-compact.md +0 -30
|
@@ -1,95 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: sdd-evolve
|
|
3
|
-
description: Spec evolution and downstream propagation for SDD workflows. Activates when updating specifications with discoveries, managing spec changes, or propagating staleness to downstream documents. Use with /evolve command.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
## What I do
|
|
7
|
-
|
|
8
|
-
- Update existing specs with new discoveries while preserving context
|
|
9
|
-
- Maintain changelog entries for spec evolution tracking
|
|
10
|
-
- Detect and mark stale downstream documents
|
|
11
|
-
- Propagate changes through the spec → plan → tasks chain
|
|
12
|
-
|
|
13
|
-
## When to use me
|
|
14
|
-
|
|
15
|
-
Use this skill when:
|
|
16
|
-
- Running `/evolve` command
|
|
17
|
-
- Discoveries during development require spec updates
|
|
18
|
-
- Architecture changes need documentation alignment
|
|
19
|
-
- Need to track what changed and why
|
|
20
|
-
|
|
21
|
-
## Evolution Protocol
|
|
22
|
-
|
|
23
|
-
### Phase 1: Analysis
|
|
24
|
-
1. Find existing specs in `specs/active/[task-id]/`
|
|
25
|
-
2. Read all related files to understand current state
|
|
26
|
-
3. Categorize the change:
|
|
27
|
-
|
|
28
|
-
| Category | Impact | Examples |
|
|
29
|
-
|----------|--------|----------|
|
|
30
|
-
| Discovery | Low | Small findings, new constraint |
|
|
31
|
-
| Refinement | Low | Clarifying requirements |
|
|
32
|
-
| Addition | Medium | New requirement, new feature |
|
|
33
|
-
| Modification | Medium | Changed approach, updated design |
|
|
34
|
-
| Removal | High | Descoping, architecture change |
|
|
35
|
-
|
|
36
|
-
### Phase 2: Planning
|
|
37
|
-
Present evolution plan with:
|
|
38
|
-
- Task ID and file to update
|
|
39
|
-
- Change summary, type, and impact level
|
|
40
|
-
- Before/after diff of relevant sections
|
|
41
|
-
- Proposed changelog entry
|
|
42
|
-
|
|
43
|
-
**Wait for user approval before proceeding.**
|
|
44
|
-
|
|
45
|
-
### Phase 3: Execution
|
|
46
|
-
1. Update spec file preserving context
|
|
47
|
-
2. Add changelog entry
|
|
48
|
-
3. Increment version number
|
|
49
|
-
4. Update timestamp
|
|
50
|
-
|
|
51
|
-
### Phase 4: Downstream Propagation
|
|
52
|
-
|
|
53
|
-
Check for stale downstream documents:
|
|
54
|
-
|
|
55
|
-
1. **List downstream files** — `plan.md`, `tasks.md`, `todo-list.md`
|
|
56
|
-
2. **Assess impact** using change category:
|
|
57
|
-
- Discovery/Refinement → downstream usually unaffected
|
|
58
|
-
- Addition/Modification → `plan.md` and `tasks.md` likely stale
|
|
59
|
-
- Removal/Architecture → all downstream docs stale
|
|
60
|
-
3. **Add staleness marker** to affected files:
|
|
61
|
-
```
|
|
62
|
-
> **[STALE]** — Upstream spec updated on [DATE]. Review needed.
|
|
63
|
-
> Change: [Brief description] (spec.md v[VERSION])
|
|
64
|
-
```
|
|
65
|
-
4. **Report affected files** in evolution summary
|
|
66
|
-
|
|
67
|
-
## Changelog Format
|
|
68
|
-
|
|
69
|
-
### For feature-brief.md
|
|
70
|
-
```markdown
|
|
71
|
-
## Changelog
|
|
72
|
-
|
|
73
|
-
| Version | Date | Changes | Reason |
|
|
74
|
-
|---------|------|---------|--------|
|
|
75
|
-
| 1.1 | [date] | [description] | [reason] |
|
|
76
|
-
| 1.0 | [date] | Initial | |
|
|
77
|
-
```
|
|
78
|
-
|
|
79
|
-
### For spec.md
|
|
80
|
-
```markdown
|
|
81
|
-
## Revision History
|
|
82
|
-
|
|
83
|
-
| Version | Date | Changes | Author |
|
|
84
|
-
|---------|------|---------|--------|
|
|
85
|
-
| 1.1 | [date] | [description] | [author] |
|
|
86
|
-
| 1.0 | [date] | Initial specification | [author] |
|
|
87
|
-
```
|
|
88
|
-
|
|
89
|
-
## When to Suggest Upgrade
|
|
90
|
-
|
|
91
|
-
Suggest `/upgrade` when:
|
|
92
|
-
- Change fundamentally alters approach
|
|
93
|
-
- Multiple related changes needed
|
|
94
|
-
- Brief is no longer sufficient for scope
|
|
95
|
-
- Architecture needs redesign
|
|
@@ -1,65 +0,0 @@
|
|
|
1
|
-
# Feature Brief: [Feature Name]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Created:** [date]
|
|
5
|
-
**Status:** Ready for Development
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## Problem Statement
|
|
10
|
-
|
|
11
|
-
[What problem does this solve? 2-3 sentences]
|
|
12
|
-
|
|
13
|
-
## Target Users
|
|
14
|
-
|
|
15
|
-
[Who will use this? Be specific]
|
|
16
|
-
|
|
17
|
-
## Core Requirements
|
|
18
|
-
|
|
19
|
-
### Must Have
|
|
20
|
-
- [ ] [Requirement 1]
|
|
21
|
-
- [ ] [Requirement 2]
|
|
22
|
-
- [ ] [Requirement 3]
|
|
23
|
-
|
|
24
|
-
### Nice to Have
|
|
25
|
-
- [ ] [Optional 1]
|
|
26
|
-
- [ ] [Optional 2]
|
|
27
|
-
|
|
28
|
-
## Technical Approach
|
|
29
|
-
|
|
30
|
-
[High-level approach, 3-5 sentences]
|
|
31
|
-
|
|
32
|
-
**Patterns to Follow:**
|
|
33
|
-
- [Existing pattern 1 from codebase]
|
|
34
|
-
- [Existing pattern 2 from codebase]
|
|
35
|
-
|
|
36
|
-
**Key Decisions:**
|
|
37
|
-
- [Decision 1]: [Rationale]
|
|
38
|
-
- [Decision 2]: [Rationale]
|
|
39
|
-
|
|
40
|
-
## Next Actions
|
|
41
|
-
|
|
42
|
-
1. [ ] [First concrete step]
|
|
43
|
-
2. [ ] [Second step]
|
|
44
|
-
3. [ ] [Third step]
|
|
45
|
-
|
|
46
|
-
## Success Criteria
|
|
47
|
-
|
|
48
|
-
- [ ] [How we know it's done 1]
|
|
49
|
-
- [ ] [How we know it's done 2]
|
|
50
|
-
|
|
51
|
-
## Open Questions
|
|
52
|
-
|
|
53
|
-
- [Any unresolved questions]
|
|
54
|
-
|
|
55
|
-
---
|
|
56
|
-
|
|
57
|
-
## Changelog
|
|
58
|
-
|
|
59
|
-
| Version | Date | Changes | Reason |
|
|
60
|
-
|---------|------|---------|--------|
|
|
61
|
-
| 1.0 | [date] | Initial | |
|
|
62
|
-
|
|
63
|
-
---
|
|
64
|
-
|
|
65
|
-
*Brief created with SDD Multi-Agent OpenCode*
|
|
@@ -1,50 +0,0 @@
|
|
|
1
|
-
# Technical Plan: [Feature Name]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Status:** Ready for Implementation
|
|
5
|
-
**Based on:** spec.md / feature-brief.md
|
|
6
|
-
|
|
7
|
-
## 1. System Architecture
|
|
8
|
-
- Overview with diagram (if helpful)
|
|
9
|
-
- Architecture decisions table (Decision | Choice | Rationale)
|
|
10
|
-
|
|
11
|
-
## 2. Technology Stack
|
|
12
|
-
- Layer | Technology | Version | Rationale table
|
|
13
|
-
- Dependencies (JSON)
|
|
14
|
-
|
|
15
|
-
## 3. Component Design
|
|
16
|
-
- For each component: Purpose, Responsibilities, Interfaces, Dependencies
|
|
17
|
-
|
|
18
|
-
## 4. Data Model
|
|
19
|
-
- Entities with TypeScript interfaces
|
|
20
|
-
- Relationships
|
|
21
|
-
- Database schema (if applicable)
|
|
22
|
-
|
|
23
|
-
## 5. API Contracts
|
|
24
|
-
- Endpoints table (Method | Path | Description)
|
|
25
|
-
- Request/Response examples
|
|
26
|
-
|
|
27
|
-
## 6. Security Considerations
|
|
28
|
-
- Authentication, Authorization, Data Protection
|
|
29
|
-
- Security checklist
|
|
30
|
-
|
|
31
|
-
## 7. Performance Strategy
|
|
32
|
-
- Optimization targets, Caching, Scaling approach
|
|
33
|
-
|
|
34
|
-
## 8. Implementation Phases
|
|
35
|
-
- Phased approach with checkboxes
|
|
36
|
-
|
|
37
|
-
## 9. Risk Assessment
|
|
38
|
-
- Risk | Impact | Likelihood | Mitigation table
|
|
39
|
-
|
|
40
|
-
## 10. Open Questions
|
|
41
|
-
- Unresolved items requiring input
|
|
42
|
-
|
|
43
|
-
## Next Steps
|
|
44
|
-
- Review plan
|
|
45
|
-
- Run `/tasks [task-id]` to generate tasks
|
|
46
|
-
- Run `/implement [task-id]` to start building
|
|
47
|
-
|
|
48
|
-
---
|
|
49
|
-
|
|
50
|
-
*Plan created with SDD Multi-Agent OpenCode*
|
|
@@ -1,114 +0,0 @@
|
|
|
1
|
-
# Research: [Topic]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Date:** [date]
|
|
5
|
-
**Status:** Complete
|
|
6
|
-
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
## Executive Summary
|
|
10
|
-
|
|
11
|
-
[2-3 paragraph summary of key findings and initial recommendation]
|
|
12
|
-
|
|
13
|
-
---
|
|
14
|
-
|
|
15
|
-
## Codebase Analysis
|
|
16
|
-
|
|
17
|
-
### Existing Patterns
|
|
18
|
-
|
|
19
|
-
[Document patterns found in codebase with code examples]
|
|
20
|
-
|
|
21
|
-
### Reusable Components
|
|
22
|
-
|
|
23
|
-
[List components/utilities that can be reused]
|
|
24
|
-
|
|
25
|
-
### Conventions to Follow
|
|
26
|
-
|
|
27
|
-
[Coding conventions and architectural patterns to maintain]
|
|
28
|
-
|
|
29
|
-
---
|
|
30
|
-
|
|
31
|
-
## External Solutions
|
|
32
|
-
|
|
33
|
-
### Option 1: [Name]
|
|
34
|
-
|
|
35
|
-
**Overview:** [Description]
|
|
36
|
-
|
|
37
|
-
**Pros:**
|
|
38
|
-
- [Pro 1]
|
|
39
|
-
- [Pro 2]
|
|
40
|
-
|
|
41
|
-
**Cons:**
|
|
42
|
-
- [Con 1]
|
|
43
|
-
- [Con 2]
|
|
44
|
-
|
|
45
|
-
**Implementation complexity:** [Low/Medium/High]
|
|
46
|
-
**Team familiarity:** [Low/Medium/High]
|
|
47
|
-
**Fit for our use case:** [High/Medium/Low]
|
|
48
|
-
|
|
49
|
-
### Option 2: [Name]
|
|
50
|
-
|
|
51
|
-
[Same structure]
|
|
52
|
-
|
|
53
|
-
### Option 3: [Name]
|
|
54
|
-
|
|
55
|
-
[Same structure]
|
|
56
|
-
|
|
57
|
-
---
|
|
58
|
-
|
|
59
|
-
## Comparison Matrix
|
|
60
|
-
|
|
61
|
-
| Criteria | Option 1 | Option 2 | Option 3 |
|
|
62
|
-
|----------|----------|----------|----------|
|
|
63
|
-
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐ |
|
|
64
|
-
| Complexity | ⭐⭐ | ⭐⭐⭐ | ⭐ |
|
|
65
|
-
| Team fit | ⭐⭐⭐ | ⭐ | ⭐⭐ |
|
|
66
|
-
| Maintenance | ⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
|
|
67
|
-
|
|
68
|
-
---
|
|
69
|
-
|
|
70
|
-
## Recommendations
|
|
71
|
-
|
|
72
|
-
### Primary Recommendation
|
|
73
|
-
|
|
74
|
-
[Recommended approach with rationale]
|
|
75
|
-
|
|
76
|
-
### Alternative Approach
|
|
77
|
-
|
|
78
|
-
[Backup option if primary doesn't work]
|
|
79
|
-
|
|
80
|
-
---
|
|
81
|
-
|
|
82
|
-
## Open Questions
|
|
83
|
-
|
|
84
|
-
- [Question for specification phase]
|
|
85
|
-
- [Decision that needs stakeholder input]
|
|
86
|
-
|
|
87
|
-
---
|
|
88
|
-
|
|
89
|
-
## Sources (deep research only)
|
|
90
|
-
|
|
91
|
-
| # | URL | Type | Reliability | Key Finding |
|
|
92
|
-
|---|-----|------|-------------|-------------|
|
|
93
|
-
| 1 | [url] | [Official docs / Benchmark / Blog / Discussion] | [High/Medium/Low] | [finding] |
|
|
94
|
-
|
|
95
|
-
---
|
|
96
|
-
|
|
97
|
-
## Confidence Assessment (deep research only)
|
|
98
|
-
|
|
99
|
-
**Overall confidence:** [High/Medium/Low]
|
|
100
|
-
**Reasoning:** [Why this confidence level]
|
|
101
|
-
**Gaps:** [What we still don't know]
|
|
102
|
-
**Suggested spike:** [If Low confidence — describe a 2-4h prototype to validate]
|
|
103
|
-
|
|
104
|
-
---
|
|
105
|
-
|
|
106
|
-
## Next Steps
|
|
107
|
-
|
|
108
|
-
1. Review findings with team
|
|
109
|
-
2. Proceed to `/specify` to define requirements
|
|
110
|
-
3. Address open questions before proceeding
|
|
111
|
-
|
|
112
|
-
---
|
|
113
|
-
|
|
114
|
-
*Research completed with SDD Multi-Agent OpenCode*
|
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"version": "1.0.0",
|
|
3
|
-
"project": {
|
|
4
|
-
"id": "[project-id]",
|
|
5
|
-
"title": "[Project Title]",
|
|
6
|
-
"description": "[Project Description]",
|
|
7
|
-
"sddVersion": "1.0.0",
|
|
8
|
-
"created": "[date]",
|
|
9
|
-
"status": "active",
|
|
10
|
-
"complexity": "medium"
|
|
11
|
-
},
|
|
12
|
-
"columns": {
|
|
13
|
-
"todo": { "title": "To Do", "order": 0 },
|
|
14
|
-
"in-progress": { "title": "In Progress", "order": 1 },
|
|
15
|
-
"review": { "title": "Review", "order": 2 },
|
|
16
|
-
"done": { "title": "Done", "order": 3 }
|
|
17
|
-
},
|
|
18
|
-
"tasks": [],
|
|
19
|
-
"epics": [],
|
|
20
|
-
"dag": {
|
|
21
|
-
"roots": [],
|
|
22
|
-
"parallelGroups": []
|
|
23
|
-
},
|
|
24
|
-
"statistics": {
|
|
25
|
-
"totalTasks": 0,
|
|
26
|
-
"completedTasks": 0,
|
|
27
|
-
"completionPercentage": 0
|
|
28
|
-
}
|
|
29
|
-
}
|
|
@@ -1,66 +0,0 @@
|
|
|
1
|
-
# Project Roadmap: [Project Title]
|
|
2
|
-
|
|
3
|
-
**Project ID:** [project-id]
|
|
4
|
-
**Status:** Active
|
|
5
|
-
**Complexity:** [Simple/Medium/Complex/Enterprise]
|
|
6
|
-
**Created:** [date]
|
|
7
|
-
|
|
8
|
-
---
|
|
9
|
-
|
|
10
|
-
## Kanban Board
|
|
11
|
-
|
|
12
|
-
### To Do
|
|
13
|
-
| Task | Epic | Priority | Dependencies |
|
|
14
|
-
|------|------|----------|-------------|
|
|
15
|
-
| | | | |
|
|
16
|
-
|
|
17
|
-
### In Progress
|
|
18
|
-
| Task | Epic | Priority | Started |
|
|
19
|
-
|------|------|----------|---------|
|
|
20
|
-
| | | | |
|
|
21
|
-
|
|
22
|
-
### Review
|
|
23
|
-
| Task | Epic | Reviewer | Status |
|
|
24
|
-
|------|------|----------|--------|
|
|
25
|
-
| | | | |
|
|
26
|
-
|
|
27
|
-
### Done
|
|
28
|
-
| Task | Epic | Completed | Notes |
|
|
29
|
-
|------|------|-----------|-------|
|
|
30
|
-
| | | | |
|
|
31
|
-
|
|
32
|
-
---
|
|
33
|
-
|
|
34
|
-
## Epic Details
|
|
35
|
-
|
|
36
|
-
### Epic 1: [Epic Name]
|
|
37
|
-
- Task 1.1: [Description]
|
|
38
|
-
- Task 1.2: [Description]
|
|
39
|
-
|
|
40
|
-
### Epic 2: [Epic Name]
|
|
41
|
-
- Task 2.1: [Description]
|
|
42
|
-
|
|
43
|
-
---
|
|
44
|
-
|
|
45
|
-
## Execution Commands
|
|
46
|
-
|
|
47
|
-
```bash
|
|
48
|
-
# Execute all tasks in parallel
|
|
49
|
-
/execute-parallel [project-id] --until-finish
|
|
50
|
-
|
|
51
|
-
# Execute single task
|
|
52
|
-
/execute-task [task-id]
|
|
53
|
-
|
|
54
|
-
# Resume after interruption
|
|
55
|
-
/execute-parallel [project-id] --resume
|
|
56
|
-
```
|
|
57
|
-
|
|
58
|
-
---
|
|
59
|
-
|
|
60
|
-
## Progress
|
|
61
|
-
|
|
62
|
-
- Total: X | Done: Y (Z%) | In Progress: A | Blocked: B
|
|
63
|
-
|
|
64
|
-
---
|
|
65
|
-
|
|
66
|
-
*Roadmap created with SDD Multi-Agent OpenCode*
|
|
@@ -1,71 +0,0 @@
|
|
|
1
|
-
# Specification: [Feature Name]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Created:** [date]
|
|
5
|
-
**Status:** Ready for Planning
|
|
6
|
-
**Version:** 1.0
|
|
7
|
-
|
|
8
|
-
## 1. Problem Statement
|
|
9
|
-
- The Problem: [Clear description]
|
|
10
|
-
- Current Situation: [How users currently handle this]
|
|
11
|
-
- Desired Outcome: [What success looks like]
|
|
12
|
-
|
|
13
|
-
## 2. User Personas
|
|
14
|
-
### Primary User: [Name]
|
|
15
|
-
- Who: [Description]
|
|
16
|
-
- Goals: [What they want to achieve]
|
|
17
|
-
- Pain points: [Current frustrations]
|
|
18
|
-
|
|
19
|
-
## 3. Functional Requirements
|
|
20
|
-
### FR-1: [Requirement Name]
|
|
21
|
-
**Description:** [What it does]
|
|
22
|
-
|
|
23
|
-
**User Story:**
|
|
24
|
-
> As a [user type], I want to [action] so that [benefit].
|
|
25
|
-
|
|
26
|
-
**Acceptance Criteria:**
|
|
27
|
-
- [ ] Given [context], when [action], then [result]
|
|
28
|
-
- [ ] [Additional criteria]
|
|
29
|
-
|
|
30
|
-
**Priority:** Must Have / Should Have / Nice to Have
|
|
31
|
-
|
|
32
|
-
## 4. Non-Functional Requirements
|
|
33
|
-
- Performance: [Specific metrics]
|
|
34
|
-
- Security: [Security requirements]
|
|
35
|
-
- Accessibility: [Accessibility requirements]
|
|
36
|
-
- Scalability: [Scalability requirements]
|
|
37
|
-
|
|
38
|
-
## 5. Out of Scope
|
|
39
|
-
- ❌ [Exclusion 1] - [Why excluded]
|
|
40
|
-
- ❌ [Exclusion 2] - [Why excluded]
|
|
41
|
-
|
|
42
|
-
## 6. Edge Cases & Error Handling
|
|
43
|
-
| Scenario | Expected Behavior |
|
|
44
|
-
|----------|-------------------|
|
|
45
|
-
| [Edge case] | [How system handles] |
|
|
46
|
-
|
|
47
|
-
| Error | User Message | System Action |
|
|
48
|
-
|-------|--------------|---------------|
|
|
49
|
-
| [Error] | "[Message]" | [Action] |
|
|
50
|
-
|
|
51
|
-
## 7. Success Metrics
|
|
52
|
-
| Metric | Target | How to Measure |
|
|
53
|
-
|--------|--------|----------------|
|
|
54
|
-
| [Metric] | [Target] | [Method] |
|
|
55
|
-
|
|
56
|
-
## 8. Open Questions
|
|
57
|
-
- [ ] [Question requiring input]
|
|
58
|
-
|
|
59
|
-
## 9. Revision History
|
|
60
|
-
| Version | Date | Changes |
|
|
61
|
-
|---------|------|---------|
|
|
62
|
-
| 1.0 | [date] | Initial specification |
|
|
63
|
-
|
|
64
|
-
## Next Steps
|
|
65
|
-
1. Review spec with stakeholders
|
|
66
|
-
2. Resolve open questions
|
|
67
|
-
3. Run `/plan [task-id]` to create technical plan
|
|
68
|
-
|
|
69
|
-
---
|
|
70
|
-
|
|
71
|
-
*Specification created with SDD Multi-Agent OpenCode*
|
|
@@ -1,48 +0,0 @@
|
|
|
1
|
-
# Implementation Tasks: [Feature Name]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Created:** [date]
|
|
5
|
-
**Status:** Ready for Implementation
|
|
6
|
-
|
|
7
|
-
## Summary
|
|
8
|
-
|
|
9
|
-
| Metric | Value |
|
|
10
|
-
|--------|-------|
|
|
11
|
-
| Total Tasks | [count] |
|
|
12
|
-
| Estimated Effort | [hours/days] |
|
|
13
|
-
| Phases | [count] |
|
|
14
|
-
|
|
15
|
-
## Phase 1: [Phase Name]
|
|
16
|
-
|
|
17
|
-
**Goal:** [What this phase accomplishes]
|
|
18
|
-
|
|
19
|
-
### Task 1.1: [Task Title]
|
|
20
|
-
|
|
21
|
-
**Description:** [What needs to be done]
|
|
22
|
-
|
|
23
|
-
**Acceptance Criteria:**
|
|
24
|
-
- [ ] [Criteria 1]
|
|
25
|
-
- [ ] [Criteria 2]
|
|
26
|
-
|
|
27
|
-
**Effort:** [X hours]
|
|
28
|
-
**Priority:** High/Medium/Low
|
|
29
|
-
**Dependencies:** None / [Task IDs]
|
|
30
|
-
|
|
31
|
-
---
|
|
32
|
-
|
|
33
|
-
[Repeat for all tasks in all phases]
|
|
34
|
-
|
|
35
|
-
## Quick Reference Checklist
|
|
36
|
-
|
|
37
|
-
- [ ] Task 1.1: [Title]
|
|
38
|
-
- [ ] Task 1.2: [Title]
|
|
39
|
-
- [ ] Task 2.1: [Title]
|
|
40
|
-
|
|
41
|
-
## Next Steps
|
|
42
|
-
|
|
43
|
-
1. Review task breakdown
|
|
44
|
-
2. Run `/implement [task-id]` to start execution
|
|
45
|
-
|
|
46
|
-
---
|
|
47
|
-
|
|
48
|
-
*Tasks created with SDD Multi-Agent OpenCode*
|
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
# Todo List: [Feature Name]
|
|
2
|
-
|
|
3
|
-
**Task ID:** [task-id]
|
|
4
|
-
**Created:** [date]
|
|
5
|
-
**Status:** In Progress
|
|
6
|
-
|
|
7
|
-
## Phase 1: [Phase Name]
|
|
8
|
-
|
|
9
|
-
- [ ] Task 1.1: [Description]
|
|
10
|
-
- Dependencies: None
|
|
11
|
-
- Files: [files to create/modify]
|
|
12
|
-
- [ ] Task 1.2: [Description]
|
|
13
|
-
- Dependencies: Task 1.1
|
|
14
|
-
- Files: [files to create/modify]
|
|
15
|
-
|
|
16
|
-
## Phase 2: [Phase Name]
|
|
17
|
-
|
|
18
|
-
- [ ] Task 2.1: [Description]
|
|
19
|
-
- Dependencies: Phase 1 complete
|
|
20
|
-
- Files: [files to create/modify]
|
|
21
|
-
|
|
22
|
-
## Progress Log
|
|
23
|
-
|
|
24
|
-
| Task | Status | Completed At | Notes |
|
|
25
|
-
|------|--------|--------------|-------|
|
|
26
|
-
| | | | |
|
|
27
|
-
|
|
28
|
-
---
|
|
29
|
-
|
|
30
|
-
*Todo list created with SDD Multi-Agent OpenCode*
|