project-iris 0.0.12 → 0.0.14

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

@@ -0,0 +1,224 @@
+# Skill: Verify Deployment
+
+---
+
+## Role
+
+Post-deployment validation skill. Runs health checks and smoke tests.
+
+**NO Checkpoint** - Verification is an automated check, not a decision point.
+
+Verification happens after each deploy skill checkpoint. If verification fails, recommend rollback.
+
+---
+
+## Goal
+
+Confirm that a deployment is healthy, functional, and meeting acceptance criteria before proceeding to next environment.
+
+---
+
+## Input
+
+- **Required**: `--unit` - The unit to verify
+- **Required**: `.iris/aidlc/memory-bank.yaml` - artifact schema
+- **Optional**: `--env` - Target environment (default: last deployed)
+- **Optional**: `--version` - Specific version (default: currently deployed)
+
+---
+
+## Process
+
+### 1. Load Deployment Context
+
+From `deployment/history.md`:
+
+- Current deployed version
+- Deployment timestamp
+- Previous version (for comparison)
+
+### 2. Execute Health Checks
+
+- [ ] **Endpoint Health**: GET `/health` → 200 OK
+- [ ] **Readiness**: GET `/ready` → 200 OK
+- [ ] **Database**: Connection test → Connected
+- [ ] **Cache**: Connection test → Connected
+- [ ] **External APIs**: Connectivity check → Reachable
+
+### 3. Run Smoke Tests
+
+Execute critical path tests:
+
+- [ ] **Authentication**: Login flow works (if applicable)
+- [ ] **Core CRUD**: Basic operations work (required)
+- [ ] **API Endpoints**: Key endpoints respond (required)
+- [ ] **Error Handling**: Errors handled gracefully (required)
+
+### 4. Check Metrics
+
+Verify operational metrics are within bounds:
+
+- [ ] **Response Time**: < SLA (p95 latency)
+- [ ] **Error Rate**: < 1% (4xx/5xx responses)
+- [ ] **CPU**: < 80% (resource utilization)
+- [ ] **Memory**: < 80% (resource utilization)
+
+### 5. Compare to Baseline
+
+If previous version exists:
+
+- Error rate comparison
+- Latency comparison
+- Resource usage comparison
+
+### 6. Document Results
+
+Create `deployment/verification-{version}.md`:
+
+```markdown
+---
+version: {version}
+environment: {env}
+verified: {timestamp}
+status: passed|failed
+---
+
+## Verification Report: {version}
+
+### Health Checks
+
+- ✅ **Endpoint**: 200 OK, 15ms
+- ✅ **Database**: Connected
+- ✅ **Cache**: Connected
+
+### Smoke Tests
+
+- ✅ **Login Flow**: 234ms
+- ✅ **Create Item**: 156ms
+- ✅ **API Health**: 12ms
+
+### Metrics
+
+- ✅ **p95 Latency**: 145ms (threshold: <200ms)
+- ✅ **Error Rate**: 0.02% (threshold: <1%)
+
+### Baseline Comparison
+
+- **p95 Latency**: 142ms → 145ms (+2%)
+- **Error Rate**: 0.01% → 0.02% (+0.01%)
+
+### Conclusion
+{passed|failed}: {summary}
+```
+
+---
+
+## Output (Verification Passed)
+
+```markdown
+## Verification Passed: {unit-name}
+
+### Status: ✅ VERIFIED
+
+### Results Summary
+
+- ✅ **Health Checks**: {n}/{n} passed
+- ✅ **Smoke Tests**: {n}/{n} passed
+- ✅ **Metric Checks**: {n}/{n} passed
+
+### Key Metrics
+
+- ✅ **Response Time (p95)**: {value}ms
+- ✅ **Error Rate**: {value}%
+- ✅ **Uptime**: 100%
+
+### Environment Status
+
+- ✅ **{env}**: `{version}` - Verified
+
+### Documentation Created
+- `{unit-path}/deployment/verification-{version}.md`
+
+### Actions
+
+1 - **monitor**: Setup monitoring for this unit
+2 - **deploy**: Deploy to next environment
+3 - **menu**: Return to operations menu
+
+### Suggested Next Step
+→ **monitor** - Setup monitoring for `{unit-name}`
+
+**Type a number or press Enter for suggested action.**
+```
+
+---
+
+## Output (Verification Failed)
+
+```markdown
+## Verification Failed: {unit-name}
+
+### Status: ❌ FAILED
+
+### Failed Checks
+
+- ❌ **{check1}**: Expected {expected}, got {actual}
+- ❌ **{check2}**: Expected {expected}, got {actual}
+
+### Error Details
+{error messages or logs}
+
+### Impact Assessment
+
+- **Severity**: {critical|high|medium|low}
+- **Affected**: {what's broken}
+
+### Recommended Action
+⚠️ **ROLLBACK RECOMMENDED**
+
+Previous stable version: `{prev-version}`
+
+Rollback command:
+deploy --unit="{unit}" --env="{env}" --version="{prev-version}"
+
+### Actions
+
+1 - **rollback**: Rollback to previous version
+2 - **investigate**: Investigate root cause
+3 - **menu**: Return to operations menu
+
+### Suggested Next Step
+→ **rollback** - Restore `{prev-version}` immediately
+
+**Type a number or press Enter for suggested action.**
+```
+
+---
+
+## Human Validation Point
+
+On success:
+> "Verification passed for `{unit}` v`{version}` in {env}. All {n} checks passed. Ready to proceed to {next-action}?"
+
+On failure:
+> "⚠️ Verification FAILED for `{unit}` v`{version}`. {n} checks failed. Recommend rollback to `{prev-version}`. Proceed with rollback?"
+
+---
+
+## Transition
+
+After verification:
+
+- → **Monitor** (`.iris/skills/operations/monitor.md`) - if verified and final environment
+- → **Deploy** (`.iris/skills/operations/deploy.md`) - to next environment if verified
+- → **Rollback** - if verification fails (deploy previous version)
+
+---
+
+## Test Contract
+
+```yaml
+input: Unit name, environment, version
+output: Verification report with health checks, smoke tests, metrics
+checkpoints: 0 (automated validation only)
+```

package/{dist/iris_bundle/frameworks/iris-core → flows/aidlc}/templates/construction/bolt-types/ddd-construction-bolt.md

@@ -100,7 +100,7 @@ This bolt type implements Domain-Driven Design (DDD) methodology through five se
 
 **Artifact**: `ddd-01-domain-model.md`
 **Template**: `.iris/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-01-domain-model-template.md`
-**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory/memory-bank.yaml`
+**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory-bank.yaml`
 *(Default: `memory-bank/bolts/{bolt-id}/ddd-01-domain-model.md`)*
 
 **Template Structure**:
@@ -180,7 +180,7 @@ created: {YYYY-MM-DDTHH:MM:SSZ}
 
 **Artifact**: `ddd-02-technical-design.md`
 **Template**: `.iris/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-02-technical-design-template.md`
-**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory/memory-bank.yaml`
+**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory-bank.yaml`
 *(Default: `memory-bank/bolts/{bolt-id}/ddd-02-technical-design.md`)*
 
 **Template Structure**:
@@ -421,7 +421,7 @@ src/{unit}/
 
 **Artifact**: `ddd-03-test-report.md`
 **Template**: `.iris/aidlc/templates/construction/bolt-types/ddd-construction-bolt/ddd-03-test-report-template.md`
-**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory/memory-bank.yaml`
+**Location**: Path defined by `schema.bolts` in `.iris/aidlc/memory-bank.yaml`
 *(Default: `memory-bank/bolts/{bolt-id}/ddd-03-test-report.md`)*
 
 **Test Structure**:

package/{dist → flows/aidlc}/templates/construction/bolt-types/spike-bolt.md

@@ -71,7 +71,7 @@ This bolt type is for research and proof-of-concept work when there are unknowns
 6 - **Evaluate trade-offs**: Compare options
 
 **Artifact**: `spike-exploration.md`
-**Location**: Path defined by `schema.units` in `.iris/aidlc/memory/memory-bank.yaml`
+**Location**: Path defined by `schema.units` in `.iris/aidlc/memory-bank.yaml`
 *(Default: `{intents-path}/{intent}/units/{unit}/spike-exploration.md`)*
 
 **Template Structure**:
@@ -133,7 +133,7 @@ time_box: {hours}
 5 - **Present to team**: Share knowledge
 
 **Artifact**: `spike-report.md`
-**Location**: Path defined by `schema.units` in `.iris/aidlc/memory/memory-bank.yaml`
+**Location**: Path defined by `schema.units` in `.iris/aidlc/memory-bank.yaml`
 *(Default: `{intents-path}/{intent}/units/{unit}/spike-report.md`)*
 
 **Template Structure**:

package/flows/aidlc/templates/construction/construction-log-template.md

@@ -0,0 +1,129 @@
+# Construction Log Template
+
+Use this template to track construction progress and replanning decisions for a unit.
+
+---
+
+## Location
+
+`{intents-path}/{intent}/units/{unit}/construction-log.md`
+
+---
+
+## Template
+
+```markdown
+---
+unit: {UUU}-{unit-name}
+intent: {NNN}-{intent-name}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+last_updated: {YYYY-MM-DDTHH:MM:SSZ}
+---
+
+# Construction Log: {unit-name}
+
+## Original Plan
+
+**From Inception**: {number} bolts planned
+**Planned Date**: {inception-date}
+
+| Bolt ID | Stories | Type |
+|---------|---------|------|
+| {bolt-1} | {stories} | {type} |
+| {bolt-2} | {stories} | {type} |
+
+## Replanning History
+
+| Date | Action | Change | Reason | Approved |
+|------|--------|--------|--------|----------|
+
+## Current Bolt Structure
+
+| Bolt ID | Stories | Status | Changed |
+|---------|---------|--------|---------|
+| {bolt-1} | {stories} | ✅ completed | - |
+| {bolt-2} | {stories} | ⏳ in-progress | - |
+| {bolt-3} | {stories} | [ ] planned | Split from bolt-2 |
+
+## Execution History
+
+| Date | Bolt | Event | Details |
+|------|------|-------|---------|
+| {date} | {bolt-id} | started | Stage 1: {stage-name} |
+| {date} | {bolt-id} | stage-complete | {stage} → {next-stage} |
+| {date} | {bolt-id} | completed | All {n} stages done |
+
+## Execution Summary
+
+| Metric | Value |
+|--------|-------|
+| Original bolts planned | {n} |
+| Current bolt count | {n} |
+| Bolts completed | {n} |
+| Bolts in progress | {n} |
+| Bolts remaining | {n} |
+| Replanning events | {n} |
+
+## Notes
+
+{Any additional observations or decisions made during construction}
+```
+
+---
+
+## When to Create
+
+Create this file when:
+
+1. First bolt for a unit starts (initialize with original plan)
+2. Any replanning action occurs (append, split, reorder)
+
+---
+
+## When to Update
+
+Update this file when:
+
+1. A bolt starts (add to Execution History, update Current Bolt Structure)
+2. A stage completes (add to Execution History)
+3. A bolt completes (add to Execution History, update Current Bolt Structure, update Execution Summary)
+4. A replanning action occurs (add to Replanning History, update Current Bolt Structure)
+5. Construction completes (add final summary to Notes)
+
+---
+
+## Replanning History Actions
+
+| Action | Description |
+|--------|-------------|
+| `append` | New bolt(s) added to plan |
+| `split` | Existing bolt split into multiple |
+| `reorder` | Execution order changed |
+| `scope-change` | Stories added/removed from bolt |
+
+---
+
+## Example Entries
+
+### Replanning History Example
+
+```markdown
+| Date | Action | Change | Reason | Approved |
+|------|--------|--------|--------|----------|
+| 2025-12-07 | split | bolt-2 → bolt-2, bolt-3 | Scope too large for single bolt | Yes |
+| 2025-12-08 | append | Added bolt-4 | New stories from feedback | Yes |
+| 2025-12-09 | reorder | bolt-4 before bolt-3 | Dependency discovered | Yes |
+```
+
+### Execution History Example
+
+```markdown
+| Date | Bolt | Event | Details |
+|------|------|-------|---------|
+| 2025-12-07 | bolt-auth-1 | started | Stage 1: Model |
+| 2025-12-07 | bolt-auth-1 | stage-complete | Model → Design |
+| 2025-12-07 | bolt-auth-1 | stage-complete | Design → Implement |
+| 2025-12-08 | bolt-auth-1 | stage-complete | Implement → Test |
+| 2025-12-08 | bolt-auth-1 | completed | All 4 stages done |
+| 2025-12-08 | bolt-auth-2 | started | Stage 1: Model |
+```

package/flows/aidlc/templates/construction/standards/coding-standards.md

@@ -0,0 +1,29 @@
+# Coding Standards
+
+## General Principles
+
+- {e.g., DRY, KISS, SOLID}
+- {e.g., Clean Code practices}
+
+## Naming Conventions
+
+- Variables: {e.g., camelCase}
+- Functions: {e.g., camelCase}
+- Classes: {e.g., PascalCase}
+- Files: {e.g., kebab-case}
+
+## Formatting
+
+- Indentation: {e.g., 2 spaces}
+- Line Length: {e.g., 80 characters}
+- Braces: {e.g., K&R style}
+
+## Comments & Documentation
+
+- {e.g., JSDoc for functions}
+- {e.g., Explain WHY, not WHAT}
+
+## Testing
+
+- {e.g., Unit tests for all business logic}
+- {e.g., Integration tests for API endpoints}

package/flows/aidlc/templates/construction/standards/system-architecture.md

@@ -0,0 +1,22 @@
+# System Architecture
+
+## Overview
+
+{High-level system description}
+
+## Architecture Diagram
+
+{Mermaid diagram or description}
+
+## Components
+
+- {Component 1}: {Purpose}
+- {Component 2}: {Purpose}
+
+## Data Flow
+
+{How data moves through the system}
+
+## Technology Stack
+
+{Languages, frameworks, databases, etc.}

package/flows/aidlc/templates/construction/standards/tech-stack.md

@@ -0,0 +1,19 @@
+# Tech Stack
+
+## Core Technologies
+
+- Language: {e.g., TypeScript, Python}
+- Framework: {e.g., React, Next.js, Django}
+- Database: {e.g., PostgreSQL, MongoDB}
+
+## Infrastructure
+
+- Cloud Provider: {e.g., AWS, GCP}
+- Containerization: {e.g., Docker, Kubernetes}
+- CI/CD: {e.g., GitHub Actions}
+
+## Tools & Libraries
+
+- Testing: {e.g., Jest, Pytest}
+- Linting: {e.g., ESLint, Pylint}
+- Documentation: {e.g., MkDocs, Storybook}

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

@@ -0,0 +1,134 @@
+# Inception Log Template
+
+Use this template to track inception progress and decisions for an intent.
+
+---
+
+## Location
+
+`{intents-path}/{intent}/inception-log.md`
+
+---
+
+## Template
+
+```markdown
+---
+intent: {NNN}-{intent-name}
+created: {YYYY-MM-DDTHH:MM:SSZ}
+completed: {YYYY-MM-DDTHH:MM:SSZ or null}
+status: {in-progress | complete}
+---
+
+# Inception Log: {intent-name}
+
+## Overview
+
+**Intent**: {brief description}
+**Type**: {green-field | brown-field | defect-fix | refactoring}
+**Created**: {date}
+
+## Artifacts Created
+
+| Artifact | Status | File |
+|----------|--------|------|
+| Requirements | ✅ | requirements.md |
+| System Context | ✅ | system-context.md |
+| Units | ✅ | units/{unit-name}/unit-brief.md |
+| Stories | ✅ | units/{unit-name}/stories/*.md |
+| Bolt Plan | ✅ | memory-bank/bolts/bolt-*.md |
+
+## Summary
+
+| Metric | Count |
+|--------|-------|
+| Functional Requirements | {n} |
+| Non-Functional Requirements | {n} |
+| Units | {n} |
+| Stories | {n} |
+| Bolts Planned | {n} |
+
+## Units Breakdown
+
+| Unit | Stories | Bolts | Priority |
+|------|---------|-------|----------|
+| {unit-1} | {n} | {n} | Must |
+| {unit-2} | {n} | {n} | Should |
+
+## Decision Log
+
+| Date | Decision | Rationale | Approved |
+|------|----------|-----------|----------|
+
+## Scope Changes
+
+| Date | Change | Reason | Impact |
+|------|--------|--------|--------|
+
+## Ready for Construction
+
+**Checklist**:
+- [ ] All requirements documented
+- [ ] System context defined
+- [ ] Units decomposed
+- [ ] Stories created for all units
+- [ ] Bolts planned
+- [ ] Human review complete
+
+## Next Steps
+
+1. Begin Construction Phase
+2. Start with Unit: {first-unit}
+3. Execute: `/iris-construction-agent --unit="{first-unit}"`
+
+## Dependencies
+
+{Execution order based on unit dependencies}
+```
+
+---
+
+## When to Create
+
+Create this file when:
+
+1. Intent is created (intent-create skill)
+2. Initialize with basic metadata and empty sections
+
+---
+
+## When to Update
+
+Update this file when:
+
+1. An artifact is completed (update Artifacts Created table)
+2. A decision is made during inception (add to Decision Log)
+3. Scope changes (add to Scope Changes)
+4. Inception completes (mark status complete, fill summary)
+
+---
+
+## Decision Log Examples
+
+```markdown
+## Decision Log
+
+| Date | Decision | Rationale | Approved |
+|------|----------|-----------|----------|
+| 2025-12-07 | Split auth into 2 units | Separation of concerns | Yes |
+| 2025-12-07 | Use JWT over sessions | Stateless API requirement | Yes |
+| 2025-12-08 | Add MFA to scope | Security requirement from review | Yes |
+```
+
+---
+
+## Scope Changes Examples
+
+```markdown
+## Scope Changes
+
+| Date | Change | Reason | Impact |
+|------|--------|--------|--------|
+| 2025-12-08 | Added MFA stories | Security requirement | +2 stories, +1 bolt |
+| 2025-12-09 | Removed social login | Out of scope for MVP | -3 stories, -1 bolt |
+```

package/flows/aidlc/templates/inception/project/README.md

@@ -0,0 +1,55 @@
+# Project Context
+
+This directory contains project-level context and metadata.
+
+## Purpose
+
+The `memory-bank/project/` directory stores information about your overall project that persists across all intents and units.
+
+## Files to Create
+
+- **project-brief.md**: High-level project overview, goals, and scope
+- **tech-stack.md**: Technology choices and rationale
+- **team.md**: Team structure and roles
+- **conventions.md**: Coding standards, naming conventions, etc.
+
+## Example: project-brief.md
+
+```markdown
+---
+created: 2024-11-22
+updated: 2024-11-22
+---
+
+# Project Brief
+
+## Project Name
+{Your project name}
+
+## Overview
+{Brief description of what this project does}
+
+## Business Goals
+- {Goal 1}
+- {Goal 2}
+
+## Target Users
+{Who will use this system}
+
+## Success Criteria
+- {Measurable criterion 1}
+- {Measurable criterion 2}
+
+## Timeline
+- Inception: {dates}
+- Construction: {dates}
+- Launch: {target date}
+```
+
+## Getting Started
+
+1. Create `project-brief.md` with your project overview
+2. Document your tech stack in `tech-stack.md`
+3. Add any other project-level context as needed
+
+These files will be referenced by agents throughout the AI-DLC workflow.