agileflow 3.4.0 → 3.4.2

package/src/core/commands/status.md

@@ -1,5 +1,6 @@
 ---
 description: Update story status and progress
+phase: pre-story
 argument-hint: "STORY=<US-ID> STATUS=<status> [SUMMARY=<text>] [PR=<url>] [TO=<agent-id>]"
 compact_context:
   priority: high

package/src/core/commands/story/edit.md

@@ -0,0 +1,204 @@
+---
+description: Edit an existing story's fields (title, owner, estimate, status, priority)
+argument-hint: "STORY=<US-ID> [TITLE=<text>] [OWNER=<id>] [ESTIMATE=<time>] [STATUS=<status>] [PRIORITY=<P0-P3|high|medium|low>]"
+compact_context:
+  priority: high
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:story:edit - Edit story fields with diff-preview-confirm"
+    - "{{RULES:json_operations}}"
+    - "{{RULES:user_confirmation}}"
+    - "{{RULES:file_preview}}"
+    - "MUST read current story from status.json BEFORE proposing changes"
+    - "MUST show diff of old vs new values"
+    - "MUST confirm with AskUserQuestion before writing"
+    - "MUST log edit event to bus/log.jsonl"
+  state_fields:
+    - story_id
+    - fields_changed
+---
+
+# /agileflow:story:edit
+
+Edit an existing story's metadata fields with diff preview and confirmation.
+
+---
+
+## STEP 0: Gather Context
+
+```bash
+node .agileflow/scripts/obtain-context.js story:edit
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:story:edit STORY=<US-ID> [TITLE=...] [OWNER=...] [ESTIMATE=...] [STATUS=...] [PRIORITY=...]`
+**Purpose**: Edit story fields in status.json with diff-preview-confirm workflow
+
+### Flow
+1. Parse STORY parameter (required) and optional field overrides
+2. Read current story from status.json
+3. Show diff of proposed changes
+4. Confirm via AskUserQuestion
+5. Apply changes to status.json
+6. Log edit event to bus/log.jsonl
+
+### Critical Rules
+- **Diff preview**: Always show old vs new before writing
+- **Confirmation**: Never write without user approval
+- **Bus logging**: Always append story-edited event
+- **Validation**: Verify JSON integrity after write
+<!-- COMPACT_SUMMARY_END -->
+
+---
+
+## Arguments
+
+| Argument | Required | Description |
+|----------|----------|-------------|
+| STORY | Yes | Story ID (e.g., US-0042) |
+| TITLE | No | New story title |
+| OWNER | No | New owner (e.g., AG-API, AG-UI) |
+| ESTIMATE | No | New estimate (e.g., 2h, 1d) |
+| STATUS | No | New status (ready, in_progress, blocked, done) |
+| PRIORITY | No | New priority (P0, P1, P2, P3, high, medium, low) |
+
+At least one optional field must be provided (otherwise suggest `/agileflow:story:view`).
+
+---
+
+## IMMEDIATE ACTIONS
+
+### Step 1: Validate Input
+
+If STORY not provided:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which story would you like to edit?",
+  "header": "Select",
+  "multiSelect": false,
+  "options": [
+    {"label": "Enter story ID", "description": "Provide a US-XXXX identifier"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+### Step 2: Read Current Story
+
+Read the story entry from `docs/09-agents/status.json`:
+
+```javascript
+const data = JSON.parse(fs.readFileSync('docs/09-agents/status.json', 'utf8'));
+const story = data.stories[storyId];
+```
+
+If story not found, show error: "Story {STORY} not found in status.json"
+
+### Step 3: Build Change Set
+
+Compare provided fields against current values. Skip fields that match current values (no-op).
+
+If no fields would change, inform user: "No changes detected. Current values match provided values."
+
+### Step 4: Show Diff Preview
+
+Display a clear diff of what will change:
+
+```markdown
+## Editing US-0042: Current Title
+
+| Field | Current | New |
+|-------|---------|-----|
+| title | "Login Form" | "Login Form with Validation" |
+| owner | AG-UI | AG-API |
+| estimate | 2h | 4h |
+
+Files modified:
+1. docs/09-agents/status.json (story entry update)
+2. docs/09-agents/bus/log.jsonl (edit event append)
+```
+
+### Step 5: Confirm Changes
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Apply these changes to US-0042?",
+  "header": "Confirm edit",
+  "multiSelect": false,
+  "options": [
+    {"label": "Yes, apply changes (Recommended)", "description": "Update status.json and log edit event"},
+    {"label": "No, cancel", "description": "Discard changes"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+### Step 6: Apply Changes
+
+On confirmation:
+
+1. **Update status.json** using Edit tool or jq:
+   - Update only the changed fields in the story entry
+   - Set `updated` timestamp to current ISO date
+
+2. **Validate JSON**:
+```bash
+node -e "JSON.parse(require('fs').readFileSync('docs/09-agents/status.json','utf8')); console.log('valid')"
+```
+
+3. **Append to bus/log.jsonl**:
+```json
+{"ts":"<ISO>","type":"story-edited","from":"USER","story":"<STORY>","changes":{"field":"old_value->new_value"},"text":"Story edited: <changed fields>"}
+```
+
+### Step 7: Confirm Success
+
+```
+Story US-0042 updated:
+  title: "Login Form" -> "Login Form with Validation"
+  owner: AG-UI -> AG-API
+```
+
+---
+
+## Example Usage
+
+```bash
+# Edit title
+/agileflow:story:edit STORY=US-0042 TITLE="Updated Title"
+
+# Change owner and estimate
+/agileflow:story:edit STORY=US-0042 OWNER=AG-API ESTIMATE=4h
+
+# Change status
+/agileflow:story:edit STORY=US-0042 STATUS=blocked
+
+# Multiple fields at once
+/agileflow:story:edit STORY=US-0042 TITLE="New Title" OWNER=AG-UI PRIORITY=high
+```
+
+---
+
+## Rules
+
+- **Always preview**: Show diff before applying
+- **Always confirm**: Use AskUserQuestion before writes
+- **Always log**: Append edit event to bus/log.jsonl
+- **Always validate**: Check JSON integrity after write
+- **No silent changes**: Every change must be visible to the user
+
+---
+
+## Related Commands
+
+- `/agileflow:story:view` - View story details
+- `/agileflow:story:list` - List all stories
+- `/agileflow:story` - Create new story
+- `/agileflow:status` - Quick status update
+- `/agileflow:epic:edit` - Edit epic fields

package/src/core/commands/story/view.md

@@ -6,6 +6,8 @@ compact_context:
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:story:view - Views story with context-aware actions"
     - "MUST read story file and status.json entry"
+    - "MUST parse AC items and cross-reference with test files for verified/pending status"
+    - "MUST display AC Progress: X/Y verified with visual progress bar"
     - "MUST display full story: AC (with checkboxes), tests, dependencies, blockers"
     - "MUST offer CONTEXT-AWARE actions based on story status"
     - "STATUS=ready → Start work, validate, view research"
@@ -51,13 +53,15 @@ node .agileflow/scripts/obtain-context.js story:view
 
 ### Flow
 1. Read story file and status.json entry
-2. Display full story details (AC, tests, progress)
-3. Offer actions based on current status
-4. Execute selected action
+2. Parse AC items and cross-reference with test files
+3. Display full story details (AC progress, tests, dependencies)
+4. Offer actions based on current status
+5. Execute selected action
 
 ### Critical Rules
+- **AC progress**: Parse AC items, cross-reference with tests, show X/Y verified with progress bar
 - **Context-aware actions**: Different options based on story status
-- **Show everything**: AC, test status, dependencies, blockers
+- **Show everything**: AC progress, test status, dependencies, blockers
 - **Always offer next steps**: End with relevant AskUserQuestion
 <!-- COMPACT_SUMMARY_END -->
 
@@ -109,7 +113,22 @@ cat docs/09-agents/status.json | jq '.stories["<STORY>"]'
 cat docs/07-testing/test-cases/<STORY>.md
 ```
 
-### Step 3: Display Story Details
+### Step 3: Parse AC and Compute Progress
+
+Before displaying, count acceptance criteria completion:
+
+1. **Parse AC from status.json**: Read the `ac` array from the story entry (string list of AC items)
+2. **Parse AC from story file** (if exists): Look for Given/When/Then patterns or `- [ ]`/`- [x]` checkboxes
+3. **Cross-reference with tests**: Check `docs/07-testing/test-cases/<STORY>.md` and `__tests__/<STORY>.test.*` for matching test descriptions
+4. **Compute progress**: Count verified (has matching test OR `[x]` checkbox) vs total AC items
+5. **Build ac_status**: `{ total: N, verified: M, items: [{text, verified, test_match}] }`
+
+**Matching rules:**
+- AC is "verified" if: story file has `[x]` checkbox for it, OR a test file has a describe/it/test matching the AC text
+- Use fuzzy substring matching (lowercase, strip "given/when/then" prefixes)
+- If no test files found, fall back to checkbox status only
+
+### Step 4: Display Story Details
 
 ```markdown
 ## US-0042: User Login Form
@@ -124,11 +143,14 @@ cat docs/07-testing/test-cases/<STORY>.md
 
 ---
 
-### Acceptance Criteria
+### AC Progress: 1/3 verified
+
+[==========....................] 33%
 
 - [x] Given a user on the login page
       When they enter valid credentials
       Then they are redirected to dashboard
+      (matched: LoginForm.test.tsx > "redirects on valid credentials")
 
 - [ ] Given a user on the login page
       When they enter invalid credentials
@@ -143,7 +165,7 @@ cat docs/07-testing/test-cases/<STORY>.md
 ### Dependencies
 
 - US-0040: API authentication endpoint (done)
-- US-0041: Session management (ready) ⚠️ Not started yet
+- US-0041: Session management (ready) - Not started yet
 
 ---
 

package/src/core/commands/story-validate.md

@@ -1,5 +1,6 @@
 ---
 description: Validate story completeness before development
+phase: pre-story
 argument-hint: "STORY=<US-ID>"
 compact_context:
   priority: high

package/src/core/commands/story.md

@@ -1,5 +1,6 @@
 ---
 description: Create a user story with acceptance criteria
+phase: pre-story
 argument-hint: "EPIC=<EP-ID> STORY=<US-ID> TITLE=<text> OWNER=<id> [ESTIMATE=<pts>] [AC=<list>] [TDD=true]"
 compact_context:
   priority: high

package/src/core/commands/tdd.md

@@ -1,5 +1,6 @@
 ---
 description: Start TDD workflow with RED→GREEN→REFACTOR phases
+phase: implementation
 argument-hint: "<US-ID>"
 compact_context:
   priority: high

package/src/core/commands/team/start.md

@@ -43,12 +43,16 @@ node -e "console.log(JSON.stringify({ agentTeams: !!process.env.CLAUDE_CODE_EXPE
 
 The argument specifies which team template to use. Available templates are in `.agileflow/teams/`:
 
-| Template | Description |
-|----------|-------------|
-| `fullstack` | API + UI + Testing specialists |
-| `code-review` | Code reviewer + Security + Performance |
-| `builder-validator` | Paired builders with validators |
-| `logic-audit` | Multi-perspective logic analysis |
+| Template | Description | Best For |
+|----------|-------------|----------|
+| `fullstack` | API + UI + Testing specialists | Full-stack feature development |
+| `backend` | API + Database + Security specialists | Backend/API work |
+| `frontend` | UI + Accessibility + Testing specialists | Frontend/component work |
+| `solo` | Mentor + Testing (lightweight) | Solo developers, learning |
+| `qa` | QA Strategy + Testing + Browser QA | Test coverage, regression |
+| `code-review` | Code reviewer + Security + Performance | Pre-PR quality gates |
+| `builder-validator` | Paired builders with validators | High-reliability features |
+| `logic-audit` | Multi-perspective logic analysis | Complex business logic |
 
 If no argument given, use AskUserQuestion to let user choose.
 

package/src/core/commands/tests.md

@@ -1,5 +1,6 @@
 ---
 description: Set up automated testing infrastructure
+phase: implementation
 argument-hint: "(no arguments)"
 compact_context:
   priority: high

package/src/core/commands/verify.md

@@ -1,5 +1,6 @@
 ---
 description: Run project tests and update story test status
+phase: implementation
 argument-hint: "[<US-ID>]"
 compact_context:
   priority: critical
@@ -259,7 +260,32 @@ Record test verification in current session:
 }
 ```
 
-### 7. Generate Report
+### 7. AC Coverage Report (Optional)
+
+After tests pass, if the current story has acceptance criteria, run the AC-to-test matcher to show coverage:
+
+```bash
+node -e "
+const { matchACToTests } = require('./.agileflow/scripts/lib/ac-test-matcher');
+const result = matchACToTests('{{STORY_ID}}');
+console.log(JSON.stringify(result, null, 2));
+"
+```
+
+Append AC coverage to the verification report:
+
+```
+AC Coverage: 3/5 (60%)
+  ✅ AC1: "Create audit command" → matched to audit.test.js (high)
+  ✅ AC2: "Accept story ID" → matched to audit.test.js (high)
+  ✅ AC3: "Run tests" → matched to verify.test.js (medium)
+  ⬜ AC4: "Check AC met" → no matching tests
+  ⬜ AC5: "Prompt for learnings" → no matching tests
+```
+
+If no story is specified or story has no AC, skip this section.
+
+### 8. Generate Report
 
 **Success Report**:
 ```

package/src/core/commands/workflow.md

@@ -1,5 +1,6 @@
 ---
 description: Define and run parameterized workflow templates
+phase: implementation
 argument-hint: "<template> [<arguments>]"
 compact_context:
   priority: normal
@@ -228,6 +229,7 @@ docs/08-project/workflows/
 ---
 name: deploy-staging
 description: Deploy to staging environment
+phase: implementation
 arguments:
   - name: version
     required: true

package/src/core/teams/backend.json

@@ -0,0 +1,41 @@
+{
+  "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/frontend.json

@@ -0,0 +1,41 @@
+{
+  "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/qa.json

@@ -0,0 +1,41 @@
+{
+  "name": "qa",
+  "description": "QA-focused team with test strategy, coverage analysis, and regression testing",
+  "version": "1.0.0",
+  "lead": {
+    "agent": "team-lead",
+    "delegate_mode": true,
+    "plan_approval": false
+  },
+  "teammates": [
+    {
+      "agent": "agileflow-qa",
+      "role": "strategist",
+      "domain": "test-strategy",
+      "description": "Defines test strategy, identifies coverage gaps, and plans regression suites"
+    },
+    {
+      "agent": "agileflow-testing",
+      "role": "builder",
+      "domain": "test-implementation",
+      "description": "Implements unit, integration, and end-to-end tests"
+    },
+    {
+      "agent": "agileflow-browser-qa",
+      "role": "validator",
+      "domain": "ui-testing",
+      "description": "Runs exploratory UI tests with browser automation and screenshot validation"
+    }
+  ],
+  "quality_gates": {
+    "teammate_idle": {
+      "tests": true,
+      "lint": false,
+      "types": false
+    },
+    "task_completed": {
+      "require_validator_approval": true
+    }
+  },
+  "tags": ["qa", "testing", "quality", "regression"]
+}

package/src/core/teams/solo.json

@@ -0,0 +1,35 @@
+{
+  "name": "solo",
+  "description": "Solo developer preset with mentor guidance and automated validation",
+  "version": "1.0.0",
+  "lead": {
+    "agent": "team-lead",
+    "delegate_mode": true,
+    "plan_approval": false
+  },
+  "teammates": [
+    {
+      "agent": "agileflow-mentor",
+      "role": "mentor",
+      "domain": "guidance",
+      "description": "Guides implementation approach, suggests patterns, and reviews decisions"
+    },
+    {
+      "agent": "agileflow-testing",
+      "role": "validator",
+      "domain": "quality",
+      "description": "Generates and runs tests to validate implementation"
+    }
+  ],
+  "quality_gates": {
+    "teammate_idle": {
+      "tests": true,
+      "lint": false,
+      "types": false
+    },
+    "task_completed": {
+      "require_validator_approval": false
+    }
+  },
+  "tags": ["solo", "mentor", "beginner-friendly"]
+}

package/src/core/templates/agileflow-metadata.json

@@ -133,6 +133,11 @@
     "default_audit_model": null,
     "description": "Override via MODEL=haiku|sonnet|opus in audit command arguments. null = use agent defaults."
   },
+  "ci_feedback_loops": {
+    "enabled": true,
+    "max_rounds": 3,
+    "description": "Auto-retry agent work when CI/tests fail, up to max_rounds before escalating to human"
+  },
   "ultradeep": {
     "tab_naming": "prefix:name",
     "custom_colors": null,