agileflow 3.4.3 → 4.0.0-alpha.10

package/src/core/commands/debt.md

@@ -1,491 +0,0 @@
----
-description: Track and prioritize technical debt items
-argument-hint: "(no arguments)"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "Scan for debt indicators: TODOs, complexity >10, functions >50 lines, duplication, coverage <70%"
-    - "Parse story tags: tech-debt: true, blocked by debt, 'refactor' or 'cleanup' in title"
-    - "Check ADRs for deprecated status and negative consequences"
-    - "Analyze git history: high churn files, unclear ownership"
-    - "Score each item (0-100): Severity × Scope × Pain / 10"
-    - "Categorize: Architecture/CodeQuality/Documentation/Testing/Security/Performance/Dependencies"
-    - "NEVER auto-create stories without user approval"
-    - "Provide realistic effort estimates (err on high side)"
-    - "Show debt trend analysis and recommendations for reduction"
-  state_fields:
-    - debt_items_found
-    - critical_count
-    - high_count
-    - stories_created
----
-
-# tech-debt
-
-STEP 0: ACTIVATE COMPACT SUMMARY MODE
-Before reading the full command, execute this script to display the compact summary:
-```bash
-sed -n '/<!-- COMPACT_SUMMARY_START -->/,/<!-- COMPACT_SUMMARY_END -->/p' "$(dirname "$0")/debt.md" | grep -v "COMPACT_SUMMARY"
-```
-If the user confirms they want the full details, continue. Otherwise, stop here.
-
-Track and visualize technical debt across the codebase.
-
-<!-- COMPACT_SUMMARY_START -->
-## Compact Summary
-
-**Command**: `tech-debt` - Identify, categorize, and prioritize technical debt for refactoring
-
-**Quick Usage**:
-```
-/agileflow:tech-debt SCAN=quick OUTPUT=report THRESHOLD=medium
-```
-
-**What It Does**: Scan codebase → Categorize debt → Score by Severity/Scope/Pain → Generate report → Optional stories
-
-**Optional Inputs**:
-- `SCAN=full|quick` (default: quick)
-- `OUTPUT=report|stories|both` (default: report)
-- `THRESHOLD=high|medium|low` (default: medium)
-
-### Tool Usage Examples
-
-**Bash** (to scan codebase for TODOs, complexity, etc.):
-```xml
-<invoke name="Bash">
-<parameter name="command">grep -r "TODO\|FIXME\|HACK" src/ --include="*.ts" --include="*.js" | head -20</parameter>
-<parameter name="description">Find TODO comments in codebase</parameter>
-</invoke>
-```
-
-**Glob** (to find high-churn files):
-```xml
-<invoke name="Glob">
-<parameter name="pattern">src/**/*.{ts,js}</parameter>
-</invoke>
-```
-
-**Read** (to analyze git history and ADRs):
-```xml
-<invoke name="Read">
-<parameter name="file_path">/full/path/to/docs/03-decisions/adr-0015-deprecated.md</parameter>
-</invoke>
-```
-
-**Write** (to save debt report):
-```xml
-<invoke name="Write">
-<parameter name="file_path">/full/path/to/docs/08-project/tech-debt-20251222.md</parameter>
-<parameter name="content"># Technical Debt Report
-
-**Generated**: 2025-12-22
-**Total Debt Items**: 42
-**Critical**: 3 | **High**: 12 | **Medium**: 18 | **Low**: 9
-
-## Critical Debt (Score >80)
-
-### 1. Auth service tightly coupled to database
-**Type**: Architecture | **Score**: 87
-**Impact**: Blocks US-0055 (OAuth), US-0061 (2FA)
-**Files**: src/services/auth.ts (287 lines, complexity 18)
-**Estimate**: 3-5 days
-
-### 2. Missing integration tests for payments
-**Type**: Testing | **Score**: 85
-**Impact**: High regression risk, blocking production
-**Files**: src/api/payments/*.ts (12 files, 0% coverage)
-**Estimate**: 2-3 days</parameter>
-</invoke>
-```
-
-**Write** (to create debt stories):
-```xml
-<invoke name="Write">
-<parameter name="file_path">/full/path/to/docs/06-stories/EP-XXXX/US-XXXX-refactor-auth.md</parameter>
-<parameter name="content">---
-story_id: US-XXXX
-type: tech-debt
-debt_score: 87
-estimate: 3d
----
-
-# US-XXXX: Refactor auth service to separate concerns
-
-## Current State (Before)
-Auth service tightly coupled to database layer...
-
-## Desired State (After)
-Clear separation: AuthService, AuthRepository, AuthController...</parameter>
-</invoke>
-```
-
-**AskUserQuestion** (use actual counts from scan):
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Found [N] debt items ([critical] critical, [high] high). Total effort: ~[days] days. What next?",
-  "header": "Action",
-  "multiSelect": false,
-  "options": [
-    {"label": "Generate [N] stories for critical items (Recommended)", "description": "Create trackable stories for the [critical] critical-severity debt items"},
-    {"label": "Review debt items in detail first", "description": "Show full analysis for each item before deciding"},
-    {"label": "Export debt report to docs/08-project/", "description": "Save report as tech-debt-[date].md for team review"},
-    {"label": "Skip for now", "description": "Scan complete, [N] items identified"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**Debt Categories**:
-- Architecture: Wrong abstractions, tight coupling
-- Code Quality: Duplication, complexity, style issues
-- Documentation: Missing, outdated, incomplete
-- Testing: Low coverage, flaky tests, missing E2E
-- Security: Outdated deps, exposed secrets, weak auth
-- Performance: N+1 queries, memory leaks, slow ops
-- Dependencies: Outdated packages, unmaintained libs
-
-**Output Files**: `docs/08-project/tech-debt-<YYYYMMDD>.md` | Optional stories | Optional dashboard
-<!-- COMPACT_SUMMARY_END -->
-
-## Prompt
-
-ROLE: Technical Debt Tracker
-
-OBJECTIVE
-Identify, categorize, and prioritize technical debt to guide refactoring efforts.
-
-INPUTS (optional)
-- SCAN=full|quick (default: quick - only flagged areas)
-- OUTPUT=report|stories|both (default: report)
-- THRESHOLD=high|medium|low (default: medium - minimum severity to report)
-
-DEBT DETECTION
-
-### 1. Code Quality Signals
-Scan for common debt indicators:
-- TODO/FIXME/HACK comments
-- Long functions (>50 lines)
-- High cyclomatic complexity (>10)
-- Duplicated code blocks (copy-paste)
-- Large files (>500 lines)
-- Deep nesting (>4 levels)
-- God objects (classes with >10 methods)
-- Low test coverage (<70%)
-
-### 2. Story Tags
-Search docs/06-stories/ for:
-- Stories tagged `tech-debt: true`
-- Stories with status=blocked by debt
-- Stories with "refactor" or "cleanup" in title
-
-### 3. ADR Analysis
-Check docs/03-decisions/ for:
-- ADRs with status=Deprecated (implementations may still exist)
-- ADRs with documented "negative consequences"
-- ADRs noting "temporary solution"
-
-### 4. Git History
-Analyze:
-- Files with high churn (frequently modified)
-- Files with many authors (ownership unclear)
-- Old branches not merged (potential context loss)
-
-### 5. Linter/Analyzer Output
-Parse output from:
-- ESLint, TSLint, Pylint
-- SonarQube, CodeClimate
-- Code coverage reports
-
-CATEGORIZATION
-
-Group debt by type:
-- **Architecture**: Wrong abstractions, tight coupling, missing patterns
-- **Code Quality**: Duplication, complexity, inconsistent style
-- **Documentation**: Missing, outdated, or incomplete docs
-- **Testing**: Low coverage, flaky tests, missing E2E
-- **Security**: Outdated dependencies, exposed secrets, weak auth
-- **Performance**: N+1 queries, memory leaks, slow operations
-- **Dependencies**: Outdated packages, unmaintained libraries
-
-SCORING
-
-Each debt item gets a score (0-100):
-- **Severity**: Low (1-3), Medium (4-6), High (7-9), Critical (10)
-- **Scope**: How many files affected (1-10 scale)
-- **Pain**: Developer frustration (1-10 scale)
-
-Score = Severity × Scope × Pain / 10
-
-DEBT REPORT
-```markdown
-# Technical Debt Report
-
-**Generated**: <ISO timestamp>
-**Total Debt Items**: 42
-**Critical**: 3 | **High**: 12 | **Medium**: 18 | **Low**: 9
-
----
-
-## Critical Debt (Score >80)
-
-### 1. Auth service tightly coupled to database layer
-**Type**: Architecture
-**Score**: 87
-**Impact**: Blocks US-0055 (Add OAuth), US-0061 (Add 2FA)
-**Files**: src/services/auth.ts (287 lines, complexity 18)
-**ADR**: ADR-0003 recommends service layer separation (not implemented)
-**Estimate**: 3-5 days to refactor
-**Stories**:
-- Create epic: EP-0010 "Refactor auth architecture"
-- Stories: Separate concerns, add interface, migrate callers
-
----
-
-### 2. Missing integration tests for payment flow
-**Type**: Testing
-**Score**: 85
-**Impact**: High risk for regressions, blocking production deploy
-**Files**: src/api/payments/*.ts (12 files, 0% integration coverage)
-**Last incident**: 2025-09-15 (payment bug in production)
-**Estimate**: 2-3 days
-**Stories**:
-- US-XXXX: Write integration tests for payment flow
-
----
-
-### 3. Unmaintained dependency: old-oauth-lib (3 years outdated)
-**Type**: Security
-**Score**: 82
-**Impact**: 2 known CVEs, blocks security audit
-**Files**: 8 files import this library
-**ADR**: ADR-0012 marked this for replacement (6 months ago)
-**Estimate**: 1-2 days to migrate to modern-oauth-lib
-**Stories**:
-- US-XXXX: Migrate from old-oauth-lib to modern-oauth-lib
-
----
-
-## High Debt (Score 60-80)
-
-[12 items...]
-
----
-
-## Summary by Category
-
-| Category | Count | Avg Score | Estimated Effort |
-|----------|-------|-----------|------------------|
-| Architecture | 8 | 72 | 15 days |
-| Code Quality | 15 | 58 | 8 days |
-| Testing | 10 | 65 | 12 days |
-| Security | 3 | 78 | 5 days |
-| Performance | 4 | 61 | 6 days |
-| Documentation | 2 | 45 | 2 days |
-
-**Total Estimated Effort**: 48 days
-
----
-
-## Trend Analysis
-
-Debt added this sprint: +5 items
-Debt resolved this sprint: -2 items
-Net change: +3 items ⚠️
-
----
-
-## Recommendations
-
-1. **Immediate** (Critical): Address auth refactor and payment tests
-2. **This Sprint**: Tackle 3 high-severity items (choose by ROI)
-3. **Next Sprint**: Reserve 20% capacity for debt reduction
-4. **Ongoing**: Require tests for all new code (enforce in CI)
-
----
-
-## Debt Heatmap
-
-Most problematic files:
-- src/services/auth.ts: 3 debt items (arch, complexity, coupling)
-- src/api/payments/process.ts: 2 debt items (no tests, deprecated API)
-- src/utils/legacy.ts: 2 debt items (duplication, no docs)
-```
-
-ACTIONS (after user review)
-
-1. Ask: "Generate stories for critical debt? (YES/NO)"
-2. If YES:
-   - Create epic: "EP-XXXX: Technical Debt Reduction"
-   - Create stories for top 5 critical items
-   - Use templates with AC focused on "before/after" state
-
-3. Ask: "Save report to docs/08-project/? (YES/NO)"
-4. If YES:
-   - Save to docs/08-project/tech-debt-<YYYYMMDD>.md
-   - Update docs/08-project/README.md with link
-
-5. Suggest adding to roadmap:
-   - Reserve 10-20% of each sprint for debt reduction
-   - Add debt review to retrospectives
-
-INTEGRATION
-
-### Story Template for Debt
-```markdown
----
-story_id: US-XXXX
-title: Refactor auth service to separate concerns
-type: tech-debt
-debt_score: 87
-estimate: 3d
----
-
-## Context
-Auth service is tightly coupled to database layer, blocking OAuth integration.
-
-## Current State (Before)
-- auth.ts contains DB queries, business logic, and HTTP handling
-- 287 lines, complexity 18
-- Hard to test, hard to extend
-
-## Desired State (After)
-- Clear separation: AuthService, AuthRepository, AuthController
-- Each <100 lines, complexity <8
-- 80%+ test coverage
-- Enables US-0055 (OAuth)
-
-## Acceptance Criteria
-- [ ] AuthRepository handles all DB operations
-- [ ] AuthService contains only business logic
-- [ ] AuthController handles only HTTP/routing
-- [ ] Tests cover each layer independently
-- [ ] All existing auth tests still pass
-- [ ] No breaking changes to API
-
-## References
-- ADR-0003: Service layer separation
-- Blocked stories: US-0055, US-0061
-```
-
-### Dashboard Integration
-Suggest creating a simple dashboard:
-```
-docs/08-project/debt-dashboard.md
-
-# Debt Dashboard (Updated Weekly)
-
-## Trend
-Week 42: 42 items (↑ from 39)
-Week 41: 39 items (↓ from 43)
-
-## Critical Items: 3
-[List with links to stories]
-
-## This Sprint Goal
-Reduce critical debt from 3 → 1
-```
-
-AUTOMATION
-
-Suggest adding to CI (weekly):
-```yaml
-- cron: '0 0 * * 1'  # Monday
-- name: Technical debt scan
-  run: npx claude-code /agileflow:tech-debt SCAN=full OUTPUT=report
-```
-
-RULES
-- Never auto-create stories without approval
-- Be honest about estimates (err on high side)
-- Link debt items to blocked stories when possible
-- Prioritize debt that blocks future work
-- Celebrate debt reduction in retrospectives
-
-OUTPUT
-- Technical debt report (markdown)
-- Optional: Stories for top debt items
-- Optional: Trend analysis
-- Recommendations for debt reduction
-
----
-
-## Expected Output
-
-### Success - Debt Report
-
-```
-📊 Technical Debt Analysis
-══════════════════════════════════════════════════════════════
-Scan date: 2026-01-29
-Files analyzed: 127
-
-🔴 HIGH PRIORITY (3)
-┌──────────────────────────────────────────────────────────────┐
-│ 1. Legacy auth module (src/auth/legacy.js)                   │
-│    Impact: Security risk, blocks OAuth work                  │
-│    Effort: 3 days                                            │
-│    ROI: High (unblocks US-0053, US-0054)                     │
-├──────────────────────────────────────────────────────────────┤
-│ 2. Untyped API responses                                     │
-│    Impact: Runtime errors, poor DX                           │
-│    Effort: 2 days                                            │
-│    ROI: High (prevents bugs)                                 │
-├──────────────────────────────────────────────────────────────┤
-│ 3. Test coverage gap in /api/orders                          │
-│    Impact: 23% coverage vs 80% target                        │
-│    Effort: 1 day                                             │
-│    ROI: Medium (risk reduction)                              │
-└──────────────────────────────────────────────────────────────┘
-
-🟡 MEDIUM PRIORITY (5)
-- Deprecated dependencies (lodash 3.x)
-- Console.log statements in production
-- Missing error boundaries
-- Hardcoded configuration
-- Duplicate validation logic
-
-📈 Trend: +2 items since last scan (2026-01-22)
-
-Create stories for high-priority items? [Y/n]
-```
-
-### Success - Debt Reduced
-
-```
-📊 Technical Debt Update
-══════════════════════════════════════════════════════════════
-
-✓ Resolved: Legacy auth module
-✓ Resolved: Test coverage gap
-
-Debt Score: 15 → 9 (-40%)
-Sprint Impact: Unblocked 2 stories
-
-🎉 Great progress on debt reduction!
-```
-
-### Error - No Analysis Available
-
-```
-⚠️ No technical debt analysis found
-
-Run initial scan first:
-/agileflow:debt SCAN=true
-
-This will analyze:
-- Code complexity
-- Test coverage
-- Dependency freshness
-- Security vulnerabilities
-```
-
----
-
-## Related Commands
-
-- `/agileflow:diagnose` - System health diagnostics
-- `/agileflow:review` - AI-powered code review
-- `/agileflow:packages` - Manage dependencies and audits
-- `/agileflow:story` - Create stories for debt items
-- `/agileflow:retro` - Sprint retrospective with debt review