agileflow 3.3.0 → 3.4.1

package/src/core/commands/export.md

@@ -0,0 +1,238 @@
+---
+description: Export stories and epics to CSV, JSON, or Markdown for stakeholder reporting
+argument-hint: "FORMAT=csv|json|md [EPIC=<EP-ID>] [STATUS=<status>] [OWNER=<id>]"
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:export - Export stories/epics to CSV/JSON/Markdown"
+    - "{{RULES:json_operations}}"
+    - "MUST read status.json as data source"
+    - "MUST support FORMAT=csv|json|md (default: csv)"
+    - "MUST support optional filters: EPIC, STATUS, OWNER"
+    - "MUST save output to docs/08-project/exports/"
+  state_fields:
+    - format
+    - filter_epic
+    - filter_status
+    - filter_owner
+    - output_path
+---
+
+# /agileflow:export
+
+Export stories and epics from status.json to CSV, JSON, or Markdown for stakeholder reporting.
+
+---
+
+## STEP 0: Gather Context
+
+```bash
+node .agileflow/scripts/obtain-context.js export
+```
+
+---
+
+<!-- COMPACT_SUMMARY_START -->
+## Compact Summary
+
+**Command**: `/agileflow:export FORMAT=csv|json|md [EPIC=...] [STATUS=...] [OWNER=...]`
+**Purpose**: Export filtered stories to CSV, JSON, or Markdown files
+
+### Flow
+1. Parse FORMAT and optional filters
+2. Read status.json
+3. Apply filters (epic, status, owner)
+4. Generate output in requested format
+5. Save to docs/08-project/exports/export-YYYYMMDD.{csv|json|md}
+6. Show summary and file path
+
+### Critical Rules
+- **Default format**: CSV if not specified
+- **CSV must be Excel-compatible**: Proper quoting, comma-separated
+- **JSON mirrors status.json**: Filtered subset of stories structure
+- **Markdown generates table**: Paste-ready for docs/reports
+- **Always show count**: "Exported N stories to <path>"
+<!-- COMPACT_SUMMARY_END -->
+
+---
+
+## Arguments
+
+| Argument | Required | Default | Description |
+|----------|----------|---------|-------------|
+| FORMAT | No | csv | Output format: `csv`, `json`, or `md` |
+| EPIC | No | all | Filter by epic ID (e.g., EP-0041) |
+| STATUS | No | all | Filter by status: ready, in_progress, blocked, done, completed |
+| OWNER | No | all | Filter by owner (e.g., AG-API, AG-UI) |
+
+Multiple filters can be combined. All are AND-joined (stories must match all filters).
+
+---
+
+## IMMEDIATE ACTIONS
+
+### Step 1: Parse Arguments
+
+```
+FORMAT = argument or "csv" (default)
+EPIC = optional epic filter
+STATUS = optional status filter
+OWNER = optional owner filter
+```
+
+Validate FORMAT is one of: csv, json, md. If invalid, show error and suggest valid values.
+
+### Step 2: Read and Filter Data
+
+Read `docs/09-agents/status.json` and filter stories:
+
+```javascript
+const data = JSON.parse(fs.readFileSync('docs/09-agents/status.json', 'utf8'));
+let stories = Object.entries(data.stories).map(([id, s]) => ({ id, ...s }));
+
+// Apply filters
+if (EPIC) stories = stories.filter(s => s.epic === EPIC);
+if (STATUS) stories = stories.filter(s => s.status === STATUS);
+if (OWNER) stories = stories.filter(s => s.owner === OWNER);
+```
+
+If no stories match, inform user: "No stories match the given filters."
+
+### Step 3: Generate Output
+
+#### CSV Format
+
+Columns: ID, Title, Epic, Status, Owner, Priority, Estimate
+
+```csv
+ID,Title,Epic,Status,Owner,Priority,Estimate
+US-0380,"Add story:edit and epic:edit commands",EP-0041,done,AG-API,high,3h
+US-0381,"Add status:undo command for story status rollback",EP-0041,done,AG-API,high,2h
+```
+
+Rules:
+- First row is header
+- Quote fields containing commas or quotes
+- Escape quotes by doubling them
+- Use UTF-8 encoding
+
+#### JSON Format
+
+```json
+{
+  "exported_at": "2026-03-03T12:00:00Z",
+  "filters": { "epic": "EP-0041", "status": null, "owner": null },
+  "count": 8,
+  "stories": [
+    {
+      "id": "US-0380",
+      "title": "Add story:edit and epic:edit commands",
+      "epic": "EP-0041",
+      "status": "done",
+      "owner": "AG-API",
+      "priority": "high",
+      "estimate": "3h"
+    }
+  ]
+}
+```
+
+#### Markdown Format
+
+```markdown
+# Story Export - 2026-03-03
+
+**Filters**: Epic: EP-0041
+**Count**: 8 stories
+
+| ID | Title | Epic | Status | Owner | Priority | Estimate |
+|----|-------|------|--------|-------|----------|----------|
+| US-0380 | Add story:edit and epic:edit commands | EP-0041 | done | AG-API | high | 3h |
+| US-0381 | Add status:undo command | EP-0041 | done | AG-API | high | 2h |
+```
+
+### Step 4: Save Output
+
+Create output directory if needed:
+```bash
+mkdir -p docs/08-project/exports
+```
+
+Save to: `docs/08-project/exports/export-YYYYMMDD.{csv|json|md}`
+
+If file already exists for today, append a counter: `export-YYYYMMDD-2.csv`
+
+### Step 5: Show Summary
+
+```
+Exported 8 stories to docs/08-project/exports/export-20260303.csv
+
+Filters applied:
+  Epic: EP-0041
+  Status: all
+  Owner: all
+
+Preview (first 3 rows):
+  US-0380 | Add story:edit and epic:edit commands | done
+  US-0381 | Add status:undo command | done
+  US-0382 | Add export command | in_progress
+```
+
+Then offer next steps:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Export complete. What next?",
+  "header": "Next steps",
+  "multiSelect": false,
+  "options": [
+    {"label": "Open/view the exported file", "description": "Display full file contents"},
+    {"label": "Export in another format", "description": "Re-export as json/md/csv"},
+    {"label": "Done", "description": "Export saved successfully"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+---
+
+## Example Usage
+
+```bash
+# Export all stories as CSV (default)
+/agileflow:export
+
+# Export specific epic as JSON
+/agileflow:export FORMAT=json EPIC=EP-0041
+
+# Export ready stories as Markdown
+/agileflow:export FORMAT=md STATUS=ready
+
+# Export specific owner's stories as CSV
+/agileflow:export OWNER=AG-API STATUS=done
+
+# Combine filters
+/agileflow:export FORMAT=md EPIC=EP-0041 STATUS=ready OWNER=AG-API
+```
+
+---
+
+## Rules
+
+- **CSV Excel-compatible**: Proper quoting, commas, UTF-8
+- **JSON well-formed**: Pretty-printed, includes metadata
+- **Markdown paste-ready**: Standard table format
+- **Always show preview**: Display first few rows after export
+- **Always show path**: User needs to know where the file is
+- **No destructive overwrites**: Counter suffix for same-day exports
+
+---
+
+## Related Commands
+
+- `/agileflow:story:list` - Interactive story listing
+- `/agileflow:epic:list` - Interactive epic listing
+- `/agileflow:board` - Visual kanban board
+- `/agileflow:sprint` - Sprint planning view
+- `/agileflow:changelog` - Generate changelog

package/src/core/commands/help.md

@@ -87,7 +87,22 @@ Print a concise, one-screen overview:
 - What Epics, Stories, ADRs are; how docs/09-agents/status.json + bus/log.jsonl work
 - Daily flow: Pick story → Implement to AC → Tests → PR → Update status
 - WIP limit: max 2 stories/agent
-- List ALL available commands with one-line examples
+- List ALL available commands grouped by lifecycle phase
+- Show the current detected phase (from smart-detect.json) to highlight relevant commands
+
+### Lifecycle Phases
+
+Commands are organized by the project phase where they're most useful:
+
+| Phase | Description | Key Commands |
+|-------|------------|--------------|
+| **Pre-Story** | Story selection and project setup | epic, story, board, sprint, choose, configure |
+| **Planning** | Architecture and research decisions | adr, impact, council, multi-expert, baseline |
+| **Implementation** | Active development work | babysit, tdd, tests, verify, ci, workflow |
+| **Post-Impl** | Review, docs, and quality checks | audit, review, docs, changelog, diagnose |
+| **Pre-PR** | Final checks before pull request | pr, compress |
+
+**Tip**: Commands have a `phase` tag in their frontmatter. Run the command most relevant to your current phase.
 
 <!-- {{COMMAND_LIST}} -->
 

package/src/core/commands/{discovery → ideate}/brief.md

@@ -4,7 +4,7 @@ argument-hint: "TOPIC=<text> [IDEATION=<path>] [RESEARCH=<path,...>]"
 compact_context:
   priority: critical
   preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:discovery:brief - Product Brief synthesis"
+    - "ACTIVE COMMAND: /agileflow:ideate:brief - Product Brief synthesis"
     - "MUST read ideation report and/or research files as input"
     - "MUST generate a Product Brief using the product-brief template structure"
     - "MoSCoW mapping: HIGH-confidence ideas = MUST HAVE, single-expert ideas = SHOULD HAVE"
@@ -20,7 +20,7 @@ compact_context:
     - brief_generated
 ---
 
-# /agileflow:discovery:brief
+# /agileflow:ideate:brief
 
 Synthesize brainstorming results and research findings into a professional Product Brief artifact.
 
@@ -33,14 +33,14 @@ Generate a structured Product Brief that combines:
 - Research data (competitive analysis, market sizing, best practices)
 - Your own knowledge synthesis
 
-This can be used standalone (with existing ideation/research files) or as Phase 3 of the `/agileflow:discovery:new` workflow.
+This can be used standalone (with existing ideation/research files) or as Phase 3 of the `/agileflow:ideate:discover` workflow.
 
 ---
 
 ## STEP 0: Gather Context
 
 ```bash
-node .agileflow/scripts/obtain-context.js discovery:brief
+node .agileflow/scripts/obtain-context.js ideate:brief
 ```
 
 ---
@@ -49,13 +49,13 @@ node .agileflow/scripts/obtain-context.js discovery:brief
 
 ## Compact Summary
 
-**Command**: `/agileflow:discovery:brief` - Generate Product Brief from ideation + research
+**Command**: `/agileflow:ideate:brief` - Generate Product Brief from ideation + research
 
 **Quick Usage**:
 ```
-/agileflow:discovery:brief TOPIC="Mobile time tracking app"
-/agileflow:discovery:brief TOPIC="AI code review" IDEATION=docs/08-project/ideation/ideation-20260213.md
-/agileflow:discovery:brief TOPIC="Dashboard" RESEARCH=docs/10-research/20260213-dashboard-research.md
+/agileflow:ideate:brief TOPIC="Mobile time tracking app"
+/agileflow:ideate:brief TOPIC="AI code review" IDEATION=docs/08-project/ideation/ideation-20260213.md
+/agileflow:ideate:brief TOPIC="Dashboard" RESEARCH=docs/10-research/20260213-dashboard-research.md
 ```
 
 **What It Does**: Read ideation + research inputs -> Synthesize into Product Brief -> Save to docs/08-project/briefs/
@@ -307,19 +307,19 @@ Summary:
 
 ### Standalone (no prior ideation)
 ```
-/agileflow:discovery:brief TOPIC="Real-time collaboration for docs"
+/agileflow:ideate:brief TOPIC="Real-time collaboration for docs"
 ```
 Generates a brief from internal knowledge + topic analysis.
 
 ### With existing ideation
 ```
-/agileflow:discovery:brief TOPIC="API rate limiter" IDEATION=docs/08-project/ideation/ideation-20260213-api-rate-limiter.md
+/agileflow:ideate:brief TOPIC="API rate limiter" IDEATION=docs/08-project/ideation/ideation-20260213-api-rate-limiter.md
 ```
 Reads the ideation report and synthesizes into a brief.
 
 ### With ideation + research
 ```
-/agileflow:discovery:brief TOPIC="Mobile app" IDEATION=docs/08-project/ideation/ideation-20260213-mobile-app.md RESEARCH=docs/10-research/20260213-mobile-market-research.md,docs/10-research/20260213-mobile-competitors.md
+/agileflow:ideate:brief TOPIC="Mobile app" IDEATION=docs/08-project/ideation/ideation-20260213-mobile-app.md RESEARCH=docs/10-research/20260213-mobile-market-research.md,docs/10-research/20260213-mobile-competitors.md
 ```
 Full synthesis from both sources.
 
@@ -355,7 +355,7 @@ What would you like to do next?
 
 ## Related Commands
 
-- `/agileflow:discovery:new` - Full discovery workflow (brainstorm + research + brief)
+- `/agileflow:ideate:discover` - Full discovery workflow (brainstorm + research + brief)
 - `/agileflow:ideate:new` - Generate ideation report
 - `/agileflow:research:ask` - Generate research prompts
 - `/agileflow:research:synthesize` - Synthesize multiple research files

package/src/core/commands/{discovery/new.md → ideate/discover.md}

@@ -1,20 +1,21 @@
 ---
 description: Run structured discovery workflow - brainstorm, research, and generate a Product Brief
-argument-hint: "TOPIC=<text> [DEPTH=quick|guided|deep]"
+argument-hint: "TOPIC=<text> [DEPTH=quick|guided|deep] [MODEL=haiku|sonnet|opus]"
 compact_context:
   priority: critical
   preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:discovery:new - Discovery workflow orchestrator"
+    - "ACTIVE COMMAND: /agileflow:ideate:discover - Discovery workflow orchestrator"
     - "DEPTH modes: quick (skip research, auto-generate), guided (interactive, optional research), deep (comprehensive research + curation)"
     - "Phase 1: Brainstorm via /agileflow:ideate:new SCOPE=all"
     - "Phase 2: Research via /agileflow:research:ask (optional in quick mode)"
-    - "Phase 3: Generate Product Brief via /agileflow:discovery:brief"
+    - "Phase 3: Generate Product Brief via /agileflow:ideate:brief"
     - "Output: docs/08-project/briefs/{date}-{topic-slug}-brief.md"
-    - "MUST parse TOPIC (required) and DEPTH (default: guided)"
+    - "MUST parse TOPIC (required), DEPTH (default: guided), and MODEL (default: haiku, passed to ideate:new)"
     - "After brief generation, offer: create epic, refine brief, or done"
   state_fields:
     - topic
     - depth
+    - model
     - brainstorm_complete
     - research_complete
     - brief_generated
@@ -22,7 +23,7 @@ compact_context:
     - research_files
 ---
 
-# /agileflow:discovery:new
+# /agileflow:ideate:discover
 
 Run a structured discovery workflow that produces a professional Product Brief. Chains brainstorming, optional research, and synthesis into a single orchestrated flow.
 
@@ -33,7 +34,7 @@ Run a structured discovery workflow that produces a professional Product Brief.
 Bridge the gap between "vague idea" and "epic planning". This command validates product viability BEFORE decomposing into stories/epics.
 
 ```
-Vague Idea --> /discovery:new --> Product Brief --> /epic --> Stories --> Implementation
+Vague Idea --> /ideate:discover --> Product Brief --> /epic --> Stories --> Implementation
 ```
 
 ---
@@ -41,7 +42,7 @@ Vague Idea --> /discovery:new --> Product Brief --> /epic --> Stories --> Implem
 ## STEP 0: Gather Context
 
 ```bash
-node .agileflow/scripts/obtain-context.js discovery
+node .agileflow/scripts/obtain-context.js ideate:discover
 ```
 
 ---
@@ -50,19 +51,20 @@ node .agileflow/scripts/obtain-context.js discovery
 
 ## Compact Summary
 
-**Command**: `/agileflow:discovery:new` - Orchestrate brainstorm + research + Product Brief generation
+**Command**: `/agileflow:ideate:discover` - Orchestrate brainstorm + research + Product Brief generation
 
 **Quick Usage**:
 ```
-/agileflow:discovery:new TOPIC="Mobile time tracking app"
-/agileflow:discovery:new TOPIC="AI code review tool" DEPTH=deep
-/agileflow:discovery:new TOPIC="Internal dashboard" DEPTH=quick
+/agileflow:ideate:discover TOPIC="Mobile time tracking app"
+/agileflow:ideate:discover TOPIC="AI code review tool" DEPTH=deep
+/agileflow:ideate:discover TOPIC="Internal dashboard" DEPTH=quick
+/agileflow:ideate:discover TOPIC="Enterprise CRM" MODEL=opus
 ```
 
 **Phases**:
 1. Brainstorm (delegates to `/agileflow:ideate:new`)
 2. Research (delegates to `/agileflow:research:ask` - optional in quick mode)
-3. Brief Generation (delegates to `/agileflow:discovery:brief`)
+3. Brief Generation (delegates to `/agileflow:ideate:brief`)
 
 **Depth Modes**:
 - `quick`: Auto-run brainstorm, skip research, generate brief immediately (~5-10 min)
@@ -87,7 +89,7 @@ node .agileflow/scripts/obtain-context.js discovery
 ## How It Works
 
 ```
-USER: /agileflow:discovery:new TOPIC="..." DEPTH=guided
+USER: /agileflow:ideate:discover TOPIC="..." DEPTH=guided
                     |
                     v
     +-------------------------------+
@@ -114,7 +116,7 @@ USER: /agileflow:discovery:new TOPIC="..." DEPTH=guided
                     v
     +-------------------------------+
     |   STEP 4: GENERATE BRIEF      |
-    |   Delegate to discovery:brief |
+    |   Delegate to ideate:brief    |
     |   Synthesize all inputs       |
     |   Output: Product Brief       |
     +-------------------------------+
@@ -142,6 +144,7 @@ Parse the user's input:
 |----------|----------|---------|-------------|
 | TOPIC | Yes | - | The product/feature idea to explore |
 | DEPTH | No | guided | Discovery depth: quick, guided, or deep |
+| MODEL | No | haiku | Model for expert subagents (haiku, sonnet, opus). Passed through to ideate:new brainstorm phase. |
 
 **If TOPIC is missing**, ask the user:
 
@@ -191,7 +194,7 @@ From your {DOMAIN} perspective, generate 3-5 ideas covering:
 Be specific and actionable. Reference real-world examples where helpful.
 ```
 
-Deploy all experts with `run_in_background: true`, then collect results with TaskOutput.
+Deploy all experts with `run_in_background: true`, then collect results with TaskOutput. **If MODEL is specified**, pass it to each Task call via the `model` parameter.
 
 #### Guided Mode
 Same as Quick, but after collecting results:
@@ -343,6 +346,7 @@ Present the completed brief and ask what to do next:
 |----------|--------|---------|-------------|
 | TOPIC | Free text | (required) | The product/feature idea to explore |
 | DEPTH | quick, guided, deep | guided | Discovery depth level |
+| MODEL | haiku, sonnet, opus | haiku | Model for expert subagents. Passed to brainstorm phase Task calls. |
 
 {{argument}}
 
@@ -386,7 +390,7 @@ What would you like to do next?
 
 ## Related Commands
 
-- `/agileflow:discovery:brief` - Generate a Product Brief from existing ideation + research
+- `/agileflow:ideate:brief` - Generate a Product Brief from existing ideation + research
 - `/agileflow:ideate:new` - Run multi-expert brainstorming
 - `/agileflow:research:ask` - Generate external research prompts
 - `/agileflow:research:import` - Import research results