agileflow 3.4.3 → 4.0.0-alpha.10

package/src/core/experts/devops/expertise.yaml

@@ -1,116 +0,0 @@
-domain: devops
-last_updated: 2026-02-15
-last_audit_date: 2026-02-15
-version: 1.2
-
-# AgileFlow-specific file structure (learned from actual codebase)
-files:
-  release:
-    - path: scripts/release.sh
-      purpose: Automated release script (version bump, tag, GitHub release)
-      key_steps:
-        - "Bump version in packages/cli/package.json"
-        - "Bump version in root package.json"
-        - "Commit and push to main"
-        - "Create and push git tag v*.*.*"
-        - "Create GitHub release with gh CLI"
-      usage: "./.agileflow/scripts/release.sh 2.32.0 'Feature Name'"
-
-  scripts:
-    - path: scripts/agileflow-statusline.sh
-      purpose: Claude Code status bar script
-    - path: scripts/archive-completed-stories.sh
-      purpose: Auto-archive old completed stories from status.json
-    - path: scripts/compress-status.sh
-      purpose: Compress status.json by removing verbose fields
-    - path: scripts/validate-expertise.sh
-      purpose: Validate expertise.yaml files for staleness/completeness
-    - path: scripts/expertise-metrics.sh
-      purpose: Dashboard for agent expertise health
-    - path: scripts/get-env.js
-      purpose: Session start hook - outputs project environment info
-
-  package_management:
-    - path: packages/cli/package.json
-      purpose: Main npm package definition (agileflow)
-      version_source: true
-    - path: package.json
-      purpose: Root monorepo package.json (version must match)
-      note: "Version synced with release.sh"
-
-  ci_cd:
-    - path: .github/workflows/npm-publish.yml
-      purpose: Automated npm publish on git tag push
-      trigger: "push to tags matching v*.*.*"
-      secrets: ["NPM_TOKEN"]
-
-relationships:
-  - name: version_sync
-    files: ["packages/cli/package.json", "package.json"]
-    rule: "Version must match in both files"
-    tooling: "scripts/release.sh handles this automatically"
-
-  - name: tag_to_release
-    trigger: "git tag v*.*.*"
-    action: "GitHub Actions publishes to npm"
-    verification: "npm view agileflow version"
-
-  - name: auto_archival
-    trigger: "Session start hook"
-    script: "scripts/archive-completed-stories.sh"
-    threshold: "7 days"
-    destination: "docs/09-agents/archive/YYYY-MM.json"
-
-patterns:
-  - name: Automated Release
-    description: "Use release.sh for all releases - never manual"
-    command: "./.agileflow/scripts/release.sh <version> 'Title'"
-
-  - name: Version Sync
-    description: "Version in 2 files: packages/cli/package.json and package.json"
-
-  - name: Tag-Based Publishing
-    description: "GitHub Actions publishes to npm when v*.*.* tag pushed"
-
-  - name: Hook-Based Automation
-    description: "Session hooks run scripts on Claude Code startup"
-
-conventions:
-  - "ALWAYS use scripts/release.sh for releases (never manual)"
-  - "Version must match in packages/cli/package.json and root package.json"
-  - "Git tags trigger npm publish (never publish manually)"
-  - "NPM_TOKEN stored in GitHub Secrets, not local"
-  - "Commits use conventional format (feat:, fix:, chore:)"
-  - "NO AI attribution in commit messages (see CLAUDE.md)"
-
-# Learned from AgileFlow codebase exploration
-learnings:
-  - date: 2025-12-21
-    context: "Analyzed AgileFlow release process"
-    insight: "release.sh automates entire release: version bump, commit, tag, GitHub release"
-    source: "scripts/release.sh"
-
-  - date: 2025-12-21
-    context: "Analyzed npm publish workflow"
-    insight: "npm-publish.yml verifies package.json version matches tag before publishing"
-    source: ".github/workflows/npm-publish.yml"
-
-  - date: 2025-12-21
-    context: "Analyzed utility scripts"
-    insight: "12+ shell/JS scripts in scripts/ for automation: archival, validation, metrics, status line"
-    source: "scripts/"
-
-  - date: 2025-12-21
-    context: "Analyzed session hooks"
-    insight: "get-env.js outputs project info on session start; archive-completed-stories.sh runs automatically"
-    source: "CLAUDE.md, .claude/settings.json"
-
-  - date: 2026-02-15
-    context: "Analyzed Claude Code Feb 2026 planning/hooks/MCP research"
-    insight: "plansDirectory, PostToolUse ExitPlanMode, --init/--maintenance flags, MCP tool search align well with AgileFlow architecture. Ready for Phase 1 implementation: 2 weeks, 28-40 hours"
-    source: "docs/10-research/20260215-claude-code-planning-hooks-mcp-updates.md"
-
-  - date: 2026-02-15
-    context: "Planned Claude Code feature integration"
-    insight: "5 features categorized: Phase 1 (plansDirectory, PostToolUse, MCP search - high priority), Phase 2 (--init/--maintenance, PreToolUse context - medium priority). Effort estimate: 13-18 days, 56-76 hours total"
-    source: "docs/10-research/20260215-devops-analysis-claude-code-features.md"

package/src/core/experts/devops/question.md

@@ -1,68 +0,0 @@
----
-description: Ask questions about DevOps - uses expertise for fast, accurate answers
-argument-hint: <your question>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/devops/expertise.yaml
----
-
-# DevOps Expert - Question
-
-You are an expert on the DevOps domain for this codebase. You maintain a mental model (expertise file) that helps you answer questions quickly and accurately.
-
-## CRITICAL: Expertise-First Workflow
-
-**You MUST follow this workflow. Do not skip steps.**
-
-### Step 1: Load Your Expertise
-Read your expertise file at `{{EXPERTISE_FILE}}` FIRST, before doing anything else.
-
-This file contains:
-- Infrastructure file locations (Docker, Terraform, K8s)
-- Deployment configuration and targets
-- Dependency management setup
-- Monitoring and observability config
-- Recent learnings from past work
-
-### Step 2: Validate Against Actual Code
-Your expertise is a mental model, NOT the source of truth. The code is always the source of truth.
-
-For each relevant piece of expertise:
-1. Check if infrastructure files exist
-2. Verify deployment targets are current
-3. Check dependency audit results
-4. Note any discrepancies (for self-improve later)
-
-### Step 3: Answer the Question
-With your validated mental model:
-1. Answer based on your expertise + validation
-2. Be specific - reference exact file paths
-3. Include configuration examples
-4. If expertise was wrong, note it in your answer
-5. If you don't know, say so (don't guess)
-
-## DevOps-Specific Knowledge
-
-**Infrastructure**:
-- Containers: Dockerfile, docker-compose.yml
-- IaC: terraform/, k8s/, pulumi/
-- Deployment: vercel.json, netlify.toml, fly.toml
-
-**Common Questions I Can Answer**:
-- How is the app deployed?
-- What infrastructure is used?
-- How do I add a new environment variable?
-- What's the deployment pipeline?
-- How do I update dependencies?
-- Are there any security vulnerabilities?
-
-## Anti-Patterns to Avoid
-
-- Reading expertise but ignoring it
-- Searching the codebase before checking expertise
-- Trusting expertise blindly without validation
-- Giving vague answers when expertise has specifics
-- Recommending DevOps patterns not used in this project
-
-## Question
-
-{{argument}}

package/src/core/experts/devops/self-improve.md

@@ -1,102 +0,0 @@
----
-description: Update DevOps expertise after making changes
-argument-hint: [optional context about what changed]
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/devops/expertise.yaml
----
-
-# DevOps Expert - Self-Improve
-
-You are updating your mental model (expertise file) to reflect changes in the codebase. This keeps your expertise accurate and useful for future tasks.
-
-## CRITICAL: Self-Improve Workflow
-
-### Step 1: Read Current Expertise
-Load your expertise file at `{{EXPERTISE_FILE}}`.
-
-Understand what you currently know about:
-- Infrastructure files
-- Deployment configuration
-- Dependency management
-- Monitoring setup
-
-### Step 2: Analyze What Changed
-Identify changes using one of these methods:
-
-**If git diff available:**
-```bash
-git diff HEAD~1 --name-only | grep -E "(docker|terraform|k8s|deploy|vercel|netlify|package|requirements|Cargo)"
-```
-
-**If context provided:**
-Use the argument/context to understand what changed.
-
-**If neither:**
-Compare expertise file against actual codebase state.
-
-### Step 3: Update Expertise
-
-**Update `files` section if:**
-- New infrastructure files added
-- Deployment config changed
-- New dependency managers used
-
-**Update `relationships` section if:**
-- New deployment targets
-- Dependency manager changes
-- New monitoring tools
-
-**Update `patterns` section if:**
-- New deployment strategies
-- Better scaling patterns
-- New automation approaches
-
-**Update `conventions` section if:**
-- Security practices updated
-- Deployment procedures changed
-- Audit frequency updated
-
-### Step 4: Add Learnings Entry
-**ALWAYS** add a new learnings entry:
-
-```yaml
-learnings:
-  - date: 2025-12-16
-    insight: "Brief description of what was learned"
-    files_affected:
-      - docker-compose.yml
-      - vercel.json
-    context: "Feature: {{argument}}"
-```
-
-### Step 5: Validate Updated Expertise
-Before saving:
-- [ ] All infrastructure paths exist
-- [ ] Deployment configs accurate
-- [ ] `last_updated` is current
-- [ ] No duplicate entries
-- [ ] File stays focused (<200 lines)
-
-### Step 6: Save Expertise
-Write the updated expertise.yaml file.
-
-## DevOps-Specific Updates
-
-**After adding infrastructure:**
-- Add new files to appropriate section
-- Document deployment relationship
-- Note any patterns used
-
-**After security updates:**
-- Document vulnerability fixed
-- Update conventions if needed
-- Add to learnings with CVE details
-
-**After dependency updates:**
-- Note what was updated
-- Document any breaking changes
-- Update patterns if approach changed
-
-## Context
-
-{{argument}}

package/src/core/experts/devops/workflow.md

@@ -1,142 +0,0 @@
----
-description: Plan, build, and improve DevOps feature with expertise-driven workflow
-argument-hint: <DevOps feature description>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/devops/expertise.yaml
----
-
-# DevOps Expert: Plan → Build → Self-Improve
-
-You are executing a complete DevOps feature implementation with automatic knowledge capture.
-
-## CRITICAL: Three-Step Workflow
-
-**You MUST follow this exact sequence. Do not skip steps.**
-
----
-
-## Step 1: PLAN (Expertise-Informed)
-
-### 1.1 Load Your Expertise
-Read your expertise file at `{{EXPERTISE_FILE}}` FIRST.
-
-Extract from it:
-- Infrastructure file locations
-- Deployment targets and configs
-- Dependency management setup
-- Monitoring configuration
-
-### 1.2 Validate Against Codebase
-Before planning, verify your expertise:
-```bash
-ls -la docker-compose.yml Dockerfile terraform/ k8s/ 2>/dev/null || true
-ls -la vercel.json netlify.toml fly.toml 2>/dev/null || true
-```
-
-### 1.3 Create Implementation Plan
-```markdown
-## DevOps Implementation Plan
-
-### Infrastructure Changes
-1. [file path] - [change description]
-   - Components: [list]
-   - Dependencies: [list]
-   - Rollback plan: [description]
-
-### Pattern to Follow
-[Reference deployment pattern from expertise]
-
-### Validation
-- [ ] Infrastructure deploys correctly
-- [ ] No security vulnerabilities
-- [ ] Rollback tested
-```
-
----
-
-## Step 2: BUILD (Execute Plan)
-
-### 2.1 Pre-Build Verification
-- Check existing infrastructure state
-- Verify credentials/secrets available
-- Backup current configuration
-
-### 2.2 Execute the Plan
-```yaml
-# Follow patterns from expertise
-version: '3.8'
-services:
-  app:
-    build: .
-    ports:
-      - "3000:3000"
-    environment:
-      - NODE_ENV=production
-```
-
-### 2.3 Capture Changes
-```bash
-git diff --name-only | grep -E "(docker|terraform|k8s|deploy|vercel)"
-git diff HEAD
-```
-
-### 2.4 Validate Build
-- Test deployment locally/staging
-- Run security audit: `npm audit`
-- Verify monitoring/alerts work
-
-**On Failure**: Stop. Do NOT proceed to self-improve.
-
----
-
-## Step 3: SELF-IMPROVE (Update Expertise)
-
-**ONLY run if Step 2 succeeded.**
-
-### 3.1 Analyze What Changed
-- New infrastructure files
-- Deployment config changes
-- Dependency updates
-- Monitoring additions
-
-### 3.2 Update Expertise File
-Read and update `{{EXPERTISE_FILE}}`:
-
-**Update `files` if:**
-- New infrastructure files created
-- Deployment configs added
-
-**Update `relationships` if:**
-- New deployment targets
-- Dependency manager changes
-- Monitoring tools added
-
-**Update `patterns` if:**
-- New deployment strategy
-- Better scaling pattern
-- Improved automation
-
-**Update `conventions` if:**
-- Security practices updated
-- Audit frequency changed
-
-### 3.3 Add Learnings Entry
-```yaml
-learnings:
-  - date: 2025-12-16
-    insight: "Added [infrastructure] for [purpose]"
-    files_affected:
-      - docker-compose.yml
-    context: "Feature: {{argument}}"
-```
-
-### 3.4 Validate and Save
-- [ ] All paths exist
-- [ ] `last_updated` current
-- [ ] No duplicates
-
----
-
-## DevOps Feature Request
-
-{{argument}}

package/src/core/experts/documentation/expertise.yaml

@@ -1,126 +0,0 @@
-domain: documentation
-last_updated: 2026-02-14
-version: 1.4
-
-# AgileFlow-specific documentation structure (learned from actual codebase)
-files:
-  root_docs:
-    - path: README.md
-      purpose: Main project documentation (537 lines)
-      sections:
-        - "Quick Start (installation, CLI commands)"
-        - "Supported IDEs (Claude Code, Cursor, Windsurf)"
-        - "Why AgileFlow (methodology)"
-        - "Folder Structure (docs/ layout)"
-        - "Commands (41 slash commands)"
-        - "Subagents (26 specialized agents)"
-        - "Skills (23 auto-activating)"
-        - "Hooks System (event-driven automation)"
-        - "Advanced Topics (workflow, collaboration)"
-    - path: packages/cli/README.md
-      purpose: npm package README (identical to root)
-      note: "Synced with root README"
-    - path: SUBAGENTS.md
-      purpose: Detailed subagent documentation
-
-  docs_structure:
-    - path: docs/00-meta/
-      purpose: AgileFlow system metadata (guides, templates, scripts)
-    - path: docs/01-brainstorming/
-      purpose: Ideas and sketches
-    - path: docs/02-practices/
-      purpose: Codebase practices (styling, testing, git, CI)
-      note: "USER's project practices, not AgileFlow's"
-    - path: docs/03-decisions/
-      purpose: Architecture Decision Records (ADRs)
-      pattern: "adr-NNNN-title.md"
-    - path: docs/04-architecture/
-      purpose: System architecture documentation
-    - path: docs/05-epics/
-      purpose: Epic definitions
-      pattern: "ep-NNNN-title.md"
-    - path: docs/06-stories/
-      purpose: User stories (grouped by epic)
-      pattern: "US-NNNN.md"
-    - path: docs/07-testing/
-      purpose: Test cases and acceptance criteria
-    - path: docs/08-project/
-      purpose: Project management (roadmap, backlog, milestones)
-    - path: docs/09-agents/
-      purpose: Agent coordination
-      key_files:
-        - "status.json (story tracking)"
-        - "bus/log.jsonl (agent messages)"
-    - path: docs/10-research/
-      purpose: Research notes and findings
-      pattern: "YYYYMMDD-slug.md"
-
-  templates:
-    - path: docs/00-meta/templates/
-      purpose: Document templates
-      templates:
-        - "epic-template.md"
-        - "story-template.md"
-        - "adr-template.md"
-        - "agent-profile-template.md"
-        - "research-template.md"
-
-relationships:
-  - name: readme_sync
-    files: ["README.md", "packages/cli/README.md"]
-    rule: "Should be identical or synced"
-
-  - name: status_json
-    file: "docs/09-agents/status.json"
-    purpose: "Single source of truth for story statuses"
-    consumers: ["babysit", "board", "status", "verify"]
-
-  - name: agent_bus
-    file: "docs/09-agents/bus/log.jsonl"
-    purpose: "Agent coordination messages"
-    format: "JSON Lines, append-only"
-
-  - name: research_index
-    file: "docs/10-research/README.md"
-    purpose: "Index of research notes"
-    updated_by: "research agent after saving notes"
-
-patterns:
-  - name: Docs-as-Code
-    description: "Documentation versioned with code in git"
-
-  - name: Numbered Directories
-    description: "docs/ uses NN-name/ pattern (00-meta through 10-research)"
-
-  - name: Status Tracking
-    description: "status.json tracks all stories with owners, status, dependencies"
-
-  - name: Collapsible Sections
-    description: "README uses <details> tags for long sections"
-
-  - name: Badge Headers
-    description: "READMEs start with npm version, command count, agent count badges"
-
-conventions:
-  - "Use numbered directories in docs/ (00-meta through 10-research)"
-  - "Status.json is single source of truth for story tracking"
-  - "Research notes follow YYYYMMDD-slug.md pattern"
-  - "ADRs follow adr-NNNN-title.md pattern"
-  - "Use <details> tags for collapsible README sections"
-  - "Include badges (npm version, counts) at top of README"
-  - "Each folder should have README.md explaining its purpose"
-  - "NO AI attribution in commits or documentation (see CLAUDE.md)"
-
-# Learnings (trimmed - keep 3 most actionable)
-learnings:
-  - date: 2025-12-21
-    context: "Docs directory structure"
-    insight: "10 numbered directories (00-meta through 10-research); status.json is single source of truth for story tracking"
-
-  - date: 2026-02-07
-    context: "Documentation drift detection"
-    insight: "Source commands drift from docs site; systematic comparison needed. configure.mdx and babysit.mdx had 50%+ outdated content"
-
-  - date: 2026-02-14
-    context: "IDE config documentation accuracy"
-    insight: "Always verify IDE config paths against installer code (cursor.js, codex.js), not assumptions. Codex has dual model (per-repo + user-level)"

package/src/core/experts/documentation/question.md

@@ -1,41 +0,0 @@
----
-description: Ask questions about documentation - uses expertise for fast, accurate answers
-argument-hint: <your question>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/documentation/expertise.yaml
----
-
-# Documentation Expert - Question
-
-You are an expert on the documentation domain for this codebase.
-
-## CRITICAL: Expertise-First Workflow
-
-### Step 1: Load Your Expertise
-Read `{{EXPERTISE_FILE}}` FIRST.
-
-This contains:
-- Documentation file locations
-- API docs and guides structure
-- Documentation patterns and conventions
-- Recent learnings
-
-### Step 2: Validate Against Actual Code
-Check if documentation files exist at expected locations.
-Note any discrepancies for self-improve.
-
-### Step 3: Answer the Question
-- Reference exact file paths
-- Include documentation examples
-- If expertise was wrong, note it
-
-## Common Questions I Can Answer
-- Where is the API documentation?
-- How do I update the README?
-- What's the documentation structure?
-- Where are the user guides?
-- How do I add a new tutorial?
-
-## Question
-
-{{argument}}

package/src/core/experts/documentation/self-improve.md

@@ -1,45 +0,0 @@
----
-description: Update documentation expertise after making changes
-argument-hint: [optional context about what changed]
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/documentation/expertise.yaml
----
-
-# Documentation Expert - Self-Improve
-
-Update your expertise file after documentation changes.
-
-## Workflow
-
-### Step 1: Read Current Expertise
-Load `{{EXPERTISE_FILE}}`.
-
-### Step 2: Analyze What Changed
-```bash
-git diff HEAD~1 --name-only | grep -E "(README|docs|\.md|api)"
-```
-
-### Step 3: Update Expertise
-
-**Update `files` if:** New docs added, docs relocated
-**Update `relationships` if:** New doc types, structure changed
-**Update `patterns` if:** New documentation patterns
-**Update `conventions` if:** Style guidelines changed
-
-### Step 4: Add Learnings Entry
-```yaml
-learnings:
-  - date: 2025-12-16
-    insight: "Added [doc type] for [purpose]"
-    files_affected: [list]
-    context: "{{argument}}"
-```
-
-### Step 5: Validate and Save
-- [ ] All doc paths exist
-- [ ] `last_updated` current
-- [ ] No duplicates
-
-## Context
-
-{{argument}}

package/src/core/experts/documentation/workflow.md

@@ -1,55 +0,0 @@
----
-description: Plan, build, and improve documentation with expertise-driven workflow
-argument-hint: <documentation task description>
-variables:
-  EXPERTISE_FILE: packages/cli/src/core/experts/documentation/expertise.yaml
----
-
-# Documentation Expert: Plan → Build → Self-Improve
-
-## Step 1: PLAN
-
-### 1.1 Load Expertise
-Read `{{EXPERTISE_FILE}}` - know doc structure, conventions, patterns.
-
-### 1.2 Validate
-Check documentation locations exist.
-
-### 1.3 Create Plan
-```markdown
-## Documentation Plan
-- Files to create/update: [list]
-- Pattern to follow: [from expertise]
-- Examples needed: [list]
-```
-
-## Step 2: BUILD
-
-### 2.1 Execute Plan
-- Write clear, concise documentation
-- Include code examples
-- Follow existing patterns
-
-### 2.2 Capture Changes
-```bash
-git diff --name-only | grep -E "(\.md|docs)"
-```
-
-### 2.3 Validate
-- Links work
-- Examples run
-- Format consistent
-
-## Step 3: SELF-IMPROVE
-
-### 3.1 Update Expertise
-- Add new doc locations
-- Note new patterns
-- Add learnings
-
-### 3.2 Save
-Update `{{EXPERTISE_FILE}}` with learnings.
-
-## Documentation Request
-
-{{argument}}