agileflow 3.4.3 → 4.0.0-alpha.1

package/src/core/templates/browser-qa-spec.yaml

@@ -1,94 +0,0 @@
-# Browser QA Test Spec Template
-# Part of AgileFlow Bowser Four-Layer Browser Automation
-#
-# Usage: Copy this template and fill in your scenario details.
-# Place specs in: .agileflow/ui-review/specs/ or docs/07-testing/agentic/
-# Run with: /agileflow:browser-qa SCENARIO=<path-to-this-file>
-#
-# Schema Version: 1.0.0
-
-# --- Required Fields ---
-
-# Unique test identifier (format: AGENTIC-NNN)
-test_id: AGENTIC-001
-
-# Associated user story (optional, links results to status.json)
-story_id: US-XXXX
-
-# Human-readable name for this test scenario
-name: "Example User Login Flow"
-
-# What this test validates
-description: "Verify that a user can log in with valid credentials and reach the dashboard"
-
-# --- Configuration ---
-
-# Base URL of the application under test
-url: http://localhost:3000
-
-# Maximum time for entire scenario (default: 60s)
-timeout: 60s
-
-# Retry attempts on failure before marking as failed (default: 2)
-max_retries: 2
-
-# Minimum pass rate to consider validated (default: 0.80)
-pass_rate_threshold: 0.80
-
-# Browsers to test against (default: [chromium])
-browsers:
-  - chromium
-
-# --- Test Steps ---
-# Each step has: name, action, and action-specific fields
-# Supported actions: navigate, click, fill, assert, wait, screenshot
-#
-# Optional per-step fields:
-#   wait_for: CSS selector to wait for before proceeding
-#   screenshot: true/false - capture screenshot after this step
-#   timeout: per-step timeout override
-
-steps:
-  - name: Navigate to login page
-    action: navigate
-    url: /login
-    wait_for: "[data-testid='login-form']"
-    screenshot: true
-
-  - name: Fill email field
-    action: fill
-    fields:
-      - selector: "[data-testid='email-input']"
-        value: "test@example.com"
-
-  - name: Fill password field
-    action: fill
-    fields:
-      - selector: "[data-testid='password-input']"
-        value: "testpassword123"
-
-  - name: Click login button
-    action: click
-    selector: "[data-testid='login-button']"
-    screenshot: true
-
-  - name: Verify dashboard loaded
-    action: assert
-    assertion: "User sees the dashboard page with a welcome message"
-    wait_for: "[data-testid='dashboard']"
-    screenshot: true
-
-# --- Expected Result ---
-# Natural language description of what success looks like
-expected_result: "User is logged in and sees the dashboard with their name displayed"
-
-# --- Metadata ---
-# Optional fields for tracking and reporting
-
-metadata:
-  author: AG-BROWSER-QA
-  created: "2026-02-16"
-  tags:
-    - authentication
-    - critical-path
-  priority: high

package/src/core/templates/ci-workflow.yml

@@ -1,74 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [main, develop]
-  pull_request:
-    branches: [main, develop]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-  pull-requests: read
-
-jobs:
-  lint:
-    name: Lint
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Run linter
-        run: |
-          echo "TODO: Configure linter (eslint, pylint, clippy, etc.)"
-          # Example: npm run lint
-          # Example: pylint src/
-          # Example: cargo clippy
-
-  typecheck:
-    name: Type Check
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Run type checker
-        run: |
-          echo "TODO: Configure type checker (tsc, mypy, etc.)"
-          # Example: npm run typecheck
-          # Example: mypy src/
-          # Example: cargo check
-
-  test:
-    name: Test
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Run tests
-        run: |
-          echo "TODO: Configure test runner (jest, pytest, cargo test, etc.)"
-          # Example: npm test
-          # Example: pytest --cov=src tests/
-          # Example: cargo test
-
-      - name: Upload coverage
-        if: always()
-        run: |
-          echo "TODO: Upload coverage to codecov/coveralls if desired"
-          # Example: bash <(curl -s https://codecov.io/bash)
-
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Build project
-        run: |
-          echo "TODO: Configure build command"
-          # Example: npm run build
-          # Example: python -m build
-          # Example: cargo build --release

package/src/core/templates/claude-settings.advanced.example.json

@@ -1,75 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '🚀 AgileFlow v{{VERSION}} loaded - Type /agileflow:help for commands'"
-          },
-          {
-            "type": "command",
-            "command": "echo '📁 Project: $(node .agileflow/scripts/get-env.js PROJECT_NAME \"Unnamed Project\")'"
-          },
-          {
-            "type": "command",
-            "command": "echo '👤 Developer: $(node .agileflow/scripts/get-env.js USER_NAME \"Developer\")'"
-          },
-          {
-            "type": "command",
-            "command": "if [ -d docs ]; then echo '✅ AgileFlow docs/ structure found'; else echo '⚠️  No docs/ structure - run /agileflow:setup-system'; fi"
-          },
-          {
-            "type": "command",
-            "command": "node .agileflow/scripts/context-loader.js 2>/dev/null || true"
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "matcher": ".*create story.*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '[LOG] Story creation detected at $(date)' >> .claude/activity.log"
-          }
-        ]
-      },
-      {
-        "matcher": ".*epic.*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '[LOG] Epic planning detected at $(date)' >> .claude/activity.log"
-          }
-        ]
-      },
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '[LOG] User prompt submitted at $(date)' >> .claude/prompt-history.log"
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '✅ Claude finished responding at $(date)'"
-          },
-          {
-            "type": "command",
-            "command": "echo '[LOG] Session ended at $(date)' >> .claude/session.log"
-          }
-        ]
-      }
-    ]
-  }
-}

package/src/core/templates/claude-settings.example.json

@@ -1,26 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo '🚀 AgileFlow v{{VERSION}} loaded - Use /agileflow:help to see available commands'"
-          }
-        ]
-      },
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash .agileflow/scripts/archive-completed-stories.sh > /dev/null 2>&1 &"
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [],
-    "Stop": []
-  }
-}

package/src/core/templates/command-documentation.md

@@ -1,187 +0,0 @@
-# Command Documentation Template
-
-This template provides a standardized structure for documenting AgileFlow slash commands.
-
-## File Structure
-
-```markdown
----
-# REQUIRED: Frontmatter section
-description: Brief one-line description of what the command does
-argument-hint: PARAM1=<value> [PARAM2=<optional>]
-compact_context:
-  priority: high|medium|low
-  preserve_rules:
-    - "Rule descriptions for compact context"
-  state_fields:
-    - field_name
----
-
-# command-name
-
-Full description of the command's purpose and primary use case.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js command-name
-```
-
-This gathers relevant context for the command.
-
----
-
-## Context Loading (Documentation)
-
-**PURPOSE**: Description of why context is loaded.
-
-**ACTIONS**:
-1. Action item 1
-2. Action item 2
-
-**WHY**: Explanation of benefits.
-
----
-
-## Syntax
-
-```
-/agileflow:command-name PARAM1=value [PARAM2=optional]
-```
-
-### Parameters
-
-| Parameter | Required | Default | Description |
-|-----------|----------|---------|-------------|
-| PARAM1 | Yes | - | Description |
-| PARAM2 | No | default | Description |
-
----
-
-## Examples
-
-### Basic Usage
-
-```
-/agileflow:command-name PARAM1=example
-```
-
-### Advanced Usage
-
-```
-/agileflow:command-name PARAM1=example PARAM2=custom
-```
-
----
-
-## Expected Output
-
-### Success Case
-
-```
-✓ Operation completed successfully
-
-Results:
-- Item 1: value
-- Item 2: value
-```
-
-### Error Cases
-
-#### Missing Required Parameter
-
-```
-❌ Error: PARAM1 is required
-Usage: /agileflow:command-name PARAM1=<value>
-```
-
-#### Invalid Parameter Value
-
-```
-❌ Error: Invalid value for PARAM1: 'invalid'
-Expected: description of valid values
-```
-
----
-
-## Related Commands
-
-- `/agileflow:related1` - Description
-- `/agileflow:related2` - Description
-
----
-
-## Troubleshooting
-
-### Common Issue 1
-
-**Symptom**: Description of what goes wrong.
-
-**Cause**: Explanation of why it happens.
-
-**Solution**: Steps to resolve.
-
-### Common Issue 2
-
-**Symptom**: Description.
-
-**Cause**: Explanation.
-
-**Solution**: Steps.
-
----
-
-## See Also
-
-- [Practice Guide](link) - Related practice documentation
-- [Architecture Doc](link) - Technical implementation details
-```
-
-## Best Practices for Command Documentation
-
-### 1. Description Quality
-
-- **Frontmatter description**: Keep to one line, action-oriented (e.g., "Create a new story" not "This command creates stories")
-- **Main description**: 1-2 sentences explaining the command's purpose and when to use it
-
-### 2. Expected Output Section
-
-Always include:
-- **Success case**: Show actual CLI output the user will see
-- **At least 2 error cases**: Common failures with their messages
-- Use actual ANSI color indicators if present:
-  - `✓` (green) for success
-  - `❌` (red) for errors
-  - `⚠️` (yellow) for warnings
-
-### 3. Parameter Documentation
-
-- Table format for clarity
-- Always specify Required/Optional
-- Include default values
-- Provide meaningful descriptions
-
-### 4. Examples
-
-- Start with simplest usage
-- Progress to advanced scenarios
-- Include real-world use cases
-
-### 5. Consistency
-
-- Use consistent heading levels
-- Follow the template structure
-- Match the formatting of existing commands
-
-## Checklist Before Publishing
-
-- [ ] Frontmatter has description and argument-hint
-- [ ] Expected Output section exists
-- [ ] At least one success example shown
-- [ ] At least two error scenarios documented
-- [ ] Parameters are documented in a table
-- [ ] Examples demonstrate common use cases
-- [ ] Related commands are linked
-- [ ] Troubleshooting section addresses common issues

package/src/core/templates/command-prerequisites.yaml

@@ -1,169 +0,0 @@
-# command-prerequisites.yaml
-#
-# Declarative prerequisites for AgileFlow commands.
-# Checked before command execution to warn about unmet requirements.
-#
-# Schema:
-#   commands.<name>.prerequisites[]:
-#     signal      - Dot-path into extracted signals (e.g. git.branch, statusJson)
-#     description - Human-readable explanation of what's needed
-#     fix         - Actionable instruction to resolve
-#     severity    - critical (will fail) | high (poor results) | medium (suboptimal)
-#
-# Signals are extracted by smart-detect.js extractSignals() and include:
-#   git.branch, git.onFeatureBranch, git.isClean, git.filesChanged
-#   statusJson, storyCount, story, story.epic
-#   packageJson, tests.hasTestSetup
-#   files.playwright, files.tsconfig, files.coverage, files.ciConfig
-
-version: "1.0.0"
-
-settings:
-  fail_open: true
-  max_warnings: 5
-
-commands:
-  verify:
-    prerequisites:
-      - signal: tests.hasTestSetup
-        description: "Test framework must be configured (scripts.test in package.json)"
-        fix: "Add a test script to package.json, e.g. \"test\": \"jest\" or \"test\": \"vitest\""
-        severity: critical
-
-  babysit:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist with stories to work on"
-        fix: "Run: /agileflow:story to create stories, or /agileflow:epic to plan an epic"
-        severity: critical
-
-  pr:
-    prerequisites:
-      - signal: git.onFeatureBranch
-        description: "Must be on a feature branch (not main/master)"
-        fix: "Create a feature branch: git checkout -b feat/your-feature"
-        severity: critical
-      - signal: story
-        description: "An active story should be set for PR description"
-        fix: "Run: /agileflow:status to set a current story"
-        severity: high
-
-  deploy:
-    prerequisites:
-      - signal: git.branch
-        description: "Git repository must be initialized"
-        fix: "Run: git init"
-        severity: critical
-      - signal: packageJson
-        description: "package.json must exist for deployment configuration"
-        fix: "Run: npm init -y"
-        severity: critical
-
-  audit:
-    prerequisites:
-      - signal: story
-        description: "An active story is needed to audit completion"
-        fix: "Run: /agileflow:status to set a current story"
-        severity: critical
-      - signal: statusJson
-        description: "status.json must exist with story data"
-        fix: "Run: /agileflow:story to create stories"
-        severity: critical
-
-  board:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist to display the board"
-        fix: "Run: /agileflow:story to create your first story"
-        severity: critical
-      - signal: storyCount
-        description: "At least one story must exist"
-        fix: "Run: /agileflow:story to create a story"
-        severity: high
-
-  sprint:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist for sprint planning"
-        fix: "Run: /agileflow:story to create stories first"
-        severity: critical
-      - signal: storyCount
-        description: "Stories are needed for sprint planning"
-        fix: "Run: /agileflow:epic to break down features into stories"
-        severity: high
-
-  browser-qa:
-    prerequisites:
-      - signal: files.playwright
-        description: "Playwright must be configured (playwright.config.ts or .js)"
-        fix: "Run: npm init playwright@latest"
-        severity: critical
-
-  review:
-    prerequisites:
-      - signal: git.onFeatureBranch
-        description: "Must be on a feature branch for code review"
-        fix: "Create a feature branch: git checkout -b feat/your-feature"
-        severity: critical
-      - signal: git.filesChanged
-        description: "There should be changed files to review"
-        fix: "Make some code changes before requesting a review"
-        severity: high
-
-  baseline:
-    prerequisites:
-      - signal: tests.hasTestSetup
-        description: "Test framework must be configured to establish a baseline"
-        fix: "Add a test script to package.json"
-        severity: critical
-      - signal: git.branch
-        description: "Git repository must be initialized"
-        fix: "Run: git init"
-        severity: high
-
-  metrics:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist for metrics calculation"
-        fix: "Run: /agileflow:story to start tracking work"
-        severity: critical
-      - signal: storyCount
-        description: "Stories are needed to compute metrics"
-        fix: "Run: /agileflow:story to create stories"
-        severity: high
-
-  velocity:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist for velocity tracking"
-        fix: "Run: /agileflow:story to start tracking work"
-        severity: critical
-      - signal: storyCount
-        description: "Completed stories are needed for velocity calculation"
-        fix: "Complete some stories to build velocity history"
-        severity: high
-
-  compress:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist to compress"
-        fix: "No status.json to compress - create stories first with /agileflow:story"
-        severity: critical
-
-  retro:
-    prerequisites:
-      - signal: statusJson
-        description: "status.json must exist for retrospective data"
-        fix: "Run: /agileflow:story to start tracking work"
-        severity: critical
-      - signal: storyCount
-        description: "Stories are needed for meaningful retrospective"
-        fix: "Complete some stories before running a retrospective"
-        severity: high
-
-  changelog:
-    prerequisites:
-      - signal: git.branch
-        description: "Git repository must be initialized with commit history"
-        fix: "Run: git init && git add -A && git commit -m 'initial commit'"
-        severity: critical

package/src/core/templates/comms-note-template.md

@@ -1,24 +0,0 @@
-# Handoff: {{STORY_ID}}
-
-**Date**: {{DATE}}
-**From**: {{FROM}}
-**To**: {{TO}}
-
-## Summary of Work Completed
-{{SUMMARY}}
-
-## Current State
-- Branch: `{{BRANCH}}`
-- Files changed: {{FILES}}
-- Tests: {{TEST_STATUS}}
-
-## Next Steps
-1.
-
-## Blockers / Open Questions
-{{BLOCKERS}}
-
-## References
-- Story: `docs/06-stories/{{EPIC}}/{{STORY_ID}}-*.md`
-- Tests: `docs/07-testing/test-cases/{{STORY_ID}}.md`
-- PR: {{PR_URL}}