agileflow 2.30.0

package/src/core/commands/feedback.md

@@ -0,0 +1,307 @@
+---
+description: Collect and process agent feedback
+allowed-tools: Bash, Read, Edit, Write, Glob, Grep
+---
+
+# agent-feedback
+
+Collect feedback from agents and humans for continuous process improvement.
+
+## Prompt
+
+ROLE: Feedback Collector & Retrospective Facilitator
+
+OBJECTIVE
+Gather feedback on story completion, agent performance, and process effectiveness for continuous improvement.
+
+INPUTS (optional)
+- SCOPE=story|epic|sprint (default: story - feedback on single story)
+- STORY=<US_ID> (required if SCOPE=story)
+- EPIC=<EP_ID> (required if SCOPE=epic)
+- ANONYMOUS=yes|no (default: no)
+
+FEEDBACK TYPES
+
+### 1. Story Completion Feedback
+After marking story as "done", prompt for:
+```markdown
+## Story Feedback: <US_ID>
+
+**Completed by**: <agent or human>
+**Date**: <ISO timestamp>
+
+### Definition of Ready (1-5 scale)
+- Were acceptance criteria clear? (1=very unclear, 5=crystal clear): ___
+- Were dependencies resolved? (1=many blockers, 5=no issues): ___
+- Was estimate accurate? (1=way off, 5=spot on): ___
+
+### Implementation Process (1-5 scale)
+- How smooth was implementation? (1=many obstacles, 5=smooth): ___
+- Were tests adequate? (1=missing, 5=comprehensive): ___
+- Was documentation sufficient? (1=inadequate, 5=excellent): ___
+
+### What Went Well? (2-3 bullets)
+-
+-
+-
+
+### What Could Be Improved? (2-3 bullets)
+-
+-
+-
+
+### Blockers Encountered? (if any)
+-
+
+### Learning/Insights? (optional)
+-
+```
+
+### 2. Agent Performance Feedback
+Track agent effectiveness:
+```markdown
+## Agent Feedback: <AGENT_ID>
+
+**Time Period**: <start> to <end>
+**Stories Completed**: X
+**Stories Blocked**: Y
+**Avg Completion Time**: Z days
+
+### Strengths (observed patterns)
+- Consistently writes thorough tests
+- Updates status.json reliably
+- Good at identifying edge cases
+
+### Areas for Improvement
+- Sometimes skips accessibility checks
+- Could improve commit message clarity
+
+### Recommendations
+- Add accessibility checklist to workflow
+- Review Conventional Commits guide
+```
+
+### 3. Epic Retrospective
+After epic completion:
+```markdown
+## Epic Retrospective: <EP_ID>
+
+**Completed**: <ISO timestamp>
+**Duration**: X days (estimated: Y days)
+**Stories**: X completed, Y blocked, Z punted
+
+### Success Metrics (from epic definition)
+- [ ] Goal 1: <status>
+- [ ] Goal 2: <status>
+
+### What Went Well?
+-
+-
+
+### What Didn't Go Well?
+-
+-
+
+### Surprises/Learnings?
+-
+-
+
+### Actions for Next Epic
+- [ ] Action 1
+- [ ] Action 2
+```
+
+### 4. Sprint Retrospective
+After sprint/iteration:
+```markdown
+## Sprint Retrospective: Sprint <N>
+
+**Dates**: <start> to <end>
+**Velocity**: X stories completed
+**Team**: <list of agents/humans>
+
+### Continue (keep doing)
+-
+-
+
+### Stop (no longer useful)
+-
+-
+
+### Start (new practices)
+-
+-
+
+### Experiments (try next sprint)
+-
+-
+
+### Blockers Removed This Sprint
+-
+-
+
+### Recurring Issues (need addressing)
+-
+-
+```
+
+COLLECTION WORKFLOW
+
+1. Auto-prompt at trigger points:
+   - Story status → done
+   - Epic 100% complete
+   - Sprint end date reached
+
+2. Present feedback form with pre-filled context
+
+3. Ask: "Provide feedback now? (YES/NO/LATER)"
+   - YES: Collect feedback interactively
+   - NO: Skip (not required)
+   - LATER: Add reminder to docs/09-agents/bus/log.jsonl
+
+4. Save feedback to:
+   - docs/08-project/feedback/<YYYYMMDD>-<US_ID or EP_ID>.md
+   - Append summary to docs/08-project/retrospectives.md
+
+ANALYSIS
+
+### Patterns & Insights
+Scan all feedback for patterns:
+- Stories with "unclear AC" → Improve story template
+- "Blocked by missing tests" → Enforce test stubs earlier
+- "Estimate off by 2x" → Revise estimation guide
+
+### Metrics Tracking
+Track over time:
+- Avg story clarity score (target: >4.0)
+- Avg estimate accuracy (target: within 50%)
+- Blocker frequency (target: <20% of stories)
+
+### Agent Performance
+Per agent:
+- Completion rate
+- Test coverage avg
+- Status update reliability
+- Feedback sentiment
+
+ACTIONABLE OUTPUTS
+
+### Improvement Stories
+Auto-generate stories for recurring issues:
+```
+Issue: 5 stories in last sprint had "unclear AC" (score <3)
+Suggested story: "US-XXXX: Improve story template with AC examples"
+
+Issue: Estimates consistently off by 2x for API stories
+Suggested ADR: "ADR-XXXX: Update estimation guidelines for backend work"
+```
+
+### Recognition
+Celebrate wins:
+```
+🎉 AG-UI completed 8 stories this sprint with 100% test coverage!
+🎉 AG-API reduced avg completion time from 2.1d to 1.6d
+```
+
+### Process Changes
+Suggest concrete improvements:
+```
+Pattern detected: Stories with test stubs created upfront (by epic-planner)
+have 40% fewer blockers.
+
+Recommendation: Always create test stubs with /story-new.
+```
+
+RETROSPECTIVE REPORT
+```markdown
+# Retrospective Summary
+
+**Period**: <start> to <end>
+**Stories Reviewed**: X
+**Epics Reviewed**: Y
+
+---
+
+## Overall Sentiment
+📈 Improving: AC clarity (4.2 → 4.5)
+📉 Declining: Estimate accuracy (85% → 78%)
+➡️ Stable: Test coverage (avg 87%)
+
+---
+
+## Top Wins 🎉
+1. Zero critical bugs this sprint
+2. All security stories completed on time
+3. Improved docs sync (100% of PRs had doc updates)
+
+---
+
+## Top Challenges ⚠️
+1. Dependencies blocking 3 stories
+2. Estimates off for DB migration work
+3. Flaky E2E tests caused delays
+
+---
+
+## Actions for Next Iteration
+- [ ] Review estimation guide for DB work (assign: EPIC-PLANNER)
+- [ ] Fix flaky tests (assign: AG-CI, priority: high)
+- [ ] Improve dependency tracking in story planning
+
+---
+
+## Insights & Learning
+- Smaller stories (<1d) have 50% fewer blockers
+- Pairing AG-UI and AG-API on complex features reduces handoff issues
+- Weekly debt reviews prevent accumulation
+```
+
+INTEGRATION
+
+### Story Creation
+If feedback reveals issues, offer to create stories:
+```
+Feedback indicates: Test coverage inadequate for 3 stories
+
+Create story? (YES/NO)
+→ US-XXXX: Add missing tests for authentication flow
+```
+
+### ADR Creation
+If architectural learnings emerge:
+```
+Learning: Microservices added complexity without clear benefit
+
+Create ADR to document this? (YES/NO)
+→ ADR-XXXX: Revert to modular monolith architecture
+```
+
+### Message Bus
+Log feedback events:
+```json
+{"ts":"2025-10-16T10:00:00Z","type":"feedback","story":"US-0042","clarity":5,"smooth":4,"improved":"Add more examples in AC"}
+```
+
+AUTOMATION
+
+Suggest periodic reminders:
+```
+# In docs/08-project/roadmap.md
+- Every Friday: Sprint retrospective (if applicable)
+- End of epic: Epic retrospective
+- Monthly: Review all feedback for patterns
+```
+
+RULES
+- Feedback is always optional (never block workflow)
+- Keep feedback forms short (<5 min to complete)
+- Focus on actionable insights, not blame
+- Anonymize if requested
+- Share retrospective summaries with team
+- Celebrate wins before discussing challenges
+
+OUTPUT
+- Feedback form (interactive)
+- Saved feedback (markdown)
+- Optional: Retrospective summary
+- Optional: Auto-generated improvement stories

package/src/core/commands/handoff.md

@@ -0,0 +1,33 @@
+---
+description: Document work handoff between agents
+allowed-tools: Bash, Read, Edit, Write, Glob, Grep
+---
+
+# handoff
+
+Document handoff between agents with summary and blockers.
+
+## Prompt
+
+ROLE: Handoff Scribe
+
+TODO LIST TRACKING
+**CRITICAL**: Immediately create a todo list using TodoWrite tool to track handoff documentation:
+```
+1. Parse inputs (STORY, FROM, TO, SUMMARY, BLOCKERS)
+2. Create docs/09-agents/comms/<STORY>-<YYYYMMDD>-handoff.md
+3. Append bus line with type="handoff"
+4. Show preview and wait for YES/NO confirmation
+```
+
+Mark each step complete as you finish it. This ensures nothing is forgotten.
+
+INPUTS
+STORY=<US-ID>  FROM=<id>  TO=<id>
+SUMMARY=<what changed>  BLOCKERS=<optional list>
+
+ACTIONS
+1) Create docs/09-agents/comms/<STORY>-<YYYYMMDD>-handoff.md from comms-note-template.md.
+2) Append bus line type="handoff".
+
+Diff-first; YES/NO.

package/src/core/commands/help.md

@@ -0,0 +1,90 @@
+---
+description: Display AgileFlow system overview and commands
+allowed-tools: Bash, Read, Edit, Write, Glob, Grep
+---
+
+# system-help
+
+Display a concise overview of the AgileFlow system.
+
+## Prompt
+
+ROLE: System Guide
+
+TASK
+Print a concise, one-screen overview:
+- Folder map (docs/*) and what lives where
+- What Epics, Stories, ADRs are; how docs/09-agents/status.json + bus/log.jsonl work
+- Daily flow: Pick story → Implement to AC → Tests → PR → Update status
+- WIP limit: max 2 stories/agent
+- List ALL available commands with one-line examples
+
+<!-- AUTOGEN:COMMAND_LIST:START -->
+<!-- Auto-generated on 2025-12-12. Do not edit manually. -->
+
+**Collaboration:**
+- `/AgileFlow:feedback` - Collect and process agent feedback
+- `/AgileFlow:handoff` - Document work handoff between agents
+- `/AgileFlow:retro` - Generate retrospective with Start/Stop/Continue format
+- `/AgileFlow:update` - Generate stakeholder progress report
+
+**Deployment & Operations:**
+- `/AgileFlow:deploy` - Set up automated deployment pipeline
+- `/AgileFlow:packages` - Manage dependencies with updates and security audits
+
+**Development:**
+- `/AgileFlow:babysit` - Interactive mentor for end-to-end feature implementation
+- `/AgileFlow:baseline` - Mark current state as verified baseline
+- `/AgileFlow:resume` - Resume work with verification and context loading
+- `/AgileFlow:session-init` - Initialize session harness with test verification
+- `/AgileFlow:verify` - Run project tests and update story test status
+
+**Documentation:**
+- `/AgileFlow:adr` - Create an Architecture Decision Record
+- `/AgileFlow:docs` - Synchronize documentation with code changes
+- `/AgileFlow:readme-sync` - Synchronize a folder's README.md with its current contents
+
+**Maintenance:**
+- `/AgileFlow:compress` - Compress status.json by removing verbose fields and keeping only tracking metadata
+- `/AgileFlow:debt` - Track and prioritize technical debt items
+- `/AgileFlow:template` - Create and manage custom document templates
+
+**Other:**
+- `/AgileFlow:blockers` - Track and resolve blockers with actionable suggestions
+- `/AgileFlow:changelog` - Auto-generate changelog from commit history
+- `/AgileFlow:context` - Generate context export for web AI tools
+- `/AgileFlow:impact` - Analyze change impact across codebase
+- `/AgileFlow:pr` - Generate pull request description from story
+
+**Planning & Metrics:**
+- `/AgileFlow:board` - Display visual kanban board with WIP limits
+- `/AgileFlow:deps` - Visualize dependency graph with critical path detection
+- `/AgileFlow:metrics` - Analytics dashboard with cycle time and throughput
+- `/AgileFlow:sprint` - Data-driven sprint planning with velocity forecasting
+
+**Quality & Testing:**
+- `/AgileFlow:ci` - Bootstrap CI/CD workflow with testing and quality checks
+- `/AgileFlow:review` - AI-powered code review with quality suggestions
+- `/AgileFlow:tests` - Set up automated testing infrastructure
+- `/AgileFlow:velocity` - Track velocity and forecast sprint capacity
+
+**Research & Strategy:**
+- `/AgileFlow:research` - Initialize research note with structured template
+
+**Story Management:**
+- `/AgileFlow:assign` - Assign or reassign a story to an owner
+- `/AgileFlow:epic` - Create a new epic with stories
+- `/AgileFlow:status` - Update story status and progress
+- `/AgileFlow:story` - Create a user story with acceptance criteria
+- `/AgileFlow:story-validate` - Validate story completeness before development
+
+**System:**
+- `/AgileFlow:agent` - Onboard a new agent with profile and contract
+- `/AgileFlow:auto` - Auto-generate stories from PRDs, mockups, or specs
+- `/AgileFlow:diagnose` - System health diagnostics
+- `/AgileFlow:help` - Display AgileFlow system overview and commands
+- `/AgileFlow:setup` - Bootstrap entire AgileFlow system in current project
+
+<!-- AUTOGEN:COMMAND_LIST:END -->
+
+OUTPUT: plain markdown only (no file writes)

package/src/core/commands/impact.md

@@ -0,0 +1,204 @@
+---
+description: Analyze change impact across codebase
+allowed-tools: Bash, Read, Edit, Write, Glob, Grep
+---
+
+# impact-analysis
+
+Analyze the impact of code changes on other parts of the codebase.
+
+## Prompt
+
+ROLE: Impact Analyzer
+
+OBJECTIVE
+Identify which files, tests, and features are affected by code changes to prevent regressions.
+
+INPUTS (optional)
+- FILES=<comma-separated paths> (default: auto-detect from git diff)
+- BASE=<base branch> (default: main/master)
+- RUN_TESTS=yes|no (default: yes, if tests found)
+
+DETECTION
+1. Get changed files:
+   ```bash
+   git diff <BASE>...HEAD --name-only
+   ```
+
+2. For each changed file, find:
+   - **Direct imports**: Files that import this file
+   - **Indirect imports**: Files that import files that import this file (2 levels)
+   - **Test files**: Corresponding test files (*\.test\*, *\.spec\*)
+   - **Related stories**: Stories mentioning this file in docs/06-stories/
+
+ANALYSIS METHODS
+
+### Static Analysis (AST parsing)
+- Parse import/require statements
+- Build dependency graph
+- Identify circular dependencies
+- Find dead code (exported but never imported)
+
+### Test Coverage Mapping
+- Read coverage reports (coverage/lcov.info, coverage.json)
+- Map changed lines to test files
+- Identify uncovered changes
+
+### Pattern Matching
+- API routes → API tests
+- Components → Component tests + Storybook stories
+- Services → Service tests + Integration tests
+- Database models → Migration tests
+
+IMPACT REPORT
+```markdown
+# Impact Analysis Report
+
+**Branch**: <BRANCH>
+**Base**: <BASE>
+**Changed Files**: 5
+**Potentially Affected Files**: 23
+**Tests to Run**: 12
+
+## Direct Impacts
+
+### src/api/auth/login.ts (MODIFIED)
+**Type**: API endpoint
+**Changes**: 23 lines modified
+
+**Direct dependents** (3):
+- src/api/auth/index.ts (exports this endpoint)
+- src/middleware/auth.ts (uses login logic)
+- tests/api/auth/login.test.ts (tests this file)
+
+**Indirect dependents** (8):
+- src/app.ts → src/api/auth/index.ts → login.ts
+- src/routes.ts → src/api/auth/index.ts → login.ts
+- [6 more...]
+
+**Related tests**:
+- ✅ tests/api/auth/login.test.ts (exists)
+- ⚠️ tests/integration/auth-flow.test.ts (may need updates)
+- ❌ Missing: E2E test for login flow
+
+**Related stories**:
+- US-0042: Implement JWT authentication (IN-REVIEW)
+
+**Coverage**: 87% (lines 45-52 uncovered)
+
+---
+
+### src/components/LoginForm.tsx (MODIFIED)
+**Type**: UI component
+**Changes**: 15 lines modified
+
+**Direct dependents** (2):
+- src/pages/Login.tsx
+- src/components/AuthModal.tsx
+
+**Related tests**:
+- ✅ tests/components/LoginForm.test.tsx (exists)
+- ⚠️ Accessibility tests not found
+
+**Related stories**:
+- US-0041: Create login form UI (IN-REVIEW)
+
+**Coverage**: 92%
+```
+
+## Breaking Changes Detection
+
+Analyze function signatures and types:
+```
+⚠️ BREAKING CHANGE DETECTED
+
+File: src/api/auth/login.ts
+Function: login()
+
+Before:
+  login(email: string, password: string): Promise<Token>
+
+After:
+  login(credentials: LoginRequest): Promise<AuthResponse>
+
+Affected callers (3):
+- src/middleware/auth.ts:45
+- tests/api/auth/login.test.ts:23
+- tests/integration/auth-flow.test.ts:67
+```
+
+## Test Recommendations
+
+Based on changes, suggest tests to run:
+
+**Critical** (always run):
+- tests/api/auth/login.test.ts (direct test)
+- tests/integration/auth-flow.test.ts (integration)
+
+**Recommended** (affected indirectly):
+- tests/api/users/*.test.ts (uses auth)
+- tests/e2e/login.spec.ts (E2E)
+
+**Optional** (low risk):
+- tests/components/Header.test.tsx (displays user from auth)
+
+ACTIONS (after user review)
+
+1. Show impact summary
+2. Ask: "Run affected tests? (YES/NO)"
+3. If YES:
+   ```bash
+   # Run only affected tests
+   npm test -- tests/api/auth/login.test.ts tests/integration/auth-flow.test.ts
+   ```
+4. If tests fail:
+   - Show failures
+   - Suggest creating story: "US-XXXX: Fix regressions from <change>"
+
+5. If breaking changes detected:
+   - Warn user
+   - Suggest creating ADR if architectural change
+   - Create stories for updating affected callers
+
+INTEGRATION
+
+### CI Optimization
+Suggest optimized CI that only runs affected tests:
+```yaml
+- name: Impact analysis
+  run: npx claude-code /AgileFlow:impact-analysis BASE=main
+
+- name: Run affected tests
+  run: npm test -- $(cat affected-tests.txt)
+```
+
+### Story Updates
+- Update related stories with impact notes
+- Create new stories for regressions or breaking changes
+- Append to bus/log.jsonl: {"type":"impact","affected":23,"tests":12}
+
+VISUALIZATION (optional)
+Generate dependency graph:
+```
+src/api/auth/login.ts
+├── src/api/auth/index.ts
+│   ├── src/app.ts
+│   └── src/routes.ts
+├── src/middleware/auth.ts
+│   └── src/app.ts
+└── tests/api/auth/login.test.ts
+```
+
+RULES
+- Use static analysis when possible (faster than running tests)
+- Prioritize tests by risk (critical path first)
+- Never skip tests for modified files
+- Warn about uncovered changes
+- Suggest creating tests for uncovered code
+- Diff-first for any file modifications
+
+OUTPUT
+- Impact analysis report (markdown)
+- List of affected files and tests
+- Test recommendations (critical/recommended/optional)
+- Optional: Run tests and report results