project-iris 0.5.0 → 0.5.1

package/flows/aidlc/README.md

@@ -127,6 +127,7 @@ src/flows/aidlc/
 **Goal**: Complete planning and design before construction begins
 
 **Activities**:
+
 - Capture intents (high-level goals)
 - Gather requirements (functional and non-functional)
 - Assess risks (technical, business, operational)
@@ -138,6 +139,7 @@ src/flows/aidlc/
 **Command**: `/iris-inception-agent --intent="intent-name"`
 
 **Outputs**:
+
 - PRFAQ document
 - Requirements with measurement criteria
 - Risk assessment
@@ -151,6 +153,7 @@ src/flows/aidlc/
 **Goal**: Build working software through iterative bolt execution
 
 **Activities**:
+
 - Execute bolts through DDD stages:
   1. **Domain Design** - Model business logic using DDD principles
   2. **Logical Design** - Apply NFRs and architectural patterns
@@ -161,6 +164,7 @@ src/flows/aidlc/
 **Command**: `/iris-construction-agent --unit="unit-name"`
 
 **Outputs**:
+
 - Domain design documents
 - Logical design documents
 - Architectural Decision Records (ADRs)
@@ -172,6 +176,7 @@ src/flows/aidlc/
 **Goal**: Deploy and operate the system
 
 **Activities**:
+
 - Build deployment artifacts (containers, functions, bundles)
 - Deploy through environments (Dev → Staging → Production)
 - Verify deployments with health checks
@@ -181,6 +186,7 @@ src/flows/aidlc/
 **Command**: `/iris-operations-agent --unit="unit-name"`
 
 **Outputs**:
+
 - Deployment units
 - Monitoring dashboards
 - Alert configurations
@@ -192,19 +198,24 @@ src/flows/aidlc/
 ## Project Scenarios
 
 ### Greenfield (New Projects)
+
 Starting fresh with no existing code:
+
 1. Initialize project with standards
 2. Begin Inception phase immediately
 3. Build from scratch using AI-DLC methodology
 
 ### Brownfield (Existing Codebases)
+
 Adding features to existing code:
+
 1. Initialize project with standards
 2. **Run code elevation** to analyze existing codebase
 3. AI creates static and dynamic models for context
 4. Begin Inception with full codebase understanding
 
 **Code Elevation Process**:
+
 - **Static Model**: Components, responsibilities, and relationships
 - **Dynamic Model**: How components interact for significant use cases
 
@@ -227,6 +238,7 @@ Intent (feature/capability)
 **Bolts** are time-boxed execution sessions scoped to a **Unit**. A Unit may require multiple Bolts to complete all its Stories.
 
 **Example**:
+
 - **Intent**: User Authentication
   - **Unit**: Auth Service
     - **Story 1**: User Registration
@@ -385,21 +397,27 @@ memory-bank/
 ## Key Principles
 
 ### 1. AI Drives, Human Validates
+
 AI proposes plans, decompositions, and implementations. Humans review and approve at checkpoints.
 
 ### 2. Human Oversight as Loss Function
+
 Validation at each step catches errors early before they cascade downstream.
 
 ### 3. Mob Elaboration
+
 Concentrated rapid planning during Inception. Complete all planning in hours, not weeks.
 
 ### 4. Bolts are Flexible
+
 Bolts take "hours or days" depending on complexity - not fixed-duration like sprints.
 
 ### 5. DDD Focus
+
 Domain-Driven Design principles guide the Construction phase with proper separation of concerns.
 
 ### 6. Persistent Context
+
 Everything is stored in the memory bank so context is never lost between sessions.
 
 ---
@@ -457,18 +475,21 @@ Here's a complete workflow for building a feature:
 ## Tips for Success
 
 ### Planning (Inception)
+
 - Be thorough - it pays off during Construction
 - Document NFRs with measurable criteria
 - Assess risks early with mitigations
 - Group related stories into the same bolt
 
 ### Building (Construction)
+
 - Follow the DDD stages in order
 - Don't skip testing
 - Keep bolts focused (5-8 stories max)
 - Document significant decisions as ADRs
 
 ### Deploying (Operations)
+
 - Always deploy to staging first
 - Run smoke tests after every deployment
 - Setup monitoring from the start

package/flows/aidlc/agents/README.md

@@ -15,9 +15,11 @@ agents/
 ## Agent Overview
 
 ### Master Agent
+
 **Role**: Orchestrator & Navigator
 
 The central entry point that:
+
 - Initializes new projects with standards
 - Analyzes current project state
 - Routes users to the appropriate phase agent
@@ -31,9 +33,11 @@ The central entry point that:
 ---
 
 ### Inception Agent
+
 **Role**: Planning & Design Specialist
 
 Handles the Inception phase:
+
 - Captures intents (high-level goals)
 - Gathers requirements (functional and non-functional)
 - Identifies risks
@@ -49,9 +53,11 @@ Handles the Inception phase:
 ---
 
 ### Construction Agent
+
 **Role**: Builder & Implementer
 
 Handles the Construction phase:
+
 - Executes bolts through DDD stages
 - Guides domain design
 - Creates logical designs
@@ -64,6 +70,7 @@ Handles the Construction phase:
 **Command**: `/iris-construction-agent --unit="unit-name"`
 
 **DDD Bolt Stages**:
+
 1. Domain Design
 2. Logical Design
 3. ADR Analysis (optional)
@@ -73,9 +80,11 @@ Handles the Construction phase:
 ---
 
 ### Operations Agent
+
 **Role**: DevOps Engineer & Deployment Orchestrator
 
 Handles the Operations phase:
+
 - Builds deployment artifacts
 - Deploys through environments (Dev → Staging → Production)
 - Verifies deployments
@@ -120,22 +129,28 @@ Each agent file follows this structure:
 ## Key Principles
 
 ### 1. Agent Independence
+
 Each agent operates independently but can redirect to other agents when appropriate:
+
 - Master → Inception (when ready to plan)
 - Master → Construction (when ready to build)
 - Inception → Construction (when inception complete)
 - Construction → Operations (when construction complete)
 
 ### 2. Human Validation
+
 All agents implement checkpoints where they pause for human approval before proceeding with significant actions.
 
 ### 3. Context Loading
+
 Agents load context from the memory bank at startup:
+
 - Standards (tech-stack, coding-standards)
 - Current phase state
 - Relevant artifacts
 
 ### 4. Consistent Output
+
 All agents follow the same output formatting rules defined in Mandatory Output Rules.
 
 ## Phase Flow

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

@@ -9,6 +9,7 @@ You are the **Inception Agent** for AI-DLC (AI-Driven Development Life Cycle).
 ### ⛔ CRITICAL: NO ASCII TABLES
 
 **NEVER use ASCII box tables like this - FORBIDDEN:**
+
 ```
 ┌────────┬─────────────────────────────────────┐
 │ Option │            Description              │
@@ -20,6 +21,7 @@ You are the **Inception Agent** for AI-DLC (AI-Driven Development Life Cycle).
 ```
 
 **ALWAYS use numbered list format instead:**
+
 ```
 1 - **Option A** - Some option description
 2 - **Option B** - Another option description
@@ -44,6 +46,7 @@ This applies to ALL questions, options, and choices throughout the entire incept
 When asking clarifying questions with multiple choice options:
 
 **WRONG** - ASCII table:
+
 ```
 ┌────────┬──────────────────────────────────┐
 │ Option │           Description            │
@@ -55,6 +58,7 @@ When asking clarifying questions with multiple choice options:
 ```
 
 **CORRECT** - Numbered list:
+
 ```
 **Content Depth**
 
@@ -66,11 +70,13 @@ When asking clarifying questions with multiple choice options:
 ### Checkpoint Options Format (CRITICAL)
 
 **WRONG** - Open-ended question:
+
 ```
 Do these requirements capture your intent?
 ```
 
 **CORRECT** - Numbered options:
+
 ```
 ### Options
 

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

@@ -99,6 +99,7 @@ No project configuration found. This appears to be a new project.
 ```
 
 **CRITICAL**: When user selects "Initialize project", the `project-init` skill MUST:
+
 1. Ask project type question FIRST (full-stack, backend, frontend, CLI, library)
 2. Then detect/ask scenario (greenfield/brownfield/hybrid)
 3. Save `project.yaml` with BOTH fields before proceeding to standards

package/flows/aidlc/skills/README.md

@@ -83,18 +83,23 @@ Every skill file follows this structure:
 ## Key Principles
 
 ### 1. Mandatory Output Rules
+
 Every skill starts with formatting rules to ensure consistent output:
+
 - Never use ASCII tables (they break at different terminal widths)
 - Always use numbered list format for options
 - Always use status indicators (✅ ⏳ [ ] 🚫)
 
 ### 2. Human Checkpoints
+
 Skills that make significant decisions include checkpoints where the AI pauses for human validation before proceeding.
 
 ### 3. Artifact Creation
+
 Skills that create artifacts reference templates from `../templates/` and follow the schema defined in `../memory-bank.yaml`.
 
 ### 4. Context Loading
+
 Skills load context as defined in `../context-config.yaml` to ensure consistent information access.
 
 ## Adding New Skills

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

@@ -32,10 +32,12 @@
 When referencing bolt files to the user, ALWAYS show the **bolt ID prominently**, not just "bolt.md":
 
 **WRONG**:
+
 - "Working on bolt.md"
 - "Open bolt.md to see details"
 
 **CORRECT**:
+
 - "Working on **001-extension-foundation**"
 - "Open **001-extension-foundation/bolt.md** to see details"
 
@@ -46,6 +48,7 @@ The bolt ID (directory name like `001-extension-foundation`) is the identifier.
 ## Checkpoints
 
 **Checkpoint 1**: Which bolt to work on?
+
 - Wait for: User selection
 
 ---

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

@@ -44,11 +44,13 @@
 When referencing bolt files to the user, ALWAYS show the **bolt ID prominently**, not just "bolt.md":
 
 **WRONG**:
+
 - "Working on bolt.md"
 - "Updating bolt.md status"
 - "Approve changes to bolt.md?"
 
 **CORRECT**:
+
 - "Working on **001-extension-foundation**"
 - "Updating **001-extension-foundation** status"
 - "Approve changes to **001-extension-foundation/bolt.md**?"
@@ -155,6 +157,7 @@ agents:
 **Check if UI design guidance may be relevant:**
 
 Scan the bolt's unit name, story titles, and story descriptions for these signals:
+
 - `screen`, `page`, `view`, `layout`
 - `component`, `widget`, `button`, `form`, `modal`, `dialog`
 - `ui`, `ux`, `frontend`, `presentation`
@@ -300,19 +303,12 @@ For the current stage, follow the bolt type definition:
    - Template used: {yes/no}
 ```
 
-**Common artifacts by bolt type:**
+**Required artifacts are defined by the bolt type definition file.**
 
-| Bolt Type | Stage | Required Artifact |
-|-----------|-------|-------------------|
-| simple-construction | Plan | `implementation-plan.md` |
-| simple-construction | Code Generation | `implementation-walkthrough.md` |
-| simple-construction | Testing | `test-walkthrough.md` |
-| ddd-construction | Domain Design | `ddd-01-domain-design.md` |
-| ddd-construction | Logical Design | `ddd-02-logical-design.md` |
-| ddd-construction | Code Generation | `ddd-04-implementation-walkthrough.md` |
-| ddd-construction | Testing | `ddd-03-test-report.md` |
+Each bolt type specifies its own stages and required artifacts. Refer to:
+`templates/construction/bolt-types/{bolt_type}.md`
 
-**If bolt type specifies an artifact, you MUST create it.**
+**If the bolt type definition specifies an artifact for a stage, you MUST create it.**
 
 ### 7b. Story-by-Story Execution (Code Generation Stages) - HARD GATE
 

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

@@ -7,6 +7,7 @@
 ### ⛔ CRITICAL: NO ASCII TABLES
 
 **NEVER use ASCII box tables like this - FORBIDDEN:**
+
 ```
 ┌────────┬─────────────────────────────────────┐
 │ Option │            Description              │
@@ -16,12 +17,14 @@
 ```
 
 **ALWAYS use numbered list format instead:**
+
 ```
 1 - **Option A** - Some option description
 2 - **Option B** - Another option description
 ```
 
 ### General Rules
+
 - 🚫 **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`
@@ -33,6 +36,7 @@
 - ⚠️ **ALWAYS** show numbered options at checkpoints - NEVER ask "approve?" without options
 
 ### Functional Requirements Rules
+
 - ✅ **ALWAYS** start with user/goal clarification before listing FRs
 - ✅ **ALWAYS** include User Story format: "As a {user}, I want {action} so that {benefit}"
 - ✅ **ALWAYS** include testable Acceptance Criteria (binary pass/fail)
@@ -40,6 +44,7 @@
 - ✅ **ALWAYS** identify dependencies between FRs
 
 ### Non-Functional Requirements Rules
+
 - ✅ **ALWAYS** walk through ALL 5 NFR categories (Performance, Scalability, Security, Reliability, Compliance)
 - ✅ **ALWAYS** ensure NFRs have measurable metrics (not vague)
 - ✅ **ALWAYS** define SLOs for critical requirements

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

@@ -119,6 +119,7 @@ Intent → Requirements → Units → Stories → Bolts
    - [ ] Bolt dependencies respect story dependencies
 
 **Validation Outcome:**
+
 - ✅ = Complete traceability
 - ⚠️ = Partial traceability (gaps identified)
 - ❌ = Broken traceability (must fix before Construction)

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

@@ -5,6 +5,7 @@
 ## Mandatory Output Rules (READ FIRST)
 
 ### General Rules
+
 - 🚫 **NEVER** use ASCII tables for options - they break at different terminal widths
 - ✅ **ALWAYS** use numbered list format: `N - **Option**: Description`
 - ✅ **ALWAYS** use status indicators: ✅ (done) ⏳ (current) [ ] (pending)
@@ -14,6 +15,7 @@
 - 🛑 **STOP** at each checkpoint - wait for user response
 
 ### Risk Register Rules
+
 - ✅ **ALWAYS** categorize risks (Technical, Business, Operational, External, Compliance)
 - ✅ **ALWAYS** use standard impact/likelihood scoring (1-5 scale)
 - ✅ **ALWAYS** calculate risk score (Impact × Likelihood)
@@ -134,6 +136,7 @@ Please answer these questions so I can generate an accurate risk register.
 After user answers, generate risks covering all 5 categories:
 
 **Risk Scoring Matrix:**
+
 - **Impact** (1-5): 1=Negligible, 2=Minor, 3=Moderate, 4=Major, 5=Catastrophic
 - **Likelihood** (1-5): 1=Rare, 2=Unlikely, 3=Possible, 4=Likely, 5=Almost Certain
 - **Risk Score** = Impact × Likelihood
@@ -539,11 +542,13 @@ Requirements
 During Construction and Operations, risks should be reviewed:
 
 ### Construction Phase
+
 - Review technical risks before each Bolt
 - Update risk status as mitigations are implemented
 - Add new risks discovered during development
 
 ### Operations Phase
+
 - Review operational risks before deployment
 - Update external/compliance risks as regulations change
 - Close mitigated risks, add new operational risks

package/flows/aidlc/skills/master/analyze-context.md

@@ -145,7 +145,7 @@ If inconsistencies found, report them:
   Current: `draft` → Expected: `complete`
   Reason: All bolts complete
 
-- **requirements: 011-vscode-extension**
+- **requirements: 007-user-auth**
   Current: `units-defined` → Expected: `construction`
   Reason: Has in-progress units
 
@@ -192,9 +192,9 @@ Append entry to `memory-bank/maintenance-log.md` (create if doesn't exist):
 
 | Artifact | Old Status | New Status | Reason |
 |----------|------------|------------|--------|
-| 011-vscode-extension/units/file-watcher/unit-brief.md | draft | complete | All bolts complete (1/1) |
-| 011-vscode-extension/units/extension-core/unit-brief.md | draft | complete | All bolts complete (1/1) |
-| 011-vscode-extension/requirements.md | units-defined | construction | Has in-progress units |
+| 007-user-auth/units/login-service/unit-brief.md | draft | complete | All bolts complete (1/1) |
+| 007-user-auth/units/session-manager/unit-brief.md | draft | complete | All bolts complete (1/1) |
+| 007-user-auth/requirements.md | units-defined | construction | Has in-progress units |
 
 ---
 ```

package/flows/aidlc/skills/master/code-elevate.md

@@ -32,6 +32,7 @@
 ## AI-DLC Specification Reference
 
 > **Brown-Field Scenarios:** In the brown-field (existing application) scenarios, the construction phase involves first elevating the codes into a semantic rich modelling representation so that the context to AI becomes concise and accurate. The suggested modelling representations are:
+>
 > - **Static models** (just the domain components, responsibilities and their relationships)
 > - **Dynamic models** (how the components interact to realize the significant use cases)
 
@@ -42,11 +43,13 @@
 This skill is executed by the **Master Agent** after project initialization for brownfield projects.
 
 **When triggered:**
+
 - After `project-init` completes with `scenario: brownfield`
 - When returning user has brownfield project without elevation
 - Master offers: "Run code elevation to analyze existing code?"
 
 **Why project-level (not intent-level):**
+
 - Codebase structure is project-wide, not per-intent
 - Elevation done once, reused by all intents
 - Avoids redundant analysis for each feature
@@ -210,6 +213,7 @@ Proceed with analysis?
 - **Framework**: {detected framework}
 - **Database**: {detected DB client/ORM}
 - **External APIs**: {detected integrations}
+
 ```
 
 **Checkpoint 1**: Present static model for validation.
@@ -277,17 +281,20 @@ Does this static model accurately represent your codebase?
 ```
 
 **Step-by-Step**:
+
 1. {Step 1}: {Component A} receives {input} from {source}
 2. {Step 2}: {Component A} calls {Component B}.{method}({params})
 3. {Step 3}: {Component B} queries {Component C} for {data}
 4. {Step 4}: {Response} returned to {originator}
 
 **Data Flow**:
+
 - Input: {data structure}
 - Output: {data structure}
 - Side Effects: {external changes, events emitted}
 
 #### Use Case 2: {Name}
+
 ...
 
 ### Integration Points
@@ -303,6 +310,7 @@ Does this static model accurately represent your codebase?
 - **Happy Path**: {primary success scenario}
 - **Error Handling**: {how errors propagate}
 - **Authentication Flow**: {if applicable}
+
 ```
 
 **Checkpoint 2**: Present dynamic model for validation.
@@ -388,11 +396,13 @@ memory-bank/elevation/
 ### Usage by Other Agents
 
 **Inception Agent**:
+
 - Loads elevation models when creating intents
 - Uses component list to suggest unit decomposition
 - References existing patterns in requirements
 
 **Construction Agent**:
+
 - Loads elevation models during bolt execution
 - References static model during Domain Design stage
 - References dynamic model during Logical Design stage

package/flows/aidlc/skills/master/project-init.md

@@ -191,7 +191,7 @@ This file MUST be created before proceeding to standards facilitation, as other
 
 **Add AI-DLC tooling entries to `.gitignore`** to keep the product repository clean.
 
-#### If `.gitignore` exists:
+#### If `.gitignore` exists
 
 Check if entries already exist. If not, append:
 
@@ -202,7 +202,7 @@ Check if entries already exist. If not, append:
 .claude/
 ```
 
-#### If `.gitignore` doesn't exist:
+#### If `.gitignore` doesn't exist
 
 Create it with:
 

package/flows/aidlc/skills/operations/build.md

@@ -130,11 +130,13 @@ Create or update `memory-bank/operations/deployment-units/{unit-name}.md` using
 2. **If exists**: Update the Packaged Artifacts and Deployment History sections
 
 **Required sections to populate:**
+
 - Packaged Artifacts (executable code, registry location)
 - Version and status
 - Build timestamp
 
 **Sections populated by other skills:**
+
 - Test Validation → populated by `verify` skill
 - Deployment History → updated by `deploy` skill
 - Monitoring Integration → populated by `monitor` skill

package/flows/aidlc/skills/operations/rollback.md

@@ -213,6 +213,7 @@ Rollback from {from-version} to {to-version} in {env}
 ### Emergency Contacts
 
 {From project configuration or runbooks}
+
 ```
 
 ---

package/flows/aidlc/templates/README.md

@@ -53,16 +53,20 @@ templates/
 ## Template Usage
 
 ### Inception Templates
+
 Used by Inception Agent skills to create planning artifacts:
+
 - **requirements-template.md**: Captures functional and non-functional requirements
 - **prfaq-template.md**: Documents business intent and expected benefits
 - **risks-template.md**: Identifies and assesses project risks
 - **unit-brief-template.md**: Defines scope and details for each unit
 
 ### Construction Templates
+
 Used by Construction Agent during bolt execution:
 
 **Bolt Types** define the stages and checkpoints for different types of work:
+
 - **ddd-construction-bolt.md**: For complex business logic (5 stages)
   1. Domain Design
   2. Logical Design
@@ -78,16 +82,21 @@ Used by Construction Agent during bolt execution:
 - **spike-bolt.md**: For research and exploration
 
 **Stage Templates** (in `bolt-types/ddd-construction-bolt/`):
+
 - **ddd-01-domain-design-template.md**: Entities, value objects, aggregates
 - **ddd-02-logical-design-template.md**: APIs, schemas, cloud resources
 - **ddd-03-test-report-template.md**: Test results and coverage
 
 ### Operations Templates
+
 Used by Operations Agent for deployment:
+
 - **deployment-unit-template.md**: Documents deployment artifacts, configurations, and infrastructure
 
 ### Standards Templates
+
 Used by Master Agent during project initialization:
+
 - Facilitation guides help agents gather project standards through conversation
 - Standards are saved to `memory-bank/standards/`