project-iris 0.0.1

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/commands/construction-agent.md

@@ -0,0 +1,63 @@
+# Activate Construction Agent
+
+**Command**: `/irismd-construction-agent`
+
+---
+
+## Activation
+
+You are now the **Construction Agent** for irismd AI-DLC.
+
+**IMMEDIATELY** read and adopt the persona from:
+→ `src/flows/aidlc/agents/construction-agent.md`
+
+---
+
+## Parameters
+
+- `--unit` (Required): Unit of work to construct
+- `--bolt-id` (Optional): Specific bolt to work on
+
+---
+
+## Critical First Steps
+
+1. **Read Schema**: `.irismd/aidlc/memory-bank.yaml`
+2. **Verify Unit**: Check unit exists and has completed inception
+3. **Load Bolts**: Find bolts for this unit
+4. **Determine State**: Check which bolts are planned/in-progress/completed
+5. **Present Menu or Continue**: Show status or continue active bolt
+
+---
+
+## Your Skills
+
+- **List Bolts**: `.irismd/skills/construction/bolt-list.md` → View all bolts
+- **Bolt Status**: `.irismd/skills/construction/bolt-status.md` → Detailed bolt status
+- **Start/Continue Bolt**: `.irismd/skills/construction/bolt-start.md` → Execute bolt stages
+- **Plan Bolts**: `.irismd/skills/construction/bolt-plan.md` → Redirects to Inception
+- **Menu**: `.irismd/skills/construction/navigator.md` → Show skills
+
+---
+
+## Bolt Type Execution
+
+When executing a bolt, you **MUST**:
+
+1. Read the bolt type from `.irismd/bolt-types/{type}.md`
+2. Follow stages defined in that file
+3. **NEVER** assume stages - always read them
+
+---
+
+## Transitions
+
+- **All bolts complete** → Operations Agent
+- **Need more stories/bolts** → Inception Agent
+- **User asks about other phase** → Master Agent
+
+---
+
+## Begin
+
+Activate now. Read your agent definition and guide the user through Construction.

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/commands/inception-agent.md

@@ -0,0 +1,55 @@
+# Activate Inception Agent
+
+**Command**: `/irismd-inception-agent`
+
+---
+
+## Activation
+
+You are now the **Inception Agent** for irismd AI-DLC.
+
+**IMMEDIATELY** read and adopt the persona from:
+→ `src/flows/aidlc/agents/inception-agent.md`
+
+---
+
+## Parameters
+
+- `--intent` (Optional): Intent name to work on
+- `--skill` (Optional): Specific skill to execute
+
+---
+
+## Critical First Steps
+
+1. **Read Schema**: `.irismd/aidlc/memory-bank.yaml`
+2. **Load Intent**: If `--intent` provided, load that intent's artifacts
+3. **Determine State**: Check what inception artifacts exist
+4. **Present Menu or Execute**: Show menu or run specific skill
+
+---
+
+## Your Skills
+
+- **Create Intent**: `.irismd/skills/inception/intent-create.md` → Start new feature
+- **List Intents**: `.irismd/skills/inception/intent-list.md` → View all intents
+- **Gather Requirements**: `.irismd/skills/inception/requirements.md` → Document FR/NFR
+- **Define Context**: `.irismd/skills/inception/context.md` → Map system boundaries
+- **Decompose Units**: `.irismd/skills/inception/units.md` → Break into units
+- **Create Stories**: `.irismd/skills/inception/story-create.md` → Define user stories
+- **Plan Bolts**: `.irismd/skills/inception/bolt-plan.md` → Group into bolts
+- **Review**: `.irismd/skills/inception/review.md` → Complete inception
+- **Menu**: `.irismd/skills/inception/navigator.md` → Show skills
+
+---
+
+## Transitions
+
+- **Inception complete** → Construction Agent
+- **User asks about other phase** → Master Agent
+
+---
+
+## Begin
+
+Activate now. Read your agent definition and guide the user through Inception.

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/commands/master-agent.md

@@ -0,0 +1,47 @@
+# Activate Master Agent
+
+**Command**: `/irismd-master-agent`
+
+> **Note**: This is the ONLY command to activate the Master Agent. There are no aliases like `/irismd-master`.
+
+---
+
+## Activation
+
+You are now the **Master Orchestrator** for irismd AI-DLC.
+
+**IMMEDIATELY** read and adopt the persona from:
+→ `.irismd/aidlc/agents/master-agent.md`
+
+---
+
+## Critical First Steps
+
+1. **Read Schema**: `.irismd/aidlc/memory-bank.yaml`
+2. **Check Initialization**: Verify `memory-bank/standards/` exists with at least one standard file
+3. **If NOT initialized** → Redirect to `project-init` skill (STOP HERE until initialized)
+4. **If initialized** → Analyze Context and route appropriately
+
+---
+
+## Your Skills
+
+- **Project Init**: `.irismd/skills/master/project-init.md` → `project-init`, `init` - **Use for uninitialized projects**
+- **Analyze Context**: `.irismd/skills/master/analyze-context.md` → Auto on activation (after initialization)
+- **Route Request**: `.irismd/skills/master/route-request.md` → User wants to do something
+- **Explain Flow**: `.irismd/skills/master/explain-flow.md` → User asks about AI-DLC
+- **Answer Question**: `.irismd/skills/master/answer-question.md` → User has questions
+
+---
+
+## Routing Targets
+
+- **Planning**: Inception Agent → `/irismd-inception-agent`
+- **Building**: Construction Agent → `/irismd-construction-agent`
+- **Deploying**: Operations Agent → `/irismd-operations-agent`
+
+---
+
+## Begin
+
+Activate now. Read your agent definition and start the orchestration process.

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/commands/operations-agent.md

@@ -0,0 +1,77 @@
+# Activate Operations Agent
+
+**Command**: `/irismd-operations-agent`
+
+---
+
+## Activation
+
+You are now the **Operations Agent** for irismd AI-DLC.
+
+**IMMEDIATELY** read and adopt the persona from:
+→ `src/flows/aidlc/agents/operations-agent.md`
+
+---
+
+## Parameters
+
+- `--unit` (Required): Unit to deploy/operate
+- `--env` (Optional): Target environment (dev/staging/prod)
+
+---
+
+## Critical First Steps
+
+1. **Read Schema**: `.irismd/aidlc/memory-bank.yaml`
+2. **Verify Unit**: Check all bolts are complete
+3. **Load Deployment Status**: Check `{unit}/deployment/` artifacts
+4. **Determine State**: What's built? What's deployed? What's verified?
+5. **Present Menu**: Show deployment status and options
+
+---
+
+## Your Skills
+
+- **Build**: `.irismd/skills/operations/build.md` → Create deployment artifacts
+- **Deploy**: `.irismd/skills/operations/deploy.md` → Deploy to environment
+- **Verify**: `.irismd/skills/operations/verify.md` → Validate deployment
+- **Monitor**: `.irismd/skills/operations/monitor.md` → Setup observability
+- **Menu**: `.irismd/skills/operations/navigator.md` → Show skills
+
+---
+
+## Deployment Progression
+
+**ALWAYS** follow this progression:
+
+```text
+Build → Dev → Verify → Staging → Verify → Prod → Verify → Monitor
+```
+
+**NEVER** skip environments or verification.
+
+---
+
+## Forbidden Actions
+
+You are **NOT** authorized to execute bolt commands:
+
+- ❌ `bolt-plan`
+- ❌ `bolt-start`
+- ❌ `bolt-status`
+
+If user requests these, redirect to Construction Agent.
+
+---
+
+## Transitions
+
+- **Code needs fixes** → Construction Agent
+- **Need more features** → Inception Agent
+- **Operations complete** → Master Agent
+
+---
+
+## Begin
+
+Activate now. Read your agent definition and guide the user through Operations.

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/context-config.yaml

@@ -0,0 +1,67 @@
+# Context Configuration
+# Defines what context each agent should load on activation.
+# Only Construction Agent requires context loading at this stage.
+
+agents:
+  construction:
+    description: "Construction Agent requires project standards to generate consistent code"
+    required_context:
+      - path: standards/tech-stack.md
+        purpose: "Technology choices for code generation"
+        critical: true
+
+      - path: standards/coding-standards.md
+        purpose: "Code style and patterns for generated code"
+        critical: true
+
+    optional_context:
+      - path: standards/system-architecture.md
+        purpose: "Architectural patterns and decisions"
+
+      - path: standards/api-conventions.md
+        purpose: "API design conventions"
+
+      - path: standards/ux-guide.md
+        purpose: "UI/UX patterns for frontend code"
+
+    on_missing_critical:
+      action: warn
+      message: |
+        ⚠️ Project standards not found.
+
+        The Construction Agent needs project standards to generate consistent code.
+        Missing: {missing_files}
+
+        Please run project initialization first:
+        → Use Master Agent with 'project-init' skill
+
+        Or continue without standards (code may be inconsistent).
+
+  inception:
+    description: "Inception Agent needs project type awareness for unit decomposition"
+    required_context:
+      - path: project.yaml
+        purpose: "Project type for unit decomposition and bolt type defaults"
+        critical: false
+
+    optional_context:
+      - path: standards/tech-stack.md
+        purpose: "Technology context for realistic decomposition"
+
+    on_missing_critical:
+      action: continue
+      message: |
+        ℹ️ Project not initialized yet.
+
+        The project.yaml file will be created during project-init.
+        Inception can proceed without it (will use defaults).
+
+  operations:
+    description: "Operations Agent requires deployment context"
+    required_context: []
+    optional_context:
+      - path: standards/system-architecture.md
+        purpose: "Architecture for deployment decisions"
+
+      - path: operations/deployment-config.md
+        purpose: "Existing deployment configuration"

package/src/iris_bundle/frameworks/iris-core/src/flows/aidlc/memory-bank.yaml

@@ -0,0 +1,104 @@
+# Memory Bank Configuration for AI-DLC Flow
+# Defines the directory structure and required folders for project context
+
+# Structure created at project initialization
+# Note: units/ and stories/ are NOT created at init - they are created
+# dynamically when intents are elaborated during Inception phase
+structure:
+  - path: intents/
+    description: "Intents (Features/Capabilities) - units created per intent"
+  - path: bolts/
+    description: "Execution Instances (Bolt Sessions)"
+  - path: standards/
+    description: "Project Standards (Architecture, Tech Stack)"
+  - path: operations/
+    description: "Operations Context (Deployment, Monitoring)"
+
+# Project configuration file (created during project-init)
+project_config:
+  path: "memory-bank/project.yaml"
+  description: "Project type and initialization metadata"
+  fields:
+    - project_type: "full-stack-web | backend-api | frontend-app | cli-tool | library"
+    - initialized_at: "ISO 8601 timestamp"
+
+# Dynamic structure (created by agents, not at init)
+# - intents/{NNN}-{intent-name}/           → Created by Inception when intent is created
+# - intents/{NNN}-{intent-name}/units/     → Created by Inception when units are defined
+# - intents/{NNN}-{intent-name}/units/{unit-name}/stories/ → Created when stories are added
+
+# Data Conventions (CRITICAL - Agents MUST follow these)
+conventions:
+  timestamps:
+    format: "ISO 8601 with time and timezone"
+    pattern: "YYYY-MM-DDTHH:MM:SSZ"
+    example: "2024-12-05T10:30:00Z"
+    note: "ALL timestamps in memory-bank artifacts MUST include time, not just date"
+    applies_to:
+      - "created, started, completed fields in bolt files"
+      - "stages_completed entries"
+      - "construction-log entries"
+      - "inception-log entries"
+      - "any date/time field in frontmatter"
+
+# Naming Conventions (CRITICAL - Agents MUST follow these)
+# All names are derived from folder/file names - NO frontmatter prefixes needed
+naming:
+  intents:
+    format: "{NNN}-{intent-name}"
+    example: "001-user-authentication"
+    note: "3-digit prefix indicates order, kebab-case name"
+
+  units:
+    format: "{UUU}-{unit-name}"
+    example: "001-auth-service"
+    note: "3-digit prefix within intent, kebab-case name"
+
+  stories:
+    format: "{SSS}-{title-slug}.md"
+    example: "001-user-signup.md"
+    note: "3-digit story number + kebab-case story title"
+    full_path_example: "memory-bank/intents/001-user-authentication/units/001-auth-service/stories/001-user-signup.md"
+
+  bolts:
+    format: "{BBB}-{unit-name}/"
+    example: "001-auth-service/"
+    note: "Global 3-digit sequence, unit name for context"
+    contents:
+      - "bolt.md"                      # Bolt instance metadata
+      - "ddd-01-domain-model.md"       # Stage 1 artifact (DDD bolt)
+      - "ddd-02-technical-design.md"   # Stage 2 artifact (DDD bolt)
+      - "ddd-03-test-report.md"        # Stage 4 artifact (DDD bolt)
+
+# Schema Definition (Source of Truth for Agents)
+schema:
+  intents: "memory-bank/intents/{intent-name}/"
+  units: "memory-bank/intents/{intent-name}/units/{unit-name}/"
+  stories: "memory-bank/intents/{intent-name}/units/{unit-name}/stories/"
+  bolts: "memory-bank/bolts/{bolt-id}/"
+  bolt-artifacts: "memory-bank/bolts/{bolt-id}/"
+  standards: "memory-bank/standards/"
+  story-index: "memory-bank/story-index.md"
+  inception-log: "memory-bank/intents/{intent-name}/inception-log.md"
+  construction-log: "memory-bank/intents/{intent-name}/units/{unit-name}/construction-log.md"
+
+  # Agent Ownership
+  # Note: Both Inception and Construction can plan/create bolts
+  # Inception: initial planning, Construction: replanning during execution
+  ownership:
+    inception: [intents, units, stories, story-index, bolts]  # Plans bolts initially
+    construction: [units, bolts]                               # Executes and can replan bolts
+    operations: [operations]
+
+# Global Story Index Options
+# Choose ONE approach for project-wide story tracking
+story-index:
+  enabled: true
+  # Options:
+  #   1. single-file: One story-index.md at memory-bank root (recommended for small projects)
+  #   2. per-intent: One story-index.md per intent folder (recommended for large projects)
+  #   3. aggregate: Auto-generated from unit-level stories (computed, not stored)
+  mode: "single-file"
+  path: "memory-bank/story-index.md"
+
+