agileflow 2.33.1 → 2.35.0

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2025 AgileFlow Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/README.md

@@ -0,0 +1,536 @@
+<p align="center">
+  <img src="assets/banner.png" alt="AgileFlow" />
+</p>
+
+[![npm version](https://img.shields.io/npm/v/agileflow?color=brightgreen)](https://www.npmjs.com/package/agileflow)
+[![Commands](https://img.shields.io/badge/commands-41-blue)](#commands)
+[![Subagents](https://img.shields.io/badge/subagents-26-orange)](SUBAGENTS.md)
+[![Skills](https://img.shields.io/badge/skills-23-purple)](#skills)
+
+**AI-driven agile development for Claude Code, Cursor, Windsurf, and more.** Combining Scrum, Kanban, ADRs, and docs-as-code principles into one framework-agnostic system.
+
+## Quick Start
+
+### Installation
+
+#### Option 1: Global Installation (Recommended)
+
+```bash
+npm install -g agileflow
+agileflow setup
+```
+
+#### Option 2: Project-Level Installation
+
+```bash
+npm install agileflow
+npx agileflow setup
+```
+
+This will:
+1. Prompt where to install AgileFlow
+2. Prompt to select your IDE(s)
+3. Install AgileFlow core (commands, agents, skills)
+4. Configure your selected IDEs
+5. Create documentation structure
+
+### CLI Commands
+
+**Global installation:**
+```bash
+agileflow setup       # Set up AgileFlow in project
+agileflow status      # Check installation + updates
+agileflow update      # Update to latest version
+agileflow doctor      # Diagnose issues
+agileflow uninstall   # Remove from project
+```
+
+**Project-level installation (use `npx`):**
+```bash
+npx agileflow setup       # Set up AgileFlow in project
+npx agileflow status      # Check installation + updates
+npx agileflow update      # Update to latest version
+npx agileflow doctor      # Diagnose issues
+npx agileflow uninstall   # Remove from project
+```
+
+### After Setup
+
+**Initialize the system:**
+```
+/AgileFlow:setup
+```
+Scaffolds docs structure, templates, and optional CI configuration.
+
+**Get help:**
+```
+/AgileFlow:help
+```
+View system overview and available commands.
+
+**Use the mentor (recommended):**
+```
+Use the mentor subagent to guide me through implementing <feature>
+```
+Interactive mentor guides you through epic/story creation, implementation, and PR preparation.
+
+### Supported IDEs
+
+| IDE | Status | Config Location |
+|-----|--------|-----------------|
+| Claude Code | ✅ Supported | `.claude/commands/AgileFlow/` |
+| Cursor | ✅ Supported | `.cursor/rules/agileflow/` |
+| Windsurf | ✅ Supported | `.windsurf/workflows/agileflow/` |
+
+## Why AgileFlow?
+
+AgileFlow combines three proven methodologies:
+
+- **Agile (Scrum/Kanban)** - Break work into Epics → Stories → Acceptance Criteria with WIP limits
+- **ADRs** - Record architectural decisions so future teams don't re-debate
+- **Docs-as-Code** - Humans and AI agents coordinate via versioned files (traceable, reviewable, automatable)
+
+**Key Benefits:**
+- Clear priorities and testable increments
+- Durable memory and decision history
+- Effortless multi-agent collaboration via message bus
+- Works with any tech stack or framework
+
+<details>
+<summary><strong>📁 Folder Structure</strong> (click to expand)</summary>
+
+After running `/AgileFlow:setup`:
+
+```
+docs/
+  00-meta/             # Templates, glossary, conventions
+  01-brainstorming/    # Ideas and sketches
+  02-practices/        # Testing, git, CI, security practices
+    prompts/agents/    # Agent profiles and contracts
+  03-decisions/        # ADRs (Architecture Decision Records)
+  04-architecture/     # Architecture documentation
+  05-epics/            # Epic definitions
+  06-stories/          # User stories (grouped by epic)
+  07-testing/          # Test cases and acceptance criteria
+  08-project/          # Roadmap, backlog, milestones, risks
+  09-agents/           # Agent status and message bus
+    bus/log.jsonl      # Agent communication log
+    status.json        # Current story statuses
+  10-research/         # Saved research notes
+  context.md           # One-page context brief for web AI tools
+```
+
+</details>
+
+<details>
+<summary><strong>📚 Commands</strong> (41 total - click to expand)</summary>
+
+### Core Workflow
+- `/AgileFlow:setup` - Bootstrap the entire system
+- `/AgileFlow:help` - Display system overview
+- `/AgileFlow:babysit` - Interactive mentor for end-to-end implementation
+
+### Planning & Structure
+- `/AgileFlow:epic` - Create a new epic
+- `/AgileFlow:story` - Create a user story with acceptance criteria
+- `/AgileFlow:story-validate` - Validate story completeness before development
+- `/AgileFlow:sprint` - Data-driven sprint planning with velocity forecasting
+- `/AgileFlow:adr` - Create an Architecture Decision Record
+- `/AgileFlow:agent` - Onboard a new agent
+
+### Task Management
+- `/AgileFlow:assign` - Assign/reassign a story
+- `/AgileFlow:status` - Update story status
+- `/AgileFlow:handoff` - Document handoff between agents
+
+### Quality & CI
+- `/AgileFlow:pr` - Generate PR description
+- `/AgileFlow:ci` - Bootstrap CI workflow
+- `/AgileFlow:readme-sync` - Sync folder READMEs
+- `/AgileFlow:tests` - Automated testing infrastructure setup
+- `/AgileFlow:review` - AI-powered code review
+- `/AgileFlow:verify` - Run tests and update story test status (Session Harness)
+- `/AgileFlow:session-init` - Initialize session harness with test verification (Phase 2)
+- `/AgileFlow:resume` - Resume session with environment verification and context (Phase 2)
+- `/AgileFlow:baseline` - Mark current state as verified baseline (Phase 2)
+- `/AgileFlow:compress` - Compress status.json (fixes token limit issues)
+
+### Automation & DevOps
+- `/AgileFlow:packages` - Manage dependencies (dashboard, updates, security audits)
+- `/AgileFlow:docs` - Synchronize docs with code changes
+- `/AgileFlow:impact` - Analyze change impact on codebase
+- `/AgileFlow:debt` - Track and prioritize technical debt
+- `/AgileFlow:deploy` - Automated deployment pipeline setup
+- `/AgileFlow:changelog` - Auto-generate changelog from commits
+- `/AgileFlow:auto` - Generate stories from PRDs/mockups/specs
+- `/AgileFlow:template` - Create and manage custom templates
+- `/AgileFlow:feedback` - Collect feedback for continuous improvement
+- `/AgileFlow:update` - Generate stakeholder reports
+
+### Visualization & Analytics
+- `/AgileFlow:board` - Visual kanban board with WIP limits
+- `/AgileFlow:blockers` - Comprehensive blocker tracking with resolution suggestions
+- `/AgileFlow:velocity` - Velocity tracking and forecasting
+- `/AgileFlow:metrics` - Analytics dashboard (cycle time, lead time, throughput, flow efficiency)
+- `/AgileFlow:retro` - Automated retrospective generator with insights
+- `/AgileFlow:deps` - Dependency graph visualization with critical path detection
+
+### Web AI Integration
+- `/AgileFlow:context` - Generate/export/manage context for web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.)
+- `/AgileFlow:research` - Save research notes
+
+</details>
+
+<details>
+<summary><strong>🤖 Subagents</strong> (26 specialized agents - click to expand)</summary>
+
+AgileFlow includes **26 specialized subagents** that operate in separate context windows for focused work. See [SUBAGENTS.md](SUBAGENTS.md) for complete documentation.
+
+### Core Implementation Agents
+
+**`ui`** - UI/Presentation Layer Specialist
+- Front-end components, styling, theming, accessibility (WCAG 2.1 AA)
+- Invocation: "Use the ui subagent to implement this UI feature"
+
+**`api`** - Services/Data Layer Specialist
+- Backend APIs, business logic, data models, API tests
+- Invocation: "Use the api subagent to implement this API endpoint"
+
+**`ci`** - CI/CD & Quality Specialist
+- CI/CD pipelines, linting, type checking, test coverage
+- Invocation: "Use the ci subagent to set up the test pipeline"
+
+### Orchestration & Planning Agents
+
+**`mentor`** - End-to-End Implementation Mentor
+- Guides feature implementation from idea to PR
+- Invocation: "Use the mentor subagent to guide me through this feature"
+
+**`epic-planner`** - Epic & Story Planning Specialist
+- Breaks down features into epics and stories with acceptance criteria
+- Invocation: "Use the epic-planner subagent to plan this feature"
+
+**`adr-writer`** - Architecture Decision Record Specialist
+- Documents technical decisions, trade-offs, alternatives
+- Invocation: "Use the adr-writer subagent to document this decision"
+
+**`research`** - Research & Knowledge Management Specialist
+- Conducts technical research, builds research prompts, saves notes
+- Invocation: "Use the research subagent to research authentication approaches"
+
+### Additional Specialized Agents
+- `devops` - DevOps & Automation
+- `security` - Security & Compliance
+- `database` - Database & Data Layer
+- `testing` - Testing & QA Automation
+- `product` - Product Management & Prioritization
+- `performance` - Performance Optimization
+- `mobile` - Mobile Development
+- `integrations` - Third-Party Integrations
+- `refactor` - Code Refactoring & Technical Debt
+- `design` - Design Systems & UI/UX
+- `accessibility` - Accessibility Compliance (WCAG)
+- `analytics` - Analytics & Metrics Implementation
+- `datamigration` - Data Migration & ETL
+- `qa` - Quality Assurance & Test Planning
+- And more...
+
+**When to Use Subagents:**
+- Complex, multi-step implementation work
+- Specialized tasks requiring focused expertise
+- Work benefiting from separate context
+- Tasks needing to run commands or write code
+
+**When to Use Commands:**
+- Quick, single-purpose actions
+- Status updates and assignments
+- Generating templates or prompts
+- Simple file operations
+
+</details>
+
+<details>
+<summary><strong>🎯 Skills</strong> (23 auto-loaded skills - click to expand)</summary>
+
+Skills are **context-aware helpers** that activate automatically based on keywords (no manual invocation needed).
+
+### How Skills Work
+- **Activation:** Automatic (keyword-based detection)
+- **Context:** Main conversation
+- **Purpose:** Quick enhancements and formatting
+- **Structure:** Follow Anthropic's minimal specification (v2.21.0+)
+
+### Skills by Category
+
+#### AgileFlow Skills (8 skills)
+Auto-formatted outputs following AgileFlow templates:
+- `agileflow-story-writer` - Converts discussions to user stories
+- `agileflow-acceptance-criteria` - Generates Given/When/Then AC
+- `epic-planner` - Breaks features into epics/stories
+- `agileflow-sprint-planner` - Plans sprints with velocity
+- `agileflow-retro-facilitator` - Structures retrospectives
+- `agileflow-adr` - Captures architectural decisions
+- `agileflow-commit-messages` - Formats Conventional Commits
+- `agileflow-tech-debt` - Tracks technical debt
+
+#### Template Generators (15 skills)
+Generate code templates and documentation:
+- `story-skeleton` - Story template scaffolding
+- `acceptance-criteria-generator` - AC formatting
+- `commit-message-formatter` - Git commit messages
+- `adr-template` - Architecture decision records
+- `api-documentation-generator` - OpenAPI/Swagger docs
+- `changelog-entry` - Keep a Changelog format
+- `pr-description` - Pull request descriptions
+- `test-case-generator` - Test cases from AC
+- `type-definitions` - TypeScript interfaces
+- `sql-schema-generator` - SQL schemas with migrations
+- `error-handler-template` - Error handling patterns
+- `diagram-generator` - Mermaid/ASCII diagrams
+- `validation-schema-generator` - Joi/Zod/Yup schemas
+- `deployment-guide-generator` - Deployment runbooks
+- `migration-checklist` - Data migration checklists
+
+### Example Activation
+```
+User: "I need to create a user story for login functionality"
+[agileflow-story-writer skill activates automatically]
+Claude: Generates formatted story with AC, owner, priority, estimate
+```
+
+</details>
+
+<details>
+<summary><strong>🎯 Hooks System</strong> (event-driven automation - click to expand)</summary>
+
+AgileFlow supports **event-driven automation** through Claude Code's official hooks system.
+
+### What Are Hooks?
+
+Hooks are automatic triggers that execute commands in response to events:
+- **SessionStart** - Runs when Claude Code session starts
+- **UserPromptSubmit** - Runs after you submit a prompt
+- **Stop** - Runs when Claude stops responding
+
+### Quick Setup
+
+1. **Create .claude directory:**
+   ```bash
+   mkdir -p .claude
+   ```
+
+2. **Copy template:**
+   ```bash
+   cp templates/claude-settings.example.json .claude/settings.json
+   ```
+
+3. **Customize hooks** (edit `.claude/settings.json`):
+   ```json
+   {
+     "hooks": {
+       "SessionStart": [{
+         "hooks": [{
+           "type": "command",
+           "command": "echo '🚀 AgileFlow loaded - Type /AgileFlow:help'"
+         }]
+       }]
+     }
+   }
+   ```
+
+4. **Restart Claude Code**
+
+### Example Use Cases
+
+**Welcome message:**
+```json
+{
+  "SessionStart": [{
+    "hooks": [{
+      "type": "command",
+      "command": "echo '👋 Welcome! Current sprint: $(cat docs/08-project/current-sprint.txt)'"
+    }]
+  }]
+}
+```
+
+**Activity logging:**
+```json
+{
+  "UserPromptSubmit": [{
+    "hooks": [{
+      "type": "command",
+      "command": "echo '[LOG] Prompt at $(date)' >> .claude/activity.log"
+    }]
+  }]
+}
+```
+
+### Configuration Files
+- `.claude/settings.json` - Project-level config (committed to git)
+- `.claude/settings.local.json` - User-specific overrides (gitignored)
+
+</details>
+
+<details>
+<summary><strong>🔧 Advanced Topics</strong> (click to expand)</summary>
+
+### Daily Workflow
+
+1. **Pick a story** - Use `mentor` or check `docs/09-agents/status.json`
+2. **Implement to AC** - Follow acceptance criteria
+3. **Write tests** - Reference `docs/07-testing/test-cases/<STORY_ID>.md`
+4. **Update status** - Use `/AgileFlow:status`
+5. **Create PR** - Use `/AgileFlow:pr`
+6. **Mark done** - Update status after merge
+
+### Multi-Agent Collaboration
+
+AgileFlow uses a message bus (`docs/09-agents/bus/log.jsonl`) for coordination:
+- Agents update `docs/09-agents/status.json` with current work
+- Messages logged to bus for async communication
+- Use `/AgileFlow:handoff` to transfer work between agents
+- WIP limit: max 2 stories per agent
+
+### Git Worktrees for Context Preservation
+
+For advanced users handling urgent hotfixes during feature work:
+
+**Benefits:**
+- Preserve AI context when switching tasks
+- Handle production bugs without losing feature flow
+- Compare implementations side-by-side
+- Test risky refactors in isolation
+
+**Quick Start:**
+```bash
+# Use helper script (created by /AgileFlow:setup)
+./docs/00-meta/scripts/worktree-create.sh auth-hotfix
+
+# Open in new window
+code ../myapp-auth-hotfix
+/AgileFlow:babysit
+```
+
+See `docs/00-meta/guides/worktrees.md` for comprehensive guide.
+
+### Web AI Integration
+
+Share context with web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.):
+
+1. Run `/AgileFlow:context` to generate/refresh context
+2. Use `/AgileFlow:context MODE=export` for concise excerpt
+3. Paste into web AI tool for research/ideation
+4. Use `/AgileFlow:context MODE=research TOPIC="..."` for structured prompts
+5. Save results with `/AgileFlow:research`
+
+### Session Harness System (v2.24.0+)
+
+Ensures test verification and session continuity for long-running projects. Prevents agents from breaking functionality and maintains progress across context windows.
+
+**The Problem:**
+Without verification, agents can:
+- Break existing functionality without noticing
+- Claim features work when tests fail
+- Lose context between sessions
+- Mark incomplete work as finished
+
+**The Solution:**
+Session Harness System tracks test status, verifies baselines, and maintains session state.
+
+**Quick Start:**
+```bash
+# First time setup (interactive)
+/AgileFlow:session-init
+
+# Start each session (or auto-run via hook)
+/AgileFlow:resume
+
+# Run tests and update test status
+/AgileFlow:verify
+
+# Create verified checkpoint
+/AgileFlow:baseline "Sprint 12 complete"
+```
+
+**How It Works:**
+1. **Test Tracking**: Every story has `test_status` field (passing/failing/not_run)
+2. **Pre-Implementation**: Agents check test_status before starting work
+3. **Post-Implementation**: Agents run `/AgileFlow:verify` before marking complete
+4. **Session Resume**: Loads context and detects regressions
+5. **Baselines**: Git tags mark known-good states for reset points
+
+**Benefits:**
+- **No Broken Baselines**: Agents can't mark stories complete with failing tests
+- **Fail Fast**: Catch regressions immediately, not at PR review
+- **Context Continuity**: Structured handoff between sessions
+- **Regression Detection**: Alerts when tests were passing, now failing
+
+**Agent Integration (v2.26.0):**
+All 18 dev agents now include verification protocol:
+- ui, api, ci, devops
+- security, database, testing
+- performance, mobile, integrations
+- refactor, design, accessibility
+- analytics, datamigration, monitoring
+- compliance, qa
+
+**Learn More:** See CLAUDE.md "Session Harness System" section for complete documentation.
+
+### Status.json Compression
+
+Prevent "file too large" errors:
+
+```bash
+# Compress status.json (removes verbose fields)
+/AgileFlow:compress
+
+# Typical result: 80-90% size reduction
+```
+
+Full story content remains in `docs/06-stories/` markdown files (no data loss).
+
+</details>
+
+## Examples
+
+### Creating an Epic with Stories
+```
+/AgileFlow:epic EPIC=EP-0001 TITLE="User Authentication" OWNER=AG-API GOAL="Secure user login and registration" STORIES="US-0001|Login form|AG-UI,US-0002|Auth API|AG-API"
+```
+
+### Working on a Story
+```
+/AgileFlow:assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress NOTE="Starting implementation"
+# ... do the work ...
+/AgileFlow:status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete with tests" PR=https://github.com/...
+```
+
+### Recording a Decision
+```
+/AgileFlow:adr NUMBER=0001 TITLE="Use JWT for authentication" CONTEXT="Need stateless auth for API" DECISION="JWT with 15min access + refresh tokens" CONSEQUENCES="Simpler scaling but requires token refresh flow"
+```
+
+## Templates
+
+All templates are located in `templates/` and `docs/00-meta/templates/`:
+
+- `epic-template.md` - Epic structure
+- `story-template.md` - User story format
+- `adr-template.md` - Architecture decision record
+- `agent-profile-template.md` - Agent profile and contract
+- `comms-note-template.md` - Handoff documentation
+- `research-template.md` - Research note structure
+- `README-template.md` - Folder README template
+
+## Contributing
+
+This plugin is designed to be framework-agnostic. Customize templates and commands to fit your team's workflow.
+
+## License
+
+MIT
+
+## Support
+
+For issues or questions, please visit the [GitHub repository](https://github.com/projectquestorg/AgileFlow).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agileflow",
-  "version": "2.33.1",
+  "version": "2.35.0",
   "description": "AI-driven agile development system for Claude Code, Cursor, Windsurf, and more",
   "keywords": [
     "agile",

package/src/core/agents/adr-writer.md

@@ -71,10 +71,6 @@ SLASH COMMANDS (Proactive Use)
 **Research**:
 - `/AgileFlow:context MODE=research TOPIC=...` → Generate research for alternatives before writing ADR
 
-**External Sync** (if enabled):
-- `/AgileFlow:notion DATABASE=adrs` → Sync new ADR to Notion
-- `/AgileFlow:github-sync` → Sync to GitHub
-
 RESEARCH INTEGRATION
 
 **Before Writing ADR**:
@@ -87,14 +83,6 @@ RESEARCH INTEGRATION
 - Reference research note in ADR "References" section
 - Link ADR back to research note
 
-NOTION/GITHUB AUTO-SYNC (if enabled)
-
-**Always sync after**:
-- Creating new ADR → `/AgileFlow:notion DATABASE=adrs`
-- Updating ADR status (Deprecated, Superseded) → Re-sync
-
-**Why**: ADRs guide implementation. Stakeholders need visibility into architectural decisions.
-
 WORKFLOW
 1. **[KNOWLEDGE LOADING]** Before writing:
    - Check docs/10-research/ for relevant research (or invoke `/AgileFlow:context MODE=research`)
@@ -114,10 +102,7 @@ WORKFLOW
 5. Show preview (diff-first, YES/NO)
 6. Create docs/03-decisions/adr-<NUMBER>-<slug>.md
 7. Update docs/03-decisions/README.md (add entry to table)
-8. **[CRITICAL]** Immediately sync to external systems:
-   - Invoke `/AgileFlow:notion DATABASE=adrs` (if Notion enabled)
-   - Invoke `/AgileFlow:github-sync` (if GitHub enabled)
-9. Notify user: "ADR-<NUMBER> created and synced to Notion/GitHub."
+8. Notify user: "ADR-<NUMBER> created."
 
 ADR TEMPLATE STRUCTURE
 ```markdown
@@ -197,14 +182,13 @@ FIRST ACTION
 1. Read docs/03-decisions/README.md → Get next ADR number (sequential)
 2. Check docs/10-research/ → Look for research supporting the decision
 3. Scan recent ADRs → Identify related decisions
-4. Check .mcp.json → Determine if Notion/GitHub sync is enabled
 
 **Then Output**:
 1. ADR context: "Next ADR: ADR-<NUMBER>, recent decisions: <list of last 3 ADRs>"
 2. If research exists: "Found research: <topic> (docs/10-research/<file>)"
 3. If no research: "No research found. I can invoke `/AgileFlow:context MODE=research` to gather alternatives."
 4. Ask: "What technical decision would you like to document?"
-5. Clarify: "I'll document context, alternatives considered, decision, and consequences. Syncs to Notion/GitHub."
+5. Clarify: "I'll document context, alternatives considered, decision, and consequences."
 
 **After User Describes Decision**:
 1. Clarify context (why now? what forces?)
@@ -212,4 +196,4 @@ FIRST ACTION
 3. Identify 2-5 alternatives with pros/cons
 4. Propose ADR structure (show preview)
 5. Get approval (YES/NO)
-6. Create ADR + update README + sync to Notion/GitHub
+6. Create ADR + update README