agileflow 2.61.0 → 2.63.0

package/src/core/skills/agileflow-story-writer/examples/good-story-example.md

@@ -1,63 +0,0 @@
-# [STORY-042] Add Dark Mode Toggle to Settings
-
-**Owner**: AG-UI
-**Status**: TODO
-**Epic**: [EPIC-005] User Experience Improvements
-**Priority**: P2
-**Estimate**: 5 story points
-
-## User Story
-
-As a user who works at night,
-I want to toggle dark mode in the settings,
-So that I can reduce eye strain and improve readability in low-light conditions.
-
-## Acceptance Criteria
-
-### AC1: Settings Toggle Available
-**Given** I am on the settings page
-**When** I navigate to the "Appearance" section
-**Then** I should see a dark mode toggle switch
-
-### AC2: Theme Switches Immediately
-**Given** I am viewing the app in light mode
-**When** I toggle dark mode on
-**Then** the entire UI should switch to dark theme within 200ms
-
-### AC3: Preference Persists
-**Given** I have enabled dark mode
-**When** I close and reopen the application
-**Then** dark mode should still be active
-
-### AC4: System Preference Detection
-**Given** I have not set a preference
-**When** the app loads for the first time
-**Then** it should default to my system's dark mode preference
-
-## Technical Notes
-
-- Use CSS custom properties for theme colors
-- Store preference in localStorage: `theme: 'light' | 'dark' | 'system'`
-- Listen to `prefers-color-scheme` media query for system default
-- Ensure all components support both themes
-- Add transition animations for smooth mode switching
-
-## Testing Strategy
-
-- Test theme switching in all major browsers (Chrome, Firefox, Safari)
-- Verify localStorage persistence across sessions
-- Test system preference detection on different OS
-- Validate WCAG contrast ratios in dark mode
-- Test with keyboard navigation (accessibility)
-
-## Definition of Done
-
-- [ ] Dark mode toggle implemented in settings UI
-- [ ] Theme preference stored in localStorage
-- [ ] All components styled for dark mode
-- [ ] System preference detection working
-- [ ] Unit tests for theme switching logic
-- [ ] E2E tests for toggle interaction
-- [ ] Documentation updated with theme implementation details
-- [ ] Deployed to staging and tested
-- [ ] Accessibility audit passed (WCAG AA)

package/src/core/skills/agileflow-story-writer/templates/story-template.md

@@ -1,44 +0,0 @@
-# [STORY-###] {Title}
-
-**Owner**: {AG-UI | AG-API | AG-CI | AG-DEVOPS}
-**Status**: TODO
-**Epic**: {Link to epic if applicable}
-**Priority**: {P0 | P1 | P2 | P3}
-**Estimate**: {1-13 story points}
-
-## User Story
-
-As a {user type},
-I want to {action/capability},
-So that {benefit/value}.
-
-## Acceptance Criteria
-
-### AC1: {Criterion Name}
-**Given** {initial context/state}
-**When** {action/trigger}
-**Then** {expected outcome}
-
-### AC2: {Another Criterion}
-**Given** {context}
-**When** {action}
-**Then** {outcome}
-
-## Technical Notes
-
-- {Implementation details}
-- {Dependencies}
-- {Risks/Considerations}
-
-## Testing Strategy
-
-- {How to test this story}
-- {Edge cases to verify}
-
-## Definition of Done
-
-- [ ] Code implemented and reviewed
-- [ ] Tests written and passing
-- [ ] Documentation updated
-- [ ] Deployed to staging
-- [ ] Acceptance criteria validated

package/src/core/skills/agileflow-tech-debt/SKILL.md

@@ -1,215 +0,0 @@
----
-name: agileflow-tech-debt
-description: Identifies and tracks technical debt items with impact/effort matrix and prioritization. Loads when discussing code quality, refactoring, or long-term maintenance.
----
-
-# AgileFlow Tech Debt
-
-Identifies, documents, prioritizes, and tracks technical debt using impact/effort matrix and priority scoring to manage debt systematically.
-
-## When to Use
-
-This skill activates when:
-- Discussing code quality, refactoring, maintenance issues
-- Keywords: "tech debt", "needs cleanup", "messy code", "technical debt"
-- Team pain points from retrospectives
-- Developer complaints about specific code areas
-- During code reviews when debt is identified
-
-## What This Does
-
-1. Identifies technical debt from user descriptions
-2. Classifies type (Code Quality, Performance, Security, Maintainability, Testing)
-3. Assesses impact/urgency/effort (1-5 scale)
-4. Calculates priority score: (Impact × Urgency) / Effort
-5. Documents in docs/08-quality/tech-debt.md
-6. Suggests actions (create story for high-priority items)
-
-## Instructions
-
-1. **Identify tech debt** from user description or code analysis:
-   - What specific code/system is problematic?
-   - Why is this debt (not just "messy" but concrete issues)?
-   - What pain does it cause?
-
-2. **Classify type**:
-   - Code Quality | Performance | Security | Maintainability | Testing
-
-3. **Assess dimensions** (1-5 scale):
-   - **Impact**: How much does this hurt us?
-   - **Urgency**: How soon must we fix?
-   - **Effort**: How hard to fix?
-
-4. **Calculate priority score**: (Impact × Urgency) / Effort
-   - Score >10: High Priority (DO NOW)
-   - Score 3-10: Medium Priority (PLAN)
-   - Score <3: Low Priority (LATER)
-
-5. **Document item** in docs/08-quality/tech-debt.md:
-   - ID: TD-### (next sequential number)
-   - Include: Problem, Impact, Proposed Solution, Effort, Priority Score, Status
-
-6. **Suggest actions**:
-   - **High priority (>10)**: Create story via `/agileflow:story`
-   - **Major refactoring**: Document via `/agileflow:adr-new`
-   - **Blocking features**: Update status.json with blocked stories
-
-## Tech Debt Item Template
-
-```markdown
-### [TD-###] Descriptive Title
-
-**Impact**: 1-5 (Low/Medium/High)
-**Urgency**: 1-5 (Low/Medium/High)
-**Effort**: 1-5 (Low <1 sprint / Medium 1-2 sprints / High >2 sprints)
-**Priority Score**: (Impact × Urgency) / Effort = X.X
-**Type**: Code Quality | Performance | Security | Maintainability | Testing
-**Status**: Identified | Planned | In Progress | Resolved
-
-**Problem**:
-[What's wrong? Be specific, not vague.]
-
-**Impact**:
-- [How does this hurt us? Specific pain points]
-- [What can't we do because of this?]
-
-**Proposed Solution**:
-- [What should we do to address this?]
-- [What tools/patterns to use?]
-
-**Estimated Effort**: X story points
-```
-
-## Priority Score Formula
-
-```
-Priority = (Impact × Urgency) / Effort
-
-Impact:  1 (Low), 3 (Medium), 5 (High)
-Urgency: 1 (Low), 3 (Medium), 5 (High)
-Effort:  1 (Low <1 sprint), 3 (Medium 1-2 sprints), 5 (High >2 sprints)
-```
-
-**Examples**:
-- TD-042: (3 × 3) / 1 = 9 (High Priority - duplicate code, easy fix)
-- TD-067: (5 × 5) / 1 = 25 (Critical Priority - slow query, add index)
-- TD-089: (1 × 1) / 5 = 0.2 (Low Priority - minor cleanup, major refactor)
-
-## Impact/Effort Matrix
-
-```
-High Impact,  │ DO NOW │ DO NOW │        │
-Low Effort    │        │        │        │
-              ├────────┼────────┼────────┤
-High Impact,  │ PLAN   │ PLAN   │        │
-Med Effort    │        │        │        │
-              ├────────┼────────┼────────┤
-Low Impact,   │ LATER  │ LATER  │ NEVER  │
-Any Effort    │        │        │        │
-              └────────┴────────┴────────┘
-              Low      Medium    High
-                    EFFORT
-```
-
-## Types of Tech Debt
-
-**Code Quality**: Duplicate code, complex logic, poor naming, missing docs
-- Example: User validation copy-pasted in 8 files
-
-**Performance**: Slow queries, N+1 problems, inefficient algorithms, missing caching
-- Example: Login query takes 500ms due to missing index
-
-**Security**: Outdated dependencies, vulnerable packages, missing auth, insufficient validation
-- Example: Package X has known CVE, needs update
-
-**Maintainability**: Tightly coupled code, missing tests, unclear architecture
-- Example: Module X has 0 tests, 300 LOC
-
-**Testing**: Low coverage, flaky tests, slow suite, missing integration tests
-- Example: Test coverage at 45%, target is 80%
-
-## When to Address Tech Debt
-
-**Continuous** (Every Sprint):
-- Allocate 10-20% of sprint capacity for debt reduction
-- Boy Scout Rule: Leave code cleaner than you found it
-
-**Scheduled** (Quarterly):
-- Tech debt sprint (full sprint dedicated to quality)
-- Major refactoring initiatives
-
-**Opportunistic**:
-- While working on nearby code
-- When adding related features
-- During bug fixes in affected areas
-
-**Strategic**:
-- Before major new features (clean foundation)
-- When debt blocks progress (unblock development)
-- When quality metrics decline
-
-## Tech Debt Metrics
-
-Track in docs/08-quality/tech-debt.md:
-
-```markdown
-## Tech Debt Health (Q4 2025)
-
-**Total Items**: 24 (🔴 6 High, 🟡 11 Medium, 🟢 7 Low)
-**Total Estimated Effort**: 156 story points
-**Resolved This Quarter**: 8 items (42 story points)
-**New This Quarter**: 5 items (18 story points)
-**Net Change**: -3 items (-24 points) ✅ Improving
-```
-
-## Quality Checklist
-
-Before creating tech debt item:
-- [ ] Problem clearly described (specific code/system, not vague)
-- [ ] Impact explained with concrete pain points
-- [ ] Proposed solution is specific and actionable
-- [ ] Effort estimated realistically
-- [ ] Priority score calculated: (Impact × Urgency) / Effort
-- [ ] Type assigned correctly
-- [ ] Owner or responsible team identified
-- [ ] Status set appropriately
-- [ ] TD-### ID is next sequential number
-
-## Priority Tiers
-
-- **🔴 High Priority (score >10)**: DO NOW - High impact, low-medium effort
-- **🟡 Medium Priority (score 3-10)**: PLAN - Mixed impact/effort
-- **🟢 Low Priority (score <3)**: LATER - Low impact or high effort
-
-## Integration
-
-- **agileflow-story**: Convert high-priority debt (>10) to stories
-- **agileflow-adr**: Document major refactoring decisions
-- **agileflow-retro**: Retrospectives surface new tech debt
-- **agileflow-sprint**: Allocate 10-20% sprint capacity for debt reduction
-
-## Preventing Tech Debt
-
-**Best Practices**:
-- Code reviews catch issues early
-- Automated testing prevents regressions (80%+ coverage)
-- Regular refactoring (Boy Scout Rule)
-- Document intentional decisions (ADRs)
-- Allocate time for quality work
-
-**Warning Signs**:
-- Slowing velocity (stories taking longer)
-- Increasing bug rate
-- Developers avoiding certain code
-- Long PR review times
-- New developer onboarding difficulty
-
-## Notes
-
-- Track tech debt, don't let it hide (visibility is key)
-- Make it visible (metrics, reviews)
-- Allocate consistent capacity (10-20% per sprint)
-- Celebrate debt reduction
-- Prevent new debt through code review
-- Balance new features with quality
-- Not all "ugly code" is debt - document intentional trade-offs as ADRs

package/src/core/skills/api-documentation-generator/SKILL.md

@@ -1,65 +0,0 @@
----
-name: api-documentation-generator
-description: Generate OpenAPI/Swagger documentation with request/response schemas
----
-
-# api-documentation-generator
-
-Generate OpenAPI/Swagger snippets with proper schemas.
-
-## Activation Keywords
-- "API doc", "OpenAPI", "Swagger", "endpoint docs", "endpoint documentation"
-
-## When to Use
-- Documenting REST API endpoints
-- Creating OpenAPI/Swagger specifications
-- Need endpoint documentation with request/response examples
-
-## What This Does
-Generates OpenAPI 3.0 specification snippets including:
-- **Endpoint path and method** (GET, POST, etc.)
-- **Summary and description**
-- **Request body** with schema and examples
-- **Response schemas** (success and error cases)
-- **Parameters** (query, path, header)
-- **Authentication** requirements
-- **Status codes** and descriptions
-
-Coordinates with documentation agent for full API docs.
-
-## Output
-OpenAPI YAML/JSON snippet ready for integration into spec
-
-## Example Activation
-User: "Document POST /api/auth/login endpoint"
-Skill: Generates:
-```yaml
-/api/auth/login:
-  post:
-    summary: User login with email and password
-    tags: [Authentication]
-    requestBody:
-      required: true
-      content:
-        application/json:
-          schema:
-            type: object
-            properties:
-              email:
-                type: string
-                format: email
-              password:
-                type: string
-    responses:
-      '200':
-        description: Login successful
-        content:
-          application/json:
-            schema:
-              type: object
-              properties:
-                token:
-                  type: string
-      '401':
-        description: Invalid credentials
-```

package/src/core/skills/changelog-entry/SKILL.md

@@ -1,55 +0,0 @@
----
-name: changelog-entry
-description: Generate Keep a Changelog format entries for version releases
----
-
-# changelog-entry
-
-Generate Keep a Changelog format entries.
-
-## Activation Keywords
-- "changelog", "release notes", "version notes", "changelog entry"
-
-## When to Use
-- Creating release notes for new version
-- Documenting changes for changelog
-- Preparing version announcement
-
-## What This Does
-Generates changelog entries in Keep a Changelog format:
-- **Version header** with date (YYYY-MM-DD)
-- **Categories**: Added, Changed, Fixed, Improved, Deprecated, Removed, Security
-- **Detailed descriptions** of each change
-- **Breaking changes** clearly marked
-- **Links to related issues/PRs**
-- **Migration guides** for breaking changes
-
-Can auto-extract changes from commit messages if provided.
-
-## Output
-Ready-to-add section for CHANGELOG.md
-
-## Example Activation
-User: "Version 2.18.0 - Added 8 new agents"
-Skill: Generates:
-```markdown
-## [2.18.0] - 2025-10-28
-
-### Added
-- **Documentation Agent** - Technical docs, API documentation, user guides
-- **Monitoring Agent** - Observability, logging, metrics, alerting
-- **Compliance Agent** - GDPR, HIPAA, SOC2 compliance
-- **Design Agent** - Design systems, component specs
-- **Accessibility Agent** - WCAG compliance, a11y testing
-- **Analytics Agent** - Event tracking, product analytics
-- **Data Migration Agent** - Zero-downtime migrations
-- **QA Agent** - Test strategy, release gates
-
-### Changed
-- Expanded agent ecosystem from 17 to 25 agents
-- Improved agent coverage for enterprise features
-
-### Improved
-- Added comprehensive monitoring and compliance support
-- Enhanced quality assurance gates
-```

package/src/core/skills/commit-message-formatter/SKILL.md

@@ -1,50 +0,0 @@
----
-name: commit-message-formatter
-description: Generate conventional commit messages following Conventional Commits standard
----
-
-# commit-message-formatter
-
-Generate conventional commit messages with detailed descriptions.
-
-## Activation Keywords
-- "commit", "git commit", "conventional commit", "commit message"
-
-## When to Use
-- User is about to commit code changes
-- Need to format commit in conventional commits style
-- Writing clear, searchable commit messages
-
-## What This Does
-Generates properly-formatted commit messages following Conventional Commits standard:
-- Type: feat, fix, chore, docs, style, refactor, perf, test
-- Scope: module or component affected
-- Subject: concise description (imperative mood, <50 chars)
-- Body: detailed explanation of change (wrapped at 72 chars)
-- Footer: references to issues, breaking changes, co-authorship
-
-Automatically includes:
-- Claude Code co-authorship footer
-- Link to related story/issue if mentioned
-- Breaking change notation if applicable
-
-## Output
-Ready-to-use commit message for `git commit -m`
-
-## Example Activation
-User: "I implemented user login endpoint with JWT auth and rate limiting"
-Skill: Generates:
-```
-feat(auth): implement JWT-based user login endpoint
-
-Implemented POST /api/auth/login endpoint with:
-- Email/password validation
-- JWT token generation (24h expiration)
-- Rate limiting (5 attempts per 15 minutes)
-- Proper error handling and logging
-
-Matches acceptance criteria from US-0001.
-
-🤖 Generated with Claude Code
-Co-Authored-By: Claude <noreply@anthropic.com>
-```

package/src/core/skills/deployment-guide-generator/SKILL.md

@@ -1,84 +0,0 @@
----
-name: deployment-guide-generator
-description: Generate deployment guides with rollback procedures and verification steps
----
-
-# deployment-guide-generator
-
-Generate deployment guides with rollback procedures.
-
-## Activation Keywords
-- "deployment", "release guide", "deploy steps", "deployment procedure"
-
-## When to Use
-- Preparing to deploy a feature
-- Creating release runbook
-- Documenting deployment steps
-
-## What This Does
-Generates deployment guide including:
-- **Pre-deployment checklist** (tests passing, staging verified)
-- **Deployment steps** (database migrations, code deployment)
-- **Verification steps** (health checks, smoke tests)
-- **Rollback procedure** (how to revert if issues)
-- **Post-deployment monitoring** (watch metrics/logs)
-- **Communication plan** (who to notify)
-- **Estimated timeline**
-
-References monitoring for setup and rollback procedures.
-
-## Output
-Ready-to-follow deployment guide
-
-## Example Activation
-User: "Create deployment guide for user login feature"
-Skill: Generates:
-```markdown
-## Deployment Guide: User Login Feature (v2.18.0)
-
-### Pre-Deployment Checklist
-- [ ] All tests passing (npm test)
-- [ ] Staging environment verified
-- [ ] Database backup taken
-- [ ] Monitoring alerts configured
-- [ ] Team notified
-
-### Deployment Steps
-1. Run database migrations
-   \`\`\`bash
-   npm run migrate:up
-   \`\`\`
-
-2. Deploy new code
-   \`\`\`bash
-   git push production main
-   \`\`\`
-
-3. Verify deployment
-   - Check /health endpoint returns 200
-   - Verify JWT tokens working
-   - Check rate limiting active
-
-### Monitoring (Watch these metrics)
-- Login success rate (target: >95%)
-- Login latency (target: <200ms p95)
-- Error rate (alert if >1%)
-- Rate limiting hits (expected: <5%)
-
-### Rollback Procedure (if issues)
-1. Revert database migrations:
-   \`\`\`bash
-   npm run migrate:down
-   \`\`\`
-
-2. Revert code:
-   \`\`\`bash
-   git revert <commit-hash>
-   git push production main
-   \`\`\`
-
-3. Verify rollback successful
-
-**Estimated Timeline**: 15 minutes (10 min deploy + 5 min verify)
-**Rollback Time**: 10 minutes
-```

package/src/core/skills/diagram-generator/SKILL.md

@@ -1,65 +0,0 @@
----
-name: diagram-generator
-description: Generate Mermaid/ASCII diagrams for workflows, architecture, and sequence diagrams
----
-
-# diagram-generator
-
-Generate Mermaid/ASCII diagrams from descriptions.
-
-## Activation Keywords
-- "diagram", "ASCII", "Mermaid", "flowchart", "architecture", "sequence diagram"
-
-## When to Use
-- Creating architecture diagrams
-- Visualizing user workflows
-- Drawing sequence diagrams
-- System design documentation
-
-## What This Does
-Generates diagrams in Mermaid format (renders in GitHub/Markdown):
-- **Flowcharts** (user flows, decision trees)
-- **Sequence diagrams** (API interactions, service calls)
-- **Architecture diagrams** (system components, data flow)
-- **ER diagrams** (database relationships)
-- **Gantt charts** (timeline/roadmap)
-- **State diagrams** (state machines)
-
-Also supports ASCII art for simple diagrams.
-
-## Output
-Mermaid code blocks ready for markdown files
-
-## Example Activation
-User: "Draw user login flow"
-Skill: Generates:
-```mermaid
-flowchart TD
-    A[User opens login page] --> B[Enter email & password]
-    B --> C[Click submit]
-    C --> D{Valid credentials?}
-    D -->|No| E[Show error message]
-    E --> B
-    D -->|Yes| F[Generate JWT token]
-    F --> G[Redirect to dashboard]
-    G --> H[User logged in]
-
-    style D fill:#ff9999
-    style H fill:#99ff99
-```
-
-Architecture diagram example:
-```mermaid
-graph LR
-    Client[Frontend Client]
-    API[API Server]
-    DB[(Database)]
-    Cache[Redis Cache]
-    Auth[Auth Service]
-
-    Client -->|HTTP Request| API
-    API -->|Query| DB
-    API -->|Lookup| Cache
-    API -->|Verify Token| Auth
-    Auth -->|Check User| DB
-```