create-harness-vibe-coding 0.7.2 → 0.8.0

package/templates/common/{docs/harness → Harness}/dispatch.md

@@ -1,99 +1,99 @@
-# Dispatch Protocol
-
-Purpose: coordinate a small set of subagents without building a scheduler.
-
-Use [subagents.md](subagents.md) for orchestration strategy. Use this file for the dispatch table, handoff format, and status protocol.
-
-Use when work needs parallel reading, independent review, cross-layer analysis, or more than one bounded implementation pass.
-
-## Principles
-
-- Main agent owns the final decision, integration, and verification.
-- project files are the only durable communication channel; chat/subagent transcript state is non-authoritative.
-- Important assumptions, decisions, blockers, evidence, and handoffs must be written to `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, `Harness/MEMORY.md`, or `Harness/memory/*` as appropriate.
-- Prefer three or fewer active agents (WF mode overrides this; see [WF.md](WF.md)).
-- Read-only agents may run in parallel.
-- Writing agents run serially unless write sets are disjoint.
-- Use a worktree when two agents may touch overlapping files or long-running branches.
-- Only summaries enter main context. Load named files directly when details are needed.
-- Subagents read task files, return findings and PLAN patch suggestions. Only the main agent commits changes to PROGRESS.md and PLAN.md.
-
-## Dispatch Loop
-
-```text
-Goal
--> Fill task PROGRESS.md and PLAN.md
--> Apply subagents.md efficiency ladder
--> Run parallel read-only agents
--> Main agent integrates findings
--> Test Writer defines failing test or manual check
--> Implementer makes bounded change
--> Reviewer checks diff
--> Verifier records evidence
--> Main agent updates task files and closes or iterates
-```
-
-## Modes
-
-| Mode | Use When | Constraint |
-| --- | --- | --- |
-| Parallel Read | research, exploration, architecture review, docs/API check | no writes |
-| Serial Write | tests, implementation, docs sync | one writer at a time |
-| Isolated Worktree | overlapping write sets or competing approaches | merge only after review |
-
-## Common Agents
-
-| Agent | Mode | Purpose |
-| --- | --- | --- |
-| `planner` | Parallel Read | split goal into tasks, dependencies, write sets |
-| Explorer Pass | Parallel Read | bounded read-only exploration when no dedicated agent is needed |
-| `researcher` | Parallel Read | product, market, ecosystem, dependency research |
-| `docs-researcher` | Parallel Read | official docs, API, SDK, version, limits |
-| `architect` | Parallel Read | layer boundaries, ports, data flow, state impact |
-| `test-writer` | Serial Write | failing test or manual verification plan |
-| `implementer` | Serial Write | minimal change inside declared write set |
-| `debugger` | Serial Write | smallest fix for a reproduced failure |
-| `reviewer` | Parallel Read | diff review, risks, missing tests |
-| `verifier` | Parallel Read | run checks and record evidence |
-| `memory-master` | Serial Write | write/consolidate memory entries, dedup, cross-project extraction |
-| `context-master` | Parallel Read | analyze context usage, recommend compression, extract session knowledge |
-| `explore-manager` | Parallel Read | WF-MAX W0: spawn 5-10 researchers, synthesize, report to CEO |
-| `architect-manager` | Parallel Read | WF-MAX W1: spawn 3 architects, synthesize interface contracts |
-| `implement-manager` | Serial Write | WF-MAX W2: spawn implementers (one file_claim each), merge results |
-| `review-manager` | Parallel Read | WF-MAX W2R: spawn 3-4 reviewers, deduplicate, classify severity |
-
-## Dispatch Rules
-
-- Every dispatch row needs task, agent, mode, read set, write set, dependency, output, and status.
-- A write set of `none` means read-only.
-- If two write sets overlap, do not run those agents in parallel.
-- If an agent returns uncertainty, mark the row `Blocked` or add a follow-up row.
-- If docs, tests, and code disagree, stop implementation and record the conflict in `Harness/tasks/<task-id>/PROGRESS.md`.
-- In /wf max, file claims must respect WF-MAX.md leaf condition: no split below 50 avgLines, no split when files ≤ span×2.
-
-## Handoff Format
-
-Subagents return summaries in this shape:
-
-```text
-Agent:
-Task:
-Mode:
-Files read:
-Files changed:
-Findings:
-Evidence:
-Risks:
-Next:
-PLAN patch:
-Concurrency group:  <wave number — 0=exploration, 1,2,3,...=implementation waves. Optional; only used in /wf max.>
-File claim:         <list of exact file paths this agent exclusively owns. Optional; only used in /wf max.>
-Granularity floor:  <50 avgLines → do NOT spawn. Apply leaf condition from WF-MAX.md.>
-```
-
-Use `Files changed: none` for read-only agents. Use `PLAN patch: none` when no state update is needed.
-If a handoff matters after context loss, write it to `Harness/tasks/<task-id>/PROGRESS.md`, `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, or `Harness/memory/*`; do not rely on chat transcript state.
-
-## Statuses
-
-Allowed dispatch statuses: Pending / In Progress / Returned / Integrated / Blocked / Verified.
+# Dispatch Protocol
+
+Purpose: coordinate a small set of subagents without building a scheduler.
+
+Use [subagents.md](subagents.md) for orchestration strategy. Use this file for the dispatch table, handoff format, and status protocol.
+
+Use when work needs parallel reading, independent review, cross-layer analysis, or more than one bounded implementation pass.
+
+## Principles
+
+- Main agent owns the final decision, integration, and verification.
+- project files are the only durable communication channel; chat/subagent transcript state is non-authoritative.
+- Important assumptions, decisions, blockers, evidence, and handoffs must be written to `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, `Harness/MEMORY.md`, or `Harness/memory/*` as appropriate.
+- Prefer three or fewer active agents (WF mode overrides this; see [WF.md](WF.md)).
+- Read-only agents may run in parallel.
+- Writing agents run serially unless write sets are disjoint.
+- Use a worktree when two agents may touch overlapping files or long-running branches.
+- Only summaries enter main context. Load named files directly when details are needed.
+- Subagents read task files, return findings and PLAN patch suggestions. Only the main agent commits changes to PROGRESS.md and PLAN.md.
+
+## Dispatch Loop
+
+```text
+Goal
+-> Fill task PROGRESS.md and PLAN.md
+-> Apply subagents.md efficiency ladder
+-> Run parallel read-only agents
+-> Main agent integrates findings
+-> Test Writer defines failing test or manual check
+-> Implementer makes bounded change
+-> Reviewer checks diff
+-> Verifier records evidence
+-> Main agent updates task files and closes or iterates
+```
+
+## Modes
+
+| Mode | Use When | Constraint |
+| --- | --- | --- |
+| Parallel Read | research, exploration, architecture review, docs/API check | no writes |
+| Serial Write | tests, implementation, docs sync | one writer at a time |
+| Isolated Worktree | overlapping write sets or competing approaches | merge only after review |
+
+## Common Agents
+
+| Agent | Mode | Purpose |
+| --- | --- | --- |
+| `planner` | Parallel Read | split goal into tasks, dependencies, write sets |
+| Explorer Pass | Parallel Read | bounded read-only exploration when no dedicated agent is needed |
+| `researcher` | Parallel Read | product, market, ecosystem, dependency research |
+| `docs-researcher` | Parallel Read | official docs, API, SDK, version, limits |
+| `architect` | Parallel Read | layer boundaries, ports, data flow, state impact |
+| `test-writer` | Serial Write | failing test or manual verification plan |
+| `implementer` | Serial Write | minimal change inside declared write set |
+| `debugger` | Serial Write | smallest fix for a reproduced failure |
+| `reviewer` | Parallel Read | diff review, risks, missing tests |
+| `verifier` | Parallel Read | run checks and record evidence |
+| `memory-master` | Serial Write | write/consolidate memory entries, dedup, cross-project extraction |
+| `context-master` | Parallel Read | analyze context usage, recommend compression, extract session knowledge |
+| `explore-manager` | Parallel Read | WF-MAX W0: spawn 5-10 researchers, synthesize, report to CEO |
+| `architect-manager` | Parallel Read | WF-MAX W1: spawn 3 architects, synthesize interface contracts |
+| `implement-manager` | Serial Write | WF-MAX W2: spawn implementers (one file_claim each), merge results |
+| `review-manager` | Parallel Read | WF-MAX W2R: spawn 3-4 reviewers, deduplicate, classify severity |
+
+## Dispatch Rules
+
+- Every dispatch row needs task, agent, mode, read set, write set, dependency, output, and status.
+- A write set of `none` means read-only.
+- If two write sets overlap, do not run those agents in parallel.
+- If an agent returns uncertainty, mark the row `Blocked` or add a follow-up row.
+- If docs, tests, and code disagree, stop implementation and record the conflict in `Harness/tasks/<task-id>/PROGRESS.md`.
+- In /wf max, file claims must respect WF-MAX.md leaf condition: no split below 50 avgLines, no split when files ≤ span×2.
+
+## Handoff Format
+
+Subagents return summaries in this shape:
+
+```text
+Agent:
+Task:
+Mode:
+Files read:
+Files changed:
+Findings:
+Evidence:
+Risks:
+Next:
+PLAN patch:
+Concurrency group:  <wave number — 0=exploration, 1,2,3,...=implementation waves. Optional; only used in /wf max.>
+File claim:         <list of exact file paths this agent exclusively owns. Optional; only used in /wf max.>
+Granularity floor:  <50 avgLines → do NOT spawn. Apply leaf condition from WF-MAX.md.>
+```
+
+Use `Files changed: none` for read-only agents. Use `PLAN patch: none` when no state update is needed.
+If a handoff matters after context loss, write it to `Harness/tasks/<task-id>/PROGRESS.md`, `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, or `Harness/memory/*`; do not rely on chat transcript state.
+
+## Statuses
+
+Allowed dispatch statuses: Pending / In Progress / Returned / Integrated / Blocked / Verified.

package/templates/common/{docs → Harness}/research/research-results.md

@@ -1,66 +1,66 @@
-# {{projectName}} - Research Results
-
-> **Purpose**: Record final research results and decisions. Use [README.md](README.md) for process, tools, queries, and research-agent rules.
-> **Principle**: Each candidate has a clear Purpose / Strength / Weakness / Decision.
-
----
-
-## Research Date
-
-{{YYYY-MM-DD}}
-
-## Research Goal
-
-{{WHAT_YOU_ARE_RESEARCHING}}
-
----
-
-## Candidate References
-
-### 1) {{CANDIDATE_1}}
-
-- **What it is**: {{DESCRIPTION}}
-- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
-- **Checked Date**: {{YYYY-MM-DD}}
-- **Strengths**: {{STRENGTHS}}
-- **Weaknesses**: {{WEAKNESSES}}
-- **Decision**: {{ADOPT / REJECT / WATCH}}
-- **Link**: {{URL}}
-
-### 2) {{CANDIDATE_2}}
-
-- **What it is**: {{DESCRIPTION}}
-- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
-- **Checked Date**: {{YYYY-MM-DD}}
-- **Strengths**: {{STRENGTHS}}
-- **Weaknesses**: {{WEAKNESSES}}
-- **Decision**: {{ADOPT / REJECT / WATCH}}
-- **Link**: {{URL}}
-
-### 3) {{CANDIDATE_3}}
-
-- **What it is**: {{DESCRIPTION}}
-- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
-- **Checked Date**: {{YYYY-MM-DD}}
-- **Strengths**: {{STRENGTHS}}
-- **Weaknesses**: {{WEAKNESSES}}
-- **Decision**: {{ADOPT / REJECT / WATCH}}
-- **Link**: {{URL}}
-
----
-
-## Final Decision
-
-- **Architecture Style**: {{DECISION}}
-- **Core References**: {{REFERENCES}}
-- **Key Constraints**:
-  - {{CONSTRAINT_1}}
-  - {{CONSTRAINT_2}}
-  - {{CONSTRAINT_3}}
-
----
-
-## Not Adopted But Worth Watching
-
-- {{ALTERNATIVE_1}}
-- {{ALTERNATIVE_2}}
+# {{projectName}} - Research Results
+
+> **Purpose**: Record final research results and decisions. Use [README.md](README.md) for process, tools, queries, and research-agent rules.
+> **Principle**: Each candidate has a clear Purpose / Strength / Weakness / Decision.
+
+---
+
+## Research Date
+
+{{YYYY-MM-DD}}
+
+## Research Goal
+
+{{WHAT_YOU_ARE_RESEARCHING}}
+
+---
+
+## Candidate References
+
+### 1) {{CANDIDATE_1}}
+
+- **What it is**: {{DESCRIPTION}}
+- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
+- **Checked Date**: {{YYYY-MM-DD}}
+- **Strengths**: {{STRENGTHS}}
+- **Weaknesses**: {{WEAKNESSES}}
+- **Decision**: {{ADOPT / REJECT / WATCH}}
+- **Link**: {{URL}}
+
+### 2) {{CANDIDATE_2}}
+
+- **What it is**: {{DESCRIPTION}}
+- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
+- **Checked Date**: {{YYYY-MM-DD}}
+- **Strengths**: {{STRENGTHS}}
+- **Weaknesses**: {{WEAKNESSES}}
+- **Decision**: {{ADOPT / REJECT / WATCH}}
+- **Link**: {{URL}}
+
+### 3) {{CANDIDATE_3}}
+
+- **What it is**: {{DESCRIPTION}}
+- **Source Type**: {{OFFICIAL_DOCS / GITHUB_REPO / COMMUNITY / PAPER / OTHER}}
+- **Checked Date**: {{YYYY-MM-DD}}
+- **Strengths**: {{STRENGTHS}}
+- **Weaknesses**: {{WEAKNESSES}}
+- **Decision**: {{ADOPT / REJECT / WATCH}}
+- **Link**: {{URL}}
+
+---
+
+## Final Decision
+
+- **Architecture Style**: {{DECISION}}
+- **Core References**: {{REFERENCES}}
+- **Key Constraints**:
+  - {{CONSTRAINT_1}}
+  - {{CONSTRAINT_2}}
+  - {{CONSTRAINT_3}}
+
+---
+
+## Not Adopted But Worth Watching
+
+- {{ALTERNATIVE_1}}
+- {{ALTERNATIVE_2}}