agileflow 3.4.2 → 4.0.0-alpha.1

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

@@ -1,204 +0,0 @@
----
-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/list.md

@@ -1,199 +0,0 @@
----
-description: List all stories with status and filters
-argument-hint: "[EPIC=<EP-ID>] [STATUS=<status>] [OWNER=<id>]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:story:list - Lists stories with filters and quick actions"
-    - "MUST read status.json for story data"
-    - "MUST support filters: EPIC, STATUS, OWNER (combinable)"
-    - "MUST group stories by epic in output table"
-    - "MUST show: story ID, title, status, phase, owner, estimate"
-    - "MUST offer actions: view details, start work, create new"
-    - "This is READ-ONLY - no file writes"
-  state_fields:
-    - epic_filter
-    - status_filter
-    - owner_filter
-    - story_count
----
-
-# /agileflow:story:list
-
-Display all user stories with filtering and quick actions.
-
----
-
-## Purpose
-
-Shows all stories from `docs/09-agents/status.json` with:
-- Status (ready, in_progress, blocked, done)
-- Epic grouping
-- Owner assignment
-- Quick action options
-
-**This is a read-only command** - no files are written.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js story:list
-```
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-## Compact Summary
-
-**Command**: `/agileflow:story:list [EPIC=<EP-ID>] [STATUS=<status>] [OWNER=<id>]`
-**Purpose**: Display stories with filters and offer quick actions
-
-### Flow
-1. Read status.json
-2. Apply filters (epic, status, owner)
-3. Display formatted table
-4. Offer actions: view details, start work, create new
-
-### Critical Rules
-- **Read-only**: No file writes
-- **Always offer actions**: End with AskUserQuestion for next steps
-- **Group by epic**: Show stories organized by their parent epic
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Arguments
-
-| Argument | Required | Description |
-|----------|----------|-------------|
-| EPIC | No | Filter by epic (e.g., EP-0001) |
-| STATUS | No | Filter by status (ready, in_progress, blocked, done) |
-| OWNER | No | Filter by owner |
-
----
-
-## IMMEDIATE ACTIONS
-
-Upon invocation, execute these steps:
-
-### Step 1: Read Status File
-
-```bash
-cat docs/09-agents/status.json
-```
-
-### Step 2: Apply Filters
-
-If filters provided:
-- EPIC: Show only stories in that epic
-- STATUS: Show only stories with that status
-- OWNER: Show only stories assigned to that owner
-
-### Step 3: Display Stories
-
-Format output as table grouped by epic:
-
-```markdown
-## Stories
-
-### EP-0001: Authentication System
-| Story | Title | Status | Phase | Owner | Estimate |
-|-------|-------|--------|-------|-------|----------|
-| US-0001 | Login form | done | complete | AG-UI | 2h |
-| US-0002 | Password reset | in_progress | execute | AG-API | 3h |
-| US-0003 | Session management | ready | plan | AG-API | 4h |
-
-### EP-0002: User Dashboard
-| Story | Title | Status | Phase | Owner | Estimate |
-|-------|-------|--------|-------|-------|----------|
-| US-0004 | Dashboard layout | ready | plan | AG-UI | 2h |
-| US-0005 | Activity feed | ready | plan | AG-UI | 3h |
-
----
-**Summary**: 5 stories (1 done, 1 in_progress, 3 ready)
-```
-
-### Step 4: Offer Actions
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "What would you like to do?",
-  "header": "Actions",
-  "multiSelect": false,
-  "options": [
-    {"label": "View story details", "description": "See full story with acceptance criteria"},
-    {"label": "Start working on a story", "description": "Mark a ready story as in_progress"},
-    {"label": "Create new story", "description": "Add a new story to an epic"},
-    {"label": "Done", "description": "Exit"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**If "View story details"**:
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Which story would you like to view?",
-  "header": "Select",
-  "multiSelect": false,
-  "options": [
-    {"label": "US-0003: Session management (ready)", "description": "EP-0001 - AG-API"},
-    {"label": "US-0004: Dashboard layout (ready)", "description": "EP-0002 - AG-UI"},
-    {"label": "US-0005: Activity feed (ready)", "description": "EP-0002 - AG-UI"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-Then invoke: `/agileflow:story:view STORY=<selected>`
-
-**If "Start working on a story"**:
-Show only `ready` stories, then invoke:
-`/agileflow:status <selected> STATUS=in_progress`
-
-**If "Create new story"**:
-Invoke: `/agileflow:story`
-
----
-
-## Example Usage
-
-```bash
-# List all stories
-/agileflow:story:list
-
-# List stories for specific epic
-/agileflow:story:list EPIC=EP-0001
-
-# List only ready stories
-/agileflow:story:list STATUS=ready
-
-# List stories assigned to specific owner
-/agileflow:story:list OWNER=AG-UI
-
-# Combined filters
-/agileflow:story:list EPIC=EP-0001 STATUS=ready
-```
-
----
-
-## Rules
-
-- **Read-only**: No file writes
-- **Group by epic**: Always organize stories under their parent epic
-- **Show summary**: Include counts by status at the bottom
-- **Always offer actions**: End with next step options
-
----
-
-## Related Commands
-
-- `/agileflow:story:view` - View full story details
-- `/agileflow:story` - Create new story
-- `/agileflow:story-validate` - Validate story completeness
-- `/agileflow:status` - Update story status
-- `/agileflow:board` - Visual kanban board view

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

@@ -1,312 +0,0 @@
----
-description: View story details with contextual actions
-argument-hint: "STORY=<US-ID>"
-compact_context:
-  priority: medium
-  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"
-    - "STATUS=in_progress → Mark complete, mark blocked, view tests"
-    - "STATUS=blocked → View blocker, unblock, reassign"
-    - "STATUS=done → View summary, reopen, view next story"
-    - "ALWAYS offer next steps via AskUserQuestion"
-  state_fields:
-    - selected_story_id
-    - story_status
-    - story_epic
----
-
-# /agileflow:story:view
-
-View full story details and take contextual actions based on story state.
-
----
-
-## Purpose
-
-Displays complete story information and offers **context-aware actions** based on the story's current status:
-- **ready** → Start work, validate, assign
-- **in_progress** → View progress, mark blocked, complete
-- **blocked** → View blockers, unblock, reassign
-- **done** → View summary, reopen if needed
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js story:view
-```
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-## Compact Summary
-
-**Command**: `/agileflow:story:view STORY=<US-ID>`
-**Purpose**: View story details with context-aware action suggestions
-
-### Flow
-1. Read story file and status.json entry
-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 progress, test status, dependencies, blockers
-- **Always offer next steps**: End with relevant AskUserQuestion
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Arguments
-
-| Argument | Required | Description |
-|----------|----------|-------------|
-| STORY | Yes | Story ID (e.g., US-0042) |
-
----
-
-## IMMEDIATE ACTIONS
-
-Upon invocation, execute these steps:
-
-### Step 1: Validate Input
-
-If STORY not provided, list recent stories:
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Which story would you like to view?",
-  "header": "Select",
-  "multiSelect": false,
-  "options": [
-    {"label": "US-0042: Latest story", "description": "in_progress - AG-UI"},
-    {"label": "US-0041: Previous story", "description": "ready - AG-API"},
-    {"label": "Show all stories", "description": "View full story list"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### Step 2: Read Story Data
-
-Read from multiple sources:
-
-```bash
-# Story file
-cat docs/06-stories/<EPIC>/<STORY>-*.md
-
-# Status entry
-cat docs/09-agents/status.json | jq '.stories["<STORY>"]'
-
-# Test status (if exists)
-cat docs/07-testing/test-cases/<STORY>.md
-```
-
-### 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
-
-**Epic**: EP-0001 (Authentication System)
-**Status**: in_progress
-**Phase**: execute
-**Owner**: AG-UI
-**Estimate**: 3h
-**Created**: 2024-12-28
-**Updated**: 2024-12-30
-
----
-
-### 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
-      Then they see an error message
-
-- [ ] Given a user on the login page
-      When they click "Forgot Password"
-      Then they are taken to password reset flow
-
----
-
-### Dependencies
-
-- US-0040: API authentication endpoint (done)
-- US-0041: Session management (ready) - Not started yet
-
----
-
-### Test Status
-
-| Test | Status |
-|------|--------|
-| Unit: LoginForm.test.tsx | passing |
-| Integration: auth-flow.test.ts | pending |
-| E2E: login.spec.ts | not created |
-
----
-
-### Progress Notes
-
-- 2024-12-30: Started form implementation
-- 2024-12-29: Design approved
-```
-
-### Step 4: Offer Context-Aware Actions
-
-**Based on story status, show different options:**
-
-#### If STATUS = ready
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "This story is ready to start. What would you like to do?",
-  "header": "Actions",
-  "multiSelect": false,
-  "options": [
-    {"label": "Start working on this story (Recommended)", "description": "Mark as in_progress and begin implementation"},
-    {"label": "Validate story first", "description": "Check if AC and dependencies are complete"},
-    {"label": "View related research", "description": "Find research notes linked to this epic"},
-    {"label": "Back to story list", "description": "Return to /agileflow:story:list"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**If "Start working"**:
-- Run `/agileflow:status <STORY> STATUS=in_progress`
-- Suggest: "Enter plan mode to explore implementation?"
-
-#### If STATUS = in_progress
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "This story is in progress. What would you like to do?",
-  "header": "Actions",
-  "multiSelect": false,
-  "options": [
-    {"label": "Mark as complete", "description": "All AC done, move to done status"},
-    {"label": "Mark as blocked", "description": "Hit a blocker, need help"},
-    {"label": "View/run tests", "description": "Check test status for this story"},
-    {"label": "Add progress note", "description": "Document current progress"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**If "Mark as complete"**:
-- First ask: "Have all acceptance criteria been met?"
-- If yes: Run `/agileflow:status <STORY> STATUS=done`
-- Suggest: "View next ready story?"
-
-**If "Mark as blocked"**:
-- Ask: "What is blocking this story?"
-- Run `/agileflow:status <STORY> STATUS=blocked BLOCKER=<reason>`
-- Suggest: "Create blocker resolution task?"
-
-#### If STATUS = blocked
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "This story is blocked. What would you like to do?",
-  "header": "Actions",
-  "multiSelect": false,
-  "options": [
-    {"label": "View blocker details", "description": "See what's blocking this story"},
-    {"label": "Unblock and resume", "description": "Blocker resolved, continue work"},
-    {"label": "Reassign story", "description": "Assign to different owner"},
-    {"label": "Create research task", "description": "Need to research the blocker"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**If "Unblock and resume"**:
-- Run `/agileflow:status <STORY> STATUS=in_progress`
-- Clear blocker note
-
-#### If STATUS = done
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "This story is complete. What would you like to do?",
-  "header": "Actions",
-  "multiSelect": false,
-  "options": [
-    {"label": "View completion summary", "description": "See what was delivered"},
-    {"label": "Reopen story", "description": "Found issue, needs more work"},
-    {"label": "View next story in epic", "description": "Continue with related work"},
-    {"label": "Back to story list", "description": "Return to /agileflow:story:list"}
-  ]
-}]</parameter>
-</invoke>
-```
-
----
-
-## Example Usage
-
-```bash
-# View specific story
-/agileflow:story:view STORY=US-0042
-
-# Will prompt for selection if no ID
-/agileflow:story:view
-```
-
----
-
-## Rules
-
-- **Context-aware**: Actions must match current story status
-- **Show everything**: AC, tests, dependencies, blockers, notes
-- **Always offer next steps**: End with relevant action options
-- **Connect to related commands**: Link to status, validate, tests, research
-
----
-
-## Related Commands
-
-- `/agileflow:story:list` - View all stories
-- `/agileflow:story` - Create new story
-- `/agileflow:story-validate` - Validate story completeness
-- `/agileflow:status` - Update story status
-- `/agileflow:tests` - Run/view tests
-- `/agileflow:research:analyze` - Analyze related research