agileflow 2.61.0 → 2.62.0

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

@@ -1,120 +0,0 @@
-# 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

@@ -1,15 +0,0 @@
-#!/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

@@ -1,184 +0,0 @@
----
-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

package/src/core/skills/agileflow-retro-facilitator/SKILL.md

@@ -1,119 +0,0 @@
----
-name: agileflow-retro-facilitator
-description: Structures retrospective discussions using Start/Stop/Continue format with action items and accountability. Loads during retrospective conversations or sprint reviews.
----
-
-# AgileFlow Retro Facilitator
-
-Facilitates sprint retrospectives by structuring feedback, identifying actionable improvements, and tracking action items across sprints.
-
-## When to Use
-
-This skill activates when:
-- Keywords: "retrospective", "retro", "sprint review"
-- Discussing what went well/poorly in a sprint
-- Keywords: "lessons learned", "process improvements", "reflect on..."
-- Gathering team feedback
-- Running sprint reviews
-
-## Variables
-
-- default_format: start-stop-continue
-- track_action_items: true
-- include_metrics: true
-- save_to_docs: true
-
-## Cookbook
-
-Based on the context, select the appropriate retro format:
-
-### Start/Stop/Continue (Default)
-If running a standard sprint retrospective:
-Then read and execute cookbook/start-stop-continue.md
-
-Examples:
-- "run a retro for sprint 5"
-- "sprint retrospective"
-- "what went well this sprint?"
-- "let's do a retro"
-
-### Glad/Sad/Mad
-If discussing team dynamics, emotions, or interpersonal issues:
-Then read cookbook/glad-sad-mad.md
-
-Examples:
-- "the team seems frustrated"
-- "morale is low, let's talk about it"
-- "team dynamics retro"
-- "emotional check-in"
-- "glad sad mad retro"
-
-### 4Ls (Liked, Learned, Lacked, Longed For)
-If focusing on learning and growth:
-Then read cookbook/4ls.md
-
-Examples:
-- "learning retrospective"
-- "what did we learn this sprint?"
-- "growth-focused retro"
-- "4Ls retro"
-- "liked learned lacked longed"
-
-## Workflow
-
-1. Identify which format to use (check user request against Cookbook)
-2. Read the appropriate cookbook file for detailed template
-3. Gather feedback using that format's structure
-4. Create SMART action items (read prompts/action-items.md for guidance)
-5. Document in docs/08-project/retros/
-
-## What This Does
-
-1. Structures retrospective using the selected format
-2. Gathers feedback on what went well and what didn't
-3. Identifies patterns and root causes
-4. Creates SMART action items with owners and due dates
-5. Reviews previous action items
-6. Captures insights for next sprint
-
-## Instructions
-
-1. **Set the stage**:
-   - Review sprint metrics (velocity, completion rate)
-   - Check previous action items
-
-2. **Gather feedback** (using selected format):
-   - Use the cookbook file template
-   - Ensure all voices are heard
-   - Time-box each section
-
-3. **Identify patterns**:
-   - Group similar feedback
-   - Find root causes
-   - Spot recurring themes
-
-4. **Create action items** (see prompts/action-items.md):
-   - Specific, actionable steps
-   - Assign owners
-   - Set due dates
-   - Define success criteria
-
-5. **Document and share**:
-   - Save in `docs/08-project/retros/`
-   - Share with team
-   - Add action items to backlog if needed
-
-## Integration
-
-- **agileflow-sprint-planner**: Retro insights inform next sprint planning
-- **agileflow-tech-debt**: Identifies tech debt to address
-- **agileflow-story-writer**: Improves story writing process
-
-## Notes
-
-- Retros are for the team, not management reporting
-- Psychological safety is critical for honest feedback
-- Action items should be small and achievable
-- Track action item completion rate (target: >80%)
-- Vary retro format to keep it fresh
-- Celebrate wins, don't just focus on problems

package/src/core/skills/agileflow-retro-facilitator/cookbook/4ls.md

@@ -1,86 +0,0 @@
-# 4Ls Retrospective Format
-
-Best for learning-focused retros. Use when emphasizing growth, skill development, or process discovery.
-
-## When to Use
-
-- After learning sprints or experiments
-- When onboarding new team members
-- Quarterly or milestone retros
-- After trying new tools or processes
-- When team wants to focus on growth
-
-## Template
-
-```markdown
-# 4Ls Retrospective
-
-**Date**: YYYY-MM-DD
-**Facilitator**: [Name]
-**Attendees**: [Team members present]
-**Focus**: [Learning theme or milestone]
-
-## Liked (What we enjoyed)
-
-- [Liked 1: Enjoyable aspect of work]
-- [Liked 2: Positive experience]
-- [Liked 3: Successful collaboration]
-
-## Learned (New knowledge or skills)
-
-- [Learned 1: Technical skill acquired]
-- [Learned 2: Process insight]
-- [Learned 3: Team dynamic discovery]
-
-## Lacked (What was missing)
-
-- [Lacked 1: Resource or tool needed]
-- [Lacked 2: Knowledge gap]
-- [Lacked 3: Support or guidance needed]
-
-## Longed For (What we wish we had)
-
-- [Longed 1: Ideal state or tool]
-- [Longed 2: Process improvement]
-- [Longed 3: Future capability]
-
-## Key Learnings to Document
-
-| Learning | Source | How to Apply |
-|----------|--------|--------------|
-| [Learning 1] | [Sprint/Project] | [Next steps] |
-| [Learning 2] | [Sprint/Project] | [Next steps] |
-
-## Action Items
-
-- [ ] **Address [Lacked item]** - @Owner - Due: [Date]
-- [ ] **Move toward [Longed For item]** - @Owner - Due: [Date]
-- [ ] **Document [Learned item]** - @Owner - Due: [Date]
-
-## Knowledge Sharing Plan
-
-- [How will learnings be shared with broader team?]
-- [Documentation to create?]
-- [Training or pairing sessions?]
-```
-
-## Facilitation Notes
-
-**Focus on Growth**:
-- Emphasize that gaps are opportunities, not failures
-- Celebrate learning moments, even from mistakes
-- Connect learnings to future improvements
-
-**Timing**:
-- Liked: 10 minutes
-- Learned: 15 minutes
-- Lacked: 10 minutes
-- Longed For: 10 minutes
-- Action Items: 10 minutes
-- Total: ~55 minutes
-
-**Tips**:
-- "Learned" is the heart of this format - spend time here
-- Turn "Lacked" into specific asks, not complaints
-- "Longed For" should inspire, not depress
-- Create concrete knowledge-sharing actions

package/src/core/skills/agileflow-retro-facilitator/cookbook/glad-sad-mad.md

@@ -1,79 +0,0 @@
-# Glad/Sad/Mad Retrospective Format
-
-Best for emotional topics and team dynamics. Use when morale is low or interpersonal issues need addressing.
-
-## When to Use
-
-- Team seems frustrated or burnt out
-- Recent conflicts or tensions
-- Major changes (team composition, process, tools)
-- After particularly difficult sprints
-- When standard retro feels stale
-
-## Template
-
-```markdown
-# Glad/Sad/Mad Retrospective
-
-**Date**: YYYY-MM-DD
-**Facilitator**: [Name]
-**Attendees**: [Team members present]
-**Context**: [Why using this format]
-
-## Glad (Things that made us happy)
-
-- [Glad 1: Celebration or positive moment]
-- [Glad 2: Something that worked well]
-- [Glad 3: Team success]
-
-## Sad (Things that disappointed us)
-
-- [Sad 1: Unmet expectation]
-- [Sad 2: Missed opportunity]
-- [Sad 3: Something we hoped would go better]
-
-## Mad (Things that frustrated us)
-
-- [Mad 1: Recurring problem]
-- [Mad 2: Blocker or impediment]
-- [Mad 3: Process that isn't working]
-
-## Patterns Identified
-
-- [Pattern 1: Theme across categories]
-- [Pattern 2: Root cause analysis]
-
-## Action Items
-
-- [ ] **[Action 1]** - @Owner - Due: [Date]
-  - Addresses: [Which Sad/Mad item]
-
-- [ ] **[Action 2]** - @Owner - Due: [Date]
-  - Addresses: [Which Sad/Mad item]
-
-## What We Want to Protect
-
-- [Glad item to protect and maintain]
-- [Process or practice to keep]
-```
-
-## Facilitation Notes
-
-**Creating Psychological Safety**:
-- Acknowledge that emotions are valid
-- Focus on situations, not individuals
-- Use "I feel..." statements
-- Allow venting, then redirect to solutions
-
-**Timing**:
-- Glad: 10 minutes
-- Sad: 15 minutes
-- Mad: 15 minutes
-- Action Items: 15 minutes
-- Total: ~60 minutes
-
-**Tips**:
-- Start with Glad to set positive tone
-- Let people express frustration fully before problem-solving
-- End with concrete actions to channel emotions productively
-- Follow up on emotional items in 1:1s if needed