@windyroad/jtbd 0.7.2 → 0.7.3

package/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "wr-jtbd",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Jobs-to-be-done enforcement for Claude Code"
 }

package/README.md

@@ -12,7 +12,7 @@ The JTBD plugin:
 
 1. **Detects** when an edit touches user-facing UI files
 2. **Blocks** the edit until the JTBD agent has reviewed it
-3. **Reviews** changes against your `docs/JOBS_TO_BE_DONE.md` and `docs/PRODUCT_DISCOVERY.md`
+3. **Reviews** changes against your `docs/jtbd/` directory (per-persona job files)
 4. **Reports** alignment gaps -- features that don't map to a documented job, or that conflict with persona constraints
 
 ## Install
@@ -25,13 +25,13 @@ Restart Claude Code after installing.
 
 ## Usage
 
-The plugin works automatically. On first use in a project without a JTBD document, it blocks edits and directs you to create one:
+The plugin works automatically. On first use in a project without a JTBD directory, it blocks edits and directs you to create one:
 
 ```
 /wr-jtbd:update-guide
 ```
 
-This examines your existing features and asks about your user jobs, personas, and desired outcomes to generate a `docs/JOBS_TO_BE_DONE.md`.
+This examines your existing features and asks about your user jobs, personas, and desired outcomes to generate `docs/jtbd/<persona>/persona.md` plus per-job files at `docs/jtbd/<persona>/JTBD-NNN-<title>.<status>.md`. If a legacy `docs/JOBS_TO_BE_DONE.md` exists, it is migrated into the directory structure on first run (per [ADR-008](../../docs/decisions/008-jtbd-directory-structure.proposed.md)).
 
 ## How It Works
 
@@ -40,15 +40,32 @@ This examines your existing features and asks about your user jobs, personas, an
 | `jtbd-eval.sh` | Every prompt | Evaluates whether the task involves user-facing UI |
 | `jtbd-enforce-edit.sh` | Edit or Write | Blocks edits until the JTBD agent has reviewed |
 | `jtbd-mark-reviewed.sh` | Agent completes | Marks the review as done (TTL: 3600s) |
+| `jtbd-slide-marker.sh` | Agent or Bash | Slides the review marker forward across non-edit operations so an active review session is not invalidated by intervening Bash or sub-agent calls |
 
 ## Agent
 
-The `wr-jtbd:agent` reads your `docs/JOBS_TO_BE_DONE.md` and reviews proposed UI changes against:
+The `wr-jtbd:agent` reads your `docs/jtbd/` directory and reviews proposed UI changes against:
 
-- Documented user jobs and their success criteria
+- Documented user jobs (per persona) and their success criteria
 - Persona definitions and constraints
 - Screen-to-job mappings
 
+## Jobs to be Done
+
+This plugin serves the [Jobs to be Done](../../docs/jtbd/) below. Per [ADR-051](../../docs/decisions/051-jtbd-anchored-readme-with-drift-advisory.proposed.md), the persona-grouped JTBD anchor is the canonical source of truth for the README's value framing.
+
+### Solo developer
+
+- **[JTBD-001 Enforce Governance Without Slowing Down](../../docs/jtbd/solo-developer/JTBD-001-enforce-governance.proposed.md)** — JTBD review fires automatically on every UI edit; manual review is replaced by an agent reading the persona files the project already maintains.
+
+### Tech lead / consultant
+
+- **[JTBD-202 Run Pre-Flight Governance Checks Before Release or Handover](../../docs/jtbd/tech-lead/JTBD-202-pre-flight-governance-check.proposed.md)** — `/wr-jtbd:review-jobs` produces an on-demand alignment report against documented jobs, attachable to a release note or handover doc.
+
+### Plugin user
+
+- **[JTBD-302 Trust That the README Describes the Plugin I Just Installed](../../docs/jtbd/plugin-user/JTBD-302-trust-readme-describes-installed-behaviour.proposed.md)** — this README is anchored on current JTBD job IDs; drift between prose and shipped behaviour is detectable at retro time per ADR-051.
+
 ## Updating and Uninstalling
 
 ```bash

package/hooks/jtbd-enforce-edit.sh

@@ -68,6 +68,9 @@ case "$FILE_PATH" in
     exit 0 ;;
   */MEMORY.md|*/.claude/projects/*/memory/*)
     exit 0 ;;
+  # READ tolerance only — gate skips user edits to .claude/plans/. NOT a write
+  # target for agents. .claude/ is user-controlled config space; agents must not
+  # write project-generated artefacts here. See P131.
   */.claude/plans/*.md|*.claude/plans/*.md)
     exit 0 ;;
   */RISK-POLICY.md)
@@ -80,6 +83,12 @@ case "$FILE_PATH" in
     exit 0 ;;
   */docs/problems/*.md|docs/problems/*.md)
     exit 0 ;;
+  # ADR-031 / RFC-002 T1 dual-pattern: per-state subdir layout
+  # (`docs/problems/<state>/<NNN>-<slug>.md`). Coexists with the
+  # flat-layout pattern above during the migration window. Drops to
+  # single-pattern at RFC-002 T6 once Slice A migration verifies.
+  */docs/problems/*/*.md|docs/problems/*/*.md)
+    exit 0 ;;
   */docs/jtbd/*|docs/jtbd/*)
     exit 0 ;;
   */docs/PRODUCT_DISCOVERY.md|docs/PRODUCT_DISCOVERY.md)

package/hooks/jtbd-eval.sh

@@ -41,6 +41,11 @@ Does NOT apply to: CSS, images, fonts, lockfiles, changesets, memory files,
 plan files, docs/problems/ (problem tickets), docs/BRIEFING.md, docs/briefing/,
 RISK-POLICY.md, .risk-reports/, docs/jtbd/,
 docs/PRODUCT_DISCOVERY.md, docs/VOICE-AND-TONE.md, docs/STYLE-GUIDE.md.
+NOTE: these exclusions are READ tolerance — the JTBD gate skips user
+edits to these paths. They are NOT agent write targets. Never write
+project-generated artefacts (plans, audits, scratch state) under
+.claude/ — that is user-controlled config space. Project-generated
+content belongs under docs/ or directly in problem-ticket bodies (P131).
 HOOK_OUTPUT
     mark_announced "jtbd" "$SESSION_ID"
   fi

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/jtbd",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Jobs-to-be-done enforcement for UI changes",
   "bin": {
     "windyroad-jtbd": "./bin/install.mjs"