project-iris 0.0.1

package/src/iris_bundle/.iris/tools/cursor/.cursor/commands/iris-master-agent.md

@@ -0,0 +1,25 @@
+# Iris Master Agent
+
+## What this does
+Runs the IRIS **Master** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-master-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-master-agent.md`.

package/src/iris_bundle/.iris/tools/cursor/.cursor/commands/iris-operations-agent.md

@@ -0,0 +1,25 @@
+# Iris Operations Agent
+
+## What this does
+Runs the IRIS **Operations** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-operations-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-operations-agent.md`.

package/src/iris_bundle/.iris/tools/gemini/.gemini/commands/iris-construction-agent.toml

@@ -0,0 +1,29 @@
+name = "iris-construction-agent"
+    description = "Run IRIS Construction agent using .iris/aidlc doctrine"
+    prompt = """
+# Iris Construction Agent
+
+## What this does
+Runs the IRIS **Construction** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-construction-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-construction-agent.md`.
+"""

package/src/iris_bundle/.iris/tools/gemini/.gemini/commands/iris-inception-agent.toml

@@ -0,0 +1,29 @@
+name = "iris-inception-agent"
+    description = "Run IRIS Inception agent using .iris/aidlc doctrine"
+    prompt = """
+# Iris Inception Agent
+
+## What this does
+Runs the IRIS **Inception** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-inception-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-inception-agent.md`.
+"""

package/src/iris_bundle/.iris/tools/gemini/.gemini/commands/iris-master-agent.toml

@@ -0,0 +1,29 @@
+name = "iris-master-agent"
+    description = "Run IRIS Master agent using .iris/aidlc doctrine"
+    prompt = """
+# Iris Master Agent
+
+## What this does
+Runs the IRIS **Master** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-master-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-master-agent.md`.
+"""

package/src/iris_bundle/.iris/tools/gemini/.gemini/commands/iris-operations-agent.toml

@@ -0,0 +1,29 @@
+name = "iris-operations-agent"
+    description = "Run IRIS Operations agent using .iris/aidlc doctrine"
+    prompt = """
+# Iris Operations Agent
+
+## What this does
+Runs the IRIS **Operations** agent using the canonical IRIS doctrine in `.iris/aidlc/`.
+
+## REQUIRED context (load in this order)
+1. `.iris/aidlc/context/load-order.md`
+2. `.iris/aidlc/standards/phases-and-gates.md`
+3. `.iris/aidlc/standards/artifacts-registry.md`
+4. `.iris/aidlc/validation/phase-preconditions.md`
+5. `.iris/aidlc/commands/iris-operations-agent.md`
+6. Repo project signals (if present): `specs.md`, `README.md`, `package.json`, `tsconfig.json`, relevant `src/**`
+7. Phase memory-bank artifacts:
+   - Inception: `memory-bank/intents/**`
+   - Construction: `memory-bank/units/**`, `memory-bank/bolts/**`
+   - Operations: `memory-bank/logs/**`, `memory-bank/standards/**`
+
+## Hard rules
+- MUST create/update artifacts in `memory-bank/` using templates in `.iris/aidlc/templates/`.
+- MUST stop if required artifacts for the phase are missing and ask to create them.
+- MUST keep outputs deterministic: numbered steps, explicit file paths, and acceptance criteria.
+- MUST NOT delete files unless the user explicitly requests it.
+
+## Start
+Execute `.iris/aidlc/commands/iris-operations-agent.md`.
+"""

package/src/iris_bundle/frameworks/iris-core/.claude/claude.md

@@ -0,0 +1,238 @@
+# Claude Instructions for irismd Development
+
+## Primary Directive: Strict AI-DLC Adherence
+
+**Core Principle**: We are implementing AI-DLC as defined by AWS, not creating our own version of it.
+
+---
+
+## 1. **Required Reading Before Any AI-DLC Changes**
+
+When working on AI-DLC flow implementation or documentation, you MUST read these files **IN ORDER**:
+
+### Primary Source (ALWAYS FIRST)
+1. **AI-DLC Specification**
+   - PDF: `/resources/aidlc.pdf` (original AWS specification)
+   - Text: `/resources/ai-dlc-specification.md` (readable version)
+   - This is the authoritative source for AI-DLC concepts
+   - If something is not in the official spec, it's not AI-DLC
+
+### Implementation Files (READ SECOND)
+2. **`/src/flows/aidlc/agents/`** - Agent implementations
+   - Contains: Master, Inception, Construction, Operations agents
+3. **`/src/flows/aidlc/`** - Memory bank configuration and skills
+   - Contains: memory-bank.yaml, context-config.yaml, skills, templates
+
+### Specifications (Reference)
+4. **`/memory-bank/`** - Project specifications
+   - Contains: PRFAQ, glossary, term-mappings, intents, standards
+   - Structure follows AI-DLC: intents → units → stories
+
+---
+
+## 2. **AI-DLC Immutable Principles**
+
+The following are FROM THE PDF and CANNOT be changed:
+
+1. **Three Phases Only**: Inception → Construction → Operations
+2. **Mob Rituals**: Mob Elaboration (Inception), Mob Construction (Construction)
+3. **Bolt Duration**: "hours or days" (flexible, NOT fixed like "1-2 days")
+4. **DDD Integration**: Domain-Driven Design is integral to AI-DLC
+5. **Sequential Phases**: NOT iterative like Agile (phases are sequential, execution within Construction is iterative)
+6. **AI Drives, Human Validates**: AI proposes, humans approve
+
+---
+
+## 3. **Forbidden Actions**
+
+When working on AI-DLC features, you MUST NOT:
+
+- ❌ Invent or modify AI-DLC concepts not in the PDF
+- ❌ Add phases beyond Inception/Construction/Operations
+- ❌ Change "hours or days" to fixed durations (e.g., "1-2 days")
+- ❌ Use terms like "Discovery Bolt" or "Design Bolt" (these don't exist in AI-DLC)
+- ❌ Make AI-DLC iterative like Agile (phases are sequential)
+- ❌ Use verb-noun command patterns (use noun-verb instead)
+- ❌ Duplicate documentation content in this file (point to specs instead)
+- ❌ Invoke Bolt commands (`bolt-plan`, `bolt-start`, etc.) outside of Construction Agent context
+
+---
+
+## 4. **Where to Find Specifications**
+
+Instead of duplicating content here, refer to these files:
+
+| Topic | File Location |
+|-------|---------------|
+| **Term Mappings** | `/memory-bank/term-mappings.md` |
+| **Glossary** | `/memory-bank/glossary.md` |
+| **PRFAQ** | `/memory-bank/PRFAQ.md` |
+| **Standards** | `/memory-bank/standards/` (tech-stack, coding-standards, system-architecture) |
+| **Agent Specs** | `/memory-bank/intents/001-multi-agent-orchestration/units/` |
+| **Memory Bank Specs** | `/memory-bank/intents/003-memory-bank-system/units/` |
+| **Agent Implementation** | `/src/flows/aidlc/agents/` |
+| **Skills** | `/src/flows/aidlc/skills/` (inception, construction) |
+| **Templates** | `/src/flows/aidlc/templates/` |
+| **Memory Bank Config** | `/src/flows/aidlc/memory-bank.yaml` |
+
+---
+
+## 5. **Process for AI-DLC Feature Development**
+
+Follow this process for ANY AI-DLC feature work:
+
+1. **Review existing agent implementations** (`/src/flows/aidlc/agents/`)
+   - Understand established patterns and conventions
+   - Follow existing agent structure (Persona, Critical Actions, Skills, Workflow)
+
+2. **Check specifications** (`/memory-bank/`)
+   - Review glossary and term-mappings for consistent terminology
+   - Check relevant unit-briefs for requirements
+
+3. **Review skills and templates** (`/src/flows/aidlc/`)
+   - Skills define agent capabilities
+   - Templates ensure consistent artifact creation
+
+4. **If uncertain, ask rather than invent**
+   - Don't make assumptions about AI-DLC methodology
+   - Don't "improve" or modify AI-DLC concepts without discussion
+
+---
+
+## 6. **Project Context**
+
+### Company & Branding
+- **Company**: irismd (all lowercase)
+- **Website**: https://iris.md
+- **Project**: irismd (all lowercase)
+- **Primary Focus**: AI-DLC implementation for AI-native engineers
+
+### Key Conventions
+- Command naming: noun-verb pattern (e.g., `bolt-start`, `intent-create`)
+- File structure: See `/memory-bank/` for specifications, `/src/flows/aidlc/` for implementation
+
+---
+
+## 7. **Quick Validation Checklist**
+
+Before implementing any AI-DLC feature, ask:
+
+- ✅ Have I reviewed existing agent implementations in `/src/flows/aidlc/agents/`?
+- ✅ Am I following established patterns (Persona, Critical Actions, Skills, Workflow)?
+- ✅ Am I using noun-verb command pattern?
+- ✅ Am I respecting the 3-phase structure (Inception → Construction → Operations)?
+- ✅ Am I pointing to specs rather than duplicating content?
+- ✅ Have I checked `/memory-bank/glossary.md` for consistent terminology?
+
+---
+
+*These instructions ensure irismd delivers a faithful, world-class AI-DLC implementation.*
+
+---
+
+## 8. **Dogfooding: Using AI-DLC to Build irismd**
+
+irismd is built using its own AI-DLC flows. This section explains the setup.
+
+### Directory Structure
+
+```
+irismd/
+├── .irismd/aidlc/    → symlink to src/flows/aidlc/  (AI-DLC flow definitions)
+├── memory-bank/       → primary artifact storage     (intents, bolts, standards)
+└── .claude/commands/  → slash commands for agents
+```
+
+### Slash Commands Available
+
+| Command | Description |
+|---------|-------------|
+| `/irismd-master-agent` | Start here - orchestrates flow and routes to appropriate agent |
+| `/irismd-inception-agent` | Planning phase - requirements, stories, units, bolt planning |
+| `/irismd-construction-agent` | Building phase - execute bolts through DDD stages |
+| `/irismd-operations-agent` | Deployment phase - build, deploy, verify, monitor |
+
+### How It Works
+
+1. **Flow Source**: The AI-DLC flow is defined in `src/flows/aidlc/` (source)
+2. **Flow Link**: `.irismd/aidlc/` symlinks to the source for agents to read
+3. **Artifacts**: `memory-bank/` is the primary storage for project artifacts
+4. **Commands**: `.claude/commands/` contains slash commands that activate agents
+
+### Starting Development
+
+```text
+/irismd-master-agent
+```
+
+This activates the Master Orchestrator which will:
+1. Check if project is initialized (standards exist)
+2. Analyze current project state
+3. Route you to the appropriate phase/agent
+
+### Key Paths for Agents
+
+| Purpose | Path |
+|---------|------|
+| Agent Definitions | `.irismd/aidlc/agents/` |
+| Skills | `.irismd/aidlc/skills/` |
+| Templates | `.irismd/aidlc/templates/` |
+| Memory Bank Schema | `.irismd/aidlc/memory-bank.yaml` |
+| Standards | `memory-bank/standards/` |
+| Intents | `memory-bank/intents/` |
+| Bolts | `memory-bank/bolts/` |
+
+---
+
+## 9. **Git Commit Messages (Semantic Versioning)**
+
+This project uses **semantic-release** for automatic versioning. Commit messages determine version bumps.
+
+### Required Commit Format
+
+```
+<type>: <description>
+```
+
+### Commit Types and Version Impact
+
+| Type | Version Bump | When to Use |
+|------|--------------|-------------|
+| `feat:` | Minor (0.1.0) | New feature or capability |
+| `fix:` | Patch (0.0.1) | Bug fix |
+| `perf:` | Patch (0.0.1) | Performance improvement |
+| `docs:` | No release | Documentation only |
+| `chore:` | No release | Maintenance, dependencies |
+| `refactor:` | No release | Code refactor, no behavior change |
+| `style:` | No release | Formatting, whitespace |
+| `test:` | No release | Adding or updating tests |
+
+**Note:** Major versions (1.0.0, 2.0.0) are NOT auto-bumped. Update `package.json` manually for major releases.
+
+### Examples
+
+```bash
+# Triggers releases
+feat: add YAML validation support      # → minor bump (0.1.0)
+fix: resolve memory leak in watcher    # → patch bump (0.0.1)
+perf: optimize file parsing            # → patch bump (0.0.1)
+
+# No release triggered
+docs: update README installation steps
+chore: update dependencies
+refactor: simplify parser logic
+test: add unit tests for validator
+```
+
+### Important Rules
+
+- **Always use lowercase** for the type prefix
+- **Use present tense** ("add feature" not "added feature")
+- **Be concise but descriptive** in the description
+- **Major versions** require manual `package.json` update
+
+See `/dev_release_guide.md` for full workflow documentation.
+
+---
+
+*Last updated: 2025-12-25 - Added semantic versioning commit guidelines*

package/src/iris_bundle/frameworks/iris-core/.claude/commands/compare-iris.md

@@ -0,0 +1,203 @@
+# Compare Specs and Implementation
+
+**Command**: `/compare-specs`
+
+Compare specifications in `memory-bank/` with their corresponding implementations in `src/` to identify gaps, inconsistencies, and missing items.
+
+---
+
+## Comparison Modes
+
+Choose a comparison mode based on what you want to analyze:
+
+### Mode 1: Spec → Implementation (Default)
+Find what's documented in specs but missing or inconsistent in implementation.
+- Identifies incomplete implementations
+- Finds mismatches between spec requirements and actual code
+
+### Mode 2: Implementation → Spec
+Find what's implemented but not documented in specs.
+- Identifies undocumented features
+- Finds implementation details that should be in specs
+
+---
+
+## Process
+
+### Step 1: Identify Scope
+
+Ask the user:
+
+> **What would you like to compare?**
+>
+> 1. **Specific agent** (e.g., inception-agent, construction-agent, master-agent)
+> 2. **Specific feature** (e.g., bolt planning, story creation, estimation)
+> 3. **Full system** (compare all specs vs all implementations)
+>
+> **Direction:**
+> - A) Spec → Implementation (find missing implementations)
+> - B) Implementation → Spec (find missing documentation)
+> - C) Both directions
+
+### Step 2: Locate Files
+
+**Spec locations** (`memory-bank/`):
+```
+memory-bank/
+├── intents/
+│   ├── 001-multi-agent-orchestration/
+│   │   └── units/
+│   │       ├── master-agent/unit-brief.md
+│   │       ├── inception-agent/unit-brief.md
+│   │       ├── construction-agent/unit-brief.md
+│   │       └── operations-agent/unit-brief.md
+│   ├── 002-agentic-coding-tool-integration/
+│   └── 003-memory-bank-system/
+├── standards/
+│   ├── coding-standards.md
+│   ├── tech-stack.md
+│   └── system-architecture.md
+├── research/
+│   └── (research documentation)
+├── glossary.md
+└── term-mappings.md
+```
+
+**Implementation locations** (`src/flows/aidlc/`):
+```
+src/flows/aidlc/
+├── agents/
+│   ├── master-agent.md
+│   ├── inception-agent.md
+│   ├── construction-agent.md
+│   └── operations-agent.md
+├── commands/
+├── .irismd/
+│   ├── skills/
+│   │   ├── master/
+│   │   ├── inception/
+│   │   └── construction/
+│   ├── templates/
+│   └── memory-bank.yaml
+```
+
+### Step 3: Compare Content
+
+For each file pair, analyze:
+
+| Aspect | Check |
+|--------|-------|
+| **Terminology** | Same terms used consistently? |
+| **Features** | All spec features implemented? |
+| **Naming conventions** | Match between spec and implementation? |
+| **Estimation guidance** | Consistent across both? |
+| **Dependencies** | All documented dependencies implemented? |
+| **Commands** | All spec commands exist in implementation? |
+| **Skills** | All spec skills have implementations? |
+
+### Step 4: Report Findings
+
+Generate a gap analysis report:
+
+```markdown
+## Gap Analysis Report
+
+### Comparison: {scope}
+- Direction: {Spec → Impl | Impl → Spec | Both}
+- Files analyzed: {count}
+
+---
+
+### Gaps Found
+
+#### Missing in Implementation (Spec → Impl)
+| Spec | Item | Status |
+|------|------|--------|
+| inception-agent/unit-brief.md | Global story index | Not implemented |
+| ... | ... | ... |
+
+#### Missing in Specs (Impl → Spec)
+| Implementation | Item | Status |
+|----------------|------|--------|
+| inception-agent.md | Naming conventions section | Not documented |
+| ... | ... | ... |
+
+#### Inconsistencies
+| Location | Spec Says | Implementation Says |
+|----------|-----------|---------------------|
+| Bolt estimation | Hours only | Uses "1-2 days" |
+| ... | ... | ... |
+
+---
+
+### Recommended Actions
+
+1. **High Priority** (blocking or incorrect):
+   - { action }
+
+2. **Medium Priority** (missing features):
+   - { action }
+
+3. **Low Priority** (documentation polish):
+   - { action }
+
+---
+
+### Update Plan
+
+Based on chosen direction:
+
+**If updating specs:**
+1. { step }
+2. { step }
+
+**If updating implementation:**
+1. { step }
+2. { step }
+```
+
+---
+
+## Example Usage
+
+**User**: `/compare-specs`
+
+**Assistant**:
+> What would you like to compare?
+> 1. Specific agent
+> 2. Specific feature
+> 3. Full system
+>
+> And in which direction?
+> A) Spec → Implementation
+> B) Implementation → Spec
+> C) Both
+
+**User**: `1 - inception-agent, C - both`
+
+**Assistant**: *Reads spec and implementation files, generates gap analysis*
+
+---
+
+## Quick Comparisons
+
+For common comparisons, use these shortcuts:
+
+| Shortcut | Scope |
+|----------|-------|
+| `/compare-specs agents` | All agent specs vs implementations |
+| `/compare-specs skills` | All skill specs vs implementations |
+| `/compare-specs memory-bank` | Memory bank spec vs implementation |
+| `/compare-specs naming` | Naming conventions consistency |
+| `/compare-specs estimation` | Estimation guidance consistency |
+
+---
+
+## Output
+
+After analysis, provide:
+
+1. **Summary**: X gaps found (Y in implementation, Z in specs)
+2. **Gap table**: Detailed list of discrepancies
+3. **Recommended plan**: Steps to resolve gaps
+4. **User choice**: Ask if they want to fix specs, implementation, or both

package/src/iris_bundle/frameworks/iris-core/.claude/commands/irismd-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:
+→ `.irismd/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/aidlc/skills/construction/bolt-list.md` → View all bolts
+- **Bolt Status**: `.irismd/aidlc/skills/construction/bolt-status.md` → Detailed bolt status
+- **Start/Continue Bolt**: `.irismd/aidlc/skills/construction/bolt-start.md` → Execute bolt stages
+- **Replan Bolt**: `.irismd/aidlc/skills/construction/bolt-replan.md` → Modify bolt plan
+- **Menu**: `.irismd/aidlc/skills/construction/navigator.md` → Show skills
+
+---
+
+## Bolt Type Execution
+
+When executing a bolt, you **MUST**:
+
+1. Read the bolt type from `.irismd/aidlc/templates/construction/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.