agileflow 3.4.2 → 4.0.0-alpha.1

package/src/core/templates/damage-control-patterns.yaml

@@ -1,243 +0,0 @@
-# AgileFlow Damage Control - Security Rules
-# Protects your codebase from destructive agent commands
-#
-# Configuration: /agileflow:configure → Damage Control
-# Documentation: See research/20260106-claude-code-damage-control-hooks.md
-#
-# Schema Version: 1.0.0
-
-version: "1.0.0"
-
-# =====================================================
-# BLOCKED BASH COMMANDS - Always blocked (exit code 2)
-# =====================================================
-# Regex patterns matched against the full bash command
-# These commands are considered too dangerous to ever run
-
-bashToolPatterns:
-  # ─── File System Destruction ───
-  - pattern: '\brm\s+(-[rRf]+\s+)?/'
-    reason: "rm with absolute path - could delete system files"
-
-  - pattern: '\brm\s+-[rRf]*\s+\.\.'
-    reason: "rm with parent directory - could escape project"
-
-  - pattern: '\brm\s+-rf\s+'
-    reason: "Recursive force delete - extremely dangerous"
-
-  - pattern: '\brmdir\s+(-p\s+)?/'
-    reason: "rmdir with absolute path"
-
-  # ─── Git Destructive Operations ───
-  - pattern: '\bgit\s+push\s+.*--force'
-    reason: "Force push can destroy remote history"
-
-  - pattern: '\bgit\s+push\s+.*-f\b'
-    reason: "Force push can destroy remote history"
-
-  - pattern: '\bgit\s+reset\s+--hard'
-    reason: "Hard reset discards uncommitted changes"
-
-  - pattern: '\bgit\s+clean\s+-fd'
-    reason: "Git clean with force deletes untracked files"
-
-  - pattern: '\bgit\s+branch\s+-D'
-    reason: "Force delete branch without merge check"
-
-  # ─── Database Destructive Operations ───
-  - pattern: 'DROP\s+(TABLE|DATABASE|INDEX|VIEW|SCHEMA)'
-    reason: "DROP commands are destructive"
-    flags: "i"
-
-  - pattern: 'TRUNCATE\s+TABLE'
-    reason: "TRUNCATE removes all data without logging"
-    flags: "i"
-
-  - pattern: 'DELETE\s+FROM\s+\w+\s*;'
-    reason: "DELETE without WHERE clause deletes all rows"
-    flags: "i"
-
-  # ─── System Modification ───
-  - pattern: '\bsudo\s+'
-    reason: "Sudo commands require manual execution"
-
-  - pattern: '\bchmod\s+777'
-    reason: "World-writable permissions are dangerous"
-
-  - pattern: '\bchown\s+-R'
-    reason: "Recursive ownership change"
-
-  - pattern: '\bchmod\s+-R'
-    reason: "Recursive permission change"
-
-  # ─── Disk Operations ───
-  - pattern: '\bdd\s+if='
-    reason: "dd can overwrite disks"
-
-  - pattern: '\bmkfs\.'
-    reason: "Filesystem creation"
-
-  - pattern: '\bfdisk\b'
-    reason: "Disk partitioning"
-
-  # ─── Process Control ───
-  - pattern: '\bkill\s+-9'
-    reason: "Force kill processes"
-
-  - pattern: '\bkillall\b'
-    reason: "Kill all matching processes"
-
-  - pattern: '\bpkill\s+-9'
-    reason: "Force kill by pattern"
-
-  # ─── Network/System ───
-  - pattern: '\biptables\s+'
-    reason: "Firewall modification"
-
-  - pattern: '\bsystemctl\s+(stop|disable|mask)'
-    reason: "System service modification"
-
-  # ─── Credential Exposure ───
-  - pattern: '\bcat\s+.*\.pem'
-    reason: "Displaying private keys"
-
-  - pattern: '\bcat\s+.*id_rsa'
-    reason: "Displaying SSH private keys"
-
-# =====================================================
-# ASK PATTERNS - Require user confirmation
-# =====================================================
-# Risky but sometimes valid - ask first before executing
-
-askPatterns:
-  - pattern: 'DELETE\s+FROM\s+\w+\s+WHERE'
-    reason: "Deleting specific records - please confirm"
-    flags: "i"
-
-  - pattern: '\bnpm\s+publish'
-    reason: "Publishing to npm - please confirm"
-
-  - pattern: '\bgit\s+push\s+origin\s+(main|master)'
-    reason: "Pushing to main branch - please confirm"
-
-  - pattern: '\brm\s+-[rRf]*\s+node_modules'
-    reason: "Removing node_modules - please confirm"
-
-  - pattern: '\baws\s+.*delete'
-    reason: "AWS delete operation - please confirm"
-    flags: "i"
-
-  - pattern: '\bgcloud\s+.*delete'
-    reason: "GCloud delete operation - please confirm"
-    flags: "i"
-
-  - pattern: '\baz\s+.*delete'
-    reason: "Azure delete operation - please confirm"
-    flags: "i"
-
-  - pattern: '\bnpx\s+.*--force'
-    reason: "Force npx operation - please confirm"
-
-  - pattern: 'UPDATE\s+\w+\s+SET.*WHERE'
-    reason: "Database update - please confirm"
-    flags: "i"
-
-# =====================================================
-# PATH PROTECTION - File/directory access controls
-# =====================================================
-
-# Zero access - cannot read, write, edit, or delete
-# These paths are completely off-limits
-zeroAccessPaths:
-  - "~/.ssh/"
-  - "~/.aws/"
-  - "~/.gnupg/"
-  - "~/.config/gh/"
-  - ".env.production"
-  - ".env.local"
-  - ".env.secrets"
-  - "credentials.json"
-  - "secrets.yaml"
-  - "secrets.json"
-  - "*.pem"
-  - "*.key"
-  - "id_rsa"
-  - "id_ed25519"
-
-# Read-only - can read but not modify
-# Safe to view, but changes should be manual
-readOnlyPaths:
-  - "~/.bashrc"
-  - "~/.zshrc"
-  - "~/.gitconfig"
-  - "/etc/"
-  - "package-lock.json"
-  - "yarn.lock"
-  - "pnpm-lock.yaml"
-
-# No delete - can read and modify but not delete
-# Important files that shouldn't be removed
-noDeletePaths:
-  - ".claude/"
-  - ".agileflow/"
-  - "docs/09-agents/status.json"
-  - ".git/"
-  - "CLAUDE.md"
-  - "README.md"
-  - "package.json"
-  - "tsconfig.json"
-
-# =====================================================
-# AGILEFLOW-SPECIFIC PROTECTIONS
-# =====================================================
-# Additional rules specific to AgileFlow projects
-
-agileflowProtections:
-  - pattern: '\brm\s+.*status\.json'
-    reason: "status.json tracks story progress - protected"
-
-  - pattern: '\brm\s+.*\.claude/'
-    reason: "Claude Code configuration - protected"
-
-  - pattern: '\brm\s+.*\.agileflow/'
-    reason: "AgileFlow installation - protected"
-
-  - pattern: '\brm\s+.*session-state\.json'
-    reason: "Session state tracking - protected"
-
-  - pattern: '\brm\s+.*expertise\.yaml'
-    reason: "Agent expertise files - protected"
-
-# =====================================================
-# NOTES
-# =====================================================
-#
-# Exit Codes:
-#   0 = Allow command to proceed
-#   2 = Block command (show error message)
-#
-# Ask Pattern JSON Output:
-#   { "result": "ask", "message": "Confirm this action?" }
-#
-# Flags:
-#   "i" = case-insensitive matching
-#
-# Customization:
-#   Add project-specific patterns below this line
-#   Run /agileflow:configure → Damage Control to reconfigure
-#
-# =====================================================
-
-# ─── Release Process Enforcement ───
-# Forces use of ./scripts/release.sh instead of manual commands
-releaseProtections:
-  - pattern: '\bnpm\s+version\s+'
-    reason: "Use ./scripts/release.sh instead of npm version"
-
-  - pattern: '\bgit\s+tag\s+v\d+\.\d+\.\d+'
-    reason: "Use ./scripts/release.sh instead of manual git tag"
-
-# ─── Project-Specific Patterns (add yours below) ───
-# customPatterns:
-#   - pattern: 'your-pattern-here'
-#     reason: "Your reason"

package/src/core/templates/environment.json

@@ -1,18 +0,0 @@
-{
-  "$schema": "https://json-schema.org/draft-07/schema#",
-  "description": "AgileFlow session harness environment configuration",
-  "project_type": "nodejs",
-  "init_script": "./docs/00-meta/init.sh",
-  "test_command": "npm test",
-  "test_timeout_ms": 60000,
-  "dev_server": {
-    "command": "npm run dev",
-    "port": 3000,
-    "ready_pattern": "Ready on"
-  },
-  "verification_policy": "warn",
-  "baseline_commit": null,
-  "baseline_established": null,
-  "created_at": "2025-12-06T00:00:00Z",
-  "updated_at": "2025-12-06T00:00:00Z"
-}

package/src/core/templates/epic-template.md

@@ -1,27 +0,0 @@
----
-epic_id: {{EPIC_ID}}
-title: {{TITLE}}
-owner: {{OWNER}}
-status: active
-created: {{CREATED}}
-updated: {{UPDATED}}
-goal: {{GOAL}}
----
-
-# {{EPIC_ID}}: {{TITLE}}
-
-## Goal
-{{GOAL}}
-
-## Success Metrics
-- [ ] Metric 1
-- [ ] Metric 2
-
-## Stories
-<!-- List of child stories -->
-
-## Dependencies
-<!-- Other epics or external dependencies -->
-
-## Notes
-<!-- Additional context, risks, or decisions -->

package/src/core/templates/plan-template.md

@@ -1,125 +0,0 @@
----
-plan_id: {{PLAN_ID}}
-epic: {{EPIC_ID}}
-title: {{TITLE}}
-created: {{CREATED}}
----
-
-# {{TITLE}}
-
-## Overview
-
-{{GOAL}}
-
----
-
-## Phase 1: Foundation (Sequential)
-
-<!-- Stories that must complete before parallel work can begin -->
-<!-- These have no dependencies or are prerequisites for everything else -->
-
-- [ ] {{STORY_ID}}: {{STORY_TITLE}}
-- [ ] {{STORY_ID}}: {{STORY_TITLE}}
-
----
-
-## Phase 2: Features (Parallel-eligible)
-
-<!-- Stories that can run in parallel sessions -->
-<!-- All depend only on Phase 1 completion -->
-
-- [ ] {{STORY_ID}}: {{STORY_TITLE}} (Session A)
-- [ ] {{STORY_ID}}: {{STORY_TITLE}} (Session B)
-- [ ] {{STORY_ID}}: {{STORY_TITLE}} (Session C)
-
----
-
-## Phase 3: Integration (Sequential)
-
-<!-- Stories that depend on Phase 2 completion -->
-<!-- Must wait for parallel work to merge -->
-
-- [ ] {{STORY_ID}}: {{STORY_TITLE}}
-
----
-
-## Deviations Log
-
-<!-- Track decisions that differ from original plan -->
-<!-- Important: Keep this updated so next sessions have context -->
-
-| Date | Phase | Original | Changed To | Reason |
-|------|-------|----------|------------|--------|
-| | | | | |
-
----
-
-## Session Prompts
-
-<!-- Copy-paste prompts for new parallel sessions -->
-<!-- Customize based on specific stories in Phase 2 -->
-
-### Session A prompt:
-```
-Read plan.md in the project root.
-Execute Phase 2 Task A: [TASK DESCRIPTION].
-Phase 1 is complete - foundation is in place.
-Check off tasks in plan.md when done.
-Log any deviations to the Deviations Log section.
-Run tests before marking complete.
-```
-
-### Session B prompt:
-```
-Read plan.md in the project root.
-Execute Phase 2 Task B: [TASK DESCRIPTION].
-Phase 1 is complete - foundation is in place.
-Check off tasks in plan.md when done.
-Log any deviations to the Deviations Log section.
-Run tests before marking complete.
-```
-
-### Session C prompt:
-```
-Read plan.md in the project root.
-Execute Phase 2 Task C: [TASK DESCRIPTION].
-Phase 1 is complete - foundation is in place.
-Check off tasks in plan.md when done.
-Log any deviations to the Deviations Log section.
-Run tests before marking complete.
-```
-
----
-
-## Verification Session
-
-<!-- Keep one terminal dedicated to plan verification -->
-<!-- After each phase, run these checks -->
-
-### Phase completion checks:
-```
-After Phase 1:
-- [ ] All Phase 1 checkboxes checked
-- [ ] Tests passing
-- [ ] No uncommitted changes
-- [ ] Ready to spawn parallel sessions
-
-After Phase 2:
-- [ ] All Phase 2 checkboxes checked
-- [ ] All parallel branches merged
-- [ ] No merge conflicts
-- [ ] Integration tests passing
-
-After Phase 3:
-- [ ] All Phase 3 checkboxes checked
-- [ ] Final tests passing
-- [ ] Ready for review/deploy
-```
-
----
-
-## Notes
-
-<!-- Additional context, risks, or decisions -->
-<!-- Reference ADRs if architectural decisions were made -->
-

package/src/core/templates/preserve-rules-common.md

@@ -1,107 +0,0 @@
-# Common Preserve Rules
-
-This template provides standardized preserve rules that can be injected into command frontmatter.
-Commands reference rule sets using `{{RULES:<category>}}` syntax in their preserve_rules.
-
-## Usage
-
-In command frontmatter:
-```yaml
-compact_context:
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:command-name"
-    - "{{RULES:json_operations}}"
-    - "{{RULES:file_preview}}"
-    - "Command-specific rule here"
-```
-
----
-
-## Rule Categories
-
-### json_operations
-Rules for safe JSON file modifications (status.json, etc.)
-
-```
-- "MUST use Edit tool or jq for JSON operations (never echo/cat > file.json)"
-- "MUST validate JSON after every modification (jq . file.json)"
-```
-
-### file_preview
-Rules for showing previews before writing files
-
-```
-- "MUST show diff preview before confirming writes (diff-first pattern)"
-- "Wait for YES/NO confirmation BEFORE writing any file"
-```
-
-### user_confirmation
-Rules for using AskUserQuestion tool
-
-```
-- "MUST use AskUserQuestion tool for user decisions (not text prompts)"
-- "Options: YES to confirm, NO to cancel, or specific choices"
-```
-
-### task_tracking
-Rules for using Task management tools (TaskCreate, TaskUpdate, TaskList, TaskGet)
-
-```
-- "MUST use TaskCreate for 3+ step workflows, TaskUpdate to mark progress"
-- "Set status: in_progress when starting, completed when done"
-```
-
-### bus_messaging
-Rules for bus message logging
-
-```
-- "MUST append status update to docs/09-agents/bus/log.jsonl"
-- "Bus format: {ts, from, type, story, text} as single-line JSON"
-```
-
-### plan_mode
-Rules for using EnterPlanMode
-
-```
-- "MUST use EnterPlanMode for non-trivial implementation tasks"
-- "Plan first, get approval, then implement"
-```
-
-### commit_approval
-Rules about git commits
-
-```
-- "NEVER auto-commit without explicit user approval"
-- "Always show diff and ask before committing"
-```
-
-### delegation
-Rules for expert delegation
-
-```
-- "Delegate complex work to domain experts (don't do everything yourself)"
-- "Simple task -> do yourself | Complex single-domain -> spawn expert"
-```
-
----
-
-## How Injection Works
-
-The content-injector.js processes preserve_rules arrays and expands
-`{{RULES:category}}` markers into the actual rule strings.
-
-Example:
-```yaml
-# Before injection
-preserve_rules:
-  - "ACTIVE COMMAND: /agileflow:story"
-  - "{{RULES:json_operations}}"
-
-# After injection
-preserve_rules:
-  - "ACTIVE COMMAND: /agileflow:story"
-  - "MUST use Edit tool or jq for JSON operations (never echo/cat > file.json)"
-  - "MUST validate JSON after every modification (jq . file.json)"
-```
-
-This eliminates duplication while maintaining readability.

package/src/core/templates/preserve-rules.json

@@ -1,42 +0,0 @@
-{
-  "json_operations": [
-    "MUST use Edit tool or jq for JSON operations (never echo/cat > file.json)",
-    "MUST validate JSON after every modification (jq . file.json)"
-  ],
-  "file_preview": [
-    "MUST show diff preview before confirming writes (diff-first pattern)",
-    "Wait for YES/NO confirmation BEFORE writing any file"
-  ],
-  "user_confirmation": [
-    "MUST use AskUserQuestion tool for user decisions (not text prompts)",
-    "Options: YES to confirm, NO to cancel, or specific choices"
-  ],
-  "task_tracking": [
-    "MUST use TaskCreate for 3+ step workflows, TaskUpdate to mark progress",
-    "Set status: in_progress when starting, completed when done"
-  ],
-  "bus_messaging": [
-    "MUST append status update to docs/09-agents/bus/log.jsonl",
-    "Bus format: {ts, from, type, story, text} as single-line JSON"
-  ],
-  "plan_mode": [
-    "MUST use EnterPlanMode for non-trivial implementation tasks",
-    "Plan first, get approval, then implement"
-  ],
-  "commit_approval": [
-    "NEVER auto-commit without explicit user approval",
-    "Always show diff and ask before committing"
-  ],
-  "delegation": [
-    "Delegate complex work to domain experts (don't do everything yourself)",
-    "Simple task -> do yourself | Complex single-domain -> spawn expert"
-  ],
-  "research_first": [
-    "Check docs/10-research/ for existing research before starting",
-    "Invoke /agileflow:research:ask if research is missing or stale"
-  ],
-  "status_updates": [
-    "Update docs/09-agents/status.json after each status change",
-    "Valid statuses: ready|in-progress|blocked|in-review|done"
-  ]
-}

package/src/core/templates/proactive-action-spec.md

@@ -1,29 +0,0 @@
-### PROACTIVE ACTION SPECIFICATIONS
-
-This agent performs proactive actions under specific, well-defined conditions. Each action has a clear trigger, detection mechanism, and output format.
-
-**Trigger Types**:
-| Trigger | Detection Mechanism | Example |
-|---------|---------------------|---------|
-| **On Invocation** | Agent is spawned/called | First action when user invokes this agent |
-| **On Story Assignment** | `status.json` shows story with `owner=={AGENT_ID}` | When a story is assigned to this agent |
-| **On Blocker Request** | `bus/log.jsonl` contains request for `{AGENT_ID}` | Another agent requests help |
-| **On Status Change** | Story status changes in `status.json` | Story moves to `in-progress`, `in-review`, etc. |
-
-**Action Execution Pattern**:
-```
-IF [trigger condition detected]
-THEN:
-  1. [Load context - specific files/locations]
-  2. [Analyze/process - specific operations]
-  3. [Output result - specific format]
-  4. [Update state - status.json, bus message]
-```
-
-**Standard Output Formats**:
-- **Status Update**: `{"ts":"<ISO>","from":"{AGENT_ID}","type":"status","story":"<US_ID>","text":"<summary>"}`
-- **Blocked Notice**: `{"ts":"<ISO>","from":"{AGENT_ID}","type":"blocked","story":"<US_ID>","text":"Blocked: <reason>"}`
-- **Unblock Notice**: `{"ts":"<ISO>","from":"{AGENT_ID}","type":"unblock","story":"<US_ID>","text":"Unblocking <target_story>: <reason>"}`
-- **Finding/Alert**: `{"ts":"<ISO>","from":"{AGENT_ID}","type":"finding","story":"<US_ID>","text":"Finding: <details>"}`
-
-**DO NOT** perform proactive actions without a clear trigger. Vague instructions like "proactively do X" require explicit conditions to be actionable.