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,171 @@
|
|
|
1
|
+
# Skill: Define System Context
|
|
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
|
+
- [ ] Generating artifacts... ← current
|
|
14
|
+
- [ ] System Context ← this skill
|
|
15
|
+
- [ ] Units
|
|
16
|
+
- [ ] Stories
|
|
17
|
+
- [ ] Bolt Plan
|
|
18
|
+
- [ ] Artifacts reviewed (Checkpoint 3)
|
|
19
|
+
- [ ] Ready for Construction
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## Checkpoints in This Skill
|
|
25
|
+
|
|
26
|
+
**NO INDIVIDUAL Checkpoint** - This skill is part of the batched artifact generation.
|
|
27
|
+
|
|
28
|
+
All artifacts (Context, Units, Stories, Bolts) are reviewed together at **Checkpoint 3** in the `review` skill.
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
## Goal
|
|
33
|
+
|
|
34
|
+
Identify system boundaries, actors, and external dependencies to establish the "world" the system lives in.
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
## Input
|
|
39
|
+
|
|
40
|
+
- **Required**: Intent name
|
|
41
|
+
- **Required**: `requirements.md` for the intent
|
|
42
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## Process
|
|
47
|
+
|
|
48
|
+
### 1. Identify Actors
|
|
49
|
+
|
|
50
|
+
Ask questions to discover all system users:
|
|
51
|
+
|
|
52
|
+
- **Human Users**: "Who uses this directly?" (Admin, Customer, Support)
|
|
53
|
+
- **System Users**: "What systems call this?" (Scheduler, Event Bus)
|
|
54
|
+
- **External Systems**: "What third-party services interact?" (Stripe, Auth0)
|
|
55
|
+
|
|
56
|
+
### 2. Map External Systems
|
|
57
|
+
|
|
58
|
+
For each external dependency, document:
|
|
59
|
+
|
|
60
|
+
- **System name**: What is it?
|
|
61
|
+
- **Direction**: Inbound/Outbound/Both
|
|
62
|
+
- **Data Exchanged**: What data crosses?
|
|
63
|
+
- **Protocol**: REST/GraphQL/Event
|
|
64
|
+
|
|
65
|
+
### 3. Define Data Flows
|
|
66
|
+
|
|
67
|
+
Document what data crosses the boundary:
|
|
68
|
+
|
|
69
|
+
**Inbound**:
|
|
70
|
+
|
|
71
|
+
- What data enters the system?
|
|
72
|
+
- What format? (JSON, XML, Binary)
|
|
73
|
+
- What validation is needed?
|
|
74
|
+
|
|
75
|
+
**Outbound**:
|
|
76
|
+
|
|
77
|
+
- What data leaves the system?
|
|
78
|
+
- What consumers expect it?
|
|
79
|
+
- What guarantees are needed? (Delivery, ordering)
|
|
80
|
+
|
|
81
|
+
### 4. Create Context Diagram
|
|
82
|
+
|
|
83
|
+
Generate a C4 Context diagram (Mermaid):
|
|
84
|
+
|
|
85
|
+
```markdown
|
|
86
|
+
## System Context Diagram
|
|
87
|
+
|
|
88
|
+
```mermaid
|
|
89
|
+
C4Context
|
|
90
|
+
title System Context - {intent-name}
|
|
91
|
+
|
|
92
|
+
Person(user, "User", "Primary user of the system")
|
|
93
|
+
System(sys, "{System Name}", "The system being built")
|
|
94
|
+
System_Ext(ext1, "External System", "Third-party service")
|
|
95
|
+
|
|
96
|
+
Rel(user, sys, "Uses")
|
|
97
|
+
Rel(sys, ext1, "Integrates with")
|
|
98
|
+
```
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
### 5. Document Context
|
|
102
|
+
|
|
103
|
+
1. **Read Path**: Check `schema.system_context` from `.specsmd/aidlc/memory-bank.yaml`
|
|
104
|
+
*(Default: `memory-bank/intents/{intent-name}/system-context.md`)*
|
|
105
|
+
|
|
106
|
+
2. **Use Template**: `.specsmd/aidlc/templates/inception/system-context-template.md`
|
|
107
|
+
|
|
108
|
+
3. **Structure**:
|
|
109
|
+
|
|
110
|
+
```markdown
|
|
111
|
+
## Actors
|
|
112
|
+
|
|
113
|
+
- **{Actor}** ({Type}): {Description}
|
|
114
|
+
|
|
115
|
+
## External Systems
|
|
116
|
+
|
|
117
|
+
- **{System}**: {Purpose} - {Integration Type}
|
|
118
|
+
|
|
119
|
+
## Data Flows
|
|
120
|
+
### Inbound
|
|
121
|
+
### Outbound
|
|
122
|
+
|
|
123
|
+
## Context Diagram
|
|
124
|
+
{Mermaid diagram}
|
|
125
|
+
```
|
|
126
|
+
|
|
127
|
+
### 6. Validate Completeness
|
|
128
|
+
|
|
129
|
+
Ask:
|
|
130
|
+
|
|
131
|
+
- "Did I miss any third-party integrations?"
|
|
132
|
+
- "Are there legacy systems this needs to work with?"
|
|
133
|
+
- "Any planned future integrations to consider?"
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Output
|
|
138
|
+
|
|
139
|
+
```markdown
|
|
140
|
+
## System Context: {intent-name}
|
|
141
|
+
|
|
142
|
+
### Actors Identified
|
|
143
|
+
|
|
144
|
+
- **Customer** (Human): Web/Mobile UI
|
|
145
|
+
- **Admin** (Human): Admin Dashboard
|
|
146
|
+
- **Payment Gateway** (System): REST API
|
|
147
|
+
|
|
148
|
+
### External Dependencies
|
|
149
|
+
|
|
150
|
+
- **Stripe**: Payments - Risk: High
|
|
151
|
+
- **SendGrid**: Email - Risk: Medium
|
|
152
|
+
|
|
153
|
+
### Data Flow Summary
|
|
154
|
+
- **Inbound**: User requests, webhook events
|
|
155
|
+
- **Outbound**: Transaction records, notifications
|
|
156
|
+
|
|
157
|
+
### Artifact Created
|
|
158
|
+
✅ `{intent-path}/system-context.md`
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
**No menu** - Skill complete, return to agent.
|
|
162
|
+
|
|
163
|
+
---
|
|
164
|
+
|
|
165
|
+
## Test Contract
|
|
166
|
+
|
|
167
|
+
```yaml
|
|
168
|
+
input: Intent requirements
|
|
169
|
+
output: system-context.md with actors, systems, data flows
|
|
170
|
+
checkpoints: 0 (part of Checkpoint 3 batch)
|
|
171
|
+
```
|
|
@@ -0,0 +1,211 @@
|
|
|
1
|
+
# Skill: Create Intent
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## Progress Display
|
|
6
|
+
|
|
7
|
+
Show at start of this skill:
|
|
8
|
+
|
|
9
|
+
```text
|
|
10
|
+
### Inception Progress
|
|
11
|
+
- [ ] Intent created ← this skill
|
|
12
|
+
- [ ] Requirements gathered (Checkpoint 1, Checkpoint 2)
|
|
13
|
+
- [ ] Artifacts reviewed (Checkpoint 3)
|
|
14
|
+
- [ ] Ready for Construction (Checkpoint 4)
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Checkpoints in This Skill
|
|
20
|
+
|
|
21
|
+
**NO Checkpoint** - This skill is a prerequisite to the checkpoint workflow.
|
|
22
|
+
|
|
23
|
+
Intent creation is a simple initialization step. The workflow checkpoints begin in the `requirements` skill.
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## Goal
|
|
28
|
+
|
|
29
|
+
Guide the user to define a high-level feature (Intent) and initialize its structure in the Memory Bank.
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## Input
|
|
34
|
+
|
|
35
|
+
- **Required**: User's feature idea or request
|
|
36
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
37
|
+
- **Optional**: `memory-bank/project.yaml` - project type for context-aware suggestions
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## Process
|
|
42
|
+
|
|
43
|
+
### 0. Load Project Context
|
|
44
|
+
|
|
45
|
+
**Before asking questions**, read project configuration:
|
|
46
|
+
|
|
47
|
+
1. Read `memory-bank/project.yaml` to get `project_type`
|
|
48
|
+
2. List `memory-bank/intents/` directory to see existing intents
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
#### Case A: FIRST Intent (no intents exist)
|
|
53
|
+
|
|
54
|
+
**Be creative** and suggest 3-4 relevant intent examples based on project type.
|
|
55
|
+
|
|
56
|
+
Consider the project type and generate suggestions that:
|
|
57
|
+
|
|
58
|
+
- Are common starting points for that type of application
|
|
59
|
+
- Provide foundational functionality to build upon
|
|
60
|
+
- Are appropriately scoped for an intent (not too large, not too small)
|
|
61
|
+
|
|
62
|
+
**Show to user:**
|
|
63
|
+
|
|
64
|
+
```markdown
|
|
65
|
+
## Create Your First Intent
|
|
66
|
+
|
|
67
|
+
**Project Type**: {project_type}
|
|
68
|
+
|
|
69
|
+
Here are some ideas for your first feature:
|
|
70
|
+
- "{creative suggestion 1 relevant to project type}"
|
|
71
|
+
- "{creative suggestion 2 relevant to project type}"
|
|
72
|
+
- "{creative suggestion 3 relevant to project type}"
|
|
73
|
+
|
|
74
|
+
Or tell me what you'd like to build.
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
If `project.yaml` doesn't exist, ask what they want to build without suggestions.
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
#### Case B: Subsequent Intents (intents already exist)
|
|
82
|
+
|
|
83
|
+
Analyze existing intents to understand project context and suggest related features:
|
|
84
|
+
|
|
85
|
+
1. **Read existing intent names** from `memory-bank/intents/` folder names
|
|
86
|
+
2. **Read requirements.md** from each existing intent to understand scope
|
|
87
|
+
3. **Infer project domain** (e.g., e-commerce, SaaS, developer tool, social platform)
|
|
88
|
+
4. **Suggest complementary features** that would naturally extend the existing functionality
|
|
89
|
+
|
|
90
|
+
**Example Analysis:**
|
|
91
|
+
|
|
92
|
+
If existing intents are:
|
|
93
|
+
|
|
94
|
+
- `001-user-authentication`
|
|
95
|
+
- `002-product-catalog`
|
|
96
|
+
|
|
97
|
+
Then suggest:
|
|
98
|
+
|
|
99
|
+
- "Shopping cart and checkout" (natural next step for e-commerce)
|
|
100
|
+
- "Order management and history" (complements product catalog)
|
|
101
|
+
- "User reviews and ratings" (enhances product catalog)
|
|
102
|
+
- "Wishlist functionality" (user engagement feature)
|
|
103
|
+
|
|
104
|
+
**Show to user:**
|
|
105
|
+
|
|
106
|
+
```markdown
|
|
107
|
+
## Create New Intent
|
|
108
|
+
|
|
109
|
+
Based on your existing intents:
|
|
110
|
+
- `001-user-authentication` - {brief description from requirements}
|
|
111
|
+
- `002-product-catalog` - {brief description from requirements}
|
|
112
|
+
|
|
113
|
+
Your project appears to be a **{inferred domain, e.g., "e-commerce platform"}**.
|
|
114
|
+
|
|
115
|
+
Here are some features that might complement your existing work:
|
|
116
|
+
- "{suggestion 1}"
|
|
117
|
+
- "{suggestion 2}"
|
|
118
|
+
- "{suggestion 3}"
|
|
119
|
+
|
|
120
|
+
Or tell me what you'd like to build next.
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
### 1. Elicit Intent Details
|
|
124
|
+
|
|
125
|
+
Ask clarifying questions to understand the intent:
|
|
126
|
+
|
|
127
|
+
- **"What is the name for this intent?"** → Get kebab-case identifier (e.g., `user-authentication`)
|
|
128
|
+
- **"What problem does this solve?"** → Understand business value
|
|
129
|
+
- **"Who benefits from this?"** → Identify stakeholders
|
|
130
|
+
- **"What's in scope vs out of scope?"** → Set boundaries early
|
|
131
|
+
|
|
132
|
+
**IMPORTANT**: Intent names MUST have a 3-digit numeric prefix to indicate implementation order:
|
|
133
|
+
|
|
134
|
+
- Format: `{NNN}-{intent-name}` (e.g., `001-user-authentication`, `002-payment-processing`)
|
|
135
|
+
- Check existing intents to determine next available number
|
|
136
|
+
- First intent is `001-*`, second is `002-*`, etc.
|
|
137
|
+
|
|
138
|
+
Note: All naming (units, stories) is derived from folder names. No prefix fields needed in frontmatter.
|
|
139
|
+
|
|
140
|
+
### 2. Classify Intent Type
|
|
141
|
+
|
|
142
|
+
Determine the intent category:
|
|
143
|
+
|
|
144
|
+
- **New Feature**: Brand new capability (e.g., "Add payment processing")
|
|
145
|
+
- **Enhancement**: Improve existing feature (e.g., "Add MFA to auth")
|
|
146
|
+
- **Bug Fix**: Correct defective behavior (e.g., "Fix checkout race condition")
|
|
147
|
+
- **Refactor**: Technical improvement (e.g., "Migrate to new API version")
|
|
148
|
+
- **Infrastructure**: Platform/DevOps change (e.g., "Add caching layer")
|
|
149
|
+
|
|
150
|
+
### 3. Initialize Artifacts
|
|
151
|
+
|
|
152
|
+
Once confirmed, perform these file operations:
|
|
153
|
+
|
|
154
|
+
1. **Read Schema**: Check `.specsmd/aidlc/memory-bank.yaml` for `intents` path
|
|
155
|
+
*(Default: `memory-bank/intents/{intent-name}/`)*
|
|
156
|
+
|
|
157
|
+
2. **Create Directory**:
|
|
158
|
+
|
|
159
|
+
```text
|
|
160
|
+
{schema.intents}/{intent-name}/
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
3. **Create `requirements.md`**:
|
|
164
|
+
- Use template: `.specsmd/aidlc/templates/inception/requirements-template.md`
|
|
165
|
+
- Populate Goal and Scope with user input
|
|
166
|
+
- Set status to `draft`
|
|
167
|
+
|
|
168
|
+
4. **Create `inception-log.md`**:
|
|
169
|
+
- Use template: `.specsmd/aidlc/templates/inception/inception-log-template.md`
|
|
170
|
+
- Initialize with intent metadata and empty sections
|
|
171
|
+
- Track progress, decisions, and scope changes
|
|
172
|
+
|
|
173
|
+
### 5. Confirm Creation
|
|
174
|
+
|
|
175
|
+
Show confirmation with **exactly ONE action list** - no workflow overview, no extra lists:
|
|
176
|
+
|
|
177
|
+
```markdown
|
|
178
|
+
## Intent Created: `{intent-name}`
|
|
179
|
+
|
|
180
|
+
**Goal**: {user's stated goal}
|
|
181
|
+
**Type**: {intent type}
|
|
182
|
+
**Location**: `{intent-path}/`
|
|
183
|
+
|
|
184
|
+
Files created:
|
|
185
|
+
- `requirements.md` (draft)
|
|
186
|
+
- `inception-log.md` (progress tracker)
|
|
187
|
+
|
|
188
|
+
1 - **requirements**: [Recommended] Gather detailed requirements
|
|
189
|
+
2 - **context**: Define system context and boundaries
|
|
190
|
+
3 - **menu**: Return to inception menu
|
|
191
|
+
|
|
192
|
+
**Type a number to continue.**
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
---
|
|
196
|
+
|
|
197
|
+
## Transition
|
|
198
|
+
|
|
199
|
+
After intent created:
|
|
200
|
+
|
|
201
|
+
- → **requirements** - begin checkpoint workflow at Checkpoint 1
|
|
202
|
+
|
|
203
|
+
---
|
|
204
|
+
|
|
205
|
+
## Test Contract
|
|
206
|
+
|
|
207
|
+
```yaml
|
|
208
|
+
input: User's feature idea
|
|
209
|
+
output: Intent directory with requirements.md and inception-log.md
|
|
210
|
+
checkpoints: 0 (prerequisite to workflow)
|
|
211
|
+
```
|
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
# Skill: List Intents
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## Role
|
|
6
|
+
|
|
7
|
+
Utility skill to view all intents and their status.
|
|
8
|
+
|
|
9
|
+
**NO Checkpoint** - This is an informational/navigation skill.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Goal
|
|
14
|
+
|
|
15
|
+
Display all intents in the memory bank with their current status and suggest next actions.
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Input
|
|
20
|
+
|
|
21
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
22
|
+
- **Required**: Intents at path defined by `schema.intents`
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## Process
|
|
27
|
+
|
|
28
|
+
### 1. Load Schema
|
|
29
|
+
|
|
30
|
+
Read `.specsmd/aidlc/memory-bank.yaml` to get the `intents` path.
|
|
31
|
+
|
|
32
|
+
### 2. Scan Intents
|
|
33
|
+
|
|
34
|
+
For each directory in `schema.intents`:
|
|
35
|
+
|
|
36
|
+
1. Read `requirements.md` frontmatter for metadata
|
|
37
|
+
2. Check for existence of key artifacts:
|
|
38
|
+
- `requirements.md` - requirements defined?
|
|
39
|
+
- `system-context.md` - context mapped?
|
|
40
|
+
- `units.md` - decomposed?
|
|
41
|
+
- `units/*/stories/` - stories created?
|
|
42
|
+
3. Check path from `schema.bolts` for planned bolts
|
|
43
|
+
|
|
44
|
+
### 3. Determine Status
|
|
45
|
+
|
|
46
|
+
Status progression based on artifacts present:
|
|
47
|
+
|
|
48
|
+
- Only `requirements.md` (draft) → **Draft** (Early Inception)
|
|
49
|
+
- `requirements.md` complete → **Requirements Done** (Inception)
|
|
50
|
+
- `system-context.md` exists → **Context Mapped** (Inception)
|
|
51
|
+
- `units.md` exists → **Decomposed** (Inception)
|
|
52
|
+
- Stories exist → **Stories Done** (Inception)
|
|
53
|
+
- Bolts planned → **Ready for Construction** (Inception Complete)
|
|
54
|
+
- Bolts in-progress → **Building** (Construction)
|
|
55
|
+
- All bolts complete → **Ready for Deployment** (Construction Complete)
|
|
56
|
+
- Deployed → **Live** (Operations)
|
|
57
|
+
|
|
58
|
+
### 4. Display Results
|
|
59
|
+
|
|
60
|
+
```markdown
|
|
61
|
+
## Intents Overview
|
|
62
|
+
|
|
63
|
+
- ⏳ **{intent-1}**: {status} - {phase} - {x/y} progress
|
|
64
|
+
- [ ] **{intent-2}**: {status} - {phase} - {x/y} progress
|
|
65
|
+
- ✅ **{intent-3}**: Completed - Operations
|
|
66
|
+
|
|
67
|
+
### Summary
|
|
68
|
+
- **Total**: {count} intents
|
|
69
|
+
- **By Phase**: Inception ({n}), Construction ({n}), Operations ({n})
|
|
70
|
+
- **Needs Attention**: {list of blocked or stale intents}
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
---
|
|
74
|
+
|
|
75
|
+
## Output
|
|
76
|
+
|
|
77
|
+
```markdown
|
|
78
|
+
## Project Intents
|
|
79
|
+
|
|
80
|
+
### Active Intents
|
|
81
|
+
|
|
82
|
+
- ⏳ **user-authentication**: Construction - Bolt 2/3 in progress (2024-12-05)
|
|
83
|
+
- [ ] **payment-integration**: Inception - Stories needed (2024-12-04)
|
|
84
|
+
|
|
85
|
+
### Completed Intents
|
|
86
|
+
|
|
87
|
+
- ✅ **core-api**: Completed 2024-11-28 - Production
|
|
88
|
+
|
|
89
|
+
### Summary
|
|
90
|
+
- **Total**: 3 intents
|
|
91
|
+
- **Active**: 2
|
|
92
|
+
- **Completed**: 1
|
|
93
|
+
|
|
94
|
+
### Actions
|
|
95
|
+
|
|
96
|
+
1 - **payment-integration**: Create stories to complete inception
|
|
97
|
+
2 - **user-authentication**: Continue bolt execution
|
|
98
|
+
3 - **create-intent**: Create a new intent
|
|
99
|
+
|
|
100
|
+
### Suggested Next Step
|
|
101
|
+
→ **payment-integration** - Complete inception by creating stories
|
|
102
|
+
|
|
103
|
+
**Type a number or press Enter for suggested action.**
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
---
|
|
107
|
+
|
|
108
|
+
## Transition
|
|
109
|
+
|
|
110
|
+
After viewing list:
|
|
111
|
+
|
|
112
|
+
- → **intent-create** - if user wants new intent
|
|
113
|
+
- → **requirements** - if user picks intent in early inception
|
|
114
|
+
- → **Construction Agent** - if intent is ready for construction
|
|
115
|
+
|
|
116
|
+
---
|
|
117
|
+
|
|
118
|
+
## Test Contract
|
|
119
|
+
|
|
120
|
+
```yaml
|
|
121
|
+
input: Memory bank path
|
|
122
|
+
output: List of intents with status, suggested actions
|
|
123
|
+
checkpoints: 0 (informational only)
|
|
124
|
+
```
|
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
# Skill: Inception Navigator
|
|
2
|
+
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
## Role
|
|
6
|
+
|
|
7
|
+
Entry point for Inception Agent. Routes to appropriate skill based on state.
|
|
8
|
+
|
|
9
|
+
**NO Checkpoint** - Navigator is a routing skill, not a decision point.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Goal
|
|
14
|
+
|
|
15
|
+
Present the Inception Agent's skills and guide the user to the appropriate next action.
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Input
|
|
20
|
+
|
|
21
|
+
- **Optional**: Current intent (from `--intent` parameter)
|
|
22
|
+
- **Required**: `.specsmd/aidlc/memory-bank.yaml` - artifact schema
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## Process
|
|
27
|
+
|
|
28
|
+
### 1. Determine Context
|
|
29
|
+
|
|
30
|
+
If intent is specified, load its current state:
|
|
31
|
+
|
|
32
|
+
- Check which artifacts exist
|
|
33
|
+
- Identify current progress stage
|
|
34
|
+
- Determine logical next step
|
|
35
|
+
|
|
36
|
+
### 2. Present Menu
|
|
37
|
+
|
|
38
|
+
Build menu dynamically using the Output sections below based on current state.
|
|
39
|
+
|
|
40
|
+
### 3. Context-Aware Suggestions
|
|
41
|
+
|
|
42
|
+
Scan artifacts **in order** - first missing item is the suggested next step:
|
|
43
|
+
|
|
44
|
+
| Check (in order) | If missing → Suggest |
|
|
45
|
+
|-------------------------------|--------------------------|
|
|
46
|
+
| No intent folder exists | Create Intent |
|
|
47
|
+
| `requirements.md` | Gather Requirements |
|
|
48
|
+
| `system-context.md` | Define Context |
|
|
49
|
+
| `units.md` | Decompose Units |
|
|
50
|
+
| `story-index.md` | Create Stories |
|
|
51
|
+
| `bolt-plan.md` | Plan Bolts |
|
|
52
|
+
| All complete | Review & Complete |
|
|
53
|
+
|
|
54
|
+
**CRITICAL**: The suggested step becomes **Option 1** in the menu.
|
|
55
|
+
|
|
56
|
+
### 4. Handle Selection
|
|
57
|
+
|
|
58
|
+
When user selects an option:
|
|
59
|
+
|
|
60
|
+
1. Acknowledge the selection
|
|
61
|
+
2. Load the corresponding skill file
|
|
62
|
+
3. Execute with current intent context
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## Output (No Active Intent)
|
|
67
|
+
|
|
68
|
+
```markdown
|
|
69
|
+
## Inception Agent
|
|
70
|
+
|
|
71
|
+
### No Active Intent
|
|
72
|
+
|
|
73
|
+
### Get Started
|
|
74
|
+
|
|
75
|
+
1 - **Create Intent** ← Start here
|
|
76
|
+
|
|
77
|
+
### Other Actions
|
|
78
|
+
|
|
79
|
+
2 - List Intents
|
|
80
|
+
3 - Return to Main Menu
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
**Type 1 to continue, or a number for other actions.**
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## Output (With Active Intent)
|
|
90
|
+
|
|
91
|
+
**Option 1 is determined by Context-Aware Suggestions table above.**
|
|
92
|
+
|
|
93
|
+
```markdown
|
|
94
|
+
## Inception Agent
|
|
95
|
+
|
|
96
|
+
### Active Intent: `{intent-name}`
|
|
97
|
+
**Goal**: {intent goal}
|
|
98
|
+
|
|
99
|
+
### Progress
|
|
100
|
+
- {✅ or [ ]} Requirements gathered {← current if next step}
|
|
101
|
+
- {✅ or [ ]} System context defined {← current if next step}
|
|
102
|
+
- {✅ or [ ]} Units decomposed {← current if next step}
|
|
103
|
+
- {✅ or [ ]} Stories created {← current if next step}
|
|
104
|
+
- {✅ or [ ]} Bolts planned {← current if next step}
|
|
105
|
+
- [ ] Review complete {← current if all above done}
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
### Continue This Intent
|
|
110
|
+
|
|
111
|
+
1 - **{Next step from table}** ← Next step
|
|
112
|
+
{N} - Revisit {completed steps...}
|
|
113
|
+
|
|
114
|
+
### Other Actions
|
|
115
|
+
|
|
116
|
+
{N} - Create New Intent
|
|
117
|
+
{N} - List All Intents
|
|
118
|
+
{N} - Return to Main Menu
|
|
119
|
+
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
**Type 1 to continue, or a number for other actions.**
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
**Example: Requirements done, context missing**
|
|
126
|
+
|
|
127
|
+
```markdown
|
|
128
|
+
## Inception Agent
|
|
129
|
+
|
|
130
|
+
### Active Intent: `user-auth`
|
|
131
|
+
**Goal**: Implement user authentication with OAuth
|
|
132
|
+
|
|
133
|
+
### Progress
|
|
134
|
+
- ✅ Requirements gathered
|
|
135
|
+
- [ ] System context defined ← current
|
|
136
|
+
- [ ] Units decomposed
|
|
137
|
+
- [ ] Stories created
|
|
138
|
+
- [ ] Bolts planned
|
|
139
|
+
- [ ] Review complete
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
### Continue This Intent
|
|
144
|
+
|
|
145
|
+
1 - **Define Context** ← Next step
|
|
146
|
+
2 - Revisit Requirements
|
|
147
|
+
|
|
148
|
+
### Other Actions
|
|
149
|
+
|
|
150
|
+
3 - Create New Intent
|
|
151
|
+
4 - List All Intents
|
|
152
|
+
5 - Return to Main Menu
|
|
153
|
+
|
|
154
|
+
---
|
|
155
|
+
|
|
156
|
+
**Type 1 to continue, or a number for other actions.**
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
---
|
|
160
|
+
|
|
161
|
+
## Output (Inception Complete)
|
|
162
|
+
|
|
163
|
+
```markdown
|
|
164
|
+
## Inception Agent
|
|
165
|
+
|
|
166
|
+
### Intent Complete: `{intent-name}`
|
|
167
|
+
|
|
168
|
+
All inception artifacts have been created:
|
|
169
|
+
|
|
170
|
+
- ✅ Requirements gathered
|
|
171
|
+
- ✅ System context defined
|
|
172
|
+
- ✅ Units decomposed
|
|
173
|
+
- ✅ Stories created
|
|
174
|
+
- ✅ Bolts planned
|
|
175
|
+
- ✅ Review complete
|
|
176
|
+
|
|
177
|
+
### Summary
|
|
178
|
+
- Units defined: {n}
|
|
179
|
+
- Stories created: {n}
|
|
180
|
+
- Bolts planned: {n}
|
|
181
|
+
- Ready for Construction
|
|
182
|
+
|
|
183
|
+
### Next Step
|
|
184
|
+
→ Proceed to Construction: `/specsmd-construction-agent --intent="{intent-name}"`
|
|
185
|
+
|
|
186
|
+
Or create another intent.
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
---
|
|
190
|
+
|
|
191
|
+
## Transition
|
|
192
|
+
|
|
193
|
+
After user selection:
|
|
194
|
+
|
|
195
|
+
- → Load selected skill
|
|
196
|
+
- → Skill contains the Checkpoint markers
|
|
197
|
+
- → Execute skill process
|
|
198
|
+
|
|
199
|
+
---
|
|
200
|
+
|
|
201
|
+
## Test Contract
|
|
202
|
+
|
|
203
|
+
```yaml
|
|
204
|
+
input: Intent state (optional)
|
|
205
|
+
output: Menu with dynamic Option 1 based on state
|
|
206
|
+
checkpoints: 0 (routing only)
|
|
207
|
+
```
|