agileflow 3.4.2 → 4.0.0-alpha.1

package/src/core/commands/context/export.md

@@ -1,296 +0,0 @@
----
-description: Export concise context excerpt for web AI tools
-argument-hint: "(no arguments)"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:context:export - Read-only export command"
-    - "READ-ONLY: No file writes, no confirmation needed, no state changes"
-    - "OUTPUT LIMIT: ≤300 lines maximum for easy pasting into web AI tools"
-    - "REQUIRED INPUT: docs/context.md must exist (run /agileflow:context:full first if missing)"
-    - "EXTRACT ONLY: overview, focus, tech, decisions, features, next steps (skip progress, notes)"
-    - "NO TaskCreate/TaskUpdate needed - single-step read-only operation"
-  state_fields:
-    - context_file_exists
-    - output_line_count
----
-
-# /agileflow:context:export
-
-Export a concise context excerpt for pasting into web AI tools.
-
----
-
-## Purpose
-
-Reads `docs/context.md` and outputs a condensed excerpt (≤300 lines) ready to paste into ChatGPT, Perplexity, Gemini, or Claude web.
-
-**This is a read-only command** - no files are written.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js context:export
-```
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## ⚠️ COMPACT SUMMARY - /agileflow:context:export IS ACTIVE
-
-**CRITICAL**: You are exporting a condensed context brief from `docs/context.md`. Follow these rules EXACTLY.
-
-**PURPOSE**: Extract ≤300 line excerpt ready to paste into ChatGPT, Perplexity, Gemini, or Claude web for immediate context loading.
-
----
-
-### 🚨 RULE #1: READ-ONLY COMMAND
-
-**This command NEVER writes, modifies, or changes state:**
-- ✓ Read docs/context.md
-- ✓ Extract and format
-- ✓ Output to code block
-- ✗ NO file writes
-- ✗ NO Edit tool calls
-- ✗ NO confirmation needed
-- ✗ NO state changes
-
-**Purpose**: Simple read → extract → display workflow.
-
----
-
-### 🚨 RULE #2: OUTPUT LIMIT IS STRICT - ≤300 LINES
-
-**Maximum output size is 300 lines.** This is critical for pasting into web AI tools.
-
-**If context.md is longer:**
-1. Extract ONLY these sections (in order):
-   - What We're Building (overview)
-   - Current Focus (active work)
-   - Tech Stack (technologies)
-   - Key Decisions (ADRs list only, not full descriptions)
-   - Feature Map (one-line-per-epic summary)
-   - Next Steps (upcoming work)
-
-2. **SKIP these to save space:**
-   - Recent Progress (too verbose)
-   - Notes section (too long)
-   - Detailed story descriptions
-   - Full ADR content
-
-3. **Count lines as you extract** - use line counter to stay under 300
-
-**Format as:**
-```markdown
-# Project Context Brief
-Last updated: [timestamp from context.md]
-
-## What We're Building
-[Max 5 lines]
-
-## Current Focus
-[Max 5 lines]
-
-## Tech Stack
-[Max 8 lines]
-
-## Key Decisions
-[Max 10 lines - ADR titles only]
-
-## Feature Map
-[Max 15 lines - one per epic]
-
-## Next Steps
-[Max 15 lines - ready stories only]
-```
-
----
-
-### 🚨 RULE #3: REQUIRED INPUT FILE
-
-**docs/context.md MUST exist before exporting.**
-
-**If missing:**
-```
-Error: docs/context.md not found.
-
-To create it, run: /agileflow:context:full
-
-Then you can export with: /agileflow:context:export
-```
-
-**Do NOT create placeholder or fallback - user must run :full first.**
-
----
-
-### 🚨 RULE #4: EXTRACTION SEQUENCE
-
-**Extract in this EXACT order (don't rearrange):**
-
-| Step | Section | Source | Max Lines |
-|------|---------|--------|-----------|
-| 1 | Header | "# Project Context Brief" | 1 |
-| 2 | Timestamp | Last updated: [from context.md] | 1 |
-| 3 | What We're Building | From overview section | 5 |
-| 4 | Current Focus | From overview/focus section | 5 |
-| 5 | Tech Stack | From tech section (short list) | 8 |
-| 6 | Key Decisions | From decisions section (titles only) | 10 |
-| 7 | Feature Map | From features section (one per epic) | 15 |
-| 8 | Next Steps | From next section (ready stories) | 15 |
-| 9 | Footer | Paste instructions | 3 |
-| | | **TOTAL** | **≤300** |
-
----
-
-### 🚨 RULE #5: CONTENT CONDENSING RULES
-
-**When extracting, apply these rules to stay under limit:**
-
-| Element | Full Size | Condensed Size | Rule |
-|---------|-----------|----------------|------|
-| ADRs | Full description | Title + status only | "ADR-001: Feature X (Accepted)" |
-| Stories | Title + description | Title + status | "US-0042 (in-progress)" |
-| Tech | Full list + versions | Framework + key deps only | "Next.js 16, TensorFlow.js, Tailwind" |
-| Epics | Title + stories list | Title + story count + status | "EP-001: Auth (3 stories, 1 done)" |
-| Decisions | Full context | One-liner | "JWT instead of sessions" |
-
----
-
-### 🚨 RULE #6: OUTPUT FORMAT IS EXACT
-
-**Always output in code block for easy copying:**
-
-```
-markdown
-# Project Context Brief
-Last updated: [ISO timestamp]
-
-[Extracted sections...]
-
----
-**Paste this into**: ChatGPT, Perplexity, Gemini, or Claude web
-**Purpose**: Load full project context for AI assistance
-**Limit**: This excerpt is ≤300 lines for easy pasting
-```
-
-**DO NOT output as plain text, tables, or separate sections - use single code block for easy selection and copy.**
-
----
-
-### KEY FILES & STATE TO REMEMBER
-
-| File/State | Purpose | Notes |
-|-----------|---------|-------|
-| docs/context.md | Source file | Must exist, read-only |
-| Output limit | Max 300 lines | Count carefully |
-| Line counter | Track total | Update as you extract |
-| Code block | Output format | For easy copy-paste |
-
----
-
-### ANTI-PATTERNS & CORRECT PATTERNS
-
-❌ **DON'T**: Modify docs/context.md
-✅ **DO**: Read-only extract only
-
-❌ **DON'T**: Output >300 lines
-✅ **DO**: Condense to fit limit
-
-❌ **DON'T**: Include full ADR descriptions
-✅ **DO**: ADR titles + status only
-
-❌ **DON'T**: Include progress/notes sections
-✅ **DO**: Overview, focus, tech, decisions, features, next only
-
-❌ **DON'T**: Output as plain text
-✅ **DO**: Single markdown code block for copy-paste
-
----
-
-### REMEMBER AFTER COMPACTION
-
-After this command completes:
-- ✓ Excerpt extracted from docs/context.md (read-only)
-- ✓ Output ≤300 lines (verified count)
-- ✓ Formatted in markdown code block
-- ✓ Ready to paste into ChatGPT, Perplexity, Gemini, Claude web
-- ✓ Use `/agileflow:context:full` to regenerate docs/context.md
-- ✓ Use `/agileflow:context:note` to add timestamped notes to context.md
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## IMMEDIATE ACTIONS
-
-Upon invocation, execute these steps:
-
-### Step 1: Read Context File
-
-Read `docs/context.md`. If it doesn't exist, inform user to run `/agileflow:context:full` first.
-
-### Step 2: Extract Key Sections
-
-From the context file, extract only:
-- Last updated timestamp
-- What we're building (project overview)
-- Current focus (active work)
-- Tech/tooling summary
-- Key decisions (ADRs list)
-- Feature map (one line per epic)
-- Next steps
-
-### Step 3: Format Output
-
-Output the excerpt in a code block:
-
-```markdown
-# Project Context Brief
-Last updated: [timestamp]
-
-## What We're Building
-[Brief description]
-
-## Current Focus
-[Active epics/stories]
-
-## Tech Stack
-[Key technologies]
-
-## Key Decisions
-[ADR list]
-
-## Feature Map
-[Epic status summary]
-
-## Next Steps
-[Ready stories]
-```
-
-### Step 4: Add Instructions
-
-End with:
-
-```
----
-Paste this excerpt into your web AI tool (ChatGPT, Perplexity, Gemini, etc.) to load context.
-```
-
----
-
-## Constraints
-
-- **LIMIT**: ≤300 lines total output
-- **NO FILE WRITES**: This is read-only
-- **NO TaskCreate/TaskUpdate needed**: Simple single-step operation
-
----
-
-## Related Commands
-
-- `/agileflow:context:full` - Generate/refresh full context brief
-- `/agileflow:context:note` - Add quick timestamped note
-- `/agileflow:research:ask` - Generate research prompt for web AI

package/src/core/commands/context/full.md

@@ -1,353 +0,0 @@
----
-description: Generate/refresh full context brief for web AI tools
-argument-hint: "(no arguments)"
-compact_context:
-  priority: high
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:context:full - Generates docs/context.md for external AI tools"
-    - "ALWAYS create TaskCreate/TaskUpdate list for multi-step workflow tracking"
-    - "ALWAYS show diff BEFORE ANY file writes - wait for YES/NO confirmation"
-    - "PRESERVE user-written content - only update sections between MANAGED_SECTION markers"
-    - "REQUIRED SOURCES: status.json, bus/log.jsonl, epics, stories, ADRs, practices, architecture, CI, CHANGELOG"
-    - "MANAGED SECTIONS: overview, features, tech, decisions, progress, next"
-    - "DIFF-FIRST PATTERN: Read → Gather → Generate → Show diff → Confirm → Apply"
-  state_fields:
-    - context_sources
-    - managed_sections
-    - user_content_preserved
-    - user_confirmation
----
-
-# /agileflow:context:full
-
-Generate or refresh the comprehensive context brief for web AI tools.
-
----
-
-## Purpose
-
-Creates `docs/context.md` with managed sections containing:
-- What we're building and current focus
-- Feature map and tech/tooling summary
-- Key decisions (ADRs) and architecture snapshot
-- Testing & CI status
-- Recent progress (last 10 bus messages)
-- Risks and next steps
-
-This file is designed to be pasted into ChatGPT, Perplexity, Gemini, or Claude web to give external AI tools full project context.
-
----
-
-## STEP 0: Gather Context
-
-```bash
-node .agileflow/scripts/obtain-context.js context:full
-```
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## ⚠️ COMPACT SUMMARY - /agileflow:context:full IS ACTIVE
-
-**CRITICAL**: You are generating `docs/context.md` for external AI tools. Follow these rules EXACTLY.
-
-**PURPOSE**: Create comprehensive context brief with managed sections that external AI tools (ChatGPT, Claude web, Perplexity) can paste for full project understanding.
-
----
-
-### 🚨 RULE #1: ALWAYS START WITH TaskCreate/TaskUpdate LIST
-
-**Before ANY gathering, create TaskCreate/TaskUpdate to track workflow:**
-
-```xml
-<invoke name="TaskCreate/TaskUpdate">
-<parameter name="todos">[
-  {"content": "Read existing docs/context.md", "status": "in_progress", "activeForm": "Reading context file"},
-  {"content": "Gather sources (status.json, bus, epics, ADRs, practices, architecture, CI, CHANGELOG)", "status": "pending", "activeForm": "Gathering sources"},
-  {"content": "Generate/update managed sections (6 sections)", "status": "pending", "activeForm": "Generating sections"},
-  {"content": "Show diff for review", "status": "pending", "activeForm": "Showing diff"},
-  {"content": "Apply changes after YES confirmation", "status": "pending", "activeForm": "Applying changes"}
-]</parameter>
-</invoke>
-```
-
-**NEVER skip this.** It's how we track multi-step work.
-
----
-
-### 🚨 RULE #2: DIFF-FIRST - ALWAYS SHOW CHANGES BEFORE WRITING
-
-**Workflow sequence is NON-NEGOTIABLE:**
-1. **Read** existing `docs/context.md` (if exists) - identify user vs managed content
-2. **Gather** all source files (see REQUIRED SOURCES below)
-3. **Generate** new managed sections
-4. **Show diff** - display exactly what changed (use diff format)
-5. **Confirm** - call AskUserQuestion: "Apply these changes?"
-6. **Apply** - only after YES, write to file using Edit tool
-
-**❌ WRONG:** Write changes without showing diff first
-**✅ RIGHT:** Show diff, wait for YES, then write
-
----
-
-### 🚨 RULE #3: PRESERVE USER-WRITTEN CONTENT
-
-**MANAGED SECTIONS are within markers:**
-```markdown
-<!-- MANAGED_SECTION: overview -->
-[Content here - OK to update]
-<!-- END_MANAGED -->
-```
-
-**USER-WRITTEN SECTIONS have no markers:**
-```markdown
-## My Custom Section
-[Content here - NEVER touch this]
-```
-
-**Rules for updating:**
-- Only modify content between `<!-- MANAGED_SECTION: X -->` markers
-- NEVER delete or modify sections without markers
-- If user has added custom sections outside markers, preserve them
-- If user section conflicts with managed section, show diff and ask
-
----
-
-### 🚨 RULE #4: REQUIRED SOURCES & MANAGED SECTIONS
-
-**Required source files (gather ALL, even if missing):**
-```
-docs/09-agents/status.json       # Current story/epic status (REQUIRED)
-docs/09-agents/bus/log.jsonl     # Last 10 progress messages (REQUIRED)
-docs/05-epics/*.md               # Epic details (if exists)
-docs/06-stories/*/*.md           # Story details (if exists)
-docs/03-decisions/*.md           # ADRs (if exists)
-docs/02-practices/*.md           # Development practices (if exists)
-docs/04-architecture/*.md        # System architecture (if exists)
-package.json / pyproject.toml    # Project manifest (for tech stack)
-.github/workflows/*.yml          # CI config (if exists)
-CHANGELOG.md                     # Recent changes (if exists)
-```
-
-**Managed sections to generate (6 total):**
-
-| Section | Source | Purpose | Max Lines |
-|---------|--------|---------|-----------|
-| **overview** | README, package.json | What we're building + current focus | 10 |
-| **features** | status.json epics | Epic map with story counts | 20 |
-| **tech** | package.json, workflows | Tech stack and dependencies | 15 |
-| **decisions** | ADRs directory | Key ADRs with status | 15 |
-| **progress** | bus/log.jsonl | Last 10 bus messages (chronological) | 30 |
-| **next** | status.json | Ready/in-progress stories | 20 |
-
----
-
-### 🚨 RULE #5: HANDLING MISSING FILES
-
-**If file doesn't exist, DON'T ERROR - adapt:**
-
-| Missing File | Action |
-|--------------|--------|
-| `docs/context.md` | Create new file with all sections |
-| `status.json` | Skip features/next sections, leave placeholders |
-| `bus/log.jsonl` | Skip progress section |
-| `ADR files` | Skip decisions section |
-| `CI config` | Skip CI details from tech section |
-
-**Placeholder format for missing sections:**
-```markdown
-<!-- MANAGED_SECTION: features -->
-No epics found. Create epics in docs/05-epics/ to populate this section.
-<!-- END_MANAGED -->
-```
-
----
-
-### 🚨 RULE #6: CONFIRMATION BEFORE WRITING
-
-**Always use AskUserQuestion before Edit:**
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Apply these changes to docs/context.md?",
-  "header": "Confirm Context Update",
-  "multiSelect": false,
-  "options": [
-    {"label": "Yes, update", "description": "Write changes to file"},
-    {"label": "No, abort", "description": "Cancel without saving"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-**Only call Edit tool if response is YES.**
-
----
-
-### KEY FILES & STATE TO REMEMBER
-
-| File/State | Purpose | Path |
-|-----------|---------|------|
-| Managed source | List of files to read | Required sources (Rule 4) |
-| Diff display | What's changing | Show before confirm |
-| User confirmation | Gate before writing | YES = write, NO = cancel |
-| Managed sections | Content to update | 6 sections (overview, features, tech, decisions, progress, next) |
-| File markers | Protect user content | Between `<!-- MANAGED_SECTION: X -->` markers |
-
----
-
-### ANTI-PATTERNS & CORRECT PATTERNS
-
-❌ **DON'T**: Write directly without diff
-✅ **DO**: Show diff → ask → write
-
-❌ **DON'T**: Modify user-written content
-✅ **DO**: Only touch content between MANAGED_SECTION markers
-
-❌ **DON'T**: Skip gathering if file missing
-✅ **DO**: Gather what exists, use placeholders for missing
-
-❌ **DON'T**: Create context.md without section markers
-✅ **DO**: All managed content wrapped in `<!-- MANAGED_SECTION: X -->` markers
-
----
-
-### REMEMBER AFTER COMPACTION
-
-After this command completes:
-- ✓ docs/context.md created/updated with managed sections
-- ✓ User-written content preserved (outside markers untouched)
-- ✓ File ready for pasting into ChatGPT, Perplexity, Gemini, Claude web
-- ✓ Use `/agileflow:context:export` to get ≤300 line excerpt for pasting
-- ✓ Use `/agileflow:context:note` to add quick timestamped notes
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## IMMEDIATE ACTIONS
-
-Upon invocation, execute these steps:
-
-### Step 1: Create Todo List
-
-```xml
-<invoke name="TaskCreate/TaskUpdate">
-<parameter name="todos">[
-  {"content": "Read existing docs/context.md", "status": "in_progress", "activeForm": "Reading context file"},
-  {"content": "Gather sources (status.json, bus, epics, ADRs)", "status": "pending", "activeForm": "Gathering sources"},
-  {"content": "Generate managed sections", "status": "pending", "activeForm": "Generating sections"},
-  {"content": "Show diff for review", "status": "pending", "activeForm": "Showing diff"},
-  {"content": "Apply changes after YES", "status": "pending", "activeForm": "Applying changes"}
-]</parameter>
-</invoke>
-```
-
-### Step 2: Read Existing Context
-
-Read `docs/context.md` if it exists. Note which sections are managed (between `<!-- MANAGED_SECTION -->` and `<!-- END_MANAGED -->` markers) vs user-written.
-
-### Step 3: Gather Sources
-
-Read these files if they exist:
-- `docs/09-agents/status.json` - Current story status
-- `docs/09-agents/bus/log.jsonl` - Last 10 progress messages
-- `docs/05-epics/*.md` - Epic details
-- `docs/06-stories/*/*.md` - Story details
-- `docs/03-decisions/*.md` - ADRs
-- `docs/02-practices/*.md` - Practices
-- `docs/04-architecture/*.md` - Architecture docs
-- `package.json` or `pyproject.toml` - Project manifest
-- `.github/workflows/*.yml` - CI config
-- `CHANGELOG.md` - Recent changes
-
-### Step 4: Generate Managed Sections
-
-Create or update these sections:
-
-```markdown
-<!-- MANAGED_SECTION: overview -->
-## What We're Building
-[Project description from package.json or README]
-
-## Current Focus
-[From status.json: active epics/stories]
-<!-- END_MANAGED -->
-
-<!-- MANAGED_SECTION: features -->
-## Feature Map
-| Epic | Status | Stories |
-|------|--------|---------|
-[One line per epic from status.json]
-<!-- END_MANAGED -->
-
-<!-- MANAGED_SECTION: tech -->
-## Tech Stack
-- Framework: [from package.json]
-- Key dependencies: [list major deps]
-- Testing: [from scripts or CI]
-<!-- END_MANAGED -->
-
-<!-- MANAGED_SECTION: decisions -->
-## Key Decisions (ADRs)
-[List of ADRs with titles and status]
-<!-- END_MANAGED -->
-
-<!-- MANAGED_SECTION: progress -->
-## Recent Progress
-[Last 10 entries from bus/log.jsonl]
-<!-- END_MANAGED -->
-
-<!-- MANAGED_SECTION: next -->
-## Next Steps
-[Stories in READY status]
-<!-- END_MANAGED -->
-```
-
-### Step 5: Show Diff
-
-Display the changes as a diff:
-
-```diff
-- [old content]
-+ [new content]
-```
-
-### Step 6: Ask for Confirmation
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Apply these changes to docs/context.md?",
-  "header": "Confirm",
-  "multiSelect": false,
-  "options": [
-    {"label": "Yes, update", "description": "Write changes to file"},
-    {"label": "No, abort", "description": "Cancel without saving"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### Step 7: Apply Changes
-
-If YES: Write to `docs/context.md` using Edit tool, preserving user-written content.
-
----
-
-## Rules
-
-- Update ONLY managed sections (between markers)
-- NEVER modify user-written content outside markers
-- Diff-first: Always show changes before writing
-- Create file if it doesn't exist
-
----
-
-## Related Commands
-
-- `/agileflow:context:export` - Export concise excerpt for pasting
-- `/agileflow:context:note` - Add quick timestamped note
-- `/agileflow:research:ask` - Generate research prompt for web AI