create-harness-vibe-coding 0.1.8 → 0.1.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-harness-vibe-coding",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Scaffold a 0-1 product harness for AI-assisted research, PRD, planning, architecture, build, test, and feedback loops",
   "type": "module",
   "bin": {

package/templates/common/docs/features/_template.md

@@ -1,9 +1,12 @@
 # {{FEATURE_NAME}}
 
-> **When to use**: During the PRD phase, every new feature identified in `research/PRD.md` must have its own features document created from this template. One feature = one doc = one implementation unit. Do not code a PRD scope item without a corresponding features doc.
+> **When to use**: Every PRD scope item in `research/PRD.md` Section 2 must have a feature doc — either a new one from this template, or an iteration on an existing one. Do not code a PRD scope item without a corresponding features doc.
+>
+> **New vs iterate**: If the scope item has ≥85% overlap with an existing feature doc, iterate the existing doc (bump `Version`, add a `## Changelog` entry). If overlap is below 85%, create a new file from this template. When in doubt, ask the user.
 
 > **Status**: Draft / In Progress / Blocked / Done
 > **Created**: {{YYYY-MM-DD}}
+> **Version**: 1
 > **Owner**: {{OWNER_OR_AGENT}}
 > **Related Docs**: {{PRD_OR_ARCH_DOC_LINKS}}
 
@@ -142,3 +145,13 @@ Estimate the context budget for this feature. If the main agent would need to re
 
 Remaining risks:
 - {{RISK_OR_NONE}}
+
+---
+
+## 5. Changelog
+
+> Only populate when iterating an existing feature doc (Version ≥ 2).
+
+| Version | Date | What Changed | Reason |
+| --- | --- | --- | --- |
+| 1 | {{YYYY-MM-DD}} | Initial version | — |

package/templates/common/docs/harness/agent-workflow.md

@@ -12,15 +12,11 @@ If context grows, load [context-loading.md](context-loading.md) and split the wo
 
 ## Feature Packet
 
-Create `docs/features/{{FEATURE_SLUG}}.md` from [../features/_template.md](../features/_template.md) when work changes behavior, touches multiple files, crosses layers, or needs more than one short session.
+Every PRD scope item (`research/PRD.md` Section 2) must have its own feature doc at `docs/features/<name>.md` created from `docs/features/_template.md`. One feature = one doc = one implementation unit. Do not code without a feature doc.
 
-The packet must contain:
+Small scope is not an exception — a short feature doc is better than none. If the work is truly too small for a full feature doc (single-file fix, no behavior change), it is not a PRD scope item.
 
-- requirements and non-goals
-- acceptance criteria
-- allowed write set and forbidden scope
-- task list with verification commands
-- test results and residual risks
+**New vs iterate**: if a PRD scope item has ≥85% overlap with an existing feature doc, open the existing doc, bump `Version`, and add a `## Changelog` entry. Only create a new file when the scope is substantially different. When unsure, ask.
 
 ## Standard Build Loop