/help

Display a comprehensive overview of the AgileFlow system, folder structure, key concepts, and all available commands.

Quick Start

Copy/agileflow:help

Shows the complete AgileFlow system overview with no arguments required.

Parameters

This command takes no parameters - it automatically displays the full system overview.

What It Displays

The help command provides a one-screen overview of:

1. Folder Map

Shows the documentation structure and what lives where:

2. Core Concepts

Explains key AgileFlow concepts:

• Epics: Large features broken into stories
• Stories: Individual work items with acceptance criteria
• ADRs: Architecture Decision Records documenting design decisions
• status.json: Central status tracking file with story progress
• bus/log.jsonl: Agent communication log

3. Daily Workflow

Describes the typical development flow:

1. Pick story from status.json
2. Implement to acceptance criteria
3. Write and run tests
4. Create pull request
5. Update story status

WIP Limit: Maximum 2 stories per agent at once.

4. All Available Commands

Lists 40+ AgileFlow commands organized by category:

• Planning: epic, story, sprint, deps, auto
• Tracking: status, board, blockers, metrics, velocity
• Development: babysit, verify, review, pr, impact
• Operations: ci, deploy, changelog, packages, tests
• Documentation: adr, docs, readme-sync, research, context
• Collaboration: assign, handoff, update, retro, feedback
• Advanced: multi-expert, agent, configure, diagnose, validate-expertise

Example Output

Copy========================================
AGILEFLOW SYSTEM OVERVIEW
========================================
 
📁 FOLDER MAP
├── 00-meta/          Metadata, config
├── 01-brainstorming/ Ideas & proposals
├── 02-practices/     Your practices
├── 03-decisions/     Architecture decisions
├── 04-architecture/  System design docs
├── 05-epics/         Feature epics
├── 06-stories/       User stories
├── 07-testing/       Test documentation
├── 08-project/       Project management
├── 09-agents/        Status & comms
└── 10-research/      Research notes
 
📊 KEY CONCEPTS
- Epics: Large features (EP-0001)
- Stories: Individual work (US-0001)
- ADRs: Design decisions (ADR-0001)
- status.json: Progress tracking
- bus/log.jsonl: Agent communication
 
⚙️ DAILY WORKFLOW
1. Pick story from status.json
2. Implement to acceptance criteria
3. Write and run tests
4. Create pull request
5. Update story status
⚠️ WIP Limit: Max 2 stories/agent
 
📋 COMMANDS (40+)
 
PLANNING
  /epic        Create feature epic with stories
  /story       Create user story with AC
  /sprint      Data-driven sprint planning
  /deps        Visualize dependency graph
  /auto        Auto-generate stories from spec
 
TRACKING
  /status      Update story status
  /board       Visual kanban board
  /blockers    Track and resolve blockers
  /metrics     Analytics dashboard
  /velocity    Track velocity and forecast
 
DEVELOPMENT
  /babysit     Interactive mentor
  /verify      Run tests and update status
  /review      AI-powered code review
  /pr          Generate PR description
  /impact      Analyze change impact
 
[... more commands ...]
 
========================================

Usage Patterns

Use the help command when:

• New to AgileFlow: Get complete system overview
• Forgot a command: Quick command reference
• Onboarding team members: Explains system structure
• Need quick reference: One-screen overview of everything

Command Categories

Planning Commands

Create and organize work:

• epic - Create epics with stories
• story - Create individual stories
• sprint - Sprint planning with forecasting
• deps - Dependency visualization
• auto - Auto-generate stories

Tracking Commands

Monitor progress:

• status - Update story status
• board - Kanban board view
• blockers - Blocker tracking
• metrics - Analytics
• velocity - Velocity tracking

Development Commands

Implement features:

• babysit - Interactive mentor
• verify - Test runner
• review - Code review
• pr - PR generator
• impact - Impact analysis

Operations Commands

DevOps and releases:

• ci - CI/CD setup
• deploy - Deployment pipeline
• changelog - Auto-changelog
• packages - Dependency management
• tests - Test infrastructure

Documentation Commands

Maintain docs:

• adr - Architecture decisions
• docs - Doc synchronization
• readme-sync - README sync
• research - Research notes
• context - Context export

Collaboration Commands

Team coordination:

• assign - Assign stories
• handoff - Document handoffs
• update - Progress reports
• retro - Retrospectives
• feedback - Collect feedback

Advanced Commands

Complex tasks:

• multi-expert - Deploy multiple experts
• agent - Onboard agents
• configure - Configure features
• diagnose - System diagnostics
• validate-expertise - Validate expertise

WIP Limit

AgileFlow enforces a maximum of 2 stories per agent to:

• Reduce context switching
• Improve focus and quality
• Enable better collaboration
• Prevent bottlenecks

Check /board to see current WIP counts.

Daily Workflow Example

Copy1. CHECK STATUS
   /status --filter=assigned
 
2. PICK NEXT STORY
   Story: US-0042 (3 points)
   AC: Write unit tests for auth module
 
3. IMPLEMENT
   - Create test file
   - Write test cases
   - Run tests locally
 
4. VERIFY
   /verify STORY=US-0042
 
5. CREATE PR
   /pr STORY=US-0042
 
6. UPDATE STATUS
   /status STORY=US-0042 STATUS=in-review

Finding Specific Commands

If you need help with a specific command:

Copy# Example: Get help for /story command
/agileflow:story --help

Or visit the commands documentation for detailed guides on each command.

Related Commands

• /story - Create user stories
• /epic - Create epics
• /status - Update story status
• /board - View kanban board
• /diagnose - System diagnostics
• /configure - Configure features