agileflow 2.30.0

package/src/core/skills/agileflow-commit-messages/reference/bad-examples.md

@@ -0,0 +1,168 @@
+# Bad Commit Message Examples (and How to Fix Them)
+
+## ❌ Too Vague
+
+```
+fix: fix bug
+```
+
+**Problem**: Doesn't explain what bug was fixed
+**Better**:
+```
+fix(auth): prevent session timeout during active use
+
+Fixed bug where user sessions expired after 30 minutes
+even during active usage. Now sessions extend while user
+is interacting with the application.
+
+Fixes #456
+```
+
+## ❌ Wrong Tense
+
+```
+feat: added dark mode
+```
+
+**Problem**: Should be imperative mood ("add" not "added")
+**Better**:
+```
+feat(ui): add dark mode toggle
+
+Implemented dark mode with localStorage persistence
+and system preference detection.
+
+Closes #789
+```
+
+## ❌ Subject Too Long
+
+```
+feat: add a new user profile editing feature that allows users to update their name, email, and profile picture
+```
+
+**Problem**: Subject exceeds 50 characters, should be concise
+**Better**:
+```
+feat(profile): add user profile editing
+
+Users can now update their name, email, and profile
+picture from the settings page. Changes are validated
+server-side and saved to the database.
+
+Closes #123
+```
+
+## ❌ No Type
+
+```
+update README
+```
+
+**Problem**: Missing type prefix
+**Better**:
+```
+docs(readme): add API authentication examples
+
+Added code examples showing how to authenticate API
+requests using JWT tokens.
+```
+
+## ❌ Multiple Unrelated Changes
+
+```
+feat: add login and fix cart bug and update dependencies
+```
+
+**Problem**: Should be 3 separate commits
+**Better**: Split into:
+```
+feat(auth): add user login functionality
+```
+```
+fix(cart): resolve item duplication issue
+```
+```
+chore(deps): update npm packages to latest versions
+```
+
+## ❌ Description of HOW Instead of WHY
+
+```
+fix: changed if statement to switch statement
+```
+
+**Problem**: Describes implementation detail, not the reason
+**Better**:
+```
+refactor(validation): simplify input validation logic
+
+Replaced nested if statements with switch statement
+for better readability and easier maintenance. No
+functional changes.
+```
+
+## ❌ Capitalized Subject
+
+```
+feat: Add Dark Mode Support
+```
+
+**Problem**: Subject should be lowercase
+**Better**:
+```
+feat(ui): add dark mode support
+```
+
+## ❌ Period at End of Subject
+
+```
+fix: resolve login timeout issue.
+```
+
+**Problem**: Subject shouldn't end with period
+**Better**:
+```
+fix(auth): resolve login timeout issue
+
+Increased session timeout from 15 to 30 minutes to
+prevent premature logouts during form filling.
+
+Fixes #567
+```
+
+## ❌ No Context
+
+```
+fix: it works now
+```
+
+**Problem**: Completely uninformative
+**Better**:
+```
+fix(payment): resolve Stripe webhook signature validation
+
+Fixed HMAC signature verification by using raw request
+body instead of parsed JSON. Webhooks now process correctly.
+
+Fixes #890
+```
+
+## ❌ Missing Issue Reference
+
+```
+feat: add two-factor authentication
+
+Implemented TOTP-based 2FA with QR code generation.
+```
+
+**Problem**: Should reference the issue/story
+**Better**:
+```
+feat(auth): add two-factor authentication
+
+Implemented TOTP-based 2FA with QR code generation
+for enhanced account security.
+
+Closes #234, STORY-042
+```

package/src/core/skills/agileflow-commit-messages/reference/good-examples.md

@@ -0,0 +1,120 @@
+# Good Commit Message Examples
+
+## Simple Feature Addition
+
+```
+feat(auth): add password reset via email
+
+Users can now request a password reset link sent to their
+registered email address. The link expires after 1 hour.
+
+Closes #456
+```
+
+## Bug Fix with Context
+
+```
+fix(cart): prevent duplicate items in shopping cart
+
+Fixed race condition where clicking "Add to Cart" rapidly
+could add the same item multiple times. Added debouncing
+and server-side validation.
+
+Fixes #789
+```
+
+## Refactoring with Explanation
+
+```
+refactor(api): extract authentication middleware
+
+Moved authentication logic from individual route handlers
+into reusable middleware. This reduces code duplication
+and makes auth logic easier to maintain and test.
+
+No behavioral changes.
+```
+
+## Breaking Change
+
+```
+feat(api)!: migrate to v2 response format
+
+BREAKING CHANGE: All API endpoints now return data wrapped
+in a standardized envelope format.
+
+Before: { id: 1, name: "..." }
+After: { data: { id: 1, name: "..." }, meta: { version: 2 } }
+
+Migration guide: docs/api-v2-migration.md
+
+Closes #234
+```
+
+## Multiple Related Changes
+
+```
+feat(profile): add profile editing and avatar upload
+
+- Implemented profile form with field validation
+- Added avatar upload with client-side image cropping
+- Created PUT /api/users/:id endpoint
+- Added error handling for file size limits
+- Wrote unit tests for profile update logic
+
+Closes #123, #124
+```
+
+## Documentation
+
+```
+docs(readme): add installation instructions for Docker
+
+Added step-by-step guide for running the application
+in Docker containers, including environment variable
+configuration and volume mounting.
+```
+
+## Performance Improvement
+
+```
+perf(db): add index on user email column
+
+Query performance for user lookup by email improved from
+~500ms to ~5ms. Added composite index on (email, status)
+for common query patterns.
+```
+
+## Dependency Update
+
+```
+chore(deps): upgrade React to v18.2
+
+Updated React and React DOM to latest stable version.
+Migrated deprecated lifecycle methods in UserProfile
+and Dashboard components.
+
+Tested with full E2E suite - all tests passing.
+```
+
+## CI/CD Change
+
+```
+ci(github): add automated dependency updates
+
+Configured Dependabot to create PRs for npm package
+updates weekly. Auto-merge enabled for patch updates
+that pass all tests.
+```
+
+## Revert
+
+```
+revert: feat(payments): add Stripe integration
+
+This reverts commit abc123def456.
+
+Stripe webhook validation is failing in production.
+Reverting to investigate HMAC signature verification
+before re-deploying.
+```

package/src/core/skills/agileflow-commit-messages/scripts/check-attribution.sh

@@ -0,0 +1,15 @@
+#!/bin/bash
+# check-attribution.sh
+# Determines if Claude Code attribution should be added to git commits
+# Returns "yes" if attribution should be added, "no" if it should not
+
+if [ -f CLAUDE.md ]; then
+  if grep -q "DO NOT ADD AI ATTRIBUTION" CLAUDE.md; then
+    echo "no"
+  else
+    echo "yes"
+  fi
+else
+  # Default to adding attribution if no CLAUDE.md exists
+  echo "yes"
+fi

package/src/core/skills/agileflow-epic-planner/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: epic-planner
+description: Breaks down large features into properly-scoped epics with milestones and story groupings. Loads when user describes major features or initiatives.
+---
+
+# AgileFlow Epic Planner
+
+Automatically structures large features or initiatives into epics, breaking them down into logical story groupings and milestones.
+
+## When to Use
+
+This skill activates when:
+- User describes a large feature spanning multiple sprints
+- Discussing a major initiative or project
+- Keywords: "epic", "initiative", "theme", "big feature", "multi-month project"
+- Feature seems too large to be a single story (>13 story points)
+
+## What This Does
+
+1. Detects large feature descriptions
+2. Asks clarifying questions (problem, timeline, success metrics)
+3. Breaks down into logical milestones (MVP, Phase 2, Polish)
+4. Estimates effort and suggests timeline
+5. Creates epic file in docs/05-epics/
+
+## Instructions
+
+1. **Ask clarifying questions**:
+   - "What's the main problem you're solving?"
+   - "Who are the users?"
+   - "What's the timeline/urgency?"
+   - "What defines success?"
+
+2. **Break down into logical chunks**:
+   - Identify milestones (MVP, Phase 2, Polish)
+   - Group related functionality
+   - Ensure each milestone delivers value
+
+3. **Create epic structure**:
+   - Read existing epics for numbering
+   - Write epic file in `docs/05-epics/`
+   - Outline stories (create skeleton, defer details)
+
+4. **Estimate effort**:
+   - Rough story point estimates
+   - Calculate milestone totals
+   - Suggest timeline based on team velocity
+
+## Epic Format
+
+```markdown
+# [EPIC-###] Title
+
+**Status**: PLANNING | ACTIVE | ON_HOLD | COMPLETED
+**Owner**: Product Owner / Team Lead
+**Start Date**: YYYY-MM-DD
+**Target Completion**: YYYY-MM-DD
+**Priority**: P0 | P1 | P2 | P3
+**Business Value**: High | Medium | Low
+
+## Problem Statement
+
+[What problem does this epic solve? Why is it important?]
+
+## Goals and Objectives
+
+- [Goal 1: Specific, measurable outcome]
+- [Goal 2: Business or user metric to improve]
+- [Goal 3: Strategic alignment]
+
+## Success Metrics
+
+- [Metric 1: e.g., 20% increase in user engagement]
+- [Metric 2: e.g., Reduce support tickets by 30%]
+
+## User Stories
+
+### Milestone 1: [Name] (Target: YYYY-MM-DD)
+- [ ] [STORY-###: Title](../06-stories/STORY-###-title.md) - 5 pts
+- [ ] [STORY-###: Title](../06-stories/STORY-###-title.md) - 8 pts
+**Total: 16 story points**
+
+### Milestone 2: [Name] (Target: YYYY-MM-DD)
+- [ ] [STORY-###: Title](../06-stories/STORY-###-title.md) - 5 pts
+- [ ] [STORY-###: Title](../06-stories/STORY-###-title.md) - 8 pts
+**Total: 13 story points**
+
+## Dependencies
+
+- [Dependency 1: What needs to be done first]
+- [Dependency 2: External team dependencies]
+- [Dependency 3: Technical prerequisites]
+
+## Risks and Assumptions
+
+**Risks**:
+- [Risk 1: What could go wrong]
+- [Risk 2: Mitigation plan]
+
+**Assumptions**:
+- [Assumption 1: What we're assuming is true]
+- [Assumption 2: Needs validation]
+
+## Out of Scope
+
+- [What we're explicitly NOT doing in this epic]
+- [Features deferred to future epics]
+
+## Progress Tracking
+
+**Overall Progress**: X / Y stories completed (Z%)
+**Last Updated**: YYYY-MM-DD
+```
+
+## Epic vs Story
+
+**This Should Be an Epic If**:
+- Takes more than 1-2 sprints (>13 story points total)
+- Involves multiple team members or subteams
+- Has distinct phases or milestones
+- Requires coordination across different areas (UI, API, DevOps)
+- Has significant business impact or strategic value
+
+**This Should Be a Story If**:
+- Can be completed in one sprint
+- Single developer can own it
+- Clear, specific acceptance criteria
+- One or two related tasks
+
+## Milestone Planning
+
+- **Milestone 1: MVP** - Core functionality only, simplest path to value
+- **Milestone 2: Feature Complete** - All planned functionality, edge cases handled
+- **Milestone 3: Polish & Optimization** - Performance, UX enhancements, accessibility
+
+## Epic Size Guidelines
+
+- **Small Epic**: 15-30 story points (1-2 sprints)
+- **Medium Epic**: 30-60 story points (2-4 sprints)
+- **Large Epic**: 60-100 story points (4-6 sprints)
+- **Initiative**: >100 story points (break into multiple epics)
+
+## Quality Checklist
+
+Before creating epic:
+- [ ] Problem statement is clear and specific
+- [ ] Goals are measurable
+- [ ] Success metrics defined
+- [ ] At least 2 milestones planned
+- [ ] Stories grouped logically
+- [ ] Dependencies identified
+- [ ] Risks acknowledged with mitigations
+- [ ] Out-of-scope explicitly stated
+
+## Risk Management
+
+**Common Risks**:
+- **Scope creep**: Clearly define out-of-scope items
+- **Technical unknowns**: Spike stories for research
+- **Resource constraints**: Buffer time in estimates
+- **Dependency delays**: Identify critical path early
+
+**Risk Format**:
+```markdown
+**Risks**:
+- **Risk**: Integration with legacy system may be complex
+  **Impact**: High (could delay Milestone 2 by 2 weeks)
+  **Mitigation**: Allocate spike story to investigate (5 pts)
+  **Owner**: Backend Lead
+```
+
+## Integration
+
+- **agileflow-story-writer**: Creates individual stories for the epic
+- **agileflow-sprint-planner**: Assigns stories to sprints
+- **agileflow-adr**: Links architectural decisions made during epic
+
+## Notes
+
+- Epics are living documents - update as you learn
+- Don't over-plan - detail emerges during execution
+- Review epic scope at sprint planning
+- Celebrate milestone completions
+- Link to ADRs for major technical decisions