project-iris 0.0.1

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/002-agentic-coding-tool-integration/units/roo-installer/unit-brief.md

@@ -0,0 +1,107 @@
+# Unit Brief: Roo Code Installer
+
+## Overview
+
+The Roo Code Installer handles installation of irismd agents into Roo Code's `.roo/commands/` directory.
+
+---
+
+## Scope
+
+### In Scope
+
+- Roo Code detection
+- Agent file installation to `.roo/commands/`
+
+### Out of Scope
+
+- Base installation logic (handled by ToolInstaller)
+- Other tool installations
+
+---
+
+## Technical Context
+
+### File Structure
+
+```text
+src/lib/installers/
+└── RooInstaller.js
+```
+
+### Target Installation Path
+
+```text
+project-root/
+└── .roo/
+    └── commands/
+        ├── irismd-master-agent.md
+        ├── irismd-inception-agent.md
+        ├── irismd-construction-agent.md
+        └── irismd-operations-agent.md
+```
+
+---
+
+## Implementation Details
+
+### RooInstaller Class
+
+Extends `ToolInstaller` with standard behavior.
+
+### Properties
+
+| Property | Value | Description |
+|----------|-------|-------------|
+| `key` | `'roo'` | Unique identifier for factory lookup |
+| `name` | `'Roo Code'` | Display name in CLI |
+| `commandsDir` | `'.roo/commands'` | Where to install agent files |
+| `detectPath` | `'.roo'` | Directory to check for detection |
+
+### Detection Logic
+
+Roo Code is detected if `.roo/` directory exists in the project root.
+
+---
+
+## Roo Code Reference
+
+Roo Code is an AI development assistant with multiple specialized modes.
+
+### Key Features
+
+- Multiple AI agent modes (Code, Architect, Debug, etc.)
+- Custom mode creation
+- Project-aware context
+
+### Configuration Locations
+
+| Type | Location |
+|------|----------|
+| Commands | `.roo/commands/` |
+| Custom modes | `.roomodes` |
+| Rules | `.roorules` |
+
+---
+
+## Acceptance Criteria
+
+### AC-1: Detection
+
+- GIVEN a project with `.roo/` directory
+- WHEN detectTools() runs
+- THEN Roo Code is listed as detected
+
+### AC-2: Installation
+
+- GIVEN user selects Roo Code
+- WHEN installation completes
+- THEN `.roo/commands/irismd-*.md` files exist
+- AND files contain agent definitions
+
+### AC-3: Non-Detection
+
+- GIVEN a project without `.roo/` directory
+- WHEN detectTools() runs
+- THEN Roo Code is NOT listed as detected
+- BUT user can still select it manually

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/002-agentic-coding-tool-integration/units/windsurf-installer/unit-brief.md

@@ -0,0 +1,128 @@
+# Unit Brief: Windsurf Installer
+
+## Overview
+
+The Windsurf Installer handles installation of irismd workflows into Windsurf's `.windsurf/workflows/` directory with required frontmatter.
+
+---
+
+## Scope
+
+### In Scope
+
+- Windsurf detection
+- Workflow file installation to `.windsurf/workflows/`
+- Adding frontmatter with description
+
+### Out of Scope
+
+- Base installation logic (handled by ToolInstaller)
+- Other tool installations
+
+---
+
+## Technical Context
+
+### File Structure
+
+```text
+src/lib/installers/
+└── WindsurfInstaller.js
+```
+
+### Target Installation Path
+
+```text
+project-root/
+└── .windsurf/
+    └── workflows/
+        ├── irismd-master-agent.md
+        ├── irismd-inception-agent.md
+        ├── irismd-construction-agent.md
+        └── irismd-operations-agent.md
+```
+
+---
+
+## Implementation Details
+
+### WindsurfInstaller Class
+
+Extends `ToolInstaller` and overrides `installCommands()` to add frontmatter.
+
+### Properties
+
+| Property | Value | Description |
+|----------|-------|-------------|
+| `key` | `'windsurf'` | Unique identifier for factory lookup |
+| `name` | `'Windsurf'` | Display name in CLI |
+| `commandsDir` | `'.windsurf/workflows'` | Where to install workflow files |
+| `detectPath` | `'.windsurf'` | Directory to check for detection |
+
+### Detection Logic
+
+Windsurf is detected if `.windsurf/` directory exists in the project root.
+
+### Frontmatter Format
+
+Windsurf requires frontmatter with a description field:
+
+```markdown
+---
+description: irismd-master-agent
+---
+
+# Activate Master Agent
+...
+```
+
+The description is derived from the target filename (e.g., `irismd-master-agent.md` → `irismd-master-agent`).
+
+---
+
+## Windsurf Reference
+
+Windsurf is Codeium's AI-powered IDE, featuring:
+
+- Cascade: Multi-file AI editing
+- Flows: AI-driven workflows
+- Rules: Project and global configuration
+
+### Configuration Locations
+
+| Type | Location |
+|------|----------|
+| Workflows | `.windsurf/workflows/` |
+| Project rules | `.windsurf/` |
+| Global rules | `~/.windsurf/` |
+
+---
+
+## Acceptance Criteria
+
+### AC-1: Detection
+
+- GIVEN a project with `.windsurf/` directory
+- WHEN detectTools() runs
+- THEN Windsurf is listed as detected
+
+### AC-2: Installation
+
+- GIVEN user selects Windsurf
+- WHEN installation completes
+- THEN `.windsurf/workflows/irismd-*.md` files exist
+- AND files contain frontmatter with description
+- AND files contain workflow definitions
+
+### AC-3: Frontmatter
+
+- GIVEN a source file `master-agent.md`
+- WHEN installed to Windsurf
+- THEN the file has frontmatter `description: irismd-master-agent`
+
+### AC-4: Non-Detection
+
+- GIVEN a project without `.windsurf/` directory
+- WHEN detectTools() runs
+- THEN Windsurf is NOT listed as detected
+- BUT user can still select it manually

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/002-agentic-coding-tool-integration/units.md

@@ -0,0 +1,188 @@
+# Units: Agentic Coding Tool Integration
+
+## Unit Decomposition
+
+This intent is decomposed into units representing the installer infrastructure and tool-specific integrations.
+
+---
+
+## Unit 1: CLI & Installer Core
+
+Core CLI application and installation orchestration logic.
+
+**Components:**
+
+- `bin/cli.js` - Commander.js CLI entry point
+- `lib/cli-utils.js` - Terminal UI utilities (chalk, figlet, gradient)
+- `lib/constants.js` - Theme colors and flow definitions
+- `lib/installer.js` - Installation orchestrator
+
+**Responsibilities:**
+
+- Parse CLI commands
+- Detect available agentic coding tools
+- Display interactive prompts
+- Orchestrate installation flow
+- Create installation manifest
+
+---
+
+## Unit 2: Installer Factory
+
+Factory pattern for creating tool-specific installers.
+
+**Components:**
+
+- `lib/InstallerFactory.js` - Factory class
+- `lib/installers/ToolInstaller.js` - Abstract base class
+
+**Responsibilities:**
+
+- Create appropriate installer instance based on tool type
+- Provide common interface for all installers
+
+---
+
+## Unit 3: Claude Code Installer
+
+Installer for Claude Code integration.
+
+**Target:** `.claude/commands/` | **Extension:** `.md`
+
+---
+
+## Unit 4: Cursor Installer
+
+Installer for Cursor integration using MDC format.
+
+**Target:** `.cursor/rules/` | **Extension:** `.mdc` | **Special:** Adds frontmatter
+
+---
+
+## Unit 5: GitHub Copilot Installer
+
+Installer for GitHub Copilot workspace agents.
+
+**Target:** `.github/agents/` | **Extension:** `.agent.md` | **Special:** Name transform
+
+---
+
+## Unit 6: Google Antigravity Installer
+
+Installer for Google Antigravity IDE integration.
+
+**Target:** `.agent/agents/` | **Extension:** `.md`
+
+---
+
+## Unit 7: Windsurf Installer
+
+Installer for Codeium Windsurf IDE integration.
+
+**Target:** `.windsurf/workflows/` | **Extension:** `.md` | **Special:** Adds frontmatter
+
+---
+
+## Unit 8: Cline Installer
+
+Installer for Cline (VS Code extension) integration.
+
+**Target:** `.clinerules/` | **Extension:** `.md`
+
+---
+
+## Unit 9: Roo Code Installer
+
+Installer for Roo Code integration.
+
+**Target:** `.roo/commands/` | **Extension:** `.md`
+
+---
+
+## Unit 10: Kiro CLI Installer
+
+Installer for AWS Kiro CLI integration.
+
+**Target:** `.kiro/steering/` | **Extension:** `.md`
+
+---
+
+## Unit 11: Gemini CLI Installer
+
+Installer for Google Gemini CLI integration.
+
+**Target:** `.gemini/` | **Extension:** `.md`
+
+---
+
+## Unit 12: Codex Installer
+
+Installer for OpenAI Codex integration.
+
+**Target:** `.codex/` | **Extension:** `.md`
+
+---
+
+## Unit 13: Kilo Code Installer
+
+Installer for Kilo Code integration.
+
+**Target:** `.kilo/` | **Extension:** `.md`
+
+---
+
+## Unit 14: OpenCode Installer
+
+Installer for OpenCode integration.
+
+**Target:** `.opencode/` | **Extension:** `.md`
+
+---
+
+## Unit Dependency Graph
+
+```text
+┌─────────────────┐
+│   CLI (cli.js)  │
+└────────┬────────┘
+         │
+┌────────▼────────┐
+│  Installer Core │
+│ (installer.js)  │
+└────────┬────────┘
+         │
+┌────────▼────────┐
+│InstallerFactory │
+└────────┬────────┘
+         │
+         ├──────┬──────┬──────┬──────┬──────┬──────┐
+         │      │      │      │      │      │      │
+      Claude Cursor Copilot Anti- Wind- Cline  ...
+       Inst.  Inst.  Inst. gravity surf  Inst.
+         │      │      │      │      │      │
+         └──────┴──────┴──────┴──────┴──────┴──────┘
+                           │
+                  ┌────────▼────────┐
+                  │  ToolInstaller  │
+                  │     (base)      │
+                  └─────────────────┘
+```
+
+---
+
+## Installation Summary
+
+| Tool | Directory | Extension | Special Handling |
+|------|-----------|-----------|------------------|
+| Claude Code | `.claude/commands/` | `.md` | Standard |
+| Cursor | `.cursor/rules/` | `.mdc` | Adds frontmatter |
+| GitHub Copilot | `.github/prompts/` + `.github/agents/` | `.prompt.md` + `.agent.md` | Both prompts and agents |
+| Google Antigravity | `.agent/agents/` | `.md` | Standard |
+| Windsurf | `.windsurf/workflows/` | `.md` | Adds frontmatter |
+| Cline | `.clinerules/` | `.md` | Standard |
+| Roo Code | `.roo/commands/` | `.md` | Standard |
+| Kiro CLI | `.kiro/steering/` | `.md` | Standard |
+| Gemini CLI | `.gemini/commands/` | `.toml` | Converts to TOML |
+| Codex | `.codex/` | `.md` | Standard |
+| Kilo Code | `.kilo/` | `.md` | Standard |
+| OpenCode | `.opencode/agent/` | `.md` | Standard |

package/src/iris_bundle/frameworks/iris-core/memory-bank/intents/003-memory-bank-system/requirements.md

@@ -0,0 +1,196 @@
+---
+status: complete
+completed: 2025-12-25
+note: "Implemented before irismd dogfooding. Stories not tracked in AI-DLC."
+---
+
+# Intent: Memory Bank System
+
+## Overview
+
+Provide a configuration-driven artifact storage system where all agents discover artifact paths and structure by reading a central `memory-bank.yaml` configuration file.
+
+---
+
+## Core Concept
+
+The Memory Bank is NOT a database - it's a file-based storage system with a YAML configuration that serves as the source of truth for all agents. Every agent reads `.irismd/memory-bank.yaml` on activation to understand where artifacts are stored and how they're organized.
+
+---
+
+## Functional Requirements
+
+### FR-1: Central Configuration File
+
+The `memory-bank.yaml` file is the single source of truth for artifact structure.
+
+**Location**: `.irismd/memory-bank.yaml`
+
+**Structure**:
+
+```yaml
+# Memory Bank Configuration for AI-DLC Flow
+# Defines the directory structure and required folders for project context
+
+structure:
+  - path: intents/
+    description: "Intents (Features/Capabilities)"
+  - path: intents/units/
+    description: "Units of Work (Services/Components)"
+  - path: intents/units/stories/
+    description: "Individual User Stories"
+  - path: bolts/
+    description: "Execution Instances (Bolt Sessions)"
+  - path: standards/
+    description: "Project Standards (Architecture, Tech Stack)"
+  - path: operations/
+    description: "Operations Context (Deployment, Monitoring)"
+
+# 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/{story-id}.md"
+  bolts: "memory-bank/bolts/{bolt-id}.md"
+  story-index: "memory-bank/story-index.md"  # Global story index
+
+  # Agent Ownership
+  ownership:
+    inception: [intents, units, stories, story-index]
+    construction: [units, bolts]
+    operations: [operations]
+
+# Global Story Index Options
+story-index:
+  enabled: true
+  mode: "single-file"  # Options: single-file, per-intent, aggregate
+  path: "memory-bank/story-index.md"
+```
+
+- FR-1.1: System SHALL provide a `memory-bank.yaml` configuration file at `.irismd/memory-bank.yaml`
+- FR-1.2: Configuration SHALL define `structure` section listing all directory paths and descriptions
+- FR-1.3: Configuration SHALL define `schema` section with path templates for each artifact type
+- FR-1.4: Configuration SHALL define `ownership` mapping agents to artifact types they manage
+
+### FR-2: Configuration Sections
+
+#### `structure` Section
+
+Defines the conceptual organization of the Memory Bank:
+
+| Path | Description | Purpose |
+|------|-------------|---------|
+| `intents/` | Intents (Features/Capabilities) | High-level feature definitions |
+| `intents/units/` | Units of Work (Services/Components) | Decomposed work elements |
+| `intents/units/stories/` | Individual User Stories | Implementation-level tasks |
+| `bolts/` | Execution Instances (Bolt Sessions) | Tracking bolt progress |
+| `standards/` | Project Standards | Tech stack, coding standards |
+| `operations/` | Operations Context | Deployment and monitoring |
+
+#### `schema` Section
+
+Provides path templates agents use to locate artifacts:
+
+| Key | Template | Example |
+|-----|----------|---------|
+| `intents` | `memory-bank/intents/{intent-name}/` | `memory-bank/intents/001-user-auth/` |
+| `units` | `memory-bank/intents/{intent-name}/units/{unit-name}/` | `memory-bank/intents/001-user-auth/units/auth-service/` |
+| `stories` | `memory-bank/intents/{intent-name}/units/{unit-name}/stories/{story-id}.md` | `...stories/001-user-auth-AUTH-001.md` |
+| `bolts` | `memory-bank/bolts/{bolt-id}.md` | `memory-bank/bolts/bolt-auth-service-1.md` |
+
+#### `ownership` Section
+
+Maps agents to the artifact types they create and manage:
+
+| Agent | Owned Artifacts | Permissions |
+|-------|-----------------|-------------|
+| `inception` | intents, units, stories | Create/Update |
+| `construction` | units, bolts | Update/Create |
+| `operations` | operations | Create/Update |
+
+### FR-3: Agent Configuration Reading
+
+- FR-3.1: Agents SHALL read `memory-bank.yaml` on activation
+- FR-3.2: Agents SHALL use schema templates to resolve artifact paths
+- FR-3.3: Agents SHALL respect ownership boundaries (only modify owned artifact types)
+- FR-3.4: Agents SHALL create directories on-demand following schema paths
+
+### FR-4: Artifact Storage
+
+- FR-4.1: All artifacts SHALL be stored as markdown files
+- FR-4.2: Artifacts SHALL follow templates from `.irismd/aidlc/templates/`
+- FR-4.3: Artifacts SHALL be human-readable and editable
+- FR-4.4: Artifacts SHALL be version-controllable via git
+
+### FR-5: Context Persistence
+
+- FR-5.1: Artifacts SHALL persist across agent sessions
+- FR-5.2: Fresh agent invocations SHALL load state from Memory Bank
+- FR-5.3: No in-memory caching between sessions (agents are stateless)
+
+---
+
+## Non-Functional Requirements
+
+### NFR-1: Performance
+
+- Configuration read SHALL complete in under 100ms
+- Artifact read/write SHALL be filesystem operations only (no database)
+
+### NFR-2: Usability
+
+- Configuration SHALL use human-readable YAML format
+- Artifacts SHALL be viewable in any text editor
+- Structure SHALL be intuitive for developers
+
+### NFR-3: Reliability
+
+- System SHALL not corrupt artifacts on partial write
+- System SHALL handle missing directories gracefully (create on demand)
+- Configuration errors SHALL provide clear error messages
+
+---
+
+## Default Values
+
+The `memory-bank.yaml` ships with sensible defaults:
+
+| Setting | Default Value |
+|---------|---------------|
+| Base directory | `memory-bank/` |
+| Intent path | `memory-bank/intents/{intent-name}/` |
+| Unit path | Nested under intent |
+| Story path | Nested under unit |
+| Bolt path | `memory-bank/bolts/` |
+| Standards path | `memory-bank/standards/` |
+| Operations path | `memory-bank/operations/` |
+
+---
+
+## Acceptance Criteria
+
+### AC-1: Configuration Discovery
+
+- GIVEN an agent activates
+- WHEN agent reads `.irismd/memory-bank.yaml`
+- THEN agent knows all artifact paths from `schema` section
+- AND agent knows its ownership boundaries from `ownership` section
+
+### AC-2: Path Resolution
+
+- GIVEN schema template `memory-bank/intents/{intent-name}/`
+- WHEN Inception Agent creates intent `001-user-auth`
+- THEN agent resolves path to `memory-bank/intents/001-user-auth/`
+
+### AC-3: Cross-Session Persistence
+
+- GIVEN Inception Agent creates a user story
+- WHEN Construction Agent activates in a new session
+- THEN Construction Agent reads same `memory-bank.yaml`
+- AND can locate the story using schema templates
+
+### AC-4: Ownership Enforcement
+
+- GIVEN Construction Agent is active
+- WHEN Construction Agent attempts to create an intent
+- THEN action is blocked (intents owned by Inception)