@howlil/ez-agents 3.5.0 → 4.0.0

package/ez-agents/templates/debug-subagent-prompt.md

@@ -1,91 +1,91 @@
-# Debug Subagent Prompt Template
-
-Template for spawning ez-debugger agent. The agent contains all debugging expertise - this template provides problem context only.
-
----
-
-## Template
-
-```markdown
-<objective>
-Investigate issue: {issue_id}
-
-**Summary:** {issue_summary}
-</objective>
-
-<symptoms>
-expected: {expected}
-actual: {actual}
-errors: {errors}
-reproduction: {reproduction}
-timeline: {timeline}
-</symptoms>
-
-<mode>
-symptoms_prefilled: {true_or_false}
-goal: {find_root_cause_only | find_and_fix}
-</mode>
-
-<debug_file>
-Create: .planning/debug/{slug}.md
-</debug_file>
-```
-
----
-
-## Placeholders
-
-| Placeholder | Source | Example |
-|-------------|--------|---------|
-| `{issue_id}` | Orchestrator-assigned | `auth-screen-dark` |
-| `{issue_summary}` | User description | `Auth screen is too dark` |
-| `{expected}` | From symptoms | `See logo clearly` |
-| `{actual}` | From symptoms | `Screen is dark` |
-| `{errors}` | From symptoms | `None in console` |
-| `{reproduction}` | From symptoms | `Open /auth page` |
-| `{timeline}` | From symptoms | `After recent deploy` |
-| `{goal}` | Orchestrator sets | `find_and_fix` |
-| `{slug}` | Generated | `auth-screen-dark` |
-
----
-
-## Usage
-
-**From /ez:debug:**
-```python
-Task(
-  prompt=filled_template,
-  subagent_type="ez-debugger",
-  description="Debug {slug}"
-)
-```
-
-**From diagnose-issues (UAT):**
-```python
-Task(prompt=template, subagent_type="ez-debugger", description="Debug UAT-001")
-```
-
----
-
-## Continuation
-
-For checkpoints, spawn fresh agent with:
-
-```markdown
-<objective>
-Continue debugging {slug}. Evidence is in the debug file.
-</objective>
-
-<prior_state>
-Debug file: @.planning/debug/{slug}.md
-</prior_state>
-
-<checkpoint_response>
-**Type:** {checkpoint_type}
-**Response:** {user_response}
-</checkpoint_response>
-
-<mode>
-goal: {goal}
-</mode>
-```
+# Debug Subagent Prompt Template
+
+Template for spawning ez-debugger agent. The agent contains all debugging expertise - this template provides problem context only.
+
+---
+
+## Template
+
+```markdown
+<objective>
+Investigate issue: {issue_id}
+
+**Summary:** {issue_summary}
+</objective>
+
+<symptoms>
+expected: {expected}
+actual: {actual}
+errors: {errors}
+reproduction: {reproduction}
+timeline: {timeline}
+</symptoms>
+
+<mode>
+symptoms_prefilled: {true_or_false}
+goal: {find_root_cause_only | find_and_fix}
+</mode>
+
+<debug_file>
+Create: .planning/debug/{slug}.md
+</debug_file>
+```
+
+---
+
+## Placeholders
+
+| Placeholder | Source | Example |
+|-------------|--------|---------|
+| `{issue_id}` | Orchestrator-assigned | `auth-screen-dark` |
+| `{issue_summary}` | User description | `Auth screen is too dark` |
+| `{expected}` | From symptoms | `See logo clearly` |
+| `{actual}` | From symptoms | `Screen is dark` |
+| `{errors}` | From symptoms | `None in console` |
+| `{reproduction}` | From symptoms | `Open /auth page` |
+| `{timeline}` | From symptoms | `After recent deploy` |
+| `{goal}` | Orchestrator sets | `find_and_fix` |
+| `{slug}` | Generated | `auth-screen-dark` |
+
+---
+
+## Usage
+
+**From /ez:debug:**
+```python
+Task(
+  prompt=filled_template,
+  subagent_type="ez-debugger",
+  description="Debug {slug}"
+)
+```
+
+**From diagnose-issues (UAT):**
+```python
+Task(prompt=template, subagent_type="ez-debugger", description="Debug UAT-001")
+```
+
+---
+
+## Continuation
+
+For checkpoints, spawn fresh agent with:
+
+```markdown
+<objective>
+Continue debugging {slug}. Evidence is in the debug file.
+</objective>
+
+<prior_state>
+Debug file: @.planning/debug/{slug}.md
+</prior_state>
+
+<checkpoint_response>
+**Type:** {checkpoint_type}
+**Response:** {user_response}
+</checkpoint_response>
+
+<mode>
+goal: {goal}
+</mode>
+```

package/ez-agents/templates/discovery.md

@@ -1,146 +1,146 @@
-# Discovery Template
-
-Template for `.planning/phases/XX-name/DISCOVERY.md` - shallow research for library/option decisions.
-
-**Purpose:** Answer "which library/option should we use" questions during mandatory discovery in plan-phase.
-
-For deep ecosystem research ("how do experts build this"), use `/ez:research-phase` which produces RESEARCH.md.
-
----
-
-## File Template
-
-```markdown
----
-phase: XX-name
-type: discovery
-topic: [discovery-topic]
----
-
-<session_initialization>
-Before beginning discovery, verify today's date:
-!`date +%Y-%m-%d`
-
-Use this date when searching for "current" or "latest" information.
-Example: If today is 2025-11-22, search for "2025" not "2024".
-</session_initialization>
-
-<discovery_objective>
-Discover [topic] to inform [phase name] implementation.
-
-Purpose: [What decision/implementation this enables]
-Scope: [Boundaries]
-Output: DISCOVERY.md with recommendation
-</discovery_objective>
-
-<discovery_scope>
-<include>
-- [Question to answer]
-- [Area to investigate]
-- [Specific comparison if needed]
-</include>
-
-<exclude>
-- [Out of scope for this discovery]
-- [Defer to implementation phase]
-</exclude>
-</discovery_scope>
-
-<discovery_protocol>
-
-**Source Priority:**
-1. **Context7 MCP** - For library/framework documentation (current, authoritative)
-2. **Official Docs** - For platform-specific or non-indexed libraries
-3. **WebSearch** - For comparisons, trends, community patterns (verify all findings)
-
-**Quality Checklist:**
-Before completing discovery, verify:
-- [ ] All claims have authoritative sources (Context7 or official docs)
-- [ ] Negative claims ("X is not possible") verified with official documentation
-- [ ] API syntax/configuration from Context7 or official docs (never WebSearch alone)
-- [ ] WebSearch findings cross-checked with authoritative sources
-- [ ] Recent updates/changelogs checked for breaking changes
-- [ ] Alternative approaches considered (not just first solution found)
-
-**Confidence Levels:**
-- HIGH: Context7 or official docs confirm
-- MEDIUM: WebSearch + Context7/official docs confirm
-- LOW: WebSearch only or training knowledge only (mark for validation)
-
-</discovery_protocol>
-
-
-<output_structure>
-Create `.planning/phases/XX-name/DISCOVERY.md`:
-
-```markdown
-# [Topic] Discovery
-
-## Summary
-[2-3 paragraph executive summary - what was researched, what was found, what's recommended]
-
-## Primary Recommendation
-[What to do and why - be specific and actionable]
-
-## Alternatives Considered
-[What else was evaluated and why not chosen]
-
-## Key Findings
-
-### [Category 1]
-- [Finding with source URL and relevance to our case]
-
-### [Category 2]
-- [Finding with source URL and relevance]
-
-## Code Examples
-[Relevant implementation patterns, if applicable]
-
-## Metadata
-
-<metadata>
-<confidence level="high|medium|low">
-[Why this confidence level - based on source quality and verification]
-</confidence>
-
-<sources>
-- [Primary authoritative sources used]
-</sources>
-
-<open_questions>
-[What couldn't be determined or needs validation during implementation]
-</open_questions>
-
-<validation_checkpoints>
-[If confidence is LOW or MEDIUM, list specific things to verify during implementation]
-</validation_checkpoints>
-</metadata>
-```
-</output_structure>
-
-<success_criteria>
-- All scope questions answered with authoritative sources
-- Quality checklist items completed
-- Clear primary recommendation
-- Low-confidence findings marked with validation checkpoints
-- Ready to inform PLAN.md creation
-</success_criteria>
-
-<guidelines>
-**When to use discovery:**
-- Technology choice unclear (library A vs B)
-- Best practices needed for unfamiliar integration
-- API/library investigation required
-- Single decision pending
-
-**When NOT to use:**
-- Established patterns (CRUD, auth with known library)
-- Implementation details (defer to execution)
-- Questions answerable from existing project context
-
-**When to use RESEARCH.md instead:**
-- Niche/complex domains (3D, games, audio, shaders)
-- Need ecosystem knowledge, not just library choice
-- "How do experts build this" questions
-- Use `/ez:research-phase` for these
-</guidelines>
+# Discovery Template
+
+Template for `.planning/phases/XX-name/DISCOVERY.md` - shallow research for library/option decisions.
+
+**Purpose:** Answer "which library/option should we use" questions during mandatory discovery in plan-phase.
+
+For deep ecosystem research ("how do experts build this"), use `/ez:research-phase` which produces RESEARCH.md.
+
+---
+
+## File Template
+
+```markdown
+---
+phase: XX-name
+type: discovery
+topic: [discovery-topic]
+---
+
+<session_initialization>
+Before beginning discovery, verify today's date:
+!`date +%Y-%m-%d`
+
+Use this date when searching for "current" or "latest" information.
+Example: If today is 2025-11-22, search for "2025" not "2024".
+</session_initialization>
+
+<discovery_objective>
+Discover [topic] to inform [phase name] implementation.
+
+Purpose: [What decision/implementation this enables]
+Scope: [Boundaries]
+Output: DISCOVERY.md with recommendation
+</discovery_objective>
+
+<discovery_scope>
+<include>
+- [Question to answer]
+- [Area to investigate]
+- [Specific comparison if needed]
+</include>
+
+<exclude>
+- [Out of scope for this discovery]
+- [Defer to implementation phase]
+</exclude>
+</discovery_scope>
+
+<discovery_protocol>
+
+**Source Priority:**
+1. **Context7 MCP** - For library/framework documentation (current, authoritative)
+2. **Official Docs** - For platform-specific or non-indexed libraries
+3. **WebSearch** - For comparisons, trends, community patterns (verify all findings)
+
+**Quality Checklist:**
+Before completing discovery, verify:
+- [ ] All claims have authoritative sources (Context7 or official docs)
+- [ ] Negative claims ("X is not possible") verified with official documentation
+- [ ] API syntax/configuration from Context7 or official docs (never WebSearch alone)
+- [ ] WebSearch findings cross-checked with authoritative sources
+- [ ] Recent updates/changelogs checked for breaking changes
+- [ ] Alternative approaches considered (not just first solution found)
+
+**Confidence Levels:**
+- HIGH: Context7 or official docs confirm
+- MEDIUM: WebSearch + Context7/official docs confirm
+- LOW: WebSearch only or training knowledge only (mark for validation)
+
+</discovery_protocol>
+
+
+<output_structure>
+Create `.planning/phases/XX-name/DISCOVERY.md`:
+
+```markdown
+# [Topic] Discovery
+
+## Summary
+[2-3 paragraph executive summary - what was researched, what was found, what's recommended]
+
+## Primary Recommendation
+[What to do and why - be specific and actionable]
+
+## Alternatives Considered
+[What else was evaluated and why not chosen]
+
+## Key Findings
+
+### [Category 1]
+- [Finding with source URL and relevance to our case]
+
+### [Category 2]
+- [Finding with source URL and relevance]
+
+## Code Examples
+[Relevant implementation patterns, if applicable]
+
+## Metadata
+
+<metadata>
+<confidence level="high|medium|low">
+[Why this confidence level - based on source quality and verification]
+</confidence>
+
+<sources>
+- [Primary authoritative sources used]
+</sources>
+
+<open_questions>
+[What couldn't be determined or needs validation during implementation]
+</open_questions>
+
+<validation_checkpoints>
+[If confidence is LOW or MEDIUM, list specific things to verify during implementation]
+</validation_checkpoints>
+</metadata>
+```
+</output_structure>
+
+<success_criteria>
+- All scope questions answered with authoritative sources
+- Quality checklist items completed
+- Clear primary recommendation
+- Low-confidence findings marked with validation checkpoints
+- Ready to inform PLAN.md creation
+</success_criteria>
+
+<guidelines>
+**When to use discovery:**
+- Technology choice unclear (library A vs B)
+- Best practices needed for unfamiliar integration
+- API/library investigation required
+- Single decision pending
+
+**When NOT to use:**
+- Established patterns (CRUD, auth with known library)
+- Implementation details (defer to execution)
+- Questions answerable from existing project context
+
+**When to use RESEARCH.md instead:**
+- Niche/complex domains (3D, games, audio, shaders)
+- Need ecosystem knowledge, not just library choice
+- "How do experts build this" questions
+- Use `/ez:research-phase` for these
+</guidelines>

package/ez-agents/templates/discussion.md

@@ -1,68 +1,68 @@
----
-phase: {phase-number}-{phase-slug}
-status: open
-participants: [ez-requirements-agent, ez-tech-lead-agent, ez-observer-agent, ez-scrum-master-agent]
-opened: {timestamp}
-consensus: pending
----
-
-# Phase {X}: {Name} — Pre-Execution Discussion
-
-**Purpose:** Parallel agent perspectives before phase execution. Orchestrator reads consensus before spawning executors.
-
----
-
-## Requirements Perspective (ez-requirements-agent)
-
-> *Populated by ez-requirements-agent during phase kickoff*
-
-{Populated during gather-requirements or plan-phase kickoff}
-
----
-
-## Tech Lead Perspective (ez-tech-lead-agent)
-
-> *Populated by ez-tech-lead-agent during plan-phase review*
-
-{Populated during arch-review after plan creation}
-
----
-
-## Observer Perspective (ez-observer-agent)
-
-> *Populated by ez-observer-agent during execute-phase pre-flight*
-
-{Populated during execute-phase pre-flight}
-
----
-
-## Scrum Master Perspective (ez-scrum-master-agent)
-
-> *Populated by ez-scrum-master-agent during phase kickoff*
-
-{Populated during standup or phase kickoff}
-
----
-
-## Consensus
-
-> *Synthesized by orchestrator from above perspectives*
-
-**Status:** {open | consensus-reached | needs-human}
-
-### Blockers
-{List any hard blockers from any agent, or "None"}
-
-### Key Warnings
-{List significant warnings, or "None"}
-
-### Go / No-Go
-{GO — proceed to execution | NO-GO — resolve blockers first | HUMAN-NEEDED — requires user input}
-
-### Rationale
-{1-2 sentences explaining the consensus decision}
-
----
-
-*Discussion opened: {timestamp}*
-*Last updated: {timestamp}*
+---
+phase: {phase-number}-{phase-slug}
+status: open
+participants: [ez-requirements-agent, ez-tech-lead-agent, ez-observer-agent, ez-scrum-master-agent]
+opened: {timestamp}
+consensus: pending
+---
+
+# Phase {X}: {Name} — Pre-Execution Discussion
+
+**Purpose:** Parallel agent perspectives before phase execution. Orchestrator reads consensus before spawning executors.
+
+---
+
+## Requirements Perspective (ez-requirements-agent)
+
+> *Populated by ez-requirements-agent during phase kickoff*
+
+{Populated during gather-requirements or plan-phase kickoff}
+
+---
+
+## Tech Lead Perspective (ez-tech-lead-agent)
+
+> *Populated by ez-tech-lead-agent during plan-phase review*
+
+{Populated during arch-review after plan creation}
+
+---
+
+## Observer Perspective (ez-observer-agent)
+
+> *Populated by ez-observer-agent during execute-phase pre-flight*
+
+{Populated during execute-phase pre-flight}
+
+---
+
+## Scrum Master Perspective (ez-scrum-master-agent)
+
+> *Populated by ez-scrum-master-agent during phase kickoff*
+
+{Populated during standup or phase kickoff}
+
+---
+
+## Consensus
+
+> *Synthesized by orchestrator from above perspectives*
+
+**Status:** {open | consensus-reached | needs-human}
+
+### Blockers
+{List any hard blockers from any agent, or "None"}
+
+### Key Warnings
+{List significant warnings, or "None"}
+
+### Go / No-Go
+{GO — proceed to execution | NO-GO — resolve blockers first | HUMAN-NEEDED — requires user input}
+
+### Rationale
+{1-2 sentences explaining the consensus decision}
+
+---
+
+*Discussion opened: {timestamp}*
+*Last updated: {timestamp}*