specsmd 0.0.0-dev.21 → 0.0.0-dev.23
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/flows/aidlc/commands/construction-agent.md +1 -1
- package/flows/aidlc/memory-bank.yaml +2 -1
- package/flows/aidlc/skills/construction/bolt-list.md +1 -1
- package/flows/aidlc/skills/construction/bolt-status.md +1 -1
- package/flows/aidlc/skills/master/analyze-context.md +1 -1
- package/flows/aidlc/templates/construction/bolt-template.md +2 -2
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt.md +69 -11
- package/flows/aidlc/templates/standards/decision-index-template.md +32 -0
- package/flows/simple/README.md +178 -0
- package/flows/simple/agents/agent.md +134 -0
- package/flows/simple/commands/agent.md +56 -0
- package/flows/simple/context-config.yaml +34 -0
- package/flows/simple/memory-bank.yaml +66 -0
- package/flows/simple/skills/design.md +94 -0
- package/flows/simple/skills/execute.md +130 -0
- package/flows/simple/skills/requirements.md +94 -0
- package/flows/simple/skills/tasks.md +118 -0
- package/flows/simple/templates/design-template.md +133 -0
- package/flows/simple/templates/requirements-template.md +73 -0
- package/flows/simple/templates/tasks-template.md +95 -0
- package/package.json +1 -1
|
@@ -0,0 +1,95 @@
|
|
|
1
|
+
# Tasks Template
|
|
2
|
+
|
|
3
|
+
Use this template when generating tasks.md for a feature spec.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
```markdown
|
|
8
|
+
# Implementation Plan
|
|
9
|
+
|
|
10
|
+
- [ ] 1. Set up project structure and core interfaces
|
|
11
|
+
- Create directory structure for [components]
|
|
12
|
+
- Define core interfaces and types
|
|
13
|
+
- Set up testing framework if not present
|
|
14
|
+
- _Requirements: [X.Y]_
|
|
15
|
+
|
|
16
|
+
- [ ] 2. Implement [Component Group Name]
|
|
17
|
+
- [ ] 2.1 Create [specific component/module]
|
|
18
|
+
- [Implementation detail 1]
|
|
19
|
+
- [Implementation detail 2]
|
|
20
|
+
- _Requirements: [X.Y, X.Z]_
|
|
21
|
+
|
|
22
|
+
- [ ]* 2.2 Write unit tests for [component]
|
|
23
|
+
- Create test file
|
|
24
|
+
- Test [specific behavior]
|
|
25
|
+
- _Requirements: [X.Y]_
|
|
26
|
+
|
|
27
|
+
- [ ] 2.3 Implement [next component]
|
|
28
|
+
- [Details]
|
|
29
|
+
- _Requirements: [X.Y]_
|
|
30
|
+
|
|
31
|
+
- [ ] 3. Implement [Next Component Group]
|
|
32
|
+
- [ ] 3.1 Create [component]
|
|
33
|
+
- [Details]
|
|
34
|
+
- _Requirements: [X.Y]_
|
|
35
|
+
|
|
36
|
+
- [ ] 3.2 Wire components together
|
|
37
|
+
- Connect [A] to [B]
|
|
38
|
+
- [Integration details]
|
|
39
|
+
- _Requirements: [X.Y, X.Z]_
|
|
40
|
+
|
|
41
|
+
- [ ] 4. Checkpoint - Verify all tests pass
|
|
42
|
+
- Run test suite
|
|
43
|
+
- Address any failures before continuing
|
|
44
|
+
|
|
45
|
+
- [ ] 5. [Continue with remaining components...]
|
|
46
|
+
|
|
47
|
+
- [ ] N. Final Checkpoint - Ensure all tests pass
|
|
48
|
+
- Run complete test suite
|
|
49
|
+
- Verify all requirements are covered
|
|
50
|
+
- Review implementation against design
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
## Task Format Rules
|
|
56
|
+
|
|
57
|
+
### Checkbox Format
|
|
58
|
+
- `- [ ]` - Pending task
|
|
59
|
+
- `- [x]` - Completed task
|
|
60
|
+
- `- [ ]*` - Optional task (nice-to-have, not blocking)
|
|
61
|
+
|
|
62
|
+
### Numbering
|
|
63
|
+
- Top-level: `1.`, `2.`, `3.` etc.
|
|
64
|
+
- Sub-tasks: `2.1`, `2.2`, `2.3` etc.
|
|
65
|
+
- Maximum 2 levels of hierarchy
|
|
66
|
+
|
|
67
|
+
### Requirement References
|
|
68
|
+
- Always include: `_Requirements: X.Y, X.Z_`
|
|
69
|
+
- Reference specific acceptance criteria numbers
|
|
70
|
+
- Every requirement should be covered by at least one task
|
|
71
|
+
|
|
72
|
+
### Task Content
|
|
73
|
+
Each task should include:
|
|
74
|
+
1. **Clear objective** - What to implement
|
|
75
|
+
2. **Implementation details** - Sub-bullets with specifics
|
|
76
|
+
3. **Requirement reference** - Traceability
|
|
77
|
+
|
|
78
|
+
## Guidelines
|
|
79
|
+
|
|
80
|
+
1. **Coding tasks ONLY** - No deployment, user testing, documentation
|
|
81
|
+
2. **Incremental progress** - Each task builds on previous
|
|
82
|
+
3. **Test-driven where appropriate** - Mark test tasks with `*` if optional
|
|
83
|
+
4. **Include checkpoints** - Periodic verification that tests pass
|
|
84
|
+
5. **Reference requirements** - Every task traces to requirement(s)
|
|
85
|
+
6. **Actionable by AI** - Tasks should be specific enough for code generation
|
|
86
|
+
|
|
87
|
+
## Excluded Task Types (Do NOT include)
|
|
88
|
+
|
|
89
|
+
- User acceptance testing
|
|
90
|
+
- Deployment to environments
|
|
91
|
+
- Performance metrics gathering
|
|
92
|
+
- User training
|
|
93
|
+
- Documentation creation (unless code comments)
|
|
94
|
+
- Business process changes
|
|
95
|
+
- Marketing activities
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "specsmd",
|
|
3
|
-
"version": "0.0.0-dev.
|
|
3
|
+
"version": "0.0.0-dev.23",
|
|
4
4
|
"description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
|
|
5
5
|
"main": "lib/installer.js",
|
|
6
6
|
"bin": {
|