@howlil/ez-agents 3.4.1 → 3.5.0

package/ez-agents/workflows/settings.md

@@ -1,242 +1,242 @@
-<purpose>
-Interactive configuration of EZ workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences. Optionally saves settings as global defaults (`~/.ez/defaults.json`) for future projects.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="ensure_and_load_config">
-Ensure config exists and load current state:
-
-```bash
-node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" config-ensure-section
-INIT=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" state load)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Creates `.planning/config.json` with defaults if missing and loads current config values.
-</step>
-
-<step name="read_current">
-```bash
-cat .planning/config.json
-```
-
-Parse current values (default to `true` if not present):
-- `workflow.research` — spawn researcher during plan-phase
-- `workflow.plan_check` — spawn plan checker during plan-phase
-- `workflow.verifier` — spawn verifier during execute-phase
-- `workflow.nyquist_validation` — validation architecture research during plan-phase (default: true if absent)
-- `workflow.ui_phase` — generate UI-SPEC.md design contracts for frontend phases (default: true if absent)
-- `workflow.ui_safety_gate` — prompt to run /ez:ui-phase before planning frontend phases (default: true if absent)
-- `model_profile` — which model each agent uses (default: `balanced`)
-- `git.branching_strategy` — branching approach (default: `"none"`)
-</step>
-
-<step name="present_settings">
-Use AskUserQuestion with current values pre-selected:
-
-```
-AskUserQuestion([
-  {
-    question: "Which model profile for agents?",
-    header: "Model",
-    multiSelect: false,
-    options: [
-      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
-      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for execution/verification" },
-      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" }
-    ]
-  },
-  {
-    question: "Spawn Plan Researcher? (researches domain before planning)",
-    header: "Research",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Research phase goals before planning" },
-      { label: "No", description: "Skip research, plan directly" }
-    ]
-  },
-  {
-    question: "Spawn Plan Checker? (verifies plans before execution)",
-    header: "Plan Check",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Verify plans meet phase goals" },
-      { label: "No", description: "Skip plan verification" }
-    ]
-  },
-  {
-    question: "Spawn Execution Verifier? (verifies phase completion)",
-    header: "Verifier",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Verify must-haves after execution" },
-      { label: "No", description: "Skip post-execution verification" }
-    ]
-  },
-  {
-    question: "Auto-advance pipeline? (discuss → plan → execute automatically)",
-    header: "Auto",
-    multiSelect: false,
-    options: [
-      { label: "No (Recommended)", description: "Manual /clear + paste between stages" },
-      { label: "Yes", description: "Chain stages via Task() subagents (same isolation)" }
-    ]
-  },
-  {
-    question: "Enable Nyquist Validation? (researches test coverage during planning)",
-    header: "Nyquist",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Research automated test coverage during plan-phase. Adds validation requirements to plans. Blocks approval if tasks lack automated verify." },
-      { label: "No", description: "Skip validation research. Good for rapid prototyping or no-test phases." }
-    ]
-  },
-  // Note: Nyquist validation depends on research output. If research is disabled,
-  // plan-phase automatically skips Nyquist steps (no RESEARCH.md to extract from).
-  {
-    question: "Enable UI Phase? (generates UI-SPEC.md design contracts for frontend phases)",
-    header: "UI Phase",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Generate UI design contracts before planning frontend phases. Locks spacing, typography, color, and copywriting." },
-      { label: "No", description: "Skip UI-SPEC generation. Good for backend-only projects or API phases." }
-    ]
-  },
-  {
-    question: "Enable UI Safety Gate? (prompts to run /ez:ui-phase before planning frontend phases)",
-    header: "UI Gate",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "plan-phase asks to run /ez:ui-phase first when frontend indicators detected." },
-      { label: "No", description: "No prompt — plan-phase proceeds without UI-SPEC check." }
-    ]
-  },
-  {
-    question: "Git branching strategy?",
-    header: "Branching",
-    multiSelect: false,
-    options: [
-      { label: "None (Recommended)", description: "Commit directly to current branch" },
-      { label: "Per Phase", description: "Create branch for each phase (ez/phase-{N}-{name})" },
-      { label: "Per Milestone", description: "Create branch for entire milestone (ez/{version}-{name})" }
-    ]
-  }
-])
-```
-</step>
-
-<step name="update_config">
-Merge new settings into existing config.json:
-
-```json
-{
-  ...existing_config,
-  "model_profile": "quality" | "balanced" | "budget",
-  "workflow": {
-    "research": true/false,
-    "plan_check": true/false,
-    "verifier": true/false,
-    "auto_advance": true/false,
-    "nyquist_validation": true/false,
-    "ui_phase": true/false,
-    "ui_safety_gate": true/false
-  },
-  "git": {
-    "branching_strategy": "none" | "phase" | "milestone"
-  }
-}
-```
-
-Write updated config to `.planning/config.json`.
-</step>
-
-<step name="save_as_defaults">
-Ask whether to save these settings as global defaults for future projects:
-
-```
-AskUserQuestion([
-  {
-    question: "Save these as default settings for all new projects?",
-    header: "Defaults",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "New projects start with these settings (saved to ~/.ez/defaults.json)" },
-      { label: "No", description: "Only apply to this project" }
-    ]
-  }
-])
-```
-
-If "Yes": write the same config object (minus project-specific fields like `brave_search`) to `~/.ez/defaults.json`:
-
-```bash
-mkdir -p ~/.ez
-```
-
-Write `~/.ez/defaults.json` with:
-```json
-{
-  "mode": <current>,
-  "granularity": <current>,
-  "model_profile": <current>,
-  "commit_docs": <current>,
-  "parallelization": <current>,
-  "branching_strategy": <current>,
-  "workflow": {
-    "research": <current>,
-    "plan_check": <current>,
-    "verifier": <current>,
-    "auto_advance": <current>,
-    "nyquist_validation": <current>,
-    "ui_phase": <current>,
-    "ui_safety_gate": <current>
-  }
-}
-```
-</step>
-
-<step name="confirm">
-Display:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- EZ ► SETTINGS UPDATED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-| Setting              | Value |
-|----------------------|-------|
-| Model Profile        | {quality/balanced/budget} |
-| Plan Researcher      | {On/Off} |
-| Plan Checker         | {On/Off} |
-| Execution Verifier   | {On/Off} |
-| Auto-Advance         | {On/Off} |
-| Nyquist Validation   | {On/Off} |
-| UI Phase             | {On/Off} |
-| UI Safety Gate       | {On/Off} |
-| Git Branching        | {None/Per Phase/Per Milestone} |
-| Saved as Defaults    | {Yes/No} |
-
-These settings apply to future /ez:plan-phase and /ez:execute-phase runs.
-
-Quick commands:
-- /ez:set-profile <profile> — switch model profile
-- /ez:plan-phase --research — force research
-- /ez:plan-phase --skip-research — skip research
-- /ez:plan-phase --skip-verify — skip plan check
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Current config read
-- [ ] User presented with 9 settings (profile + 7 workflow toggles + git branching)
-- [ ] Config updated with model_profile, workflow, and git sections
-- [ ] User offered to save as global defaults (~/.ez/defaults.json)
-- [ ] Changes confirmed to user
-</success_criteria>
+<purpose>
+Interactive configuration of EZ workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences. Optionally saves settings as global defaults (`~/.ez/defaults.json`) for future projects.
+</purpose>
+
+<required_reading>
+Read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
+
+<process>
+
+<step name="ensure_and_load_config">
+Ensure config exists and load current state:
+
+```bash
+node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" config-ensure-section
+INIT=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" state load)
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+```
+
+Creates `.planning/config.json` with defaults if missing and loads current config values.
+</step>
+
+<step name="read_current">
+```bash
+cat .planning/config.json
+```
+
+Parse current values (default to `true` if not present):
+- `workflow.research` — spawn researcher during plan-phase
+- `workflow.plan_check` — spawn plan checker during plan-phase
+- `workflow.verifier` — spawn verifier during execute-phase
+- `workflow.nyquist_validation` — validation architecture research during plan-phase (default: true if absent)
+- `workflow.ui_phase` — generate UI-SPEC.md design contracts for frontend phases (default: true if absent)
+- `workflow.ui_safety_gate` — prompt to run /ez:ui-phase before planning frontend phases (default: true if absent)
+- `model_profile` — which model each agent uses (default: `balanced`)
+- `git.branching_strategy` — branching approach (default: `"none"`)
+</step>
+
+<step name="present_settings">
+Use AskUserQuestion with current values pre-selected:
+
+```
+AskUserQuestion([
+  {
+    question: "Which model profile for agents?",
+    header: "Model",
+    multiSelect: false,
+    options: [
+      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
+      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for execution/verification" },
+      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" }
+    ]
+  },
+  {
+    question: "Spawn Plan Researcher? (researches domain before planning)",
+    header: "Research",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Research phase goals before planning" },
+      { label: "No", description: "Skip research, plan directly" }
+    ]
+  },
+  {
+    question: "Spawn Plan Checker? (verifies plans before execution)",
+    header: "Plan Check",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify plans meet phase goals" },
+      { label: "No", description: "Skip plan verification" }
+    ]
+  },
+  {
+    question: "Spawn Execution Verifier? (verifies phase completion)",
+    header: "Verifier",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify must-haves after execution" },
+      { label: "No", description: "Skip post-execution verification" }
+    ]
+  },
+  {
+    question: "Auto-advance pipeline? (discuss → plan → execute automatically)",
+    header: "Auto",
+    multiSelect: false,
+    options: [
+      { label: "No (Recommended)", description: "Manual /clear + paste between stages" },
+      { label: "Yes", description: "Chain stages via Task() subagents (same isolation)" }
+    ]
+  },
+  {
+    question: "Enable Nyquist Validation? (researches test coverage during planning)",
+    header: "Nyquist",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Research automated test coverage during plan-phase. Adds validation requirements to plans. Blocks approval if tasks lack automated verify." },
+      { label: "No", description: "Skip validation research. Good for rapid prototyping or no-test phases." }
+    ]
+  },
+  // Note: Nyquist validation depends on research output. If research is disabled,
+  // plan-phase automatically skips Nyquist steps (no RESEARCH.md to extract from).
+  {
+    question: "Enable UI Phase? (generates UI-SPEC.md design contracts for frontend phases)",
+    header: "UI Phase",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Generate UI design contracts before planning frontend phases. Locks spacing, typography, color, and copywriting." },
+      { label: "No", description: "Skip UI-SPEC generation. Good for backend-only projects or API phases." }
+    ]
+  },
+  {
+    question: "Enable UI Safety Gate? (prompts to run /ez:ui-phase before planning frontend phases)",
+    header: "UI Gate",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "plan-phase asks to run /ez:ui-phase first when frontend indicators detected." },
+      { label: "No", description: "No prompt — plan-phase proceeds without UI-SPEC check." }
+    ]
+  },
+  {
+    question: "Git branching strategy?",
+    header: "Branching",
+    multiSelect: false,
+    options: [
+      { label: "None (Recommended)", description: "Commit directly to current branch" },
+      { label: "Per Phase", description: "Create branch for each phase (ez/phase-{N}-{name})" },
+      { label: "Per Milestone", description: "Create branch for entire milestone (ez/{version}-{name})" }
+    ]
+  }
+])
+```
+</step>
+
+<step name="update_config">
+Merge new settings into existing config.json:
+
+```json
+{
+  ...existing_config,
+  "model_profile": "quality" | "balanced" | "budget",
+  "workflow": {
+    "research": true/false,
+    "plan_check": true/false,
+    "verifier": true/false,
+    "auto_advance": true/false,
+    "nyquist_validation": true/false,
+    "ui_phase": true/false,
+    "ui_safety_gate": true/false
+  },
+  "git": {
+    "branching_strategy": "none" | "phase" | "milestone"
+  }
+}
+```
+
+Write updated config to `.planning/config.json`.
+</step>
+
+<step name="save_as_defaults">
+Ask whether to save these settings as global defaults for future projects:
+
+```
+AskUserQuestion([
+  {
+    question: "Save these as default settings for all new projects?",
+    header: "Defaults",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "New projects start with these settings (saved to ~/.ez/defaults.json)" },
+      { label: "No", description: "Only apply to this project" }
+    ]
+  }
+])
+```
+
+If "Yes": write the same config object (minus project-specific fields like `brave_search`) to `~/.ez/defaults.json`:
+
+```bash
+mkdir -p ~/.ez
+```
+
+Write `~/.ez/defaults.json` with:
+```json
+{
+  "mode": <current>,
+  "granularity": <current>,
+  "model_profile": <current>,
+  "commit_docs": <current>,
+  "parallelization": <current>,
+  "branching_strategy": <current>,
+  "workflow": {
+    "research": <current>,
+    "plan_check": <current>,
+    "verifier": <current>,
+    "auto_advance": <current>,
+    "nyquist_validation": <current>,
+    "ui_phase": <current>,
+    "ui_safety_gate": <current>
+  }
+}
+```
+</step>
+
+<step name="confirm">
+Display:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ EZ ► SETTINGS UPDATED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Setting              | Value |
+|----------------------|-------|
+| Model Profile        | {quality/balanced/budget} |
+| Plan Researcher      | {On/Off} |
+| Plan Checker         | {On/Off} |
+| Execution Verifier   | {On/Off} |
+| Auto-Advance         | {On/Off} |
+| Nyquist Validation   | {On/Off} |
+| UI Phase             | {On/Off} |
+| UI Safety Gate       | {On/Off} |
+| Git Branching        | {None/Per Phase/Per Milestone} |
+| Saved as Defaults    | {Yes/No} |
+
+These settings apply to future /ez:plan-phase and /ez:execute-phase runs.
+
+Quick commands:
+- /ez:set-profile <profile> — switch model profile
+- /ez:plan-phase --research — force research
+- /ez:plan-phase --skip-research — skip research
+- /ez:plan-phase --skip-verify — skip plan check
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Current config read
+- [ ] User presented with 9 settings (profile + 7 workflow toggles + git branching)
+- [ ] Config updated with model_profile, workflow, and git sections
+- [ ] User offered to save as global defaults (~/.ez/defaults.json)
+- [ ] Changes confirmed to user
+</success_criteria>

package/ez-agents/workflows/standup.md

@@ -0,0 +1,64 @@
+<purpose>
+Generate a sprint standup report. Analyzes recent SUMMARY.md files, STATE.md decisions/blockers, and phase progress to produce yesterday/today/blockers/velocity/health score.
+</purpose>
+
+<process>
+
+## 1. Initialize
+
+```bash
+INIT=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" init progress)
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+```
+
+Parse optional phase from $ARGUMENTS.
+
+## 2. Gather Data
+
+```bash
+STATE=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" state-snapshot)
+ROADMAP=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" roadmap analyze)
+PROGRESS_BAR=$(node "$HOME/.claude/ez-agents/bin/ez-tools.cjs" progress bar --raw)
+```
+
+Find 3-5 most recent SUMMARY.md files (last 2 sessions worth of work).
+
+## 3. Calculate Sprint Health
+
+Score 0-100 based on:
+- Plans completed vs planned (velocity): 30pts
+- Active blockers (0=30pts, 1=15pts, 2+=0pts): 30pts
+- Requirements coverage from ROADMAP: 20pts
+- Deviation rate from STATE.md: 20pts
+
+## 4. Generate Standup Report
+
+```
+## Daily Standup — {date}
+
+### Yesterday
+{recent SUMMARY.md one-liners}
+
+### Today (Planned)
+{next phase/plans from ROADMAP}
+
+### Blockers
+{from STATE.md blockers[] or "None"}
+
+### Velocity Trend
+{calculated from plan completion rate}
+
+Sprint Health: {score}/100 — {status}
+{one-line recommendation}
+```
+
+Status thresholds: 80-100=HEALTHY, 60-79=SOME FRICTION, 40-59=STRUGGLING, <40=AT RISK.
+
+</process>
+
+<success_criteria>
+- [ ] Recent work summarized
+- [ ] Next steps identified
+- [ ] Blockers surfaced
+- [ ] Sprint health score calculated
+</success_criteria>

package/ez-agents/workflows/stats.md

@@ -1,57 +1,57 @@
-<purpose>
-Display comprehensive project statistics including phases, plans, requirements, git metrics, and timeline.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="gather_stats">
-Gather project statistics:
-
-```bash
-STATS=$(node "$EZ_TOOLS" stats json)
-if [[ "$STATS" == @file:* ]]; then STATS=$(cat "${STATS#@file:}"); fi
-```
-
-Extract fields from JSON: `milestone_version`, `milestone_name`, `phases`, `total_plans`, `total_summaries`, `percent`, `requirements_total`, `requirements_complete`, `git_commits`, `git_first_commit_date`, `last_activity`.
-</step>
-
-<step name="present_stats">
-Present to the user with this format:
-
-```
-# 📊 Project Statistics — {milestone_version} {milestone_name}
-
-## Progress
-[████████░░] X/Y plans (Z%)
-
-## Phases
-| Phase | Name | Plans | Completed | Status |
-|-------|------|-------|-----------|--------|
-| ...   | ...  | ...   | ...       | ...    |
-
-## Requirements
-✅ X/Y requirements complete
-
-## Git
-- **Commits:** N
-- **Started:** YYYY-MM-DD
-- **Last activity:** YYYY-MM-DD
-
-## Timeline
-- **Project age:** N days
-```
-
-If no `.planning/` directory exists, inform the user to run `/ez:new-project` first.
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Statistics gathered from project state
-- [ ] Results formatted clearly
-- [ ] Displayed to user
-</success_criteria>
+<purpose>
+Display comprehensive project statistics including phases, plans, requirements, git metrics, and timeline.
+</purpose>
+
+<required_reading>
+Read all files referenced by the invoking prompt's execution_context before starting.
+</required_reading>
+
+<process>
+
+<step name="gather_stats">
+Gather project statistics:
+
+```bash
+STATS=$(node "$EZ_TOOLS" stats json)
+if [[ "$STATS" == @file:* ]]; then STATS=$(cat "${STATS#@file:}"); fi
+```
+
+Extract fields from JSON: `milestone_version`, `milestone_name`, `phases`, `total_plans`, `total_summaries`, `percent`, `requirements_total`, `requirements_complete`, `git_commits`, `git_first_commit_date`, `last_activity`.
+</step>
+
+<step name="present_stats">
+Present to the user with this format:
+
+```
+# 📊 Project Statistics — {milestone_version} {milestone_name}
+
+## Progress
+[████████░░] X/Y plans (Z%)
+
+## Phases
+| Phase | Name | Plans | Completed | Status |
+|-------|------|-------|-----------|--------|
+| ...   | ...  | ...   | ...       | ...    |
+
+## Requirements
+✅ X/Y requirements complete
+
+## Git
+- **Commits:** N
+- **Started:** YYYY-MM-DD
+- **Last activity:** YYYY-MM-DD
+
+## Timeline
+- **Project age:** N days
+```
+
+If no `.planning/` directory exists, inform the user to run `/ez:new-project` first.
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Statistics gathered from project state
+- [ ] Results formatted clearly
+- [ ] Displayed to user
+</success_criteria>