@codewizard-dt/bootstrap 3.2.0 → 5.1.0
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/README.md +18 -60
- package/bin/cli.js +0 -5
- package/lib/hooks/README.md +14 -5
- package/lib/hooks/lib/command-parse.js +28 -0
- package/lib/hooks/package-install-consent.js +60 -2
- package/lib/prompts/README.md +0 -1
- package/lib/scripts/README.md +20 -13
- package/lib/scripts/bootstrap-prefs.js +20 -1
- package/lib/scripts/migrate-project.sh +1 -1
- package/lib/scripts/setup-project.sh +0 -1
- package/lib/scripts/sync-wiki-scaffold.sh +3 -15
- package/lib/scripts/templates/CLAUDE-wiki.md +4 -4
- package/lib/scripts/templates/bootstrap-prefs-schema.json +10 -1
- package/lib/scripts/templates/wiki/conventions.md +1 -1
- package/lib/scripts/templates/wiki/dashboard.html +2 -2
- package/lib/scripts/templates/wiki/index.md +4 -4
- package/lib/scripts/templates/wiki/work/requirements/index.md +1 -1
- package/lib/scripts/templates/wiki/work/requirements/lifecycle.md +2 -2
- package/lib/scripts/templates/wiki/work/roadmaps/index.md +1 -1
- package/lib/scripts/templates/wiki/work/roadmaps/lifecycle.md +4 -4
- package/lib/scripts/templates/wiki/work/tasks/index.md +1 -1
- package/lib/scripts/templates/wiki/work/tasks/lifecycle.md +6 -6
- package/lib/scripts/templates/wiki/work/uat/index.md +1 -1
- package/lib/scripts/templates/wiki/work/uat/lifecycle.md +4 -4
- package/lib/scripts/wiki-dashboard-server.js +1 -1
- package/lib/skills/README.md +3 -1
- package/lib/skills/architecture-audit/SKILL.md +207 -0
- package/lib/skills/bootstrap-config/SKILL.md +1 -1
- package/lib/skills/bug-assess/SKILL.md +137 -0
- package/lib/skills/bug-close/SKILL.md +2 -2
- package/lib/skills/bug-file/SKILL.md +9 -5
- package/lib/skills/decision-create/SKILL.md +5 -1
- package/lib/skills/power-mode/SKILL.md +10 -10
- package/lib/skills/primer/SKILL.md +1 -1
- package/lib/skills/req-compile/SKILL.md +2 -2
- package/lib/skills/req-create/SKILL.md +13 -9
- package/lib/skills/req-extract-decisions/SKILL.md +10 -10
- package/lib/skills/req-finalize/SKILL.md +3 -3
- package/lib/skills/req-retire/SKILL.md +10 -10
- package/lib/skills/req-update/SKILL.md +4 -4
- package/lib/skills/roadmap-assess/SKILL.md +58 -20
- package/lib/skills/roadmap-create/SKILL.md +22 -22
- package/lib/skills/roadmap-next/SKILL.md +10 -10
- package/lib/skills/security-audit/SKILL.md +3 -0
- package/lib/skills/tackle/SKILL.md +3 -3
- package/lib/skills/task-add/SKILL.md +22 -22
- package/lib/skills/task-audit/SKILL.md +2 -2
- package/lib/skills/task-trash/SKILL.md +4 -4
- package/lib/skills/uat-generate/SKILL.md +22 -22
- package/lib/skills/uat-skip/SKILL.md +21 -21
- package/lib/skills/uat-walk/UAT-CORE.md +6 -6
- package/lib/skills/wiki-lint/SKILL.md +1 -1
- package/package.json +2 -4
- package/.github/workflows/docker-harness.yml +0 -26
- package/.github/workflows/security.yml +0 -24
- package/.gitleaks.toml +0 -15
- package/lib/prompts/setup-deployment.md +0 -322
- package/lib/scripts/setup-deployment.sh +0 -113
- package/raw/guides/deployment-strategy.md +0 -448
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: bug-assess
|
|
3
|
+
description: Survey all active bugs together — batch-triage any still-open reports first, then rank the full active set by priority, severity, impact, and blocking relationships into a single prioritized fix order with a status update for each bug
|
|
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
|
+
# Bug Assessment
|
|
12
|
+
|
|
13
|
+
Assess every active bug in `wiki/work/bugs/` together — this is the multi-bug counterpart to `/bug-triage`, which operates on exactly one bug you've already picked. Use this skill when several bugs are active and you need to decide which to fix next, based on priority, severity, impact, and the blocking relationships between them.
|
|
14
|
+
|
|
15
|
+
This skill is read-mostly with one deliberate exception: if any bug is still `status: open`, it runs a batch-triage pass first (with user confirmation per bug) so the ranking rests on real priorities rather than blanks. Deeper triage outcomes — starting work, rejecting — remain `/bug-triage`'s job.
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Step 1: Discover active bugs
|
|
20
|
+
|
|
21
|
+
`list_dir` `wiki/work/bugs/` for `BUG-*.md` files **directly** in it (not `archive/`); skip `lifecycle.md`, `index.md`. None found → STOP: `No bugs found in wiki/work/bugs/. Use /bug-file <description> to file one.`
|
|
22
|
+
|
|
23
|
+
A single active bug is still worth assessing — the status update in Step 6d is useful on its own.
|
|
24
|
+
|
|
25
|
+
## Step 2: Parse every bug
|
|
26
|
+
|
|
27
|
+
For each file, `Read` it in full and extract:
|
|
28
|
+
|
|
29
|
+
- **Frontmatter**: `id`, `title`, `status`, `severity`, `priority`, `assignee`, `tags`, `created`, `updated`.
|
|
30
|
+
- **Body signals**: `## Impact` (who is affected, what it blocks), `## Related` (duplicate-of, related bugs, blocking references), reproducibility, workaround.
|
|
31
|
+
- **Typed links**: inline `rel::[[BUG-NNNN]]`, `blocks::[[BUG-NNNN]]`, `depends_on::[[BUG-NNNN]]` anywhere in the body — a bug can gate another without a `## Related` entry. Merge these into the same per-bug reference set.
|
|
32
|
+
|
|
33
|
+
Cross-check each bug against `wiki/work/bugs/index.md`: note any bug whose index row is missing or whose status/priority text is stale. Report the drift in Step 6e — fix a row only if the Step 3 triage pass touches that bug anyway.
|
|
34
|
+
|
|
35
|
+
## Step 3: Batch-triage pass
|
|
36
|
+
|
|
37
|
+
**Run only if at least one bug is `status: open`.** Otherwise skip to Step 4.
|
|
38
|
+
|
|
39
|
+
For each open bug, derive a proposal from its body: a priority (`P0`–`P3`), a confirmed-or-revised severity, and suggested tags. Then confirm with the user via `AskUserQuestion` — batch up to 4 bugs per call, one question per bug, with your proposal as the recommended first option. Always include a **"needs full triage"** option: picking it leaves the bug `open`, untouched, and listed in Step 6b with `Next: /bug-triage BUG-NNNN`.
|
|
40
|
+
|
|
41
|
+
For each confirmed bug, apply the updates per the Step 6/7 procedure in `lib/skills/bug-triage/SKILL.md` — do not restate its edit mechanics, follow them as written: `Edit` the bug file (flip `status: open` → `triaged`, set `priority:` / `tags:`, confirm `severity:`, bump `updated:` to today) and update its `wiki/work/bugs/index.md` row's status/priority text.
|
|
42
|
+
|
|
43
|
+
Outcomes this pass does **not** handle: starting work (`in-progress`) and rejection (`wontfix` / `duplicate` / `cannot-reproduce`). Those require the impact/workaround/resolution rigor of `/bug-triage` — never shortcut them here.
|
|
44
|
+
|
|
45
|
+
Append **one** combined entry to `wiki/log.md` for the whole pass, not one per bug:
|
|
46
|
+
|
|
47
|
+
```
|
|
48
|
+
## [YYYY-MM-DD] bug-assess | batch triage
|
|
49
|
+
Triaged BUG-NNNN, BUG-MMM, … open → triaged with confirmed priorities. <one sentence>
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
## Step 4: Blocking analysis
|
|
53
|
+
|
|
54
|
+
From each bug's merged reference set (Step 2), build directed edges `blocking_bug → blocked_bug` — the bug named in a `depends_on::` / "blocked by" reference blocks the bug holding the reference; a `blocks::` reference points the other way.
|
|
55
|
+
|
|
56
|
+
A **duplicate-of** reference on an active bug is a red flag, not an edge: duplicates should have been rejected and archived at triage. Surface it in Step 6e — don't fix it here.
|
|
57
|
+
|
|
58
|
+
Deduplicate edges. Walk the graph via DFS to detect cycles — if found, flag them in Step 6e rather than silently picking a winner.
|
|
59
|
+
|
|
60
|
+
## Step 5: Rank bugs
|
|
61
|
+
|
|
62
|
+
Order all active bugs, highest priority first, using this precedence:
|
|
63
|
+
|
|
64
|
+
1. **Hard blocking order** (from Step 4) — a bug that blocks others always outranks the bugs it blocks. Never violate this to satisfy the signals below.
|
|
65
|
+
2. **Priority** — `P0` first, descending to `P3`. A bug with no priority (`—`) ranks after `P3` with a note — it shouldn't exist after Step 3 unless the user declined triage.
|
|
66
|
+
3. **Severity** — `critical` → `high` → `medium` → `low`.
|
|
67
|
+
4. **Impact** — a judgment call from `## Impact`, reproducibility, and workaround (no workaround outranks an easy one). Record a one-sentence rationale per bug in the report — this is a judgment call the user can override, not a fact.
|
|
68
|
+
5. **Tie-break only** — `in-progress` ranks above `triaged` (finishing in-flight fixes compounds value faster than starting new ones); then `BUG-NNNN` ascending.
|
|
69
|
+
|
|
70
|
+
Bugs left `open` (declined batch triage) are still ranked on the signals available, but marked **not actionable until triaged** — `/bug-triage` is their next step, not a fix.
|
|
71
|
+
|
|
72
|
+
## Step 6: Report
|
|
73
|
+
|
|
74
|
+
Print, in this order:
|
|
75
|
+
|
|
76
|
+
### 6a. Triaged this run (omit if none)
|
|
77
|
+
|
|
78
|
+
```
|
|
79
|
+
Batch-triaged (open → triaged):
|
|
80
|
+
• BUG-NNNN — <title> — P<N>, <severity>
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
### 6b. Untriaged (omit if none)
|
|
84
|
+
|
|
85
|
+
```
|
|
86
|
+
## Warning: Untriaged Bugs
|
|
87
|
+
|
|
88
|
+
These bugs are still `open` — not actionable until triaged:
|
|
89
|
+
|
|
90
|
+
| Bug | Severity | Next |
|
|
91
|
+
|-----|----------|------|
|
|
92
|
+
| BUG-NNNN — <title> | <severity> | `/bug-triage BUG-NNNN` |
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
### 6c. Prioritized Bugs
|
|
96
|
+
|
|
97
|
+
```
|
|
98
|
+
## Prioritized Bugs
|
|
99
|
+
|
|
100
|
+
| Rank | Bug | Priority | Severity | Status | Rationale | Blocks / Blocked by |
|
|
101
|
+
|------|-----|----------|----------|--------|-----------|---------------------|
|
|
102
|
+
| 1 | BUG-NNNN — <title> | P1 | high | triaged | <one sentence> | blocks BUG-MMM |
|
|
103
|
+
| 2 | BUG-MMM — <title> | P1 | medium | in-progress | <one sentence> | blocked by BUG-NNNN |
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
`Blocks / Blocked by` lists the hard edges from Step 4, or `—` if none.
|
|
107
|
+
|
|
108
|
+
### 6d. Status update per bug
|
|
109
|
+
|
|
110
|
+
One block per bug, in ranked order:
|
|
111
|
+
|
|
112
|
+
```
|
|
113
|
+
### BUG-NNNN — <title>
|
|
114
|
+
- Assignee: <assignee, or "unassigned">
|
|
115
|
+
- Status: <open | triaged | in-progress>
|
|
116
|
+
- Impact: <one line>
|
|
117
|
+
- Next: <see below>
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
`Next` by status:
|
|
121
|
+
|
|
122
|
+
- `open` → `/bug-triage BUG-NNNN`
|
|
123
|
+
- `triaged` → `/bug-triage BUG-NNNN` to start work, or suggest `/task-add` for a fix task
|
|
124
|
+
- `in-progress` → continue the fix; `/bug-close BUG-NNNN` when the fix commit and regression test land
|
|
125
|
+
|
|
126
|
+
### 6e. Warnings (omit if none found)
|
|
127
|
+
|
|
128
|
+
Flag, each as its own short block: dependency cycles (`BUG-NNNN → BUG-MMM → BUG-NNNN — these block each other; resolve manually`), active bugs carrying a duplicate-of reference (should have been rejected at triage — `/bug-triage BUG-NNNN`), and index drift from Step 2 (missing or stale rows in `wiki/work/bugs/index.md`).
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Constraints
|
|
133
|
+
|
|
134
|
+
- Read-only except the Step 3 batch-triage edits (status flip to `triaged`, triage fields, index row text, one combined log entry) — never flip to `in-progress` or a terminal status, never archive, never create task files. That is `/bug-triage`, `/bug-close`, and `/task-add`'s job once the user acts on this report.
|
|
135
|
+
- Permitted tools: `list_dir`, `find_file`, `Read`, `Edit`, `AskUserQuestion` (Step 3 confirmations only — otherwise this skill should run to completion without prompting).
|
|
136
|
+
- Never bash reads (`cat`/`find`/`grep`/`sed`/`ls`).
|
|
137
|
+
- Keep the report terse — no preamble, no closing summary beyond the tables above.
|
|
@@ -85,7 +85,7 @@ Use `AskUserQuestion` (batched where the UI permits):
|
|
|
85
85
|
| Fix commit | Short SHA (or "see PR") | **Yes** |
|
|
86
86
|
| Fix version | Release tag or `—` | No |
|
|
87
87
|
| Linked PR | `#NNN` or full URL or `—` | No (recommended) |
|
|
88
|
-
| Linked task | `[[TASK-
|
|
88
|
+
| Linked task | `[[TASK-NNNN]]` or `—` | No |
|
|
89
89
|
| **Regression test** | Path to an automated test that fails-before / passes-after, **or** path to a UAT entry that exercises the fix | **Yes** |
|
|
90
90
|
|
|
91
91
|
For **Verify and close**, both required fields must be supplied. If the user cannot name a regression test, STOP and tell them:
|
|
@@ -123,7 +123,7 @@ Use **`Edit`** — one targeted call. Never `sed`, `awk`, `perl -i`, or `echo >>
|
|
|
123
123
|
|
|
124
124
|
### Step 9: Cross-Linking
|
|
125
125
|
|
|
126
|
-
- If a `Linked task` was provided in `[[TASK-
|
|
126
|
+
- If a `Linked task` was provided in `[[TASK-NNNN]]` format: resolve the task file using `mcp__serena__find_file` with pattern `TASK-NNNN-*` searching `wiki/work/tasks/` (finds active or archived). Then open the task file and append `- Closes BUG-NNNN` to its footer (after the existing UAT link section, or under a new `**Closes**:` line). Use `Edit`.
|
|
127
127
|
- If a `Linked PR` was provided and PR is open: remind the user to add `Closes BUG-NNNN` to the PR description so GitHub auto-references the bug record.
|
|
128
128
|
|
|
129
129
|
### Step 10: Report Completion
|
|
@@ -51,7 +51,7 @@ For each missing required-on-report field, use `AskUserQuestion`. Batch related
|
|
|
51
51
|
|
|
52
52
|
**Do not** ask for `Priority`, `Assignee`, `Impact`, `Workaround`, `Tags`, `Linked task`, `Root Cause`, or `Resolution` — those belong to `/bug-triage` or `/bug-close`. Leaving them blank (or with the templated placeholder line) on initial filing is correct.
|
|
53
53
|
|
|
54
|
-
**Exception**: if the user mentions a task in `$ARGUMENTS`, accept it in either `TASK-
|
|
54
|
+
**Exception**: if the user mentions a task in `$ARGUMENTS`, accept it in either `TASK-NNNN` or `[[TASK-NNNN]]` form and normalize to `"[[TASK-NNNN]]"` for the `linked_task:` frontmatter field. If no task is mentioned, set `linked_task: "—"`.
|
|
55
55
|
|
|
56
56
|
If the user cannot supply reliable Steps to Reproduce, STOP and tell them:
|
|
57
57
|
|
|
@@ -70,21 +70,25 @@ Derive the slug from the title: lowercase, hyphen-separated, 2–5 words, ≤ 60
|
|
|
70
70
|
### Step 5: Present and Confirm
|
|
71
71
|
|
|
72
72
|
Before writing, present:
|
|
73
|
-
- Resolved filename: `wiki/work/bugs/NNNN-<slug>.md`
|
|
73
|
+
- Resolved filename: `wiki/work/bugs/BUG-NNNN-<slug>.md`
|
|
74
74
|
- Title, Severity, Reporter
|
|
75
75
|
- The gathered Environment, Steps, Expected, Actual, Reproducibility values
|
|
76
76
|
|
|
77
77
|
Ask the user to confirm via `AskUserQuestion` ("File this bug? Yes / Edit / Cancel"). If `Cancel`, STOP. If `Edit`, ask which field and re-prompt.
|
|
78
78
|
|
|
79
|
+
### Step 5a: Re-verify next bug number — IMMEDIATELY before writing
|
|
80
|
+
|
|
81
|
+
Re-run the scan from Step 4. If the number planned in Step 4/5 is now taken, silently bump to the new next-available number. **Never call `Write` before completing this re-scan.**
|
|
82
|
+
|
|
79
83
|
### Step 6: Write the Bug File
|
|
80
84
|
|
|
81
|
-
Use `Write` to create `wiki/work/bugs/NNNN-<slug>.md`, following the frontmatter schema in `wiki/work/bugs/lifecycle.md` and the field set gathered in Steps 3–5. Set:
|
|
85
|
+
Use `Write` to create `wiki/work/bugs/BUG-NNNN-<slug>.md`, following the frontmatter schema in `wiki/work/bugs/lifecycle.md` and the field set gathered in Steps 3–5. Set:
|
|
82
86
|
|
|
83
87
|
- `Status: new`
|
|
84
88
|
- `Priority: —` (filled in triage)
|
|
85
89
|
- `Assignee: —` (filled in triage)
|
|
86
90
|
- `Tags: —` (filled in triage)
|
|
87
|
-
- `linked_task:` — `"[[TASK-
|
|
91
|
+
- `linked_task:` — `"[[TASK-NNNN]]"` if a task was mentioned (normalized from either `TASK-NNNN` or `[[TASK-NNNN]]` input); `"—"` otherwise
|
|
88
92
|
- `Reported`: today's date (`YYYY-MM-DD`)
|
|
89
93
|
- `Last updated`: today's date
|
|
90
94
|
- `aliases: [BUG-NNNN]` — mirrors this file's own id: field so Obsidian's wikilink resolver can find it by short ID (ROADMAP-008)
|
|
@@ -105,7 +109,7 @@ Use **`Edit`** — one targeted call. Never `sed`, `awk`, `perl -i`, or `echo >>
|
|
|
105
109
|
### Step 8: Report Completion
|
|
106
110
|
|
|
107
111
|
Print:
|
|
108
|
-
- Created file: `wiki/work/bugs/NNNN-<slug>.md`
|
|
112
|
+
- Created file: `wiki/work/bugs/BUG-NNNN-<slug>.md`
|
|
109
113
|
- Bug ID: `BUG-NNNN`
|
|
110
114
|
- Status: `new`
|
|
111
115
|
- Next step:
|
|
@@ -77,6 +77,10 @@ Group members may share evidence sources (Shared Context), but each block needs
|
|
|
77
77
|
|
|
78
78
|
**Refuse to write the file if any block has empty `Tags`.** For groups, batch all decisions' questions in one `AskUserQuestion` when feasible, but keep questions per-decision.
|
|
79
79
|
|
|
80
|
+
## Step 4.5: Re-verify next decision number — IMMEDIATELY before writing
|
|
81
|
+
|
|
82
|
+
Re-run the scan from Step 2 (`list_dir` on `wiki/work/decisions/` and `archive/`, highest 4-digit prefix + 1). If the number planned earlier is now taken, silently bump to the new next-available number. **Never call `Write` before completing this re-scan.**
|
|
83
|
+
|
|
80
84
|
## Step 5: Generate the file
|
|
81
85
|
Write to `wiki/work/decisions/DEC-NNNN-<group-slug>.md` using this template. **Tables only, mermaid for flows** — mandatory in every block.
|
|
82
86
|
|
|
@@ -168,7 +172,7 @@ flowchart LR
|
|
|
168
172
|
### Links
|
|
169
173
|
- Related decisions: [[DEC-NNNN-slug|DEC-NNNN#DM: title]]
|
|
170
174
|
- Supersedes: [[DEC-MMMM-slug|DEC-MMMM#DK: title]] (if applicable)
|
|
171
|
-
- Source task(s): `wiki/work/tasks/TASK-
|
|
175
|
+
- Source task(s): `wiki/work/tasks/TASK-NNNN-slug.md`
|
|
172
176
|
|
|
173
177
|
---
|
|
174
178
|
|
|
@@ -19,8 +19,8 @@ Use this skill to drive tasks or roadmaps to completion using a parallel agent t
|
|
|
19
19
|
**Trigger:** `/power-mode <path>` with no additional instructions.
|
|
20
20
|
|
|
21
21
|
Inspect the path argument:
|
|
22
|
-
- Path contains `roadmap` or matches `ROADMAP-
|
|
23
|
-
- Path contains `task` or matches `TASK-
|
|
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)
|
|
24
24
|
|
|
25
25
|
---
|
|
26
26
|
|
|
@@ -57,7 +57,7 @@ All agent call examples below omit this footer for brevity — it is always requ
|
|
|
57
57
|
|
|
58
58
|
## Single-Task Executor
|
|
59
59
|
|
|
60
|
-
**Trigger:** `/power-mode <path/to/TASK-
|
|
60
|
+
**Trigger:** `/power-mode <path/to/TASK-NNNN.md>` with no additional instructions.
|
|
61
61
|
|
|
62
62
|
**Goal:** Drive one task through the full tackle → UAT-generate → UAT-auto pipeline exactly once, then stop.
|
|
63
63
|
|
|
@@ -67,7 +67,7 @@ All agent call examples below omit this footer for brevity — it is always requ
|
|
|
67
67
|
|
|
68
68
|
```
|
|
69
69
|
Agent({
|
|
70
|
-
description: "Tackle <TASK-
|
|
70
|
+
description: "Tackle <TASK-NNNN>",
|
|
71
71
|
prompt: "Run /tackle <task-path>. [append team member footer]",
|
|
72
72
|
mode: "bypassPermissions"
|
|
73
73
|
})
|
|
@@ -79,7 +79,7 @@ Wait for the agent to complete.
|
|
|
79
79
|
|
|
80
80
|
```
|
|
81
81
|
Agent({
|
|
82
|
-
description: "UAT generate <TASK-
|
|
82
|
+
description: "UAT generate <TASK-NNNN>",
|
|
83
83
|
prompt: "Run /uat-generate <task-path>. [append team member footer]",
|
|
84
84
|
mode: "bypassPermissions"
|
|
85
85
|
})
|
|
@@ -91,7 +91,7 @@ Wait for the agent to complete.
|
|
|
91
91
|
|
|
92
92
|
```
|
|
93
93
|
Agent({
|
|
94
|
-
description: "UAT auto <TASK-
|
|
94
|
+
description: "UAT auto <TASK-NNNN>",
|
|
95
95
|
prompt: "Run /uat-auto <uat-path> (infer the UAT file path from the task path — same NNN slug, under wiki/work/uat/).
|
|
96
96
|
|
|
97
97
|
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 (if any) — you do not need to instruct any of that here; it happens natively. Just wait for it to complete and report its summary.
|
|
@@ -109,7 +109,7 @@ Done. No further iteration.
|
|
|
109
109
|
|
|
110
110
|
## Roadmap-to-Completion Orchestrator
|
|
111
111
|
|
|
112
|
-
**Trigger:** `/power-mode <path/to/ROADMAP-
|
|
112
|
+
**Trigger:** `/power-mode <path/to/ROADMAP-NNNN.md>` with no additional instructions.
|
|
113
113
|
|
|
114
114
|
**Goal:** Drive the roadmap to completion — every item through the full tackle → UAT-generate → UAT-auto pipeline — looping through waves of parallelizable work until no implementation work remains.
|
|
115
115
|
|
|
@@ -150,7 +150,7 @@ Run tackle → UAT-generate → UAT-auto for all tasks in the current wave. Appl
|
|
|
150
150
|
|
|
151
151
|
Phase 1 — Tackle (parallel, minimum 5 agents when 5+ collision-safe tasks available):
|
|
152
152
|
```
|
|
153
|
-
Agent({ description: "Tackle TASK-
|
|
153
|
+
Agent({ description: "Tackle TASK-NNNN", prompt: "Run /tackle <path>. [append team member footer]", mode: "bypassPermissions" })
|
|
154
154
|
Agent({ description: "Tackle TASK-MMM", prompt: "Run /tackle <path>. [append team member footer]", mode: "bypassPermissions" })
|
|
155
155
|
// ... one per task, all in the same message
|
|
156
156
|
```
|
|
@@ -159,7 +159,7 @@ Wait for all to complete.
|
|
|
159
159
|
|
|
160
160
|
Phase 2 — Generate UAT tests (parallel, read-only):
|
|
161
161
|
```
|
|
162
|
-
Agent({ description: "UAT generate TASK-
|
|
162
|
+
Agent({ description: "UAT generate TASK-NNNN", prompt: "Run /uat-generate <task-path>. [append team member footer]", mode: "bypassPermissions" })
|
|
163
163
|
// ... one per task, all in the same message
|
|
164
164
|
```
|
|
165
165
|
|
|
@@ -168,7 +168,7 @@ Wait for all to complete.
|
|
|
168
168
|
Phase 3 — Run UATs (parallel when UAT files don't collide):
|
|
169
169
|
```
|
|
170
170
|
Agent({
|
|
171
|
-
description: "UAT auto TASK-
|
|
171
|
+
description: "UAT auto TASK-NNNN",
|
|
172
172
|
prompt: "Run /uat-auto <uat-path>.
|
|
173
173
|
|
|
174
174
|
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.
|
|
@@ -75,7 +75,7 @@ See `wiki/guides/mcp-tools.md` for the complete Serena memory reference.
|
|
|
75
75
|
|
|
76
76
|
## Step 4: Check the Task Index
|
|
77
77
|
|
|
78
|
-
`/tackle` no-args mode surveys active tasks by reading `wiki/work/tasks/index.md` — a flat bullet list of active items (`- [TASK-
|
|
78
|
+
`/tackle` no-args mode surveys active tasks by reading `wiki/work/tasks/index.md` — a flat bullet list of active items (`- [TASK-NNNN — Title](TASK-NNNN-slug.md) — one-line summary · status`), one line per `todo`/`in-progress` task. There is no table to "bootstrap"; do a lightweight consistency check so that survey stays trustworthy.
|
|
79
79
|
|
|
80
80
|
1. Use `mcp__serena__list_dir` on `wiki/work/tasks/` to list task files (top-level only, not `archive/`). If the directory is empty or has no task files, skip this step.
|
|
81
81
|
2. Read `wiki/work/tasks/index.md` (use `Read` — markdown).
|
|
@@ -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/REQ-
|
|
25
|
+
**Input:** a project dir with a `wiki/work/requirements/REQ-NNNN-slug.md` (REQ) 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.
|
|
@@ -49,7 +49,7 @@ Parse `$ARGUMENTS` to find the requirement file:
|
|
|
49
49
|
| `<path>` (e.g. `wiki/work/requirements/REQ-003-onboarding.md`) | Use as-is |
|
|
50
50
|
| `<NNN-slug>` (e.g. `003-onboarding`) | `mcp__serena__find_file` with mask `003-onboarding.md` under `wiki/work/requirements/` |
|
|
51
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-
|
|
52
|
+
| Empty / missing | Look for any `wiki/work/requirements/REQ-NNNN-slug.md` with `status: approved`; if ambiguous, ask via `AskUserQuestion` |
|
|
53
53
|
|
|
54
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.
|
|
55
55
|
|
|
@@ -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/REQ-
|
|
36
|
+
Requirements live at `wiki/work/requirements/REQ-NNNN-slug.md` (4-digit zero-padded). `list_dir` both `wiki/work/requirements/` and `wiki/work/requirements/archive/` (skip either that doesn't exist) — highest prefix across both + 1 (first is `REQ-0001`). Never re-use a number; retired requirements keep theirs forever. Derive the slug — names the **initiative**, lowercase dash-separated ≤60 chars (e.g. "Self-serve billing portal" → `REQ-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**:
|
|
@@ -68,13 +68,17 @@ Walk the elicitations **in order**. Batch related ones into a single round when
|
|
|
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
|
+
### Step 5a: Re-verify next requirement number — IMMEDIATELY before writing
|
|
72
|
+
|
|
73
|
+
Re-run the scan from Step 2. If the number planned earlier is now taken, silently bump to the new next-available number. **Never call `Write` before completing this re-scan.**
|
|
74
|
+
|
|
71
75
|
## Step 6: Write the file
|
|
72
|
-
After confirmation, `Write` `wiki/work/requirements/REQ-
|
|
76
|
+
After confirmation, `Write` `wiki/work/requirements/REQ-NNNN-slug.md`.
|
|
73
77
|
|
|
74
78
|
```yaml
|
|
75
79
|
---
|
|
76
|
-
id: REQ-
|
|
77
|
-
aliases: [REQ-
|
|
80
|
+
id: REQ-NNNN
|
|
81
|
+
aliases: [REQ-NNNN]
|
|
78
82
|
type: requirement
|
|
79
83
|
status: draft
|
|
80
84
|
created: YYYY-MM-DD
|
|
@@ -86,21 +90,21 @@ tags: [<tag1>, <tag2>]
|
|
|
86
90
|
---
|
|
87
91
|
```
|
|
88
92
|
|
|
89
|
-
Sections in order: `# REQ-
|
|
93
|
+
Sections in order: `# REQ-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) · `## Amendments` (empty, `<!-- Amendments appear here as ## Amendment 1, ## Amendment 2, etc. -->`).
|
|
90
94
|
|
|
91
95
|
**Refuse to write** if any required-non-empty field is missing or fails its bar — loop back to Step 4.
|
|
92
96
|
|
|
93
97
|
## Step 7: Update indexes + log (`Edit` only, never `sed`/`awk`/`echo >>`)
|
|
94
|
-
|
|
98
|
+
Append (or replace the placeholder row) in `wiki/work/requirements/index.md` using the format documented at the top of that file: `- [REQ-NNNN — Title](REQ-NNNN-slug.md) — one-line summary · status`, in ascending REQ order. Append to `wiki/log.md`: `## [YYYY-MM-DD] req-create | REQ-NNNN <title>`.
|
|
95
99
|
|
|
96
100
|
## Step 8: Cross-link related artifacts
|
|
97
|
-
If prompted by an existing task/research note/reference, link both ways (`Read` then `Edit`, never `sed`): source artifact gets `**Requirement**: REQ-
|
|
101
|
+
If prompted by an existing task/research note/reference, link both ways (`Read` then `Edit`, never `sed`): source artifact gets `**Requirement**: REQ-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.
|
|
98
102
|
|
|
99
103
|
## Step 9: Update memory if appropriate
|
|
100
|
-
`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 `REQ-
|
|
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 `REQ-NNNN` in the body.
|
|
101
105
|
|
|
102
106
|
## Step 10: Report
|
|
103
|
-
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 `/req-finalize wiki/work/requirements/REQ-
|
|
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 `/req-finalize wiki/work/requirements/REQ-NNNN-slug.md`. Note any placeholder-reduced field under a **Gaps** section for the user to address before `/req-finalize`.
|
|
104
108
|
|
|
105
109
|
---
|
|
106
110
|
|
|
@@ -134,7 +134,7 @@ For **each proposed group**, ask: "Create this as a decision now?" with options:
|
|
|
134
134
|
| `merge into <Gx>` | Combine this group with another listed group |
|
|
135
135
|
| `split` | Break this group into multiple smaller groups |
|
|
136
136
|
| `skip — already covered` | Drop the group; the ASR is handled by an existing decision |
|
|
137
|
-
| `skip — non-architectural` | Drop the group; handle directly via `/task-add --req REQ-
|
|
137
|
+
| `skip — non-architectural` | Drop the group; handle directly via `/task-add --req REQ-NNNN` |
|
|
138
138
|
|
|
139
139
|
### Step 7: Update the requirement's `## Linked Decisions` section
|
|
140
140
|
|
|
@@ -161,7 +161,7 @@ Also update the requirement's frontmatter `updated` to today's date. Both edits
|
|
|
161
161
|
Append to `wiki/log.md`:
|
|
162
162
|
|
|
163
163
|
```
|
|
164
|
-
## [YYYY-MM-DD] req-extract-decisions | REQ-
|
|
164
|
+
## [YYYY-MM-DD] req-extract-decisions | REQ-NNNN <title> — N ASRs identified
|
|
165
165
|
```
|
|
166
166
|
|
|
167
167
|
### Step 8: Update existing decisions that reuse requirement ASRs
|
|
@@ -172,8 +172,8 @@ For each affected decision file:
|
|
|
172
172
|
|
|
173
173
|
1. `Read` the file
|
|
174
174
|
2. Locate the target decision's `### Links` section
|
|
175
|
-
3. Check whether `Source REQ: REQ-
|
|
176
|
-
4. `Edit` to append: `- Source REQ: [REQ-
|
|
175
|
+
3. Check whether `Source REQ: REQ-NNNN` already exists — **skip if present** (idempotent)
|
|
176
|
+
4. `Edit` to append: `- Source REQ: [REQ-NNNN](../requirements/NNN-slug.md)`
|
|
177
177
|
|
|
178
178
|
Touch only the target decision's `### Links`. Do not modify any decision's status, metadata, or content beyond the `### Links` append.
|
|
179
179
|
|
|
@@ -183,7 +183,7 @@ Print a tabular completion report:
|
|
|
183
183
|
|
|
184
184
|
| Field | Value |
|
|
185
185
|
|-------|-------|
|
|
186
|
-
| Requirement | `REQ-
|
|
186
|
+
| Requirement | `REQ-NNNN <title>` |
|
|
187
187
|
| ASRs identified | count |
|
|
188
188
|
| ASRs covered by existing decisions | count (linked back) |
|
|
189
189
|
| New decision groups proposed | count |
|
|
@@ -198,10 +198,10 @@ Then list the **next-action commands**, one per confirmed new group:
|
|
|
198
198
|
|
|
199
199
|
```
|
|
200
200
|
To create the proposed decisions, run each:
|
|
201
|
-
/decision-create group: search-infrastructure (from REQ-
|
|
202
|
-
/decision-create hris-integration (from REQ-
|
|
201
|
+
/decision-create group: search-infrastructure (from REQ-NNNN)
|
|
202
|
+
/decision-create hris-integration (from REQ-NNNN)
|
|
203
203
|
|
|
204
|
-
After each /decision-create completes, return to REQ-
|
|
204
|
+
After each /decision-create completes, return to REQ-NNNN's `## Linked Decisions` table
|
|
205
205
|
and update the placeholder row with the actual wikilink [[NNNN-slug|DEC-NNNN#DM]].
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -209,7 +209,7 @@ If any ASRs were skipped as non-architectural, also surface:
|
|
|
209
209
|
|
|
210
210
|
```
|
|
211
211
|
The following ASRs are best handled directly as tasks (no decision needed):
|
|
212
|
-
/task-add --req REQ-
|
|
212
|
+
/task-add --req REQ-NNNN "<short description for ASR Ax>"
|
|
213
213
|
```
|
|
214
214
|
|
|
215
215
|
The skill does **not** auto-invoke `/decision-create` or `/task-add`. It surfaces the commands; the user runs them.
|
|
@@ -223,7 +223,7 @@ The skill does **not** auto-invoke `/decision-create` or `/task-add`. It surface
|
|
|
223
223
|
3. **Never invent ASRs.** Every entry in the ASR table must trace to a specific requirement section, quoted or paraphrased verbatim.
|
|
224
224
|
4. **Boundary rule is enforced strictly.** Requirements ask for outcomes, decisions admit trade-offs. If a candidate ASR sounds like a solution, reformulate it as the underlying outcome.
|
|
225
225
|
5. **Requirement edits are surgical.** Use `Read` then `Edit` to update only the `## Linked Decisions` table and the `updated` field. Never rewrite the file.
|
|
226
|
-
6. **Idempotent back-links.** If `Source REQ: REQ-
|
|
226
|
+
6. **Idempotent back-links.** If `Source REQ: REQ-NNNN` already exists in a decision's `### Links`, skip the edit. Re-running this skill against the same requirement must not duplicate links.
|
|
227
227
|
7. **Wikilinks for existing decisions.** Use `[[NNNN-slug\|DEC-NNNN#DM]]` format in the `## Linked Decisions` table.
|
|
228
228
|
|
|
229
229
|
---
|
|
@@ -182,7 +182,7 @@ If this requirement's row does not yet exist in the index table, insert a new ro
|
|
|
182
182
|
|
|
183
183
|
| Column | Format |
|
|
184
184
|
|--------|--------|
|
|
185
|
-
| `ID` | `[REQ-
|
|
185
|
+
| `ID` | `[REQ-NNNN](requirements/NNN-slug.md)` |
|
|
186
186
|
| `Title` | The requirement's initiative title |
|
|
187
187
|
| `Status` | `approved` |
|
|
188
188
|
| `Created` | The requirement's `created:` date |
|
|
@@ -193,7 +193,7 @@ If this requirement's row does not yet exist in the index table, insert a new ro
|
|
|
193
193
|
Append to `wiki/log.md`:
|
|
194
194
|
|
|
195
195
|
```
|
|
196
|
-
## [YYYY-MM-DD] req-approved | REQ-
|
|
196
|
+
## [YYYY-MM-DD] req-approved | REQ-NNNN <title>
|
|
197
197
|
```
|
|
198
198
|
|
|
199
199
|
Use `Read` then `Edit` for the index update — never `echo >>` or `sed`.
|
|
@@ -223,7 +223,7 @@ Suggested next steps:
|
|
|
223
223
|
| Suggestion | When to use it |
|
|
224
224
|
|------------|----------------|
|
|
225
225
|
| `/req-extract-decisions <file>` | The default next step — extract Architecturally Significant Requirements and propose decision candidates |
|
|
226
|
-
| `/task-add --req REQ-
|
|
226
|
+
| `/task-add --req REQ-NNNN <description>` | Only when the requirement's scope is small enough to skip decisions entirely |
|
|
227
227
|
| `/req-update <file> <change>` | If a scope change surfaces post-approval — appends an `## Amendment N` block; never rewrites |
|
|
228
228
|
|
|
229
229
|
Do **not** auto-create downstream artifacts — present them as suggestions only.
|
|
@@ -3,7 +3,7 @@ name: req-retire
|
|
|
3
3
|
description: Retire a requirement — set status to retired in frontmatter, document the reason, move to archive/, append a log entry.
|
|
4
4
|
category: planning
|
|
5
5
|
model: claude-haiku-4-5-20251001
|
|
6
|
-
argument-hint: <wiki/work/requirements/REQ-
|
|
6
|
+
argument-hint: <wiki/work/requirements/REQ-NNNN-slug.md, NNN-slug, or NNN> [reason]
|
|
7
7
|
disable-model-invocation: false
|
|
8
8
|
user-invocable: true
|
|
9
9
|
---
|
|
@@ -12,7 +12,7 @@ user-invocable: true
|
|
|
12
12
|
|
|
13
13
|
# Retire Requirement
|
|
14
14
|
|
|
15
|
-
Set a requirement's `status` to `retired`, document why, then move the file to `wiki/work/requirements/archive/`. After archiving, cross-references using `[[REQ-
|
|
15
|
+
Set a requirement's `status` to `retired`, document why, then move the file to `wiki/work/requirements/archive/`. After archiving, cross-references using `[[REQ-NNNN]]` remain valid — the ID is stable regardless of file location.
|
|
16
16
|
|
|
17
17
|
This skill is a focused shortcut for the retirement flow. For amendments that don't touch status, use `/req-update`. For supersession (a new requirement replaces this one), use `/req-update` with supersession intent or pass `status: superseded` instructions here.
|
|
18
18
|
|
|
@@ -50,8 +50,8 @@ If the file cannot be located, **stop** and report.
|
|
|
50
50
|
|----------------|--------|
|
|
51
51
|
| `draft` | Continue — may be retired before approval |
|
|
52
52
|
| `approved` | Continue — most common case |
|
|
53
|
-
| `retired` | **STOP.** Tell the user: "REQ-
|
|
54
|
-
| `superseded` | **STOP.** Tell the user: "REQ-
|
|
53
|
+
| `retired` | **STOP.** Tell the user: "REQ-NNNN is already retired. No action needed." |
|
|
54
|
+
| `superseded` | **STOP.** Tell the user: "REQ-NNNN is already superseded. No action needed." |
|
|
55
55
|
|
|
56
56
|
3. **Check for downstream artifacts** in `## Linked Decisions` and `## Linked Tasks`:
|
|
57
57
|
- List any linked decisions and their current status
|
|
@@ -74,7 +74,7 @@ Use `AskUserQuestion` to confirm. Show:
|
|
|
74
74
|
Ask the user:
|
|
75
75
|
|
|
76
76
|
1. **"Retire this requirement? (yes / no)"**
|
|
77
|
-
2. **"Reason for retiring REQ-
|
|
77
|
+
2. **"Reason for retiring REQ-NNNN?"** (if not provided in `$ARGUMENTS` — required, one line or more)
|
|
78
78
|
|
|
79
79
|
If the user says **No**, STOP. Do not proceed.
|
|
80
80
|
|
|
@@ -113,7 +113,7 @@ git mv wiki/work/requirements/<file>.md wiki/work/requirements/archive/<file>.md
|
|
|
113
113
|
Then append to `wiki/work/requirements/archive/index.md`:
|
|
114
114
|
|
|
115
115
|
```
|
|
116
|
-
| [[REQ-
|
|
116
|
+
| [[REQ-NNNN]] | <Title> | retired | YYYY-MM-DD |
|
|
117
117
|
```
|
|
118
118
|
|
|
119
119
|
Use `Read` then `Edit` for the archive index append — never `echo >>`.
|
|
@@ -123,7 +123,7 @@ Use `Read` then `Edit` for the archive index append — never `echo >>`.
|
|
|
123
123
|
Append one entry to `wiki/log.md`:
|
|
124
124
|
|
|
125
125
|
```
|
|
126
|
-
## [YYYY-MM-DD] req-retired | REQ-
|
|
126
|
+
## [YYYY-MM-DD] req-retired | REQ-NNNN <title> — reason: <one-line summary of reason>
|
|
127
127
|
```
|
|
128
128
|
|
|
129
129
|
Use `Read` then `Edit` — never `echo >>` or `sed`.
|
|
@@ -150,8 +150,8 @@ Print a tabular summary:
|
|
|
150
150
|
|
|
151
151
|
| Field | Value |
|
|
152
152
|
|-------|-------|
|
|
153
|
-
| Requirement | `REQ-
|
|
154
|
-
| File path | `wiki/work/requirements/REQ-
|
|
153
|
+
| Requirement | `REQ-NNNN <title>` |
|
|
154
|
+
| File path | `wiki/work/requirements/REQ-NNNN-slug.md` → `wiki/work/requirements/archive/REQ-NNNN-slug.md` |
|
|
155
155
|
| Old status | `draft` or `approved` |
|
|
156
156
|
| New status | `retired` |
|
|
157
157
|
| Reason | <one-line summary> |
|
|
@@ -167,7 +167,7 @@ Print a tabular summary:
|
|
|
167
167
|
|
|
168
168
|
1. Use tables for the downstream artifacts list and the completion report — never paragraph prose.
|
|
169
169
|
2. **One `Edit` call per change** — never bulk rewrites.
|
|
170
|
-
3. **After archiving, cross-references using `[[REQ-
|
|
170
|
+
3. **After archiving, cross-references using `[[REQ-NNNN]]` remain valid** — the ID is stable regardless of file location.
|
|
171
171
|
4. **The skill never auto-retires or auto-deprecates downstream artifacts** — it surfaces them with suggested commands.
|
|
172
172
|
5. **The retirement reason in `## Notes` is permanent** — it is the audit trail for why this requirement was retired.
|
|
173
173
|
|
|
@@ -61,8 +61,8 @@ If the **change instructions are empty**, use `AskUserQuestion` to elicit them b
|
|
|
61
61
|
|--------|--------|
|
|
62
62
|
| `draft` | Continue to Step 3 (you will take the **direct-edit branch** in Step 4) |
|
|
63
63
|
| `approved` | Continue to Step 3 (you will take the **amendment branch** in Step 4); also check if the user intends to retire (see retiring branch below) |
|
|
64
|
-
| `retired` | **STOP.** Tell the user: "REQ-
|
|
65
|
-
| `superseded` | **STOP.** Tell the user: "REQ-
|
|
64
|
+
| `retired` | **STOP.** Tell the user: "REQ-NNNN is retired. Run `/req-create` for any new scope." |
|
|
65
|
+
| `superseded` | **STOP.** Tell the user: "REQ-NNNN was superseded. Update the successor requirement instead." |
|
|
66
66
|
|
|
67
67
|
**Retiring branch** (when the user indicates they want to mark the requirement as retired):
|
|
68
68
|
1. Ask for the retirement reason via `AskUserQuestion`
|
|
@@ -70,7 +70,7 @@ If the **change instructions are empty**, use `AskUserQuestion` to elicit them b
|
|
|
70
70
|
3. Append reason to `## Notes` section: *"Retired YYYY-MM-DD: <reason>"*
|
|
71
71
|
4. Update `updated` in frontmatter to today's date
|
|
72
72
|
5. Remove the requirement's row from `wiki/work/requirements/index.md` (terminal status — active index only)
|
|
73
|
-
6. Append to `wiki/log.md`: `## [YYYY-MM-DD] req-retired | REQ-
|
|
73
|
+
6. Append to `wiki/log.md`: `## [YYYY-MM-DD] req-retired | REQ-NNNN <title> — <reason>`
|
|
74
74
|
7. Skip to Step 10 (report)
|
|
75
75
|
|
|
76
76
|
---
|
|
@@ -204,7 +204,7 @@ Apply each marker with one `Edit` call. Use unique surrounding text in `old_stri
|
|
|
204
204
|
Append to `wiki/log.md`:
|
|
205
205
|
|
|
206
206
|
```
|
|
207
|
-
## [YYYY-MM-DD] req-updated | REQ-
|
|
207
|
+
## [YYYY-MM-DD] req-updated | REQ-NNNN <title> — Amendment N
|
|
208
208
|
```
|
|
209
209
|
|
|
210
210
|
---
|