agileflow 3.4.3 → 4.0.0-alpha.10

package/src/core/skills/_learnings/README.md

@@ -1,91 +0,0 @@
-# Skill Learnings
-
-This directory contains learnings files for self-improving skills. Each skill can have a corresponding `.yaml` file that stores user preferences and corrections learned over time.
-
-## Purpose
-
-Just like agents have `expertise.yaml` files that accumulate codebase knowledge, skills have learnings files that accumulate **user preferences**.
-
-| Component | Agents | Skills |
-|-----------|--------|--------|
-| **What they learn** | Codebase knowledge | User preferences |
-| **Learning file** | `expertise.yaml` | `learnings.yaml` |
-| **Example learning** | "sessions table uses UUID primary keys" | "User prefers conventional commits" |
-
-## How It Works
-
-1. **On skill invocation**: Skill reads its learnings file (if exists)
-2. **Apply preferences**: Skill output follows learned preferences
-3. **On correction**: Skill extracts signal and updates learnings file
-4. **Persist**: Changes saved for next session
-
-```
-┌─────────────────────────────────────────────────────────────┐
-│ Skill Execution Flow                                         │
-├─────────────────────────────────────────────────────────────┤
-│                                                              │
-│  1. Read _learnings/{skill}.yaml                            │
-│  2. Execute skill with learned preferences                  │
-│  3. User provides output                                    │
-│  4. If correction detected:                                 │
-│     - Extract signal (what was wrong)                       │
-│     - Determine confidence (high/medium/low)                │
-│     - Update learnings file                                 │
-│  5. Continue with corrected output                          │
-│                                                              │
-└─────────────────────────────────────────────────────────────┘
-```
-
-## File Naming
-
-Learnings files are named after their skill:
-
-| Skill | Learnings File |
-|-------|----------------|
-| `commit-message-formatter` | `commit.yaml` |
-| `agileflow-story-writer` | `story-writer.yaml` |
-| `code-review` | `code-review.yaml` |
-
-## Schema
-
-See `_template.yaml` for the full schema. Key sections:
-
-```yaml
-skill: commit-message-formatter
-version: 1
-last_updated: 2026-01-06
-
-preferences:
-  - signal: "User said 'no AI attribution'"
-    learning: "Never add AI footers"
-    confidence: high
-    captured: 2026-01-06
-
-conventions:
-  - "Use imperative mood"
-  - "Keep subject under 50 chars"
-
-anti_patterns:
-  - "Don't add emojis"
-```
-
-## Confidence Levels
-
-| Level | Trigger | Example |
-|-------|---------|---------|
-| **high** | Explicit correction ("never do X", "always do Y") | "Never include AI footers" |
-| **medium** | Approval or pattern that worked | "User approved conventional commit format" |
-| **low** | Observation to review | "User seemed to prefer shorter messages" |
-
-## Version Control
-
-Learnings files are version-controlled in git. This allows:
-- **History**: See how preferences evolved over time
-- **Rollback**: Revert if learning was incorrect
-- **Sharing**: Team can share learned preferences
-
-## Related
-
-- [Agent Expert System](../../agents/experts/README.md) - Same pattern for agents
-- [20260106-self-improving-skills-claude-code.md](../../../../../../../docs/10-research/20260106-self-improving-skills-claude-code.md) - Research
-- [20251216-agent-experts-self-improving-agents.md](../../../../../../../docs/10-research/20251216-agent-experts-self-improving-agents.md) - Original pattern

package/src/core/skills/_learnings/_template.yaml

@@ -1,106 +0,0 @@
-# Skill Learnings Template
-# Copy this file and rename to match your skill (e.g., commit.yaml)
-#
-# This file stores learned user preferences for a skill.
-# It mirrors the expertise.yaml pattern used by agent experts.
-
-# Skill identifier (matches the skill filename without extension)
-skill: skill-name
-
-# Schema version for migrations
-version: 1
-
-# Last time this file was updated
-last_updated: 2026-01-06T00:00:00.000Z
-
-# =============================================================================
-# PREFERENCES
-# =============================================================================
-# Explicit preferences learned from user corrections.
-# Each entry captures: what triggered the learning, what was learned, and confidence.
-
-preferences:
-  # Example: High confidence from explicit correction
-  # - signal: "User said 'no AI attribution in commits'"
-  #   learning: "Never add AI footers or Co-Authored-By lines"
-  #   confidence: high
-  #   captured: 2026-01-06T10:30:00.000Z
-
-  # Example: Medium confidence from approval
-  # - signal: "User approved 'feat(api): add user endpoint'"
-  #   learning: "Use conventional commits with scope in parentheses"
-  #   confidence: medium
-  #   captured: 2026-01-06T11:00:00.000Z
-
-  # Example: Low confidence from observation
-  # - signal: "User shortened message from 60 to 45 chars"
-  #   learning: "User may prefer shorter commit messages"
-  #   confidence: low
-  #   captured: 2026-01-06T11:30:00.000Z
-
-# =============================================================================
-# CONVENTIONS
-# =============================================================================
-# Established patterns this skill should always follow.
-# These are high-confidence learnings that have been validated.
-
-conventions:
-  # - "Use imperative mood in commit subject"
-  # - "Keep subject line under 50 characters"
-  # - "Separate subject from body with blank line"
-
-# =============================================================================
-# ANTI-PATTERNS
-# =============================================================================
-# Things this skill should never do.
-# These are typically from explicit "never do X" corrections.
-
-anti_patterns:
-  # - "Don't add emojis unless user explicitly requests"
-  # - "Don't use past tense in commit messages"
-  # - "Don't include issue numbers without prefix"
-
-# =============================================================================
-# CONTEXT
-# =============================================================================
-# Project-specific context the skill has learned.
-# This helps the skill understand the environment it's operating in.
-
-context:
-  # project_type: nodejs
-  # primary_language: typescript
-  # framework: next.js
-  # style_guide: conventional-commits
-
-# =============================================================================
-# EXAMPLES
-# =============================================================================
-# Good examples the skill has learned from.
-# Can be referenced when generating new output.
-
-examples:
-  # good:
-  #   - "feat(auth): add OAuth2 login flow"
-  #   - "fix(api): handle null response from external service"
-  #
-  # bad:
-  #   - "Added stuff"  # Too vague
-  #   - "fixed bug"    # No scope, past tense
-
-# =============================================================================
-# METADATA
-# =============================================================================
-# Tracking information for the learnings file.
-
-metadata:
-  # Total number of corrections captured
-  corrections_count: 0
-
-  # Total number of approvals captured
-  approvals_count: 0
-
-  # When the file was first created
-  created: 2026-01-06T00:00:00.000Z
-
-  # Sessions that contributed to learnings
-  sessions: []

package/src/core/skills/_learnings/code-review.yaml

@@ -1,118 +0,0 @@
-# Learnings for agileflow-code-review skill
-# This file accumulates user preferences for code review criteria.
-
-skill: code-review
-version: 1
-last_updated: 2026-01-09T00:00:00.000Z
-
-# =============================================================================
-# PREFERENCES
-# =============================================================================
-preferences:
-  # Initial preferences from project conventions
-  - signal: "Project code review standards"
-    learning: "Use 6-category analysis with severity-based prioritization"
-    confidence: high
-    captured: 2026-01-09T00:00:00.000Z
-
-# =============================================================================
-# CONVENTIONS
-# =============================================================================
-conventions:
-  - "Be constructive, not critical - frame feedback helpfully"
-  - "Always show BAD and GOOD code examples"
-  - "Include Positive Observations section"
-  - "Calculate code quality score (0-100)"
-  - "Never auto-fix without explicit approval"
-  - "Save report to docs/08-project/code-reviews/"
-
-# =============================================================================
-# ANTI-PATTERNS
-# =============================================================================
-anti_patterns:
-  - "Don't use harsh language or blame developers"
-  - "Don't only show bad examples - show fixes too"
-  - "Don't auto-commit fixes without approval"
-  - "Don't treat MEDIUM issues as CRITICAL"
-  - "Don't skip the Positive Observations section"
-
-# =============================================================================
-# SEVERITY_THRESHOLDS
-# =============================================================================
-# Custom severity mappings learned from user feedback
-severity_thresholds:
-  # Default thresholds (can be overridden by learnings)
-  cyclomatic_complexity:
-    acceptable: 10
-    warning: 15
-    critical: 20
-
-  function_length:
-    acceptable: 50
-    warning: 100
-    critical: 150
-
-  file_length:
-    acceptable: 500
-    warning: 1000
-    critical: 1500
-
-  test_coverage:
-    acceptable: 80
-    warning: 60
-    critical: 40
-
-# =============================================================================
-# CUSTOM_RULES
-# =============================================================================
-# Project-specific rules learned from corrections
-custom_rules:
-  # Example: rules that would be learned from corrections
-  # - pattern: "console.log"
-  #   severity: "HIGH"
-  #   reason: "No console.log in production code"
-  #   confidence: high
-  #   captured: 2026-01-09T00:00:00.000Z
-
-# =============================================================================
-# FOCUS_AREAS
-# =============================================================================
-# Weighted focus areas (higher = more important)
-focus_areas:
-  security: 1.5
-  performance: 1.2
-  code_quality: 1.0
-  best_practices: 1.0
-  testing: 1.2
-  documentation: 0.8
-
-# =============================================================================
-# CONTEXT
-# =============================================================================
-context:
-  report_location: docs/08-project/code-reviews/
-  score_threshold_block: 60
-  score_threshold_warn: 80
-
-# =============================================================================
-# EXAMPLES
-# =============================================================================
-examples:
-  good_feedback:
-    - "This could be improved by using parameterized queries to prevent SQL injection"
-    - "Consider extracting this into a helper function for reusability"
-    - "Good use of TypeScript strict mode"
-
-  bad_feedback:
-    - "This code is terrible"
-    - "Wrong"
-    - "Fix this"
-
-# =============================================================================
-# METADATA
-# =============================================================================
-metadata:
-  corrections_count: 0
-  approvals_count: 0
-  created: 2026-01-09T00:00:00.000Z
-  sessions: []

package/src/core/skills/_learnings/commit.yaml

@@ -1,69 +0,0 @@
-# Learnings for commit-message-formatter skill
-# This file accumulates user preferences for commit message generation.
-
-skill: commit-message-formatter
-version: 1
-last_updated: 2026-01-06T00:00:00.000Z
-
-# =============================================================================
-# PREFERENCES
-# =============================================================================
-preferences:
-  # From CLAUDE.md project settings
-  - signal: "Project CLAUDE.md specifies no AI attribution"
-    learning: "Never add AI footers, Co-Authored-By, or robot emojis to commits"
-    confidence: high
-    captured: 2026-01-06T00:00:00.000Z
-
-# =============================================================================
-# CONVENTIONS
-# =============================================================================
-conventions:
-  - "Use conventional commits format (feat/fix/chore/docs/refactor/test/style)"
-  - "Include scope in parentheses when applicable"
-  - "Use imperative mood in subject line"
-  - "Keep subject under 50 characters"
-  - "Separate subject from body with blank line"
-  - "Wrap body at 72 characters"
-
-# =============================================================================
-# ANTI-PATTERNS
-# =============================================================================
-anti_patterns:
-  - "Don't add AI attribution (footers, Co-Authored-By, emojis)"
-  - "Don't use past tense (use 'add' not 'added')"
-  - "Don't use vague messages ('fix stuff', 'update code')"
-  - "Don't include emojis unless explicitly requested"
-
-# =============================================================================
-# CONTEXT
-# =============================================================================
-context:
-  style_guide: conventional-commits
-  attribution: none
-
-# =============================================================================
-# EXAMPLES
-# =============================================================================
-examples:
-  good:
-    - "feat(auth): add OAuth2 login flow"
-    - "fix(api): handle null response from external service"
-    - "chore: update dependencies to latest versions"
-    - "docs: add API endpoint documentation"
-    - "refactor(db): extract query builder to separate module"
-
-  bad:
-    - "Added stuff"
-    - "fixed bug"
-    - "WIP"
-    - "feat: add feature 🚀"
-
-# =============================================================================
-# METADATA
-# =============================================================================
-metadata:
-  corrections_count: 0
-  approvals_count: 0
-  created: 2026-01-06T00:00:00.000Z
-  sessions: []

package/src/core/skills/_learnings/story-writer.yaml

@@ -1,71 +0,0 @@
-# Learnings for agileflow-story-writer skill
-# This file accumulates user preferences for user story formatting.
-
-skill: story-writer
-version: 1
-last_updated: 2026-01-09T00:00:00.000Z
-
-# =============================================================================
-# PREFERENCES
-# =============================================================================
-preferences:
-  # Initial preferences from project conventions
-  - signal: "Project uses AgileFlow story template"
-    learning: "Use standard AgileFlow user story format with frontmatter"
-    confidence: high
-    captured: 2026-01-09T00:00:00.000Z
-
-# =============================================================================
-# CONVENTIONS
-# =============================================================================
-conventions:
-  - "Use 'As a [role], I want [action], So that [benefit]' format"
-  - "Include 2-5 acceptance criteria with Given/When/Then"
-  - "Use P0/P1/P2/P3 priority levels"
-  - "Use Fibonacci estimation (1,2,3,5,8,13)"
-  - "Assign owner based on work type (AG-UI, AG-API, AG-CI, AG-DEVOPS)"
-  - "Include Technical Notes section for implementation guidance"
-  - "Include Definition of Done checklist"
-  - "File naming: US-####-descriptive-name.md"
-
-# =============================================================================
-# ANTI-PATTERNS
-# =============================================================================
-anti_patterns:
-  - "Don't create stories > 13 points (split into multiple)"
-  - "Don't skip acceptance criteria"
-  - "Don't use vague descriptions ('implement feature')"
-  - "Don't forget to update status.json"
-  - "Don't skip the diff-first/YES-NO pattern"
-
-# =============================================================================
-# CONTEXT
-# =============================================================================
-context:
-  story_location: docs/06-stories/
-  status_file: docs/09-agents/status.json
-  test_stub_location: docs/07-testing/test-cases/
-  index_file: docs/06-stories/README.md
-
-# =============================================================================
-# EXAMPLES
-# =============================================================================
-examples:
-  good:
-    - "US-0042: User Login Form (clear, specific, testable)"
-    - "US-0015: Add pagination to user list (scoped, estimable)"
-    - "US-0023: Database connection pooling (technical, well-defined)"
-
-  bad:
-    - "US-0099: Implement stuff (vague)"
-    - "US-0100: Fix all bugs (not specific)"
-    - "US-0101: Make it work better (no acceptance criteria)"
-
-# =============================================================================
-# METADATA
-# =============================================================================
-metadata:
-  corrections_count: 0
-  approvals_count: 0
-  created: 2026-01-09T00:00:00.000Z
-  sessions: []

package/src/core/teams/backend.json

@@ -1,41 +0,0 @@
-{
-  "name": "backend",
-  "description": "Backend-focused team with API, database, and security specialists",
-  "version": "1.0.0",
-  "lead": {
-    "agent": "team-lead",
-    "delegate_mode": true,
-    "plan_approval": true
-  },
-  "teammates": [
-    {
-      "agent": "agileflow-api",
-      "role": "builder",
-      "domain": "api",
-      "description": "Implements API endpoints, business logic, data models, and service layer"
-    },
-    {
-      "agent": "agileflow-database",
-      "role": "builder",
-      "domain": "database",
-      "description": "Designs schemas, writes migrations, optimizes queries"
-    },
-    {
-      "agent": "agileflow-security",
-      "role": "validator",
-      "domain": "security",
-      "description": "Reviews authentication, authorization, and input validation"
-    }
-  ],
-  "quality_gates": {
-    "teammate_idle": {
-      "tests": true,
-      "lint": true,
-      "types": true
-    },
-    "task_completed": {
-      "require_validator_approval": true
-    }
-  },
-  "tags": ["development", "backend", "api", "database"]
-}

package/src/core/teams/builder-validator.json

@@ -1,51 +0,0 @@
-{
-  "name": "builder-validator",
-  "description": "Paired builder and validator teams for high-confidence implementations",
-  "version": "1.0.0",
-  "lead": {
-    "agent": "team-lead",
-    "delegate_mode": true,
-    "plan_approval": true
-  },
-  "teammates": [
-    {
-      "agent": "agileflow-api",
-      "role": "builder",
-      "domain": "backend",
-      "description": "Implements API endpoints and business logic",
-      "paired_validator": "agileflow-api-validator"
-    },
-    {
-      "agent": "agileflow-api-validator",
-      "role": "validator",
-      "domain": "backend",
-      "description": "Validates API implementations against quality gates",
-      "validates": "agileflow-api"
-    },
-    {
-      "agent": "agileflow-ui",
-      "role": "builder",
-      "domain": "frontend",
-      "description": "Implements UI components and styling",
-      "paired_validator": "agileflow-ui-validator"
-    },
-    {
-      "agent": "agileflow-ui-validator",
-      "role": "validator",
-      "domain": "frontend",
-      "description": "Validates UI implementations against accessibility and design standards",
-      "validates": "agileflow-ui"
-    }
-  ],
-  "quality_gates": {
-    "teammate_idle": {
-      "tests": true,
-      "lint": true,
-      "types": true
-    },
-    "task_completed": {
-      "require_validator_approval": true
-    }
-  },
-  "tags": ["development", "validation", "high-confidence"]
-}

package/src/core/teams/code-review.json

@@ -1,41 +0,0 @@
-{
-  "name": "code-review",
-  "description": "Code review team with security, performance, and accessibility reviewers",
-  "version": "1.0.0",
-  "lead": {
-    "agent": "team-lead",
-    "delegate_mode": true,
-    "plan_approval": false
-  },
-  "teammates": [
-    {
-      "agent": "agileflow-code-reviewer",
-      "role": "reviewer",
-      "domain": "quality",
-      "description": "Comprehensive code review for maintainability and best practices"
-    },
-    {
-      "agent": "agileflow-security",
-      "role": "reviewer",
-      "domain": "security",
-      "description": "Security vulnerability analysis and compliance checks"
-    },
-    {
-      "agent": "agileflow-performance",
-      "role": "reviewer",
-      "domain": "performance",
-      "description": "Performance profiling and optimization recommendations"
-    }
-  ],
-  "quality_gates": {
-    "teammate_idle": {
-      "tests": false,
-      "lint": false,
-      "types": false
-    },
-    "task_completed": {
-      "require_validator_approval": false
-    }
-  },
-  "tags": ["review", "quality", "security"]
-}

package/src/core/teams/frontend.json

@@ -1,41 +0,0 @@
-{
-  "name": "frontend",
-  "description": "Frontend-focused team with UI, accessibility, and design specialists",
-  "version": "1.0.0",
-  "lead": {
-    "agent": "team-lead",
-    "delegate_mode": true,
-    "plan_approval": true
-  },
-  "teammates": [
-    {
-      "agent": "agileflow-ui",
-      "role": "builder",
-      "domain": "frontend",
-      "description": "Implements UI components, styling, theming, and client-side logic"
-    },
-    {
-      "agent": "agileflow-accessibility",
-      "role": "validator",
-      "domain": "accessibility",
-      "description": "Reviews WCAG compliance, keyboard navigation, and screen reader support"
-    },
-    {
-      "agent": "agileflow-testing",
-      "role": "validator",
-      "domain": "quality",
-      "description": "Writes component tests, integration tests, and visual regression tests"
-    }
-  ],
-  "quality_gates": {
-    "teammate_idle": {
-      "tests": true,
-      "lint": true,
-      "types": false
-    },
-    "task_completed": {
-      "require_validator_approval": true
-    }
-  },
-  "tags": ["development", "frontend", "ui", "accessibility"]
-}

package/src/core/teams/fullstack.json

@@ -1,41 +0,0 @@
-{
-  "name": "fullstack",
-  "description": "Full-stack development team with API, UI, and testing specialists",
-  "version": "1.0.0",
-  "lead": {
-    "agent": "team-lead",
-    "delegate_mode": true,
-    "plan_approval": true
-  },
-  "teammates": [
-    {
-      "agent": "agileflow-api",
-      "role": "builder",
-      "domain": "backend",
-      "description": "Implements API endpoints, business logic, and data models"
-    },
-    {
-      "agent": "agileflow-ui",
-      "role": "builder",
-      "domain": "frontend",
-      "description": "Implements UI components, styling, and client-side logic"
-    },
-    {
-      "agent": "agileflow-testing",
-      "role": "validator",
-      "domain": "quality",
-      "description": "Writes and runs tests, validates implementations"
-    }
-  ],
-  "quality_gates": {
-    "teammate_idle": {
-      "tests": true,
-      "lint": true,
-      "types": false
-    },
-    "task_completed": {
-      "require_validator_approval": false
-    }
-  },
-  "tags": ["development", "feature", "fullstack"]
-}