Universal agile/docs-as-code system combining Scrum, Kanban, ADRs, and docs-as-code. Framework-agnostic command pack for managing epics, stories, decisions, research, and multi-agent collaboration with automation features.
This plugin is not yet in any themed marketplace. To install it, you'll need to add it from GitHub directly.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install agileflow@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/agileflow.jsonStep 2: Install the plugin
/plugin install agileflow@agileflowUniversal agile/docs-as-code system for Claude Code. Framework-agnostic command pack combining Scrum, Kanban, ADRs, and docs-as-code principles.
AgileFlow combines three proven methodologies into one cohesive system:
Step 1 - Add the marketplace:
/plugin marketplace add xloxn69/AgileFlow
Step 2 - Install the plugin:
/plugin install AgileFlow
Initialize the system:
/setup-system
This scaffolds the entire docs structure, templates, and optional CI.
During setup, you can optionally enable:
Get help:
/system-help
View the system overview, folder structure, and available commands.
Use the mentor subagent (recommended):
Use the agileflow-mentor subagent to guide me through implementing <your feature>
Interactive mentor that guides you through epic/story creation, implementation, research, and PR preparation.
After running /setup-system, you'll have:
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
04-architecture/ # Architecture docs
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
chatgpt.md # One-page context brief for ChatGPT
/setup-system - Bootstrap the entire system/system-help - Display system overview/babysit - Interactive mentor for end-to-end implementation/epic-new - Create a new epic/story-new - Create a user story with AC/adr-new - Create an Architecture Decision Record/agent-new - Onboard a new agent/assign - Assign/reassign a story/status - Update story status/handoff - Document handoff between agents/pr-template - Generate PR description/ci-setup - Bootstrap CI workflow/readme-sync - Sync folder READMEs/setup-tests - Automated testing infrastructure setup/ai-code-review - AI-powered code review/dependency-update - Track and update dependencies/dependencies-dashboard - Visual dependency overview/docs-sync - Synchronize docs with code changes/impact-analysis - Analyze change impact on codebase/tech-debt - Track and prioritize technical debt/setup-deployment - Automated deployment pipeline setup/generate-changelog - Auto-generate changelog from commits/auto-story - Generate stories from PRDs/mockups/specs/custom-template - Create and manage custom templates/agent-feedback - Collect feedback for continuous improvement/stakeholder-update - Generate stakeholder reports/board - Visual kanban board with WIP limits/velocity - Velocity tracking and forecasting/metrics - Comprehensive analytics dashboard (cycle time, lead time, throughput, flow efficiency)/retro - Automated retrospective generator with insights and action items/dependencies - Dependency graph visualization with critical path and circular dependency detection/github-sync - Bidirectional GitHub Issues sync (uses GitHub MCP - Model Context Protocol)/notion-export - Bidirectional Notion database sync (uses Notion MCP - Model Context Protocol)/chatgpt - Generate ChatGPT context brief/chatgpt-refresh - Refresh context/chatgpt-note - Add note to context/chatgpt-export - Export concise excerpt/chatgpt-research - Build research prompt/research-init - Save research notes/agent-ui - UI/presentation layer agent/agent-api - Services/data layer agent/agent-ci - CI & quality agentAgileFlow includes 8 specialized subagents that operate in separate context windows for focused work:
agileflow-uiUI/Presentation Layer Specialist
owner: AG-UIagileflow-apiServices/Data Layer Specialist
owner: AG-APIagileflow-ciCI/CD & Quality Specialist
owner: AG-CIagileflow-mentorEnd-to-End Implementation Mentor (Replaces /babysit command)
agileflow-epic-plannerEpic & Story Planning Specialist
agileflow-adr-writerArchitecture Decision Record Specialist
agileflow-researchResearch & Knowledge Management Specialist
agileflow-devopsDevOps & Automation Specialist
owner: AG-DEVOPSSubagents operate in separate context windows from the main conversation, allowing:
Use Subagents for:
Use Commands for:
# Planning a feature
User: "I need to add user authentication with JWT"
Claude: "Use the agileflow-epic-planner subagent to plan this feature"
[Subagent creates epic + 5 stories with AC]
# Implementing UI
User: "Use the agileflow-ui subagent to implement US-0001 (login form)"
[Subagent implements component + tests + updates status]
# Documenting decision
User: "Use the agileflow-adr-writer subagent to document why we chose JWT"
[Subagent creates ADR with context, alternatives, consequences]
agileflow-mentor subagent or check docs/09-agents/status.jsondocs/07-testing/test-cases/<STORY_ID>.md/status to track progress/pr-template to generate descriptionAgileFlow uses a message bus (docs/09-agents/bus/log.jsonl) for agent coordination:
docs/09-agents/status.json with their current work/handoff to explicitly transfer work between agentsAgileFlow integrates with Notion using Model Context Protocol (MCP) for standardized tool access:
.mcp.json.example template committed to gitCreate Notion Integration:
ntn_)Enable during system setup:
/setup-system
# Select "yes" for Notion integration
Add your token to MCP config:
# Copy MCP template to active config
cp .mcp.json.example .mcp.json
# Edit .mcp.json and replace "ntn_YOUR_NOTION_TOKEN_HERE" with your actual token
# Notion tokens start with "ntn_"
# CRITICAL: Tokens must be hardcoded in .mcp.json (env var substitution doesn't work)
# Verify .mcp.json is in .gitignore - NEVER commit it!
Restart Claude Code (to load MCP server)
Create Notion databases:
/notion-export MODE=setup
Start syncing:
/notion-export
New team members need to:
.mcp.json.example)cp .mcp.json.example .mcp.json.mcp.json and hardcode their real token (replace placeholder).mcp.json is in .gitignore (NEVER commit it!)/notion-export!.mcp.json (gitignored, never committed).mcp.json.example in git with placeholder)${NOTION_TOKEN}) does NOT work in .mcp.json.mcp.json file.mcp.json MUST be gitignored to prevent token leaks.mcp.json is in .gitignore before committingSee /notion-export command for full documentation.
AgileFlow integrates with GitHub using Model Context Protocol (MCP) for standardized tool access:
gh CLI which requires installation).mcp.json.example template committed to gitCreate GitHub Personal Access Token:
repo (full control), read:org (if using organization repos)ghp_)Enable during system setup:
/setup-system
# Select "yes" for GitHub integration
Add your token to MCP config:
# Copy MCP template to active config
cp .mcp.json.example .mcp.json
# Edit .mcp.json and replace "ghp_YOUR_GITHUB_TOKEN_HERE" with your actual token
# GitHub PATs start with "ghp_"
# CRITICAL: Tokens must be hardcoded in .mcp.json (env var substitution doesn't work)
# Verify .mcp.json is in .gitignore - NEVER commit it!
Restart Claude Code (to load MCP server)
Configure repository:
# Edit docs/08-project/github-sync-map.json
# Set "repository": "owner/repo"
Start syncing:
# Preview first
/github-sync DRY_RUN=true
# Perform sync
/github-sync
New team members need to:
.mcp.json.example)cp .mcp.json.example .mcp.json.mcp.json and hardcode their real token (replace placeholder).mcp.json is in .gitignore (NEVER commit it!)/github-sync!.mcp.json (gitignored, never committed).mcp.json.example in git with placeholder)gh CLI installation).mcp.json${GITHUB_TOKEN}) does NOT work in .mcp.json.mcp.json file.mcp.json MUST be gitignored to prevent token leaks.mcp.json is in .gitignore before committingSee /github-sync command for full documentation.
AgileFlow maintains a single source of truth context file (docs/chatgpt.md) that can be shared with ChatGPT for research and planning:
/chatgpt to generate or refresh the context/chatgpt-export to get a concise excerpt/chatgpt-research to build structured research prompts/research-init/epic-new 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,US-0003|Session management|AG-API"
/assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress NOTE="Starting implementation"
# ... do the work ...
/status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete with tests" PR=https://github.com/...
/adr-new 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"
All templates are located in templates/ and docs/00-meta/templates/:
epic-template.md - Epic structurestory-template.md - User story formatadr-template.md - Architecture decision recordagent-profile-template.md - Agent profile and contractcomms-note-template.md - Handoff documentationresearch-template.md - Research note structureREADME-template.md - Folder README templateThis plugin is designed to be framework-agnostic. Customize templates and commands to fit your team's workflow.
MIT
For issues or questions, please refer to your Claude Code plugin marketplace or repository.
2.4.0