@codewizard-dt/bootstrap 5.3.0 → 6.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE.md +105 -0
- package/README.md +22 -3
- package/bin/cli.js +16 -0
- package/lib/hooks/README.md +124 -3
- package/lib/hooks/claude-settings-guard.js +8 -2
- package/lib/prompts/README.md +1 -1
- package/lib/prompts/migrate-wiki.md +7 -7
- package/lib/scripts/README.md +111 -10
- package/lib/scripts/bootstrap-prefs-tui.js +1222 -0
- package/lib/scripts/install-global.sh +137 -6
- package/lib/scripts/migrate-project.sh +53 -11
- package/lib/scripts/rename-wiki-ids.js +232 -0
- package/lib/scripts/templates/CLAUDE-wiki.md +6 -6
- package/lib/scripts/templates/bootstrap-prefs-schema.json +11 -2
- package/lib/scripts/templates/settings-deny.json +1 -1
- package/lib/scripts/templates/settings-sandbox-unattended.json +36 -0
- package/lib/scripts/templates/settings-sandbox.json +7 -0
- package/lib/scripts/templates/wiki/conventions.md +9 -9
- package/lib/scripts/templates/wiki/dashboard.html +527 -23
- package/lib/scripts/templates/wiki/index.md +2 -2
- package/lib/scripts/templates/wiki/work/bugs/lifecycle.md +1 -1
- package/lib/scripts/templates/wiki/work/decisions/index.md +12 -4
- package/lib/scripts/templates/wiki/work/decisions/lifecycle.md +11 -9
- package/lib/scripts/templates/wiki/work/requirements/index.md +12 -4
- package/lib/scripts/templates/wiki/work/requirements/lifecycle.md +8 -8
- package/lib/scripts/templates/wiki/work/roadmaps/index.md +11 -3
- package/lib/scripts/templates/wiki/work/roadmaps/lifecycle.md +7 -5
- package/lib/scripts/templates/wiki/work/tasks/index.md +1 -1
- package/lib/scripts/templates/wiki/work/tasks/lifecycle.md +16 -8
- package/lib/scripts/templates/wiki/work/uat/lifecycle.md +3 -3
- package/lib/scripts/wiki-dashboard-server.js +98 -0
- package/lib/skills/README.md +27 -22
- package/lib/skills/_shared/ARCHIVE-WORK-ITEM.md +103 -0
- package/lib/skills/_shared/ID-RESOLUTION.md +142 -0
- package/lib/skills/_shared/SKILL-BOILERPLATE.md +50 -0
- package/lib/skills/adr-assess/SKILL.md +112 -0
- package/lib/skills/{decision-create → adr-create}/SKILL.md +26 -26
- package/lib/skills/adr-deprecate/SKILL.md +190 -0
- package/lib/skills/adr-extract/SKILL.md +255 -0
- package/lib/skills/{decision-finalize → adr-finalize}/SKILL.md +38 -38
- package/lib/skills/{decision-next → adr-next}/SKILL.md +20 -19
- package/lib/skills/{decision-walkthrough → adr-walkthrough}/SKILL.md +23 -29
- package/lib/skills/architecture-audit/SKILL.md +1 -1
- package/lib/skills/autopilot/SKILL.md +110 -0
- package/lib/skills/bootstrap-config/SKILL.md +1 -1
- package/lib/skills/bug-assess/SKILL.md +3 -3
- package/lib/skills/bug-close/SKILL.md +13 -27
- package/lib/skills/{bug-file → bug-create}/SKILL.md +10 -14
- package/lib/skills/bug-triage/SKILL.md +5 -19
- package/lib/skills/demo/SKILL.md +1 -1
- package/lib/skills/extract-feature/SKILL.md +3 -3
- package/lib/skills/git-commit/SKILL.md +4 -4
- package/lib/skills/port-feature/SKILL.md +3 -3
- package/lib/skills/power-mode/SKILL.md +42 -49
- package/lib/skills/prd-assess/SKILL.md +105 -0
- package/lib/skills/{req-compile → prd-compile}/SKILL.md +6 -13
- package/lib/skills/{req-create → prd-create}/SKILL.md +19 -19
- package/lib/skills/prd-deprecate/SKILL.md +173 -0
- package/lib/skills/{req-finalize → prd-finalize}/SKILL.md +20 -29
- package/lib/skills/primer/SKILL.md +2 -2
- package/lib/skills/research/SKILL.md +3 -3
- package/lib/skills/roadmap-assess/SKILL.md +20 -20
- package/lib/skills/roadmap-create/SKILL.md +19 -29
- package/lib/skills/roadmap-next/SKILL.md +16 -28
- package/lib/skills/security-audit/SKILL.md +1 -1
- package/lib/skills/tackle/SKILL.md +13 -15
- package/lib/skills/{task-audit → task-assess}/SKILL.md +34 -44
- package/lib/skills/task-close/SKILL.md +73 -0
- package/lib/skills/{task-add → task-create}/SKILL.md +25 -24
- package/lib/skills/uat-assess/SKILL.md +124 -0
- package/lib/skills/uat-auto/SKILL.md +9 -7
- package/lib/skills/uat-auto-plus/SKILL.md +2 -2
- package/lib/skills/{uat-generate → uat-create}/SKILL.md +10 -12
- package/lib/skills/uat-skip/SKILL.md +5 -9
- package/lib/skills/uat-walk/SKILL.md +2 -2
- package/lib/skills/uat-walk/UAT-CORE.md +29 -16
- package/lib/skills/update-docs/SKILL.md +1 -1
- package/lib/skills/usage-report/SKILL.md +52 -0
- package/lib/skills/usage-report/scripts/pricing.json +22 -0
- package/lib/skills/usage-report/scripts/usage-report.js +518 -0
- package/lib/skills/whats-next/SKILL.md +177 -0
- package/lib/skills/wiki-archive/SKILL.md +12 -23
- package/lib/skills/wiki-lint/SKILL.md +23 -13
- package/lib/skills/wiki-query/SKILL.md +1 -1
- package/lib/skills/wiki-rotate-log/SKILL.md +1 -1
- package/lib/skills/wiki-tidy/SKILL.md +6 -9
- package/package.json +3 -3
- package/lib/scripts/templates/wiki/work/decisions/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/requirements/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/roadmaps/archive/index.md +0 -10
- package/lib/skills/req-extract-decisions/SKILL.md +0 -241
- package/lib/skills/req-retire/SKILL.md +0 -185
- package/lib/skills/req-update/SKILL.md +0 -265
- package/lib/skills/task-trash/SKILL.md +0 -115
- package/lib/skills/task-update/SKILL.md +0 -136
package/lib/skills/demo/SKILL.md
CHANGED
|
@@ -39,7 +39,7 @@ Before designing the narrative, collect every stated requirement so the demo can
|
|
|
39
39
|
|
|
40
40
|
**Check for requirements documents in this order:**
|
|
41
41
|
|
|
42
|
-
1. `wiki/work/requirements/` — read every non-retired PRD file (
|
|
42
|
+
1. `wiki/work/requirements/` — read every non-retired PRD file (decide by each file's `status:`, never by location; retired PRDs stay in place, and any legacy holding folder is skipped). Extract:
|
|
43
43
|
- User stories / personas
|
|
44
44
|
- Functional requirements
|
|
45
45
|
- Success metrics / acceptance criteria
|
|
@@ -35,7 +35,7 @@ The output document is formatted to be a valid "source project" for `/port-featu
|
|
|
35
35
|
3. **Clarifying questions** — ask before proceeding if any are ambiguous:
|
|
36
36
|
- **Output location**: Should the extracted module live as a subdirectory within this project (e.g., `packages/<module-name>/`) or as a stub for a new standalone repo? (Default: subdirectory)
|
|
37
37
|
- **Constraints**: Any hard constraints — must stay in the same language, no new dependencies, must preserve the current public API for backward compatibility?
|
|
38
|
-
- **Supplementary output**: Is this extraction substantial enough to warrant a roadmap (multiple ordered steps) via `/roadmap-create`, or small enough for a single task via `/task-
|
|
38
|
+
- **Supplementary output**: Is this extraction substantial enough to warrant a roadmap (multiple ordered steps) via `/roadmap-create`, or small enough for a single task via `/task-create`? Default to a roadmap once Phase 5's extraction steps exceed ~3 steps or missing test coverage must be backfilled first.
|
|
39
39
|
|
|
40
40
|
---
|
|
41
41
|
|
|
@@ -241,7 +241,7 @@ Present the complete assessment in the conversation as structured tables/section
|
|
|
241
241
|
|
|
242
242
|
### 6b. Decide: Roadmap or Single Task
|
|
243
243
|
|
|
244
|
-
- **≤3 extraction steps, no missing test coverage flagged in 5b** → skip the roadmap. Go straight to `/task-
|
|
244
|
+
- **≤3 extraction steps, no missing test coverage flagged in 5b** → skip the roadmap. Go straight to `/task-create "Extract <feature name> into standalone module"`, carrying the full step detail into the task's steps, then skip to Phase 7.
|
|
245
245
|
- **>3 steps, missing test coverage to backfill first, or the user asked for a roadmap in Phase 0** → continue to 6c.
|
|
246
246
|
|
|
247
247
|
### 6c. Delegate to `/roadmap-create`
|
|
@@ -257,7 +257,7 @@ Feed `/roadmap-create`'s own Socratic Q&A from the analysis already gathered, ra
|
|
|
257
257
|
| Owner | Ask the user if not already known |
|
|
258
258
|
| Linked PRD/ADRs | Any `wiki/work/requirements/` or `wiki/work/decisions/` entries found during Phase 2a |
|
|
259
259
|
|
|
260
|
-
Each Extraction Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-
|
|
260
|
+
Each Extraction Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-create --roadmap ROADMAP-NNNN <step title>` (or automatically when `/roadmap-next` runs).
|
|
261
261
|
|
|
262
262
|
---
|
|
263
263
|
|
|
@@ -64,7 +64,7 @@ Scan every line this commit **adds or modifies** for comments more verbose than
|
|
|
64
64
|
- If it explains a genuinely non-obvious *why* (a workaround, a hidden constraint, a subtle invariant) but spans more lines or words than necessary, rewrite it to the single shortest sentence that preserves that reason.
|
|
65
65
|
- Preserve the comment's position (same line for a trailing comment, same location for a block comment) and its language's comment syntax — only the wording and line count change.
|
|
66
66
|
|
|
67
|
-
Use `Edit` per file for every change —
|
|
67
|
+
Use `Edit` per file for every change. Edit only — see `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Edit hygiene.
|
|
68
68
|
|
|
69
69
|
## Step 3: Assess Changes
|
|
70
70
|
|
|
@@ -257,7 +257,7 @@ git-commit "[no-bump] Fix the login redirect"
|
|
|
257
257
|
|
|
258
258
|
```bash
|
|
259
259
|
git-commit "[patch] Fix UAT verdict logic for edge-case test skips"
|
|
260
|
-
git-commit "[minor] Add /task-
|
|
260
|
+
git-commit "[minor] Add /task-assess skill with dependency graph and wave output"
|
|
261
261
|
git-commit "[major] Rename all skills to noun-first convention, drop legacy verb-first aliases"
|
|
262
262
|
```
|
|
263
263
|
|
|
@@ -265,14 +265,14 @@ git-commit "[major] Rename all skills to noun-first convention, drop legacy verb
|
|
|
265
265
|
|
|
266
266
|
```bash
|
|
267
267
|
git-commit "Fix UAT verdict logic for edge-case test skips"
|
|
268
|
-
git-commit "Add /task-
|
|
268
|
+
git-commit "Add /task-assess skill with dependency graph and wave output"
|
|
269
269
|
```
|
|
270
270
|
|
|
271
271
|
### Writing a good single-line subject
|
|
272
272
|
|
|
273
273
|
If the change feels too complex to summarize in one line, **make the subject more descriptive** — do not reach for a multi-line body. Aim for ~70–100 characters but go longer if it adds real information. Lead with the *what* and the *why* on the same line, separated by a colon when helpful:
|
|
274
274
|
|
|
275
|
-
- ✅ `[minor] Require research for every test type in /uat-
|
|
275
|
+
- ✅ `[minor] Require research for every test type in /uat-create with checkpoint gate`
|
|
276
276
|
- ✅ `[patch] Allow standard tools for markdown editing; ban bash exploration commands`
|
|
277
277
|
- ✅ `Allow standard tools for markdown editing; ban bash exploration commands` (no bump this run — the subject still carries its weight)
|
|
278
278
|
- ❌ `Update commands` (too vague — and vague is vague with or without a prefix)
|
|
@@ -33,7 +33,7 @@ Assess a specific feature or area of functionality in an external (source) proje
|
|
|
33
33
|
- Confirm the source directory exists: use `mcp__serena__find_file` or Bash `ls <source-path>` to verify it is accessible
|
|
34
34
|
|
|
35
35
|
3. **Clarifying questions** (ask before proceeding if ambiguous):
|
|
36
|
-
- Is this port substantial enough to warrant a roadmap (multiple ordered steps spanning several files/integration points) via `/roadmap-create`, or small enough for a single task via `/task-
|
|
36
|
+
- Is this port substantial enough to warrant a roadmap (multiple ordered steps spanning several files/integration points) via `/roadmap-create`, or small enough for a single task via `/task-create`? Default to a roadmap once Phase 3's porting steps exceed ~3 steps or touch more than one integration point.
|
|
37
37
|
- Is there a preferred output level of detail (high-level steps vs. file-by-file implementation plan)?
|
|
38
38
|
- Are there any known constraints (e.g., "must stay in TypeScript", "no new dependencies")?
|
|
39
39
|
|
|
@@ -218,7 +218,7 @@ Present the complete assessment in the conversation as structured tables/section
|
|
|
218
218
|
|
|
219
219
|
### 4b. Decide: Roadmap or Single Task
|
|
220
220
|
|
|
221
|
-
- **≤3 porting steps, single integration point** → skip the roadmap. Go straight to `/task-
|
|
221
|
+
- **≤3 porting steps, single integration point** → skip the roadmap. Go straight to `/task-create "Port <feature name> from <source-path>"`, carrying the full step detail (files affected, what to do, definition of done) into the task's steps, then skip to Phase 5.
|
|
222
222
|
- **>3 steps, multiple integration points, or the user asked for a roadmap in Phase 0** → continue to 4c.
|
|
223
223
|
|
|
224
224
|
### 4c. Delegate to `/roadmap-create`
|
|
@@ -234,7 +234,7 @@ Feed `/roadmap-create`'s own Socratic Q&A from the analysis already gathered, ra
|
|
|
234
234
|
| Owner | Ask the user if not already known |
|
|
235
235
|
| Linked PRD/ADRs | Any `wiki/work/requirements/` or `wiki/work/decisions/` entries found during Phase 2a/2c |
|
|
236
236
|
|
|
237
|
-
Each Porting Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-
|
|
237
|
+
Each Porting Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-create --roadmap ROADMAP-NNNN <step title>` (or automatically when `/roadmap-next` runs).
|
|
238
238
|
|
|
239
239
|
---
|
|
240
240
|
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: power-mode
|
|
3
|
-
description: Orchestrator for parallel agent teams. When invoked with a roadmap file path, drives every item through the full tackle → uat-
|
|
3
|
+
description: Orchestrator for parallel agent teams. When invoked with a roadmap file path, drives every item through the full tackle → uat-create → uat-auto pipeline until complete. When invoked with a task file path, runs that pipeline once in the current session and stops.
|
|
4
4
|
category: executing
|
|
5
5
|
model: claude-sonnet-5
|
|
6
|
-
argument-hint: "[roadmap-file-path | task-file-path]"
|
|
6
|
+
argument-hint: "[roadmap-file-path | task-file-path | TASK-NNNN]"
|
|
7
7
|
disable-model-invocation: false
|
|
8
8
|
user-invocable: true
|
|
9
9
|
---
|
|
@@ -20,7 +20,8 @@ Use this skill to drive tasks or roadmaps to completion using a parallel agent t
|
|
|
20
20
|
|
|
21
21
|
Inspect the path argument:
|
|
22
22
|
- Path contains `roadmap` or matches `ROADMAP-NNNN` → **Roadmap-to-Completion Orchestrator** (see below)
|
|
23
|
-
- Path contains `task` or matches `TASK-NNNN` → **Single-Task Executor** (see below)
|
|
23
|
+
- Path contains `task` or matches `TASK-NNNN` → **Single-Task Executor** (a pointer at the tackle → uat-create → uat-auto pipeline; see below)
|
|
24
|
+
- A task **ID** instead of a path (`TASK-0086`, `task 86`) → resolve it to its file with `find_file` on `TASK-<zero-padded NNNN>-*.md` under `wiki/work/tasks/`, then run the **Single-Task Executor** on that path. A bare number with no `TASK`/`ROADMAP` prefix is ambiguous — stop and ask which one is meant.
|
|
24
25
|
|
|
25
26
|
---
|
|
26
27
|
|
|
@@ -55,55 +56,45 @@ All agent call examples below omit this footer for brevity — it is always requ
|
|
|
55
56
|
|
|
56
57
|
---
|
|
57
58
|
|
|
58
|
-
##
|
|
59
|
-
|
|
60
|
-
**Trigger:** `/power-mode <path/to/TASK-NNNN.md>` with no additional instructions.
|
|
61
|
-
|
|
62
|
-
**Goal:** Drive one task through the full tackle → UAT-generate → UAT-auto pipeline exactly once, then stop.
|
|
59
|
+
## Agent Lifecycle — Reap Finished and Idle Agents (CRITICAL)
|
|
63
60
|
|
|
64
|
-
|
|
61
|
+
Named agents become teammates that **persist after their work is done** — a finished or idle agent keeps its panel row and process until it is explicitly shut down. Never leave them lingering. You are responsible for fully terminating every agent you spawn.
|
|
65
62
|
|
|
66
|
-
**
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
prompt: "Run /tackle <task-path>. [append team member footer]",
|
|
72
|
-
mode: "bypassPermissions"
|
|
73
|
-
})
|
|
74
|
-
```
|
|
63
|
+
**Reap sweep — run at each of these points:**
|
|
64
|
+
- Immediately after every "Wait for all to complete" (end of each phase)
|
|
65
|
+
- At the end of every wave, before returning to Step 1
|
|
66
|
+
- Periodically while waiting on long-running agents (roughly every few minutes of wall-clock time, or whenever you are notified an agent finished)
|
|
67
|
+
- Before the final report / stopping point
|
|
75
68
|
|
|
76
|
-
|
|
69
|
+
**Sweep procedure:**
|
|
70
|
+
1. Call `ListAgents` to enumerate the agents you spawned this run.
|
|
71
|
+
2. For each agent that is **finished** (reported completion, or its result already arrived) or **idle** (no activity and awaiting input it will never get), collect its report first, then terminate it:
|
|
72
|
+
- `SendMessage` the agent a shutdown request (e.g. "Work complete — shut down now."), and confirm it disappears from `ListAgents`.
|
|
73
|
+
- If it is still listed afterwards, or is hung/stuck, stop it with `TaskStop` using its task ID.
|
|
74
|
+
3. Re-run `ListAgents` and verify that no finished or idle agent from a completed phase remains. Repeat step 2 until the list is clean.
|
|
77
75
|
|
|
78
|
-
**
|
|
76
|
+
**Rules:**
|
|
77
|
+
- Never terminate an agent that is still actively working — only finished or idle ones.
|
|
78
|
+
- Never begin the next phase or wave while finished/idle agents from the previous one are still alive.
|
|
79
|
+
- Never spawn a replacement for a stuck agent without terminating the stuck one first.
|
|
80
|
+
- Do not treat "the agent returned its result" as termination — it is not. Termination is confirmed only when the agent no longer appears in `ListAgents`.
|
|
81
|
+
- The final state on stopping must be **zero** power-mode agents remaining.
|
|
79
82
|
|
|
80
|
-
|
|
81
|
-
Agent({
|
|
82
|
-
description: "UAT generate <TASK-NNNN>",
|
|
83
|
-
prompt: "Run /uat-generate <task-path>. [append team member footer]",
|
|
84
|
-
mode: "bypassPermissions"
|
|
85
|
-
})
|
|
86
|
-
```
|
|
83
|
+
---
|
|
87
84
|
|
|
88
|
-
|
|
85
|
+
## Single-Task Executor
|
|
89
86
|
|
|
90
|
-
**
|
|
87
|
+
**Trigger:** `/power-mode <path/to/TASK-NNNN.md>` (or a `TASK-NNNN` ID, resolved per Dispatch) with no additional instructions.
|
|
91
88
|
|
|
92
|
-
|
|
93
|
-
Agent({
|
|
94
|
-
description: "UAT auto <TASK-NNNN>",
|
|
95
|
-
prompt: "Run /uat-auto <uat-path> (infer the UAT file path from the task path — same NNN slug, under wiki/work/uat/).
|
|
89
|
+
A single task has nothing to parallelize, so this mode is only a pointer — no agent team, no reap sweep. Same autonomous mandate as the roadmap loop: take the task to completion. Run these three skills in order in the current session (Skill tool), without pausing, asking questions, or awaiting approval between them:
|
|
96
90
|
|
|
97
|
-
|
|
91
|
+
1. `/tackle <task-path>`
|
|
92
|
+
2. `/uat-create <task-path>`
|
|
93
|
+
3. `/uat-auto <uat-path>` — same NNNN slug, under `wiki/work/uat/`
|
|
98
94
|
|
|
99
|
-
|
|
95
|
+
Resume from the first incomplete stage by reading the task's `status:` — `todo`/`in-progress` starts at 1; `pending-uat` with no UAT file starts at 2, with one starts at 3; `done`/`trashed` → report and stop.
|
|
100
96
|
|
|
101
|
-
|
|
102
|
-
mode: "bypassPermissions"
|
|
103
|
-
})
|
|
104
|
-
```
|
|
105
|
-
|
|
106
|
-
Done. No further iteration.
|
|
97
|
+
Stop after `/uat-auto` returns. On all-pass, its own UAT-CORE Closure procedure handles task/UAT status, archiving, index rows, and the roadmap checkbox. UI tests are run in a real browser by `/uat-auto` through the Playwright MCP — expect them to pass or fail on evidence, not to be deferred wholesale. Tests left as `[FAIL: auto-judge: ... requires human verification]` (bare manual, visual-only UI Expected, Playwright unavailable) or stub-detected `- [ ] Pass` are an acceptable resting state, not a blocker — report them in the summary.
|
|
107
98
|
|
|
108
99
|
---
|
|
109
100
|
|
|
@@ -111,7 +102,7 @@ Done. No further iteration.
|
|
|
111
102
|
|
|
112
103
|
**Trigger:** `/power-mode <path/to/ROADMAP-NNNN.md>` with no additional instructions.
|
|
113
104
|
|
|
114
|
-
**Goal:** Drive the roadmap to completion — every item through the full tackle → UAT-
|
|
105
|
+
**Goal:** Drive the roadmap to completion — every item through the full tackle → UAT-create → UAT-auto pipeline — looping through waves of parallelizable work until no implementation work remains.
|
|
115
106
|
|
|
116
107
|
**AUTONOMOUS EXECUTION MANDATE:** Once triggered, drive the roadmap to completion without stopping. Do NOT pause between waves to report progress or ask for permission to continue. The only valid stopping point is when `/roadmap-next` reports no items remaining. A roadmap item is complete once it has been through the full pipeline — UAT tests requiring human verification do NOT block loop progression.
|
|
117
108
|
|
|
@@ -137,16 +128,16 @@ For any item that is an inline placeholder (no existing task file link), spawn a
|
|
|
137
128
|
```
|
|
138
129
|
Agent({
|
|
139
130
|
description: "Create task for <item>",
|
|
140
|
-
prompt: "Run /task-
|
|
131
|
+
prompt: "Run /task-create for this roadmap item: '<item description>'. Link the resulting task back into the roadmap file at wiki/work/roadmaps/<file>. Run /research before writing the task. Make all scope, naming, and structuring decisions autonomously — infer reasonable defaults from the roadmap context and existing task files in wiki/work/tasks/. [append team member footer]",
|
|
141
132
|
mode: "bypassPermissions"
|
|
142
133
|
})
|
|
143
134
|
```
|
|
144
135
|
|
|
145
|
-
Wait for all task-creation agents to complete.
|
|
136
|
+
Wait for all task-creation agents to complete, then reap them (see Agent Lifecycle).
|
|
146
137
|
|
|
147
138
|
**Step 3 — Three-phase pipeline for the wave**
|
|
148
139
|
|
|
149
|
-
Run tackle → UAT-
|
|
140
|
+
Run tackle → UAT-create → UAT-auto for all tasks in the current wave. Apply the Parallelization Mandate at every phase.
|
|
150
141
|
|
|
151
142
|
Phase 1 — Tackle (parallel, minimum 5 agents when 5+ collision-safe tasks available):
|
|
152
143
|
```
|
|
@@ -159,7 +150,7 @@ Wait for all to complete.
|
|
|
159
150
|
|
|
160
151
|
Phase 2 — Generate UAT tests (parallel, read-only):
|
|
161
152
|
```
|
|
162
|
-
Agent({ description: "UAT
|
|
153
|
+
Agent({ description: "UAT create TASK-NNNN", prompt: "Run /uat-create <task-path>. [append team member footer]", mode: "bypassPermissions" })
|
|
163
154
|
// ... one per task, all in the same message
|
|
164
155
|
```
|
|
165
156
|
|
|
@@ -173,12 +164,14 @@ Agent({
|
|
|
173
164
|
|
|
174
165
|
Note: on all-pass, /uat-auto's own UAT-CORE Closure procedure already flips the task to done, archives both files, removes index rows, and auto-checks the matching roadmap checkbox — no need to instruct any of that here.
|
|
175
166
|
|
|
176
|
-
|
|
167
|
+
UI tests (UAT-UI-*) MUST be run with the Playwright MCP — load its deferred tools via ToolSearch (query 'playwright browser') and follow /uat-auto's browser channel (UAT-CORE Step 4 channel 3). Do NOT record a UI test as needing human verification without having attempted the browser run; the only acceptable deferrals are a visual-only Expected or Playwright genuinely unavailable (say which in your report).
|
|
168
|
+
|
|
169
|
+
Tests recorded as [FAIL: auto-judge: ... requires human verification] for those reasons, or bare manual cases, do NOT block this step. If stub-detected tests remain, that's /uat-auto's own expected behavior — it leaves the file in place; report the stubs. [append team member footer]",
|
|
177
170
|
mode: "bypassPermissions"
|
|
178
171
|
})
|
|
179
172
|
```
|
|
180
173
|
|
|
181
|
-
**Step 4 —
|
|
174
|
+
**Step 4 — Reap and repeat**
|
|
182
175
|
|
|
183
|
-
|
|
176
|
+
Run the reap sweep (see Agent Lifecycle): terminate every finished or idle agent from this wave and verify via `ListAgents` that none remain. Then immediately return to Step 1. No pausing, no reporting, no confirmation. Loop until `/roadmap-next` reports no items remaining, then run a final reap sweep so zero power-mode agents remain.
|
|
184
177
|
|
|
@@ -0,0 +1,105 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: prd-assess
|
|
3
|
+
description: Survey all active PRDs together — flag approved requirements with no downstream ADRs or tasks and stale drafts, detect blocking open decisions, and rank them into one prioritized list with a status update for each
|
|
4
|
+
category: researching
|
|
5
|
+
model: claude-sonnet-5
|
|
6
|
+
disable-model-invocation: false
|
|
7
|
+
user-invocable: true
|
|
8
|
+
---
|
|
9
|
+
**Prereqs:** obey `wiki/guides/mcp-tools.md`; run /primer if not done this session.
|
|
10
|
+
|
|
11
|
+
# PRD Assessment
|
|
12
|
+
|
|
13
|
+
Assess every active PRD in `wiki/work/requirements/` together — this is the multi-PRD counterpart to `/prd-finalize` (drafts) and `/adr-extract` (approved requirements needing decisions), which each operate on exactly one PRD you've already picked. Use this skill first when several requirements exist and you need to decide which to advance next.
|
|
14
|
+
|
|
15
|
+
This skill is strictly read-only: it never flips a status, never creates a file, and never asks questions. Acting on a PRD is the job of the commands named in each `Next` line.
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Step 1: Discover active PRDs
|
|
20
|
+
|
|
21
|
+
Read the Family table in `lib/skills/_shared/ID-RESOLUTION.md` for the requirements directory and prefixes — do not hardcode them. Legacy `REQ-` files coexist with `PRD-` files until migrated, so match both prefixes.
|
|
22
|
+
|
|
23
|
+
`list_dir` the requirements directory for `.md` files **directly** in it (ignore every subdirectory); skip `lifecycle.md`, `index.md`, `README.md`. None found → STOP: `No active PRDs found in wiki/work/requirements/. Use /prd-create <idea> to draft one.`
|
|
24
|
+
|
|
25
|
+
Read the status names and which are terminal from `wiki/work/requirements/lifecycle.md` (currently `draft | approved | retired`, with `retired` terminal). Decide active vs. closed by each file's `status:`, never by location. Closed PRDs are excluded from ranking and counted once in the report footer. If nothing is active after this filter, STOP with the same empty-family text.
|
|
26
|
+
|
|
27
|
+
## Step 2: Parse every active PRD
|
|
28
|
+
|
|
29
|
+
`Read` each file in full and extract:
|
|
30
|
+
|
|
31
|
+
- **Frontmatter**: `id`, `aliases`, `title`, `status`, `owner`, `created`, `updated`, `tags`, `stakeholders`.
|
|
32
|
+
- **Amendments**: each `## Amendment N` block (count and latest date).
|
|
33
|
+
|
|
34
|
+
A `status:` outside the lifecycle's enum is reported in Step 5c, and the PRD is ranked as a fresh draft.
|
|
35
|
+
|
|
36
|
+
## Step 3: Downstream and blocking analysis
|
|
37
|
+
|
|
38
|
+
For each active PRD, `search_for_pattern` for its ID and every alias (under both prefixes) across `wiki/work/decisions/`, `wiki/work/tasks/`, and `wiki/work/roadmaps/`. Count a hit whether it is frontmatter (`linked_requirements`, `linked_prds`), a typed link (`derived_from::`, `implements::`, `relates_to::`), or a plain `[[…]]` link. Record per PRD: linked ADR groups, linked tasks, linked roadmaps.
|
|
39
|
+
|
|
40
|
+
For each linked ADR group, `Read` it and resolve every `## D1.`-style block's `Status:` as laid out in `wiki/work/decisions/lifecycle.md`. If a block is `superseded`, follow its `superseded by` pointer to the successor block and re-check that status instead. Any resolved block still `proposed` is an **open decision** blocking the PRD: record `{PRD, ADR-NNNN#DM, title}`. A missing linked file is a broken reference — note it, don't block on it.
|
|
41
|
+
|
|
42
|
+
## Step 4: Rank PRDs
|
|
43
|
+
|
|
44
|
+
**Stale-draft threshold: 30 days** — a draft is stale when `updated` is more than 30 days before today.
|
|
45
|
+
|
|
46
|
+
Order the active PRDs, highest priority first, using this precedence:
|
|
47
|
+
|
|
48
|
+
1. **Approved with no linked ADRs and no linked tasks** — approved but nothing downstream exists; oldest `updated` first.
|
|
49
|
+
2. **Approved and blocked by open decisions** — at least one linked ADR block is still `proposed` (Step 3).
|
|
50
|
+
3. **Stale drafts** — `status: draft` with `updated` older than 30 days.
|
|
51
|
+
4. **Fresh drafts.**
|
|
52
|
+
5. **Approved and fully flowing** — every linked ADR block accepted and at least one task exists; needs nothing.
|
|
53
|
+
|
|
54
|
+
Tie-break within a tier: oldest `updated`, then ID ascending. Record a one-sentence rationale per PRD — a judgment call the user can override, not a fact.
|
|
55
|
+
|
|
56
|
+
## Step 5: Report
|
|
57
|
+
|
|
58
|
+
Print, in this order:
|
|
59
|
+
|
|
60
|
+
### 5a. Prioritized PRDs
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
## Prioritized PRDs
|
|
64
|
+
|
|
65
|
+
| Rank | PRD | Status | Updated | Rationale | Blocks / Blocked by |
|
|
66
|
+
|------|-----|--------|---------|-----------|---------------------|
|
|
67
|
+
| 1 | PRD-NNNN — <title> | approved | YYYY-MM-DD | <one sentence> | no downstream items |
|
|
68
|
+
| 2 | PRD-MMMM — <title> | approved | YYYY-MM-DD | <one sentence> | blocked by ADR-NNNN#DM |
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
`Blocks / Blocked by` lists open decisions from Step 3 and, for flowing PRDs, the linked task/roadmap; `—` if none.
|
|
72
|
+
|
|
73
|
+
### 5b. Status update per PRD
|
|
74
|
+
|
|
75
|
+
One block per PRD, in ranked order:
|
|
76
|
+
|
|
77
|
+
```
|
|
78
|
+
### PRD-NNNN — <title>
|
|
79
|
+
- Owner: <owner, or "unassigned">
|
|
80
|
+
- Status: <draft | approved> — <fresh | stale | unlinked | blocked | flowing>
|
|
81
|
+
- Summary: <one line>
|
|
82
|
+
- Next: <see below>
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
`Next` by state:
|
|
86
|
+
|
|
87
|
+
- Approved, unlinked → `/adr-extract <file>`, or `/task-create <description>` when the PRD needs no architectural decision
|
|
88
|
+
- Approved, blocked → `/adr-finalize <adr-file>#DM`
|
|
89
|
+
- Draft → `/prd-finalize <file>`; a stale draft: or `/prd-deprecate <file>` if abandoned
|
|
90
|
+
- Flowing → none needed; cite the linked task/roadmap
|
|
91
|
+
|
|
92
|
+
### 5c. Warnings (omit if none found)
|
|
93
|
+
|
|
94
|
+
Flag, each as its own short block: broken references from Step 3, and PRDs with an unrecognized `status:`.
|
|
95
|
+
|
|
96
|
+
Footer, when Step 1 excluded any closed PRD: `Closed: N (not assessed)`.
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## Constraints
|
|
101
|
+
|
|
102
|
+
- Read-only — no exception. No file edits, no shell, no prompts, no log or index changes, no status flips. `/prd-finalize`, `/adr-extract`, `/adr-finalize`, and `/task-create` are the follow-up actions the user runs once they act on this report.
|
|
103
|
+
- Permitted tools: `list_dir`, `find_file`, `search_for_pattern`, `Read`.
|
|
104
|
+
- Never bash reads (`cat`/`find`/`grep`/`sed`/`ls`).
|
|
105
|
+
- Keep the report terse — no preamble, no closing summary beyond the tables above.
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
|
-
name:
|
|
2
|
+
name: prd-compile
|
|
3
3
|
description: >-
|
|
4
4
|
Compile a requirement into a running, production-grade, delightful system with minimal human time —
|
|
5
5
|
by routing every claim to its cheapest re-runnable check and building the dominant oracle
|
|
6
|
-
first. Use this whenever a project has a wiki/work/requirements/
|
|
6
|
+
first. Use this whenever a project has a wiki/work/requirements/ PRD file to build or execute
|
|
7
7
|
("build this per the requirement", "execute the spec", "turn these requirements into a working
|
|
8
8
|
system"), when scaffolding or resuming a greenfield build from a requirements document, or in
|
|
9
9
|
a build's closing phase to harvest corrections back into the method. Pairs with
|
|
@@ -13,7 +13,7 @@ model: claude-opus-5
|
|
|
13
13
|
effort: high
|
|
14
14
|
---
|
|
15
15
|
|
|
16
|
-
#
|
|
16
|
+
# prd-compile
|
|
17
17
|
|
|
18
18
|
Turn a requirement into a working system that **self-verifies**, surfacing the human only where no
|
|
19
19
|
machine can decide. The aim is not zero human corrections — some are irreducible taste, or
|
|
@@ -22,7 +22,7 @@ intent discovered mid-build — but zero *preventable* ones. This skill encodes
|
|
|
22
22
|
It inherits the global manifesto (least code, simplest architecture, maximal correctness,
|
|
23
23
|
no docs unless asked). This is the *how-to-build*; the manifesto is *what good looks like*.
|
|
24
24
|
|
|
25
|
-
**Input:** a project dir with a `wiki/work/requirements/
|
|
25
|
+
**Input:** a project dir with a `wiki/work/requirements/PRD-NNNN-slug.md` (PRD) file + a project `CLAUDE.md`
|
|
26
26
|
(stack, hosting, boundaries).
|
|
27
27
|
**Output:** code — a typed boundary contract, *failing* oracle stubs, and the answered batched
|
|
28
28
|
forks. Not documentation.
|
|
@@ -42,16 +42,9 @@ feature usually splits across several oracles. Build the **dominant** oracle fir
|
|
|
42
42
|
|
|
43
43
|
## Locating the requirement
|
|
44
44
|
|
|
45
|
-
|
|
45
|
+
Resolve the file per ~/.claude/skills/_shared/ID-RESOLUTION.md — family: requirements · scope: active · ambiguous: interactive · empty: look for any `wiki/work/requirements/PRD-NNNN-slug.md` with `status: approved`; if ambiguous, ask via `AskUserQuestion`
|
|
46
46
|
|
|
47
|
-
|
|
48
|
-
|------------|------------|
|
|
49
|
-
| `<path>` (e.g. `wiki/work/requirements/REQ-003-onboarding.md`) | Use as-is |
|
|
50
|
-
| `<NNN-slug>` (e.g. `003-onboarding`) | `mcp__serena__find_file` with mask `003-onboarding.md` under `wiki/work/requirements/` |
|
|
51
|
-
| `<NNN>` (e.g. `3` or `003`) | Pad to 3 digits; `mcp__serena__find_file` with mask `NNN-*.md` under `wiki/work/requirements/` |
|
|
52
|
-
| Empty / missing | Look for any `wiki/work/requirements/REQ-NNNN-slug.md` with `status: approved`; if ambiguous, ask via `AskUserQuestion` |
|
|
53
|
-
|
|
54
|
-
**Verify the requirement has `status: approved`** before proceeding. If `draft`, tell the user to run `/req-finalize <path>` first. If `retired` or `superseded`, refuse — no system should be built against a cancelled requirement.
|
|
47
|
+
**Verify the requirement has `status: approved`** before proceeding. If `draft`, tell the user to run `/prd-finalize <path>` first. If `retired` or `superseded`, refuse — no system should be built against a cancelled requirement.
|
|
55
48
|
|
|
56
49
|
## The loop
|
|
57
50
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name:
|
|
3
|
-
description: Draft a new
|
|
2
|
+
name: prd-create
|
|
3
|
+
description: Draft a new PRD in wiki/work/requirements/ via Socratic Q&A capturing problem, personas, user stories, success metrics, and non-goals
|
|
4
4
|
category: planning
|
|
5
5
|
model: claude-sonnet-5
|
|
6
6
|
effort: high
|
|
@@ -9,11 +9,11 @@ disable-model-invocation: false
|
|
|
9
9
|
user-invocable: true
|
|
10
10
|
---
|
|
11
11
|
**Prereqs:** obey `wiki/guides/mcp-tools.md`; run /primer if not done this session.
|
|
12
|
-
**Check `wiki/work/requirements/lifecycle.md`** for the
|
|
12
|
+
**Check `wiki/work/requirements/lifecycle.md`** for the PRD template, status lifecycle, required-non-empty fields, and anti-patterns this skill enforces; **`wiki/work/requirements/index.md`** for the index row format.
|
|
13
13
|
|
|
14
|
-
# Create
|
|
14
|
+
# Create PRD
|
|
15
15
|
|
|
16
|
-
Create a **
|
|
16
|
+
Create a **PRD** — **what to build and why** from a product perspective: problem, personas, desired outcomes, explicit non-goals. Requirements sit **upstream** of decisions and tasks; they define *what* and *why*, never *how*.
|
|
17
17
|
|
|
18
18
|
> *A requirement never justifies architecture. A decision never redefines product scope.* (Joel Parker Henderson's REQ↔Decision pattern)
|
|
19
19
|
|
|
@@ -23,7 +23,7 @@ If the user specifies file paths, libraries, schemas, or frameworks, **redirect*
|
|
|
23
23
|
|
|
24
24
|
## When to write
|
|
25
25
|
|
|
26
|
-
Write when there's a real problem worth aligning on, more than one decision area, multiple stakeholders, and the *what* is not obvious from the codebase. For a bug fix, refactor, one-line config change, or a pure *how* question — **stop and tell the user**; suggest `/task-
|
|
26
|
+
Write when there's a real problem worth aligning on, more than one decision area, multiple stakeholders, and the *what* is not obvious from the codebase. For a bug fix, refactor, one-line config change, or a pure *how* question — **stop and tell the user**; suggest `/task-create` or `/adr-create`.
|
|
27
27
|
|
|
28
28
|
---
|
|
29
29
|
|
|
@@ -33,7 +33,7 @@ Write when there's a real problem worth aligning on, more than one decision area
|
|
|
33
33
|
3. Read `CLAUDE.md`, `PROJECT_STATUS.md` (if present), `wiki/work/requirements/lifecycle.md` (authoritative template/lifecycle/anti-patterns), and a sample of recent requirements for local conventions.
|
|
34
34
|
|
|
35
35
|
## Step 2: Locate directory, assign number
|
|
36
|
-
Requirements live at `wiki/work/requirements/
|
|
36
|
+
Requirements live at `wiki/work/requirements/PRD-NNNN-slug.md` (4-digit zero-padded). Allocate the next ID per `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Number allocation (family: `wiki/work/requirements/`, prefix: `PRD-`, no index scan; also count legacy `REQ` filenames). Derive the slug — names the **initiative**, lowercase dash-separated ≤60 chars (e.g. "Self-serve billing portal" → `PRD-0004-self-serve-billing-portal.md`). Confirm number + slug via `AskUserQuestion` if non-obvious.
|
|
37
37
|
|
|
38
38
|
## Step 3: Research (optional, scoped)
|
|
39
39
|
For an unfamiliar product space, run a **lightweight** `/research` for **product context only**:
|
|
@@ -63,22 +63,22 @@ Walk the elicitations **in order**. Batch related ones into a single round when
|
|
|
63
63
|
|
|
64
64
|
**Suggested batching:** (1) Problem, Personas · (2) User Stories+AC, Success Metrics · (3) Goals, Non-Goals, Constraints, Assumptions · (4) Owner, Stakeholders, Tags, Open Questions. Adjust as the conversation flows — the rule is *every elicitation passes its bar before Step 5*.
|
|
65
65
|
|
|
66
|
-
**Redirection rule:** if the user answers with implementation specifics (file paths, function names, libraries, schema fields), respond: *"That sounds like an architectural decision, not a product requirement. Let's keep this to what and why; how is captured later in a decision via `/
|
|
66
|
+
**Redirection rule:** if the user answers with implementation specifics (file paths, function names, libraries, schema fields), respond: *"That sounds like an architectural decision, not a product requirement. Let's keep this to what and why; how is captured later in a decision via `/adr-create` after `/prd-finalize` and `/adr-extract`."* Then re-ask for the user-visible behavior/outcome.
|
|
67
67
|
|
|
68
68
|
## Step 5: Preview and confirm before writing
|
|
69
69
|
Present a **tabular preview** of every elicited section; user confirms via `AskUserQuestion` (*Approve and write* / *Edit specific section* / *Cancel*). **Do not write until explicit approval.** Preview must include at least: Header (Title, status `draft`, Owner, Stakeholders, Tags), Problem Statement (full), Personas (table), User Stories (`US-N` titles + AC counts), Success Metrics (full table), Goals→Metrics (full table showing the link), Non-Goals (full table), Constraints/Assumptions/Open Questions (tables or "(empty — none elicited)"). Edits → loop back to the relevant Step 4 elicitation and re-present.
|
|
70
70
|
|
|
71
71
|
### Step 5a: Re-verify next requirement number — IMMEDIATELY before writing
|
|
72
72
|
|
|
73
|
-
|
|
73
|
+
Repeat § Number allocation step 6 (same family and prefix as Step 2); never call `Write` before completing it.
|
|
74
74
|
|
|
75
75
|
## Step 6: Write the file
|
|
76
|
-
After confirmation, `Write` `wiki/work/requirements/
|
|
76
|
+
After confirmation, `Write` `wiki/work/requirements/PRD-NNNN-slug.md`.
|
|
77
77
|
|
|
78
78
|
```yaml
|
|
79
79
|
---
|
|
80
|
-
id:
|
|
81
|
-
aliases: [
|
|
80
|
+
id: PRD-NNNN
|
|
81
|
+
aliases: [PRD-NNNN]
|
|
82
82
|
type: requirement
|
|
83
83
|
status: draft
|
|
84
84
|
created: YYYY-MM-DD
|
|
@@ -90,21 +90,21 @@ tags: [<tag1>, <tag2>]
|
|
|
90
90
|
---
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
-
Sections in order: `#
|
|
93
|
+
Sections in order: `# PRD-NNNN: <Title>` · `## Problem Statement` · `## Goals` (table, every row links a Success Metric ID) · `## Non-Goals` (≥1 row) · `## Personas` (table) · `## User Stories` (each `### US-N. <title>` with the story sentence + an AC table) · `## Success Metrics` (table) · `## Constraints` / `## Assumptions` / `## Open Questions` (table or "(none — placeholder retained)") · `## Linked Decisions` (empty, retain explanatory blockquote) · `## Linked Tasks` (empty, blockquote) · `## Notes` (empty).
|
|
94
94
|
|
|
95
95
|
**Refuse to write** if any required-non-empty field is missing or fails its bar — loop back to Step 4.
|
|
96
96
|
|
|
97
|
-
## Step 7: Update indexes + log (`Edit` only
|
|
98
|
-
Append (or replace the placeholder row) in `wiki/work/requirements/index.md` using the format documented at the top of that file: `- [
|
|
97
|
+
## Step 7: Update indexes + log (`Edit` only)
|
|
98
|
+
Append (or replace the placeholder row) under `## Active` in `wiki/work/requirements/index.md` (a new draft is always Active; `/prd-deprecate` later moves it to `## Closed`) using the format documented at the top of that file: `- [PRD-NNNN — Title](PRD-NNNN-slug.md) — one-line summary · status`, in ascending ID order. Append to `wiki/log.md`: `## [YYYY-MM-DD] prd-create | PRD-NNNN <title>`.
|
|
99
99
|
|
|
100
100
|
## Step 8: Cross-link related artifacts
|
|
101
|
-
If prompted by an existing task/research note/reference, link both ways (`Read` then `Edit
|
|
101
|
+
If prompted by an existing task/research note/reference, link both ways (`Read` then `Edit`): source artifact gets `**Requirement**: PRD-NNNN ([file](<relative-link>))` in a sensible section; the new requirement references the source in `## Notes` (e.g. "Originated from `wiki/work/tasks/TASK-012-runbook-triage.md`"). No related artifact → skip.
|
|
102
102
|
|
|
103
103
|
## Step 9: Update memory if appropriate
|
|
104
|
-
`mcp__serena__write_memory` only for a **non-obvious** product insight future sessions benefit from (a genuinely new persona; a regulatory constraint; a known product gotcha) — skip self-evident ones or conjecture. Topic-hierarchical name (`product/personas/sre-oncall`, `product/constraints/soc2-admin-logging`), referencing `
|
|
104
|
+
`mcp__serena__write_memory` only for a **non-obvious** product insight future sessions benefit from (a genuinely new persona; a regulatory constraint; a known product gotcha) — skip self-evident ones or conjecture. Topic-hierarchical name (`product/personas/sre-oncall`, `product/constraints/soc2-admin-logging`), referencing `PRD-NNNN` in the body.
|
|
105
105
|
|
|
106
106
|
## Step 10: Report
|
|
107
|
-
Tabular summary: File path, Status (`draft`), Personas/User Stories/Success Metrics/Non-Goals counts, Constraints/Assumptions/Open Questions (populated/empty per section), index updated (1 row), log appended, cross-links (list or *none*), memory (name or *skipped*), suggested next step `/
|
|
107
|
+
Tabular summary: File path, Status (`draft`), Personas/User Stories/Success Metrics/Non-Goals counts, Constraints/Assumptions/Open Questions (populated/empty per section), index updated (1 row), log appended, cross-links (list or *none*), memory (name or *skipped*), suggested next step `/prd-finalize wiki/work/requirements/PRD-NNNN-slug.md`. Note any placeholder-reduced field under a **Gaps** section for the user to address before `/prd-finalize`.
|
|
108
108
|
|
|
109
109
|
---
|
|
110
110
|
|
|
@@ -122,7 +122,7 @@ Tabular summary: File path, Status (`draft`), Personas/User Stories/Success Metr
|
|
|
122
122
|
1. **Max 3 sub-processes at a time** if delegating Step 3 research; **always terminate processes when done**.
|
|
123
123
|
2. **Refuse to write if any required-non-empty field is empty or fails its bar** — loop back to Step 4.
|
|
124
124
|
3. **Never invent personas, metrics, user stories, or non-goals** — every entry from user-confirmed `AskUserQuestion` input.
|
|
125
|
-
4.
|
|
125
|
+
4. Edit only — see `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Edit hygiene.
|
|
126
126
|
5. **Tags non-empty is mandatory** — refuse to write if Step 4 #11 yielded zero tags.
|
|
127
127
|
6. **Never auto-create downstream artifacts** — exactly one requirement file (+ index + log + cross-link edits); no decisions, tasks, or research notes as a side effect.
|
|
128
128
|
7. **Redirect implementation talk to decision territory** — restate as *what*/*why* and re-elicit.
|