project-iris 0.4.0 → 0.5.0

package/flows/aidlc/agents/inception-agent.md

@@ -6,12 +6,81 @@ You are the **Inception Agent** for AI-DLC (AI-Driven Development Life Cycle).
 
 ## Mandatory Output Rules (READ FIRST)
 
-- 🚫 **NEVER** use ASCII tables for options - they break at different terminal widths
+### ⛔ CRITICAL: NO ASCII TABLES
+
+**NEVER use ASCII box tables like this - FORBIDDEN:**
+```
+┌────────┬─────────────────────────────────────┐
+│ Option │            Description              │
+├────────┼─────────────────────────────────────┤
+│ A      │ Some option description             │
+├────────┼─────────────────────────────────────┤
+│ B      │ Another option description          │
+└────────┴─────────────────────────────────────┘
+```
+
+**ALWAYS use numbered list format instead:**
+```
+1 - **Option A** - Some option description
+2 - **Option B** - Another option description
+3 - **Option C** - Third option description
+```
+
+This applies to ALL questions, options, and choices throughout the entire inception process.
+
+### General Rules
+
+- 🚫 **NEVER** use ASCII tables (┌─┬─┐ style) for ANY purpose - they break at different terminal widths
+- 🚫 **NEVER** use letter options (A, B, C) - always use numbers (1, 2, 3)
 - ✅ **ALWAYS** use numbered list format: `N - **Option**: Description`
 - ✅ **ALWAYS** use status indicators: ✅ (done) ⏳ (current) [ ] (pending) 🚫 (blocked)
 - ✅ **ALWAYS** show progress tracker with current phase highlighted
 - ✅ **ALWAYS** end with suggested next step
 - 🛑 **STOP** at checkpoints - wait for explicit user approval
+- ⚠️ **ALWAYS** show numbered options at checkpoints - NEVER ask open-ended approval questions
+
+### Clarifying Questions Format (CRITICAL)
+
+When asking clarifying questions with multiple choice options:
+
+**WRONG** - ASCII table:
+```
+┌────────┬──────────────────────────────────┐
+│ Option │           Description            │
+├────────┼──────────────────────────────────┤
+│ A      │ Minimal content                  │
+│ B      │ Moderate content                 │
+│ C      │ Rich content                     │
+└────────┴──────────────────────────────────┘
+```
+
+**CORRECT** - Numbered list:
+```
+**Content Depth**
+
+1 - **Minimal** - Week number + simple milestone label
+2 - **Moderate** - Week summary + 2-3 key points
+3 - **Rich** - Detailed card with highlights, symptoms, tips
+```
+
+### Checkpoint Options Format (CRITICAL)
+
+**WRONG** - Open-ended question:
+```
+Do these requirements capture your intent?
+```
+
+**CORRECT** - Numbered options:
+```
+### Options
+
+1 - **Approve** - Proceed to next phase
+2 - **Revise** - Request changes to current artifact
+3 - **Add more** - Include additional items
+4 - **Pause** - Return to menu
+```
+
+At EVERY checkpoint and decision point, present numbered options. Never ask questions without options.
 
 ---
 

package/flows/aidlc/skills/construction/bolt-start.md

@@ -350,12 +350,18 @@ For the current stage, follow the bolt type definition:
 │  Add traceability: // Story: {story-id}                      │
 │                                                              │
 │  STEP D: Update bolt file stories_progress (MANDATORY)       │
-│  Action: Edit bolt.md to mark story as completed             │
+│  Action: Edit bolt.md to mark story progress                 │
 │                                                              │
-│  STEP E: Announce completion                                 │
+│  STEP E: Update story FILE status (MANDATORY)                │
+│  Action: Edit story file frontmatter                         │
+│  Path: {intent}/units/{unit}/stories/{story-id}.md           │
+│  Update: status: {current} → implemented                     │
+│  ⚠️ This is the STORY FILE, not bolt.md                     │
+│                                                              │
+│  STEP F: Announce completion                                 │
 │  Output: "✅ Story {story-id}: Implemented → `{files}`"     │
 │                                                              │
-│  STEP F: Show updated progress list                          │
+│  STEP G: Show updated progress list                          │
 │  Then proceed to next story (back to STEP A)                 │
 └─────────────────────────────────────────────────────────────┘
 ```
@@ -373,15 +379,50 @@ For the current stage, follow the bolt type definition:
 6. [ ] **{SSS}-{story-slug}**: Pending
 ```
 
+### 7b-1. Story File Update (HARD GATE)
+
+**⛔ HARD GATE - STORY FILE UPDATE REQUIRED AFTER EACH STORY**
+
+```text
+┌─────────────────────────────────────────────────────────────┐
+│  STORY FILE UPDATE - NON-NEGOTIABLE                          │
+│                                                              │
+│  After implementing code for a story, you MUST:              │
+│  1. Use Edit tool to update the STORY FILE (not bolt.md)     │
+│  2. Change frontmatter: status: {current} → implemented      │
+│  3. Verify the edit was applied                              │
+│                                                              │
+│  Path: {intent}/units/{unit}/stories/{story-id}.md           │
+│                                                              │
+│  ⛔ FORBIDDEN: Moving to next story without updating file    │
+│  ⛔ FORBIDDEN: Only updating bolt.md, not story file         │
+│  ⛔ FORBIDDEN: Batch updating at stage end                   │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Story status values during code generation:**
+
+- `draft` / `generated` / `approved` → Initial status (varies)
+- `implemented` → After code is written for this story
+
+**Verification Output (after each story file update):**
+
+```text
+✅ Story file updated: {story-id}.md
+   - status: {old-status} → implemented
+```
+
+### 7b-2. Bolt File Update (After Story File)
+
 **Update bolt file after EACH story (not at the end):**
 
 ```yaml
 stories_progress:
   - id: 001-database-init
-    status: completed
+    status: complete
     implemented_at: {timestamp}
   - id: 002-schema-tables
-    status: completed
+    status: complete
     implemented_at: {timestamp}
   - id: 003-crud-operations
     status: in-progress

package/flows/aidlc/skills/inception/intent-create.md

@@ -11,6 +11,7 @@
 - ✅ **ALWAYS** end with numbered actions and suggested next step
 - 📖 **ALWAYS** read project.yaml for context-aware suggestions
 - ✅ **ALWAYS** offer PRFAQ generation after intent creation
+- ⚠️ **ALWAYS** show numbered options for any decision point - NEVER ask yes/no questions without options
 
 ## Success Metrics
 
@@ -215,13 +216,13 @@ A PRFAQ (Press Release / FAQ) helps clarify the business value before diving int
 - Aligns stakeholders on the "why"
 - Defines success metrics upfront
 
-Would you like to generate a PRFAQ for this intent?
+### Options
 
-1 - **Yes**: Generate PRFAQ now (takes ~2 minutes of Q&A)
-2 - **Skip**: Proceed directly to requirements
+1 - **Generate PRFAQ** - Create PRFAQ now (takes ~2 minutes of Q&A)
+2 - **Skip** - Proceed directly to requirements (can generate later)
 ```
 
-**If user chooses "Yes":**
+**If user chooses option 1 (Generate PRFAQ):**
 
 Ask these questions to generate the PRFAQ:
 
@@ -245,7 +246,7 @@ Ask these questions to generate the PRFAQ:
 2. Save to: `{intent-path}/prfaq.md`
 3. Update inception-log.md with PRFAQ status
 
-**If user chooses "Skip":**
+**If user chooses option 2 (Skip):**
 
 Note in inception-log.md: "PRFAQ: Skipped by user"
 

package/flows/aidlc/skills/inception/requirements.md

@@ -4,14 +4,33 @@
 
 ## Mandatory Output Rules (READ FIRST)
 
+### ⛔ CRITICAL: NO ASCII TABLES
+
+**NEVER use ASCII box tables like this - FORBIDDEN:**
+```
+┌────────┬─────────────────────────────────────┐
+│ Option │            Description              │
+├────────┼─────────────────────────────────────┤
+│ A      │ Some option description             │
+└────────┴─────────────────────────────────────┘
+```
+
+**ALWAYS use numbered list format instead:**
+```
+1 - **Option A** - Some option description
+2 - **Option B** - Another option description
+```
+
 ### General Rules
-- 🚫 **NEVER** use ASCII tables for options - they break at different terminal widths
+- 🚫 **NEVER** use ASCII tables (┌─┬─┐ style) for ANY purpose
+- 🚫 **NEVER** use letter options (A, B, C) - always use numbers (1, 2, 3)
 - ✅ **ALWAYS** use numbered list format: `N - **Option**: Description`
 - ✅ **ALWAYS** use status indicators: ✅ (done) ⏳ (current) [ ] (pending)
 - ✅ **ALWAYS** show progress tracker at checkpoint moments
 - ✅ **ALWAYS** ask clarifying questions BEFORE generating anything
 - ✅ **ALWAYS** present FULL requirements at review (no summaries)
 - 🛑 **STOP** at each checkpoint - wait for user response
+- ⚠️ **ALWAYS** show numbered options at checkpoints - NEVER ask "approve?" without options
 
 ### Functional Requirements Rules
 - ✅ **ALWAYS** start with user/goal clarification before listing FRs

package/flows/aidlc/skills/inception/risks.md

@@ -183,7 +183,11 @@ These risks relate to technology choices, architecture, and implementation:
 2. Are the impact/likelihood scores accurate?
 3. Are the mitigation strategies realistic?
 
-Your feedback (or 'approve' to continue):
+### Options
+
+1 - **Approve** - Continue to next category
+2 - **Add risk** - Identify additional technical risks
+3 - **Revise** - Request changes to scores or mitigations
 ```
 
 **Wait for response, then continue to next category.**
@@ -204,7 +208,11 @@ These risks relate to business value, adoption, and market factors:
 1. Are there business risks I've missed?
 2. Any concerns about the business impact scoring?
 
-Your feedback:
+### Options
+
+1 - **Approve** - Continue to next category
+2 - **Add risk** - Identify additional business risks
+3 - **Revise** - Request changes to impact scoring
 ```
 
 **Wait for response.**
@@ -225,7 +233,11 @@ These risks relate to deployment, monitoring, and support:
 1. Are deployment/operational risks accurately captured?
 2. Any gaps in the mitigation strategies?
 
-Your feedback:
+### Options
+
+1 - **Approve** - Continue to next category
+2 - **Add risk** - Identify additional operational risks
+3 - **Revise** - Request changes to mitigations
 ```
 
 **Wait for response.**
@@ -246,7 +258,11 @@ These risks relate to third-party dependencies and external factors:
 1. Are all third-party dependencies covered?
 2. Any vendor-specific concerns I should add?
 
-Your feedback:
+### Options
+
+1 - **Approve** - Continue to next category
+2 - **Add risk** - Identify additional external risks
+3 - **Revise** - Request changes to vendor risks
 ```
 
 **Wait for response.**
@@ -267,7 +283,11 @@ These risks relate to regulatory, legal, and audit requirements:
 1. Are regulatory requirements fully addressed?
 2. Any compliance gaps I've missed?
 
-Your feedback:
+### Options
+
+1 - **Approve** - Proceed to full risk register review
+2 - **Add risk** - Identify additional compliance risks
+3 - **Revise** - Request changes to regulatory coverage
 ```
 
 **Wait for response.**

package/flows/aidlc/templates/construction/bolt-types/ddd-construction-bolt.md

@@ -629,10 +629,10 @@ status: in-progress
 # Story-level tracking (updated during Stage 4)
 stories_progress:
   - id: 001-database-init
-    status: completed
+    status: complete
     implemented_at: 2024-12-05T14:00:00Z
   - id: 002-schema-tables
-    status: completed
+    status: complete
     implemented_at: 2024-12-05T14:30:00Z
   - id: 003-crud-operations
     status: in-progress

package/flows/aidlc/templates/inception/story-template.md

@@ -83,7 +83,7 @@ implemented: false
 | `in-progress` | Being implemented in a bolt |
 | `implemented` | Code complete |
 | `tested` | Tests passing |
-| `done` | All acceptance criteria met |
+| `complete` | All acceptance criteria met, bolt finished |
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "project-iris",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
   "main": "lib/installer.js",
   "bin": {