specsmd 0.0.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/README.md +300 -0
- package/bin/cli.js +21 -0
- package/flows/aidlc/README.md +372 -0
- package/flows/aidlc/agents/construction-agent.md +81 -0
- package/flows/aidlc/agents/inception-agent.md +95 -0
- package/flows/aidlc/agents/master-agent.md +61 -0
- package/flows/aidlc/agents/operations-agent.md +89 -0
- package/flows/aidlc/commands/construction-agent.md +63 -0
- package/flows/aidlc/commands/inception-agent.md +55 -0
- package/flows/aidlc/commands/master-agent.md +47 -0
- package/flows/aidlc/commands/operations-agent.md +77 -0
- package/flows/aidlc/context-config.yaml +41 -0
- package/flows/aidlc/memory-bank.yaml +104 -0
- package/flows/aidlc/quick-start.md +315 -0
- package/flows/aidlc/skills/construction/bolt-list.md +163 -0
- package/flows/aidlc/skills/construction/bolt-replan.md +343 -0
- package/flows/aidlc/skills/construction/bolt-start.md +289 -0
- package/flows/aidlc/skills/construction/bolt-status.md +185 -0
- package/flows/aidlc/skills/construction/navigator.md +196 -0
- package/flows/aidlc/skills/inception/bolt-plan.md +338 -0
- package/flows/aidlc/skills/inception/context.md +171 -0
- package/flows/aidlc/skills/inception/intent-create.md +211 -0
- package/flows/aidlc/skills/inception/intent-list.md +124 -0
- package/flows/aidlc/skills/inception/navigator.md +207 -0
- package/flows/aidlc/skills/inception/requirements.md +227 -0
- package/flows/aidlc/skills/inception/review.md +248 -0
- package/flows/aidlc/skills/inception/story-create.md +304 -0
- package/flows/aidlc/skills/inception/units.md +271 -0
- package/flows/aidlc/skills/master/analyze-context.md +132 -0
- package/flows/aidlc/skills/master/answer-question.md +141 -0
- package/flows/aidlc/skills/master/explain-flow.md +146 -0
- package/flows/aidlc/skills/master/project-init.md +281 -0
- package/flows/aidlc/skills/master/route-request.md +126 -0
- package/flows/aidlc/skills/operations/build.md +237 -0
- package/flows/aidlc/skills/operations/deploy.md +259 -0
- package/flows/aidlc/skills/operations/monitor.md +265 -0
- package/flows/aidlc/skills/operations/navigator.md +209 -0
- package/flows/aidlc/skills/operations/verify.md +224 -0
- package/flows/aidlc/templates/construction/bolt-template.md +193 -0
- package/flows/aidlc/templates/construction/bolt-types/bdd-construction-bolt.md +250 -0
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/adr-template.md +49 -0
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-01-domain-model-template.md +55 -0
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-02-technical-design-template.md +67 -0
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-03-test-report-template.md +62 -0
- package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt.md +528 -0
- package/flows/aidlc/templates/construction/bolt-types/simple-construction-bolt.md +273 -0
- package/flows/aidlc/templates/construction/bolt-types/spike-bolt.md +240 -0
- package/flows/aidlc/templates/construction/bolt-types/tdd-construction-bolt.md +259 -0
- package/flows/aidlc/templates/construction/construction-log-template.md +129 -0
- package/flows/aidlc/templates/construction/standards/coding-standards.md +29 -0
- package/flows/aidlc/templates/construction/standards/system-architecture.md +22 -0
- package/flows/aidlc/templates/construction/standards/tech-stack.md +19 -0
- package/flows/aidlc/templates/inception/inception-log-template.md +134 -0
- package/flows/aidlc/templates/inception/project/README.md +55 -0
- package/flows/aidlc/templates/inception/requirements-template.md +144 -0
- package/flows/aidlc/templates/inception/stories-template.md +38 -0
- package/flows/aidlc/templates/inception/story-template.md +147 -0
- package/flows/aidlc/templates/inception/system-context-template.md +29 -0
- package/flows/aidlc/templates/inception/unit-brief-template.md +177 -0
- package/flows/aidlc/templates/inception/units-template.md +52 -0
- package/flows/aidlc/templates/standards/catalog.yaml +345 -0
- package/flows/aidlc/templates/standards/coding-standards.guide.md +553 -0
- package/flows/aidlc/templates/standards/data-stack.guide.md +162 -0
- package/flows/aidlc/templates/standards/tech-stack.guide.md +280 -0
- package/lib/InstallerFactory.js +36 -0
- package/lib/cli-utils.js +372 -0
- package/lib/constants.js +31 -0
- package/lib/installer.js +314 -0
- package/lib/installers/AntigravityInstaller.js +22 -0
- package/lib/installers/ClaudeInstaller.js +85 -0
- package/lib/installers/ClineInstaller.js +21 -0
- package/lib/installers/CodexInstaller.js +21 -0
- package/lib/installers/CopilotInstaller.js +113 -0
- package/lib/installers/CursorInstaller.js +63 -0
- package/lib/installers/GeminiInstaller.js +75 -0
- package/lib/installers/KiroInstaller.js +22 -0
- package/lib/installers/OpenCodeInstaller.js +22 -0
- package/lib/installers/RooInstaller.js +22 -0
- package/lib/installers/ToolInstaller.js +73 -0
- package/lib/installers/WindsurfInstaller.js +76 -0
- package/lib/markdown-validator.ts +175 -0
- package/lib/yaml-validator.ts +99 -0
- package/package.json +65 -0
|
@@ -0,0 +1,227 @@
|
|
|
1
|
+
# Skill: Gather Requirements
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## Progress Display
|
|
6
|
+
|
|
7
|
+
Show at start of this skill:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
### Inception Progress
|
|
11
|
+
- [x] Intent created
|
|
12
|
+
- [ ] Requirements gathered ← current
|
|
13
|
+
- [ ] Artifacts reviewed (Context + Units + Stories + Bolts)
|
|
14
|
+
- [ ] Ready for Construction
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Checkpoints in This Skill
|
|
20
|
+
|
|
21
|
+
| Checkpoint | Purpose | Wait For |
|
|
22
|
+
|------------|---------|----------|
|
|
23
|
+
| Checkpoint 1 | Clarifying questions | User answers |
|
|
24
|
+
| Checkpoint 2 | Requirements review | User approval |
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## Goal
|
|
29
|
+
|
|
30
|
+
Elicit, analyze, and document functional and non-functional requirements through structured inquiry.
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
## Input
|
|
35
|
+
|
|
36
|
+
- **Required**: Intent name or path
|
|
37
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
38
|
+
- **Optional**: Existing `requirements.md` to update
|
|
39
|
+
|
|
40
|
+
**Note**: Agents load project standards automatically (see `.specsmd/aidlc/context-config.yaml`). Do not duplicate them in requirements.
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
## Process
|
|
45
|
+
|
|
46
|
+
### Step 1: Clarifying Questions
|
|
47
|
+
|
|
48
|
+
**Checkpoint 1**: Present questions before generating anything:
|
|
49
|
+
|
|
50
|
+
```text
|
|
51
|
+
Before I generate requirements, I need to understand:
|
|
52
|
+
1. Who are the primary users?
|
|
53
|
+
2. What key outcomes matter?
|
|
54
|
+
3. Any constraints (regulatory, technical, timeline)?
|
|
55
|
+
4. How will we measure success?
|
|
56
|
+
5. What concerns you most?
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
**Wait for user response.**
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
### Step 2: Generate Requirements
|
|
64
|
+
|
|
65
|
+
After user answers, generate functional and non-functional requirements.
|
|
66
|
+
|
|
67
|
+
**Functional Requirements** - ask about:
|
|
68
|
+
|
|
69
|
+
- Main user flows → Core functionality
|
|
70
|
+
- Error cases → Exception handling
|
|
71
|
+
- Data storage → Data requirements
|
|
72
|
+
- Integrations → External dependencies
|
|
73
|
+
|
|
74
|
+
**Non-Functional Requirements** - ask about:
|
|
75
|
+
|
|
76
|
+
- Performance: Response time, throughput
|
|
77
|
+
- Scalability: Concurrent users, growth
|
|
78
|
+
- Security: Authentication, data sensitivity
|
|
79
|
+
- Reliability: Uptime, failure tolerance
|
|
80
|
+
- Compliance: Regulatory, audit
|
|
81
|
+
|
|
82
|
+
**IMPORTANT**: Do NOT duplicate project standards. Only document intent-specific constraints.
|
|
83
|
+
|
|
84
|
+
### Step 3: Document Requirements
|
|
85
|
+
|
|
86
|
+
1. **Read Path**: Check `schema.requirements` from `.specsmd/aidlc/memory-bank.yaml`
|
|
87
|
+
*(Default: `memory-bank/intents/{intent-name}/requirements.md`)*
|
|
88
|
+
|
|
89
|
+
2. **Use Template**: `.specsmd/aidlc/templates/inception/requirements-template.md`
|
|
90
|
+
|
|
91
|
+
3. **Structure**:
|
|
92
|
+
|
|
93
|
+
```markdown
|
|
94
|
+
## Functional Requirements
|
|
95
|
+
### FR-1: {Title}
|
|
96
|
+
- **Description**: {What the system must do}
|
|
97
|
+
- **Acceptance Criteria**: {Measurable conditions}
|
|
98
|
+
- **Priority**: {Must/Should/Could}
|
|
99
|
+
|
|
100
|
+
## Non-Functional Requirements
|
|
101
|
+
### NFR-1: Performance
|
|
102
|
+
- **Metric**: Response time < 200ms for 95th percentile
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
4. **Validate Testability**:
|
|
106
|
+
- ❌ "Fast response" → ✅ "Response < 200ms p95"
|
|
107
|
+
- ❌ "Secure" → ✅ "OAuth 2.0 with MFA"
|
|
108
|
+
- ❌ "Scalable" → ✅ "Support 10K concurrent users"
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
### Step 4: Requirements Review
|
|
113
|
+
|
|
114
|
+
**Checkpoint 2**: Present FULL requirements for approval.
|
|
115
|
+
|
|
116
|
+
**CRITICAL: Do NOT summarize. Show complete details for each requirement.**
|
|
117
|
+
|
|
118
|
+
**Show progress indicator before requirements:**
|
|
119
|
+
|
|
120
|
+
```text
|
|
121
|
+
### Inception Progress
|
|
122
|
+
- [x] Intent created
|
|
123
|
+
- [ ] Requirements gathered ← current (Checkpoint 2: approval)
|
|
124
|
+
- [ ] Artifacts reviewed (Context + Units + Stories + Bolts)
|
|
125
|
+
- [ ] Ready for Construction
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
Present exactly as documented:
|
|
129
|
+
|
|
130
|
+
```text
|
|
131
|
+
### Requirements Review
|
|
132
|
+
|
|
133
|
+
## Functional Requirements
|
|
134
|
+
|
|
135
|
+
### FR-1: {Title}
|
|
136
|
+
- **Description**: {full description}
|
|
137
|
+
- **Acceptance Criteria**: {all criteria}
|
|
138
|
+
- **Priority**: {Must/Should/Could}
|
|
139
|
+
|
|
140
|
+
### FR-2: {Title}
|
|
141
|
+
- **Description**: {full description}
|
|
142
|
+
- **Acceptance Criteria**: {all criteria}
|
|
143
|
+
- **Priority**: {Must/Should/Could}
|
|
144
|
+
|
|
145
|
+
{continue for all FR and NFR...}
|
|
146
|
+
|
|
147
|
+
---
|
|
148
|
+
|
|
149
|
+
Do these requirements capture your intent?
|
|
150
|
+
1 - Yes, continue to generate artifacts
|
|
151
|
+
2 - Need changes (specify what's missing/wrong)
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
**Wait for user response.**
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
## Output
|
|
159
|
+
|
|
160
|
+
```markdown
|
|
161
|
+
## Requirements Summary: {intent-name}
|
|
162
|
+
|
|
163
|
+
### Functional Requirements
|
|
164
|
+
|
|
165
|
+
- [ ] **FR-1**: {description} - Priority: Must - Status: Draft
|
|
166
|
+
- [ ] **FR-2**: {description} - Priority: Should - Status: Draft
|
|
167
|
+
|
|
168
|
+
### Non-Functional Requirements
|
|
169
|
+
|
|
170
|
+
- **Performance**: Response time < 200ms p95
|
|
171
|
+
- **Security**: OAuth 2.0 + MFA
|
|
172
|
+
|
|
173
|
+
### Technical Constraints
|
|
174
|
+
|
|
175
|
+
Required standards will be loaded from memory-bank standards folder by Construction Agent.
|
|
176
|
+
|
|
177
|
+
Intent-specific constraints:
|
|
178
|
+
- {any feature-specific constraint not in standards}
|
|
179
|
+
|
|
180
|
+
### Artifact Updated
|
|
181
|
+
- `{intent-path}/requirements.md`
|
|
182
|
+
|
|
183
|
+
### Actions
|
|
184
|
+
|
|
185
|
+
1 - **context**: Define system context and boundaries
|
|
186
|
+
2 - **menu**: Return to inception menu
|
|
187
|
+
|
|
188
|
+
### Suggested Next Step
|
|
189
|
+
→ **context** - Define system boundaries for `{intent-name}`
|
|
190
|
+
|
|
191
|
+
**Type a number or press Enter for suggested action.**
|
|
192
|
+
```
|
|
193
|
+
|
|
194
|
+
---
|
|
195
|
+
|
|
196
|
+
## After Approval
|
|
197
|
+
|
|
198
|
+
Once requirements are approved at Checkpoint 2:
|
|
199
|
+
|
|
200
|
+
1. Save to `{intent}/requirements.md`
|
|
201
|
+
2. Update inception-log.md with artifact status
|
|
202
|
+
3. Proceed to generate remaining artifacts (Context + Units + Stories + Bolts)
|
|
203
|
+
|
|
204
|
+
---
|
|
205
|
+
|
|
206
|
+
## Transition
|
|
207
|
+
|
|
208
|
+
After requirements approved → Generate batched artifacts:
|
|
209
|
+
|
|
210
|
+
- System Context
|
|
211
|
+
- Units
|
|
212
|
+
- Stories
|
|
213
|
+
- Bolt Plan
|
|
214
|
+
|
|
215
|
+
These will be reviewed together at Checkpoint 3 (Artifacts Review).
|
|
216
|
+
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
## Test Contract
|
|
220
|
+
|
|
221
|
+
```yaml
|
|
222
|
+
input: User answers to 5 clarifying questions
|
|
223
|
+
output: requirements.md with FR-1..n, NFR-1..n
|
|
224
|
+
checkpoints: 2
|
|
225
|
+
- Checkpoint 1: Clarifying questions answered
|
|
226
|
+
- Checkpoint 2: Requirements approved
|
|
227
|
+
```
|
|
@@ -0,0 +1,248 @@
|
|
|
1
|
+
# Skill: Review & Complete Inception
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## Progress Display
|
|
6
|
+
|
|
7
|
+
Show at start of this skill:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
### Inception Progress
|
|
11
|
+
- [x] Intent created
|
|
12
|
+
- [x] Requirements gathered
|
|
13
|
+
- [ ] Artifacts reviewed ← current
|
|
14
|
+
- [ ] Ready for Construction
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Checkpoints in This Skill
|
|
20
|
+
|
|
21
|
+
| Checkpoint | Purpose | Wait For |
|
|
22
|
+
|------------|---------|----------|
|
|
23
|
+
| Checkpoint 3 | Artifacts review (Context + Units + Stories + Bolts) | User approval |
|
|
24
|
+
| Checkpoint 4 | Ready for Construction | User confirmation |
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## Goal
|
|
29
|
+
|
|
30
|
+
Ensure all inception artifacts are complete, consistent, and ready for Construction Phase.
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
## Input
|
|
35
|
+
|
|
36
|
+
- **Required**: Intent name
|
|
37
|
+
- **Required**: All intent artifacts
|
|
38
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
## Process
|
|
43
|
+
|
|
44
|
+
### 1. Artifact Verification
|
|
45
|
+
|
|
46
|
+
Check existence and completeness of all required artifacts:
|
|
47
|
+
|
|
48
|
+
- **Requirements**: `{intent}/requirements.md` - FR, NFR, constraints
|
|
49
|
+
- **System Context**: `{intent}/system-context.md` - Actors, external systems, data flows
|
|
50
|
+
- **Units**: `{intent}/units.md` - Unit list with purposes
|
|
51
|
+
- **Unit Briefs**: `{intent}/units/{unit}/unit-brief.md` - Scope, entities, success criteria
|
|
52
|
+
- **Stories**: `{intent}/units/{unit}/stories/*.md` - Acceptance criteria
|
|
53
|
+
- **Bolts**: Path from `schema.bolts` - Type, stories, status
|
|
54
|
+
|
|
55
|
+
### 2. Consistency Check
|
|
56
|
+
|
|
57
|
+
Verify cross-artifact consistency:
|
|
58
|
+
|
|
59
|
+
- **Story Coverage**: All requirements traced to stories
|
|
60
|
+
- **Unit Independence**: No circular dependencies
|
|
61
|
+
- **Bolt Completeness**: All stories assigned to bolts
|
|
62
|
+
- **Type Alignment**: Bolt types match story nature
|
|
63
|
+
|
|
64
|
+
### Step 3: Artifacts Review
|
|
65
|
+
|
|
66
|
+
**Checkpoint 3**: Present all generated artifacts for review:
|
|
67
|
+
|
|
68
|
+
```text
|
|
69
|
+
### Artifacts Review
|
|
70
|
+
|
|
71
|
+
**System Context**
|
|
72
|
+
- Actors: {list}
|
|
73
|
+
- External systems: {list}
|
|
74
|
+
- Data flows: {summary}
|
|
75
|
+
|
|
76
|
+
**Units**
|
|
77
|
+
- {unit-1}: {purpose}
|
|
78
|
+
- {unit-2}: {purpose}
|
|
79
|
+
|
|
80
|
+
**Stories** ({n} total)
|
|
81
|
+
- {unit-1}: S1, S2, S3
|
|
82
|
+
- {unit-2}: S4, S5
|
|
83
|
+
|
|
84
|
+
**Bolt Plan** ({n} bolts)
|
|
85
|
+
- bolt-{unit-1}-1: Stories S1-S3
|
|
86
|
+
- bolt-{unit-2}-1: Stories S4-S5
|
|
87
|
+
|
|
88
|
+
Review the breakdown above. Any changes needed?
|
|
89
|
+
1 - Looks good, continue
|
|
90
|
+
2 - Need changes (specify what)
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
**Wait for user response.**
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
97
|
+
### Step 4: Gap Resolution
|
|
98
|
+
|
|
99
|
+
If gaps are found:
|
|
100
|
+
|
|
101
|
+
```markdown
|
|
102
|
+
## Gaps Identified
|
|
103
|
+
|
|
104
|
+
- 🚫 **Missing NFR** in requirements.md → Add performance criteria
|
|
105
|
+
- 🚫 **No stories** for `unit-api` → Create stories for API unit
|
|
106
|
+
|
|
107
|
+
### Recommended Actions
|
|
108
|
+
|
|
109
|
+
1 - **requirements**: Add missing NFR
|
|
110
|
+
2 - **stories**: Create stories for unit-api
|
|
111
|
+
|
|
112
|
+
**Type a number to fix the gap.**
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
### 5. Update Inception Log
|
|
116
|
+
|
|
117
|
+
When all checks pass, update `inception-log.md` (created during intent-create):
|
|
118
|
+
|
|
119
|
+
- Use template: `.specsmd/aidlc/templates/inception/inception-log-template.md`
|
|
120
|
+
- Update `status` to `complete`
|
|
121
|
+
- Update `completed` date
|
|
122
|
+
- Fill in Summary section with final counts
|
|
123
|
+
- Mark all items in "Ready for Construction" checklist as complete
|
|
124
|
+
|
|
125
|
+
Update these sections:
|
|
126
|
+
|
|
127
|
+
```markdown
|
|
128
|
+
---
|
|
129
|
+
intent: {intent-name}
|
|
130
|
+
created: {original-date}
|
|
131
|
+
completed: {today}
|
|
132
|
+
status: complete
|
|
133
|
+
---
|
|
134
|
+
|
|
135
|
+
## Summary
|
|
136
|
+
|
|
137
|
+
- **Functional Requirements**: {n}
|
|
138
|
+
- **Non-Functional Requirements**: {n}
|
|
139
|
+
- **Units**: {n}
|
|
140
|
+
- **Stories**: {n}
|
|
141
|
+
- **Bolts Planned**: {n}
|
|
142
|
+
|
|
143
|
+
## Ready for Construction
|
|
144
|
+
|
|
145
|
+
**Checklist**:
|
|
146
|
+
- [x] All requirements documented
|
|
147
|
+
- [x] System context defined
|
|
148
|
+
- [x] Units decomposed
|
|
149
|
+
- [x] Stories created for all units
|
|
150
|
+
- [x] Bolts planned
|
|
151
|
+
- [x] Human review complete
|
|
152
|
+
|
|
153
|
+
## Next Steps
|
|
154
|
+
|
|
155
|
+
1 - **construction**: Start building with first bolt
|
|
156
|
+
|
|
157
|
+
→ `/specsmd-construction-agent --unit="{first-unit}"`
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
### Step 6: Update Intent Status
|
|
161
|
+
|
|
162
|
+
Update `requirements.md` frontmatter:
|
|
163
|
+
|
|
164
|
+
```yaml
|
|
165
|
+
status: inception-complete
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
170
|
+
### Step 7: Ready for Construction
|
|
171
|
+
|
|
172
|
+
**Checkpoint 4**: Confirm ready to proceed:
|
|
173
|
+
|
|
174
|
+
```text
|
|
175
|
+
### Ready for Construction?
|
|
176
|
+
|
|
177
|
+
✅ Inception complete for {intent-name}
|
|
178
|
+
|
|
179
|
+
Summary:
|
|
180
|
+
- {n} functional requirements
|
|
181
|
+
- {m} non-functional requirements
|
|
182
|
+
- {x} units
|
|
183
|
+
- {y} stories
|
|
184
|
+
- {z} bolts planned
|
|
185
|
+
|
|
186
|
+
Ready to start construction?
|
|
187
|
+
1 - Yes, start with {first-unit}
|
|
188
|
+
2 - Yes, start with different unit
|
|
189
|
+
3 - Review something first
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
**Wait for user response.**
|
|
193
|
+
|
|
194
|
+
---
|
|
195
|
+
|
|
196
|
+
## Output
|
|
197
|
+
|
|
198
|
+
```markdown
|
|
199
|
+
## Inception Review: {intent-name}
|
|
200
|
+
|
|
201
|
+
### Verification Results
|
|
202
|
+
|
|
203
|
+
- ✅ Artifacts complete
|
|
204
|
+
- ✅ Cross-references valid
|
|
205
|
+
- ✅ Stories have acceptance criteria
|
|
206
|
+
- ✅ Bolts planned
|
|
207
|
+
|
|
208
|
+
### Log Updated
|
|
209
|
+
- `{schema.intents}/{intent-name}/inception-log.md`
|
|
210
|
+
|
|
211
|
+
### Ready for Construction
|
|
212
|
+
✅ **INCEPTION COMPLETE**
|
|
213
|
+
|
|
214
|
+
Intent `{intent-name}` is ready for Construction Phase.
|
|
215
|
+
|
|
216
|
+
### Actions
|
|
217
|
+
|
|
218
|
+
1 - **construction**: Start building with first bolt
|
|
219
|
+
|
|
220
|
+
### Suggested Next Step
|
|
221
|
+
→ **construction** - Start with `/specsmd-construction-agent --unit="{first-unit}" --bolt-id="{first-bolt}"`
|
|
222
|
+
|
|
223
|
+
**Type a number or press Enter for suggested action.**
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
---
|
|
227
|
+
|
|
228
|
+
## Transition
|
|
229
|
+
|
|
230
|
+
After user confirms at Checkpoint 4:
|
|
231
|
+
|
|
232
|
+
- → **Construction Agent** - `/specsmd-construction-agent --unit="{unit}"`
|
|
233
|
+
|
|
234
|
+
If gaps found at Checkpoint 3:
|
|
235
|
+
|
|
236
|
+
- → Return to appropriate skill to fix
|
|
237
|
+
|
|
238
|
+
---
|
|
239
|
+
|
|
240
|
+
## Test Contract
|
|
241
|
+
|
|
242
|
+
```yaml
|
|
243
|
+
input: All inception artifacts (requirements, context, units, stories, bolts)
|
|
244
|
+
output: inception-log.md updated, intent status = inception-complete
|
|
245
|
+
checkpoints: 2
|
|
246
|
+
- Checkpoint 3: Artifacts reviewed and approved
|
|
247
|
+
- Checkpoint 4: Ready for Construction confirmed
|
|
248
|
+
```
|