@codewizard-dt/bootstrap 4.0.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/lib/prompts/README.md +0 -1
- package/lib/scripts/README.md +1 -2
- 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 +1 -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 +2 -1
- package/lib/skills/architecture-audit/SKILL.md +207 -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 +7 -7
- 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 +1 -1
|
@@ -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
|
---
|
|
@@ -54,9 +54,9 @@ This step is read-only — never run `/decision-finalize` yourself; surface the
|
|
|
54
54
|
|
|
55
55
|
## Step 5: Cross-roadmap dependency analysis
|
|
56
56
|
|
|
57
|
-
For every remaining roadmap's `task-link` items (skip `inline` items — no task file exists yet to inspect): `Read` the task file, find `## Dependencies` / `## Blocked by` / `depends_on::` / `blocks::` refs, extract `TASK-
|
|
57
|
+
For every remaining roadmap's `task-link` items (skip `inline` items — no task file exists yet to inspect): `Read` the task file, find `## Dependencies` / `## Blocked by` / `depends_on::` / `blocks::` refs, extract `TASK-NNNN` IDs.
|
|
58
58
|
|
|
59
|
-
For each referenced `TASK-
|
|
59
|
+
For each referenced `TASK-NNNN`, check whether it belongs to a *different* roadmap (scan the parsed item lists from Step 2 for that ID). If so, record a directed edge `blocking_roadmap → blocked_roadmap` (the roadmap holding the prerequisite task blocks the roadmap holding the dependent task).
|
|
60
60
|
|
|
61
61
|
Also note — but do not treat as a hard edge — soft relatedness: roadmaps sharing a `linked_requirements` or `linked_decisions` entry. If a shared linked decision's text explicitly states a sequence ("do X before Y", "requires X shipped first"), `Read` that decision file and promote it to a hard edge instead.
|
|
62
62
|
|
|
@@ -70,7 +70,7 @@ Order the remaining roadmaps, highest priority first, using this precedence:
|
|
|
70
70
|
2. **Functional priority** — a judgment call from each roadmap's `## Goal`, `tags`, and any linked requirement's priority/severity field (`Read` it if present). Goals that unblock or protect other work (infra, security, load-bearing bug fixes) outrank polish or nice-to-have goals. Record a one-sentence rationale per roadmap in the report — this is a judgment call the user can override, not a fact.
|
|
71
71
|
3. **Momentum** (tie-break only — never overrides #1 or #2) — a higher `done/total` ratio ranks slightly higher; finishing in-flight work compounds value faster than starting a new thread.
|
|
72
72
|
|
|
73
|
-
If two or more roadmaps are genuinely indistinguishable on all three signals, keep their existing relative order (`ROADMAP-
|
|
73
|
+
If two or more roadmaps are genuinely indistinguishable on all three signals, keep their existing relative order (`ROADMAP-NNNN` ascending) rather than guessing.
|
|
74
74
|
|
|
75
75
|
An outstanding decision (Step 4) does **not** change a roadmap's rank — it changes what "next" means for it. A blocked roadmap can still be #1 in priority; it's just not actionable via `/roadmap-next` until the decision resolves. Reflect that in the rank table's `Depends on` column and in the Step 6d status block.
|
|
76
76
|
|
|
@@ -104,8 +104,8 @@ These roadmaps are gated on decisions still `proposed` — resolve via `/decisio
|
|
|
104
104
|
|
|
105
105
|
| Rank | Roadmap | Progress | Priority rationale | Depends on |
|
|
106
106
|
|------|---------|----------|---------------------|------------|
|
|
107
|
-
| 1 | ROADMAP-
|
|
108
|
-
| 2 | ROADMAP-MMM — <title> | M/N | <one sentence> | ROADMAP-
|
|
107
|
+
| 1 | ROADMAP-NNNN — <title> | M/N | <one sentence> | — |
|
|
108
|
+
| 2 | ROADMAP-MMM — <title> | M/N | <one sentence> | ROADMAP-NNNN (Phase X blocks it) |
|
|
109
109
|
```
|
|
110
110
|
|
|
111
111
|
`Depends on` lists the hard-edge blockers found in Step 5, or `—` if none. A roadmap with an outstanding decision also gets `Blocked by DEC-NNNN#DM` appended here even if it has no roadmap-to-roadmap dependency.
|
|
@@ -115,7 +115,7 @@ These roadmaps are gated on decisions still `proposed` — resolve via `/decisio
|
|
|
115
115
|
One block per roadmap, in ranked order:
|
|
116
116
|
|
|
117
117
|
```
|
|
118
|
-
### ROADMAP-
|
|
118
|
+
### ROADMAP-NNNN — <title>
|
|
119
119
|
- Owner: <owner, or "unassigned">
|
|
120
120
|
- Progress: M/N items checked
|
|
121
121
|
- Status: <active — on track | active — stalled | active — mostly inline placeholders, not yet materialized | blocked — awaiting decision(s)>
|
|
@@ -135,7 +135,7 @@ If the roadmap has an outstanding decision from Step 4, set `Status: blocked —
|
|
|
135
135
|
```
|
|
136
136
|
## Warning: Dependency Cycle
|
|
137
137
|
|
|
138
|
-
ROADMAP-
|
|
138
|
+
ROADMAP-NNNN → ROADMAP-MMM → ROADMAP-NNNN
|
|
139
139
|
These roadmaps block each other — resolve the cycle manually before treating either as higher priority.
|
|
140
140
|
```
|
|
141
141
|
|
|
@@ -19,7 +19,7 @@ The hard boundary:
|
|
|
19
19
|
|
|
20
20
|
> *A roadmap shows order. A task contains implementation steps. Never smuggle step-level detail into a roadmap item.*
|
|
21
21
|
|
|
22
|
-
If a checkbox starts growing sub-bullets like "run `pnpm install`" or "edit `src/foo.ts`", that content belongs in a real task file — created via `/task-add` (or `/task-add --roadmap ROADMAP-
|
|
22
|
+
If a checkbox starts growing sub-bullets like "run `pnpm install`" or "edit `src/foo.ts`", that content belongs in a real task file — created via `/task-add` (or `/task-add --roadmap ROADMAP-NNNN` to auto-link). Redirect the user when this happens.
|
|
23
23
|
|
|
24
24
|
This skill drives a **short** Socratic Q&A session via `AskUserQuestion`. Roadmap creation is execution planning, not product strategy — keep questions focused and tight. Aim for one or two batched `AskUserQuestion` rounds plus per-phase follow-ups, not a full PRD-style interrogation.
|
|
25
25
|
|
|
@@ -54,14 +54,14 @@ If the topic is a single task with several steps, **stop and tell the user** —
|
|
|
54
54
|
|
|
55
55
|
### Step 2: Locate the roadmap directory and assign a number
|
|
56
56
|
|
|
57
|
-
Roadmaps live at `wiki/work/roadmaps/
|
|
57
|
+
Roadmaps live at `wiki/work/roadmaps/ROADMAP-NNNN-slug.md`. Numbers are 4-digit zero-padded.
|
|
58
58
|
|
|
59
|
-
1. **Use `mcp__serena__list_dir` on `wiki/work/roadmaps/` and `wiki/work/roadmaps/archive/`** (skip either that doesn't exist) to scan existing files. Collect every `
|
|
59
|
+
1. **Use `mcp__serena__list_dir` on `wiki/work/roadmaps/` and `wiki/work/roadmaps/archive/`** (skip either that doesn't exist) to scan existing files. Collect the numeric value from every `ROADMAP-<digits>-` prefix across **both** directories, regardless of digit count (existing files are 3-digit; new ones are 4-digit) — ignore leading zeros when comparing.
|
|
60
60
|
2. **Use `mcp__serena__search_for_pattern`** against `wiki/work/roadmaps/index.md` for `ROADMAP-\d{3}` entries — these may reserve numbers not yet on disk.
|
|
61
|
-
3. Take `max + 1`, zero-pad to
|
|
61
|
+
3. Take `max + 1`, zero-pad the result to 4 digits. In a brand-new project the first roadmap is `ROADMAP-0001`; in this repo, continue from the current max (do not restart at 1).
|
|
62
62
|
4. **Derive the file slug** — names the **initiative**. Lowercase, dash-separated, ≤ 60 chars:
|
|
63
|
-
- "Ship the billing portal" → `
|
|
64
|
-
- "Migrate to Postgres 17" → `
|
|
63
|
+
- "Ship the billing portal" → `ROADMAP-0001-ship-billing-portal.md`
|
|
64
|
+
- "Migrate to Postgres 17" → `ROADMAP-0004-migrate-postgres-17.md`
|
|
65
65
|
|
|
66
66
|
Confirm the chosen number and slug with the user via `AskUserQuestion` only if either is non-obvious.
|
|
67
67
|
|
|
@@ -86,18 +86,18 @@ Then **per-phase**, in a single follow-up `AskUserQuestion` round (one question
|
|
|
86
86
|
|
|
87
87
|
| # | Elicitation | Quality bar |
|
|
88
88
|
|---|-------------|-------------|
|
|
89
|
-
| 5 | **Phase N items** | For each phase, the user names (a) any existing tasks (`TASK-
|
|
89
|
+
| 5 | **Phase N items** | For each phase, the user names (a) any existing tasks (`TASK-NNNN` or slug fragments) that belong in this phase, and (b) any inline placeholder items. Items may be empty if the user wants to fill in later by editing the roadmap file directly or via `/task-add --roadmap ROADMAP-NNNN` — but **at least one phase must contain at least one item** (a roadmap with zero items is not a roadmap) |
|
|
90
90
|
|
|
91
91
|
When the user supplies a task reference:
|
|
92
92
|
|
|
93
|
-
- Look it up in `wiki/work/tasks/` via `mcp__serena__find_file` to confirm it exists. The link must read `[[TASK-
|
|
93
|
+
- Look it up in `wiki/work/tasks/` via `mcp__serena__find_file` to confirm it exists. The link must read `[[TASK-NNNN: <task title>]]`.
|
|
94
94
|
- If the user supplies a task reference that does **not** exist, treat it as an inline placeholder (do not fabricate a link). Note in the per-phase clarification that a task file must be created before this item can be worked on — it will be created automatically when `/roadmap-next` is run.
|
|
95
95
|
|
|
96
96
|
**Inline placeholders**: items without a corresponding task file are written as `- [ ] <description>`. They are valid at creation time because tasks may not exist yet. However, **inline items cannot be worked on** — `/roadmap-next` will automatically invoke `/task-add` to create a task file for each inline item before surfacing it. The roadmap item is then upgraded to a task-link in place.
|
|
97
97
|
|
|
98
98
|
**Redirection rule**: if the user starts spelling out implementation detail under an item (file paths, function names, sub-steps), respond:
|
|
99
99
|
|
|
100
|
-
> That sounds like task content, not a roadmap item. Roadmaps show *ordering*. The *how* belongs in a task file — file one with `/task-add --roadmap ROADMAP-
|
|
100
|
+
> That sounds like task content, not a roadmap item. Roadmaps show *ordering*. The *how* belongs in a task file — file one with `/task-add --roadmap ROADMAP-NNNN <description>` and the roadmap will auto-link to it.
|
|
101
101
|
|
|
102
102
|
Then re-ask for a single checkbox-sized item.
|
|
103
103
|
|
|
@@ -110,7 +110,7 @@ Before writing the file, present a **tabular preview** of the roadmap:
|
|
|
110
110
|
| Header | Title, Status (`active`), Owner, Linked PRD, Linked ADRs, Tags |
|
|
111
111
|
| Goal | Full text |
|
|
112
112
|
| Phases | Table of `Phase N` → `Name` → `# items` (task-link + inline counts) |
|
|
113
|
-
| Per-phase items | One sub-list per phase showing each item's rendered form (`[[TASK-
|
|
113
|
+
| Per-phase items | One sub-list per phase showing each item's rendered form (`[[TASK-NNNN: title]]` or inline text) |
|
|
114
114
|
|
|
115
115
|
The user confirms via `AskUserQuestion` with options like *Approve and write*, *Edit specific phase*, *Cancel*. Do **not** write the file until the user explicitly approves.
|
|
116
116
|
|
|
@@ -122,18 +122,18 @@ The number determined in Step 2 may now be stale (other roadmaps created mid-ses
|
|
|
122
122
|
|
|
123
123
|
- `mcp__serena__list_dir` on `wiki/work/roadmaps/` **and** `wiki/work/roadmaps/archive/` (skip either that doesn't exist)
|
|
124
124
|
- `mcp__serena__search_for_pattern` against `wiki/work/roadmaps/index.md` for `ROADMAP-\d{3}` entries
|
|
125
|
-
- Collect every `
|
|
125
|
+
- Collect the numeric value from every `ROADMAP-<digits>-` prefix across both directories, regardless of digit count (existing files are 3-digit; new ones are 4-digit) — ignore leading zeros when comparing. Take `max + 1`, zero-pad the result to 4 digits.
|
|
126
126
|
- If the number you planned to use in Step 4 has been taken, silently bump to the new next-available number and use it. Do not re-prompt the user.
|
|
127
127
|
- **Never call `Write` before completing this re-scan.**
|
|
128
128
|
|
|
129
129
|
### Step 6: Write the roadmap file
|
|
130
130
|
|
|
131
|
-
Use `Write` to create `wiki/work/roadmaps/
|
|
131
|
+
Use `Write` to create `wiki/work/roadmaps/ROADMAP-NNNN-slug.md` following the field table below and the item-rendering rules **exactly**; the frontmatter must match the schema in `wiki/work/roadmaps/lifecycle.md`.
|
|
132
132
|
|
|
133
133
|
| Field | Value at creation time |
|
|
134
134
|
|-------|------------------------|
|
|
135
135
|
| `Status` | `active` |
|
|
136
|
-
| `aliases` | `[ROADMAP-
|
|
136
|
+
| `aliases` | `[ROADMAP-NNNN]` — mirrors the file's own `id:` value |
|
|
137
137
|
| `Created` | Today's date (derive at runtime — use the conversation environment's `currentDate`, otherwise `date +%Y-%m-%d`) |
|
|
138
138
|
| `Last updated` | Same as `Created` |
|
|
139
139
|
| `Owner` | From Step 3 #3 |
|
|
@@ -146,7 +146,7 @@ Use `Write` to create `wiki/work/roadmaps/NNN-slug.md` following the field table
|
|
|
146
146
|
|
|
147
147
|
**Item rendering rules**:
|
|
148
148
|
|
|
149
|
-
- Task-link item: `- [ ] [[TASK-
|
|
149
|
+
- Task-link item: `- [ ] [[TASK-NNNN: <task title>]]`
|
|
150
150
|
- Inline item: `- [ ] <free-form description>`
|
|
151
151
|
|
|
152
152
|
**Refuse to write** if:
|
|
@@ -165,7 +165,7 @@ Edit `wiki/work/roadmaps/index.md` to add a new bullet line (active items only
|
|
|
165
165
|
2. If the placeholder line (`_(none yet)_` or a "no roadmaps yet" note) exists, **replace** it with the new line. Otherwise **append** the new line in numerical order.
|
|
166
166
|
3. Use the entry format documented at the top of `index.md`:
|
|
167
167
|
|
|
168
|
-
`- [ROADMAP-
|
|
168
|
+
`- [ROADMAP-NNNN — <title>](ROADMAP-NNNN-slug.md) — <one-line summary> · 0/<total> items checked`
|
|
169
169
|
|
|
170
170
|
where `<title>` is the roadmap's H1 sub-title (without any `Roadmap NNN:` prefix), `<one-line summary>` is a short description of the goal, and `<total>` is the count of `- [ ]` checkboxes you just wrote across all phases.
|
|
171
171
|
|
|
@@ -181,7 +181,7 @@ Print a tabular summary:
|
|
|
181
181
|
|
|
182
182
|
| Field | Value |
|
|
183
183
|
|-------|-------|
|
|
184
|
-
| File path | `wiki/work/roadmaps/
|
|
184
|
+
| File path | `wiki/work/roadmaps/ROADMAP-NNNN-slug.md` |
|
|
185
185
|
| Status | `active` |
|
|
186
186
|
| Phases | N |
|
|
187
187
|
| Total items | M (task-link: X, inline: Y) |
|
|
@@ -189,9 +189,9 @@ Print a tabular summary:
|
|
|
189
189
|
| Linked PRD | PRD-NNN or `—` |
|
|
190
190
|
| Linked ADRs | list or `—` |
|
|
191
191
|
| Index updated | yes (1 row added) |
|
|
192
|
-
| Suggested next steps | `/roadmap-next wiki/work/roadmaps/
|
|
192
|
+
| Suggested next steps | `/roadmap-next wiki/work/roadmaps/ROADMAP-NNNN-slug.md` — surfaces the first item and creates task files for any inline placeholders • `/task-add --roadmap ROADMAP-NNNN <description>` — file a new task auto-linked to this roadmap |
|
|
193
193
|
|
|
194
|
-
If any phase was left empty by design (user plans to fill it in later by editing the roadmap file directly or via `/task-add --roadmap ROADMAP-
|
|
194
|
+
If any phase was left empty by design (user plans to fill it in later by editing the roadmap file directly or via `/task-add --roadmap ROADMAP-NNNN`), note it in a separate **Gaps** section so the user can address it before execution begins.
|
|
195
195
|
|
|
196
196
|
If the roadmap contains any inline placeholder items (items without a task-link), include a **Placeholders** section listing them:
|
|
197
197
|
|
|
@@ -208,17 +208,17 @@ This is informational only — no action required now.
|
|
|
208
208
|
1. **Tables, not bullets, for every preview and summary in the conversation.** The roadmap file itself uses checklists (that's its format), but every Q&A preview and Step 8 report uses tables.
|
|
209
209
|
2. **Phase names are short and execution-flavored.** "Foundation", "API", "Tests", "Release" — not "Phase where we figure out the database stuff".
|
|
210
210
|
3. **Items are single checkbox-sized.** No sub-bullets, no indented steps, no embedded code blocks. If an item needs detail, it's a task — file one. Items without a task file are written as inline placeholders (`- [ ] <description>`) and are valid at creation time, but will be converted to task-links automatically by `/roadmap-next` before they can be worked on.
|
|
211
|
-
4. **Task-link items must use `[[TASK-
|
|
211
|
+
4. **Task-link items must use `[[TASK-NNNN: <title>]]` format.** The `TASK-NNNN:` prefix is required so the auto-checkoff machinery can detect references. Path-based markdown links break when files move to `archive/`; wiki-style ID links never do.
|
|
212
212
|
5. **At least one phase must contain at least one item.** An empty roadmap is a hard fail — loop back to Step 3 #5.
|
|
213
|
-
6. **Never invent task references.** If the user says "TASK-42" and no `042-*.md` file exists, render it as an inline placeholder, not a `[[TASK-
|
|
213
|
+
6. **Never invent task references.** If the user says "TASK-42" and no `042-*.md` file exists, render it as an inline placeholder, not a `[[TASK-NNNN: ...]]` wiki link.
|
|
214
214
|
|
|
215
215
|
---
|
|
216
216
|
|
|
217
217
|
## CRITICAL Rules
|
|
218
218
|
|
|
219
219
|
1. **Refuse to write the file if any required field is empty or fails its quality bar** (Goal, Owner, ≥1 phase with ≥1 item). Loop back to Step 3 — do not silently fill gaps with invented content.
|
|
220
|
-
2. **Never invent task links.** Every `[[TASK-
|
|
220
|
+
2. **Never invent task links.** Every `[[TASK-NNNN: ...]]` wiki link must correspond to a real file under `wiki/work/tasks/`. Verify with `mcp__serena__find_file` before rendering.
|
|
221
221
|
3. **Never use `sed`, `awk`, `echo >>`, or shell redirection to edit markdown.** Always `Read` then `Edit`. See `wiki/guides/mcp-tools.md`.
|
|
222
|
-
4. **Never auto-create downstream artifacts.** This skill creates exactly one roadmap file (plus the index row edit). Do **not** create tasks, PRDs, or ADRs as a side effect — the user can file tasks afterward via `/task-add --roadmap ROADMAP-
|
|
222
|
+
4. **Never auto-create downstream artifacts.** This skill creates exactly one roadmap file (plus the index row edit). Do **not** create tasks, PRDs, or ADRs as a side effect — the user can file tasks afterward via `/task-add --roadmap ROADMAP-NNNN`.
|
|
223
223
|
5. **Redirect step-level detail to task territory** — if the user starts specifying *how* under an item, restate the question as "what's the single checkable unit?" and re-elicit.
|
|
224
224
|
6. **Status starts as `active` and stays there.** This skill never writes `done`. The flip from `active` → `done` is a manual decision the human makes when every box is `[x]`. After flipping, the file may be moved to `wiki/work/roadmaps/archive/` — `/roadmap-next` will suggest this step.
|
|
@@ -20,7 +20,7 @@ Surface unchecked items in a single roadmap, grouped into parallelizable waves,
|
|
|
20
20
|
|
|
21
21
|
This skill operates on exactly one roadmap — it no longer scans across all roadmaps. If `$ARGUMENTS` is empty, **stop** and report:
|
|
22
22
|
|
|
23
|
-
> `/roadmap-next` requires a roadmap (path, `NNN-slug`, or number). Run `/roadmap-assess` to see a prioritized status update across all active roadmaps, then re-run `/roadmap-next <ROADMAP-
|
|
23
|
+
> `/roadmap-next` requires a roadmap (path, `NNN-slug`, or number). Run `/roadmap-assess` to see a prioritized status update across all active roadmaps, then re-run `/roadmap-next <ROADMAP-NNNN>` on the one you want to work.
|
|
24
24
|
|
|
25
25
|
## Step 1: Resolve the file (`find_file`/`list_dir`, never bash)
|
|
26
26
|
|
|
@@ -40,7 +40,7 @@ Run the three shared procedures below, in order, on the resolved file.
|
|
|
40
40
|
|
|
41
41
|
### Parse a roadmap
|
|
42
42
|
|
|
43
|
-
`Read` the file (markdown). Extract: **phases** (`## Phase N: <name>` in order), **items** (`- [ ]` unchecked / `- [x]` checked), **status** (`- **Status**: active | done`), and the `roadmap_id` (`- **ID**: ROADMAP-
|
|
43
|
+
`Read` the file (markdown). Extract: **phases** (`## Phase N: <name>` in order), **items** (`- [ ]` unchecked / `- [x]` checked), **status** (`- **Status**: active | done`), and the `roadmap_id` (`- **ID**: ROADMAP-NNNN` front matter — always read this first — or, as a fallback, the filename prefix, e.g. `ROADMAP-0013-billing.md` → `ROADMAP-0013`, or a legacy 3-digit file `ROADMAP-012-billing.md` → `ROADMAP-012`). Per item capture: `phase` (nearest preceding heading, or `(no phase)`), `checked`, `text`, `kind` (`task-link` if body starts `[[TASK-NNNN`, else `inline`), `task_id` (from `[[TASK-NNNN: title]]`), `task_path` (`find_file` `TASK-NNNN-*` in `wiki/work/tasks/` — matches active or archived). Compute `total`, `done`. Collect unchecked items into `candidate_items`, **capped at 9 total**.
|
|
44
44
|
|
|
45
45
|
For each `candidate_items` item that is already `kind == 'task-link'` (skip this for `inline` items until after they're upgraded below): `Read` `task_path`'s frontmatter and store `task_status` (`todo | in-progress | pending-uat | done | trashed`, per [tasks lifecycle](../tasks/lifecycle.md)). If `task_status == 'pending-uat'`, also resolve `uat_path` — read the task's `uat:` frontmatter field if present and `find_file` it; if empty or not found, leave `uat_path` unset (implementation finished but `/uat-generate` hasn't run yet).
|
|
46
46
|
|
|
@@ -49,27 +49,27 @@ For each `candidate_items` item that is already `kind == 'task-link'` (skip this
|
|
|
49
49
|
**All roadmap items must eventually be task files** — inline items are placeholders. For each `candidate_items` item with `kind == 'inline'`:
|
|
50
50
|
|
|
51
51
|
1. Announce: `Inline item found: "<text>"[ (in <roadmap_title>)] — checking for an existing task before creating one.`
|
|
52
|
-
2. **Check for an existing task:** `Read` `wiki/work/tasks/index.md`, scan its active-item bullets for one whose title/summary plausibly covers the intent; if likely, `Read` that task to confirm. Found → use its `TASK-
|
|
52
|
+
2. **Check for an existing task:** `Read` `wiki/work/tasks/index.md`, scan its active-item bullets for one whose title/summary plausibly covers the intent; if likely, `Read` that task to confirm. Found → use its `TASK-NNNN` + path, skip to step 5 (do **not** call `task-add`).
|
|
53
53
|
3. Else invoke `Skill` `task-add` with the item text as `args` (**no** `--roadmap` flag — the link is managed here to avoid a duplicate item).
|
|
54
|
-
4. Extract the new task path + ID from task-add's summary (`File path` row); if parsing fails, `list_dir` `wiki/work/tasks/` for the newest `.md` not present before, and `Read` it to confirm `TASK-
|
|
55
|
-
5. `Edit` the roadmap: `- [ ] <item_text>` → `- [ ] [[TASK-
|
|
54
|
+
4. Extract the new task path + ID from task-add's summary (`File path` row); if parsing fails, `list_dir` `wiki/work/tasks/` for the newest `.md` not present before, and `Read` it to confirm `TASK-NNNN` + title (from `# NNN: <title>`).
|
|
55
|
+
5. `Edit` the roadmap: `- [ ] <item_text>` → `- [ ] [[TASK-NNNN: <title>]]`.
|
|
56
56
|
6. Update the record: `kind='task-link'`, `task_id`, `task_path` (from `find_file`). A freshly created task is always `status: todo` — set `task_status = 'todo'` directly, no need to re-read the file.
|
|
57
57
|
|
|
58
58
|
If `task-add` fails/cancels, **stop and report**: `Task creation cancelled for: "<text>"[ (in <roadmap_title>)]. Inline items cannot be worked on without a task file. Re-run /roadmap-next after /task-add <description>.`
|
|
59
59
|
|
|
60
60
|
### Parallelism analysis → waves
|
|
61
61
|
|
|
62
|
-
After upgrades, for each item: `Read` its `task_path`, find `## Dependencies` / `## Blocked by`, extract `TASK-
|
|
62
|
+
After upgrades, for each item: `Read` its `task_path`, find `## Dependencies` / `## Blocked by`, extract `TASK-NNNN` refs; an **active blocker** is a dep whose `TASK-NNNN` also appears in `candidate_items`. Store as `blockers`. Topological sort: **Wave 1** = empty `blockers`; **Wave 2** = blockers all in Wave 1; **Wave 3** = blockers all in Wave 1∪2. Omit Wave 4+. **Cap each wave at 3 items** (document order); note overflow count. Store as `waves`.
|
|
63
63
|
|
|
64
64
|
### Archive a fully-complete roadmap (`total > 0` and `done == total`) — run automatically, no prompt
|
|
65
65
|
|
|
66
66
|
1. If `status: active`, `Edit` → `status: done`.
|
|
67
67
|
2. Remove its row from `wiki/work/roadmaps/index.md` (active-only index).
|
|
68
68
|
3. `git mv <roadmap_path> wiki/work/roadmaps/archive/<filename>` (Bash — `git mv` only).
|
|
69
|
-
4. Append to `wiki/work/roadmaps/archive/index.md`: `| [[ROADMAP-
|
|
69
|
+
4. Append to `wiki/work/roadmaps/archive/index.md`: `| [[ROADMAP-NNNN]] | <title> | done | YYYY-MM-DD |`.
|
|
70
70
|
5. Append to `wiki/log.md`:
|
|
71
71
|
```
|
|
72
|
-
## [YYYY-MM-DD] archive | <ROADMAP-
|
|
72
|
+
## [YYYY-MM-DD] archive | <ROADMAP-NNNN> — completed, moved to archive
|
|
73
73
|
All items checked. Moved to wiki/work/roadmaps/archive/<filename>.
|
|
74
74
|
```
|
|
75
75
|
|
|
@@ -86,7 +86,7 @@ After upgrades, for each item: `Read` its `task_path`, find `## Dependencies` /
|
|
|
86
86
|
**Wave 1** — ready now (run these in parallel):
|
|
87
87
|
| # | Phase | Item | Action |
|
|
88
88
|
|---|-------|------|--------|
|
|
89
|
-
| 1 | Phase N: name | TASK-
|
|
89
|
+
| 1 | Phase N: name | TASK-NNNN: item title | `/tackle <task_path>` |
|
|
90
90
|
|
|
91
91
|
**Wave 2** — start after Wave 1 completes: …
|
|
92
92
|
**Wave 3** — start after Wave 2 completes: …
|
|
@@ -100,7 +100,7 @@ After upgrades, for each item: `Read` its `task_path`, find `## Dependencies` /
|
|
|
100
100
|
- `pending-uat` with no `uat_path` → `` `/uat-generate <task_path>` `` — annotate the Item cell with a trailing `⏳ awaiting UAT (no tests yet)`
|
|
101
101
|
- `task_path` not found → `` `/tackle <task_path>` `` with ` (file not found)` appended, regardless of status (can't read a status that isn't there)
|
|
102
102
|
|
|
103
|
-
- **Zero items** → `Roadmap has no checklist items yet. Edit the roadmap file directly to add items, or link a new task to it with /task-add --roadmap <ROADMAP-
|
|
103
|
+
- **Zero items** → `Roadmap has no checklist items yet. Edit the roadmap file directly to add items, or link a new task to it with /task-add --roadmap <ROADMAP-NNNN> <description>.`
|
|
104
104
|
|
|
105
105
|
---
|
|
106
106
|
|
|
@@ -211,6 +211,8 @@ Huge inputs (malicious or not) exhaust token budgets, spike rate limits, and inf
|
|
|
211
211
|
|
|
212
212
|
## Reporting
|
|
213
213
|
|
|
214
|
+
**Output**: after compiling findings, write the full report to `.docs/security-audit/report-<YYYY-MM-DD>.md` using the **Write** tool (create the directory if it doesn't exist). If a report for today already exists, write `report-<YYYY-MM-DD>-2.md` (then `-3`, …) rather than overwriting — a persisted history is what makes check B4 ("benchmark results tracked over time") true instead of aspirational. Print the same report in the conversation as well; the file is a durable copy, not a replacement for the reply.
|
|
215
|
+
|
|
214
216
|
**Per-check status:** ✅ PASS (control exists & effective) · ⚠️ WARN (partial / has gaps) · ❌ FAIL (no evidence; vulnerable) · ℹ️ N/A (not applicable) · 🔍 NEEDS-REVIEW (can't determine from code — flag for manual review).
|
|
215
217
|
|
|
216
218
|
**Report structure:**
|
|
@@ -244,3 +246,4 @@ Categories audited: [list]
|
|
|
244
246
|
5. **Do not fix** — audit and report only; hand off fixes to the user or `/task-add`.
|
|
245
247
|
6. **Scope to the repo** — don't speculate about external infra unless config files are present.
|
|
246
248
|
7. **One category at a time** — complete each fully before the next; don't interleave findings.
|
|
249
|
+
8. **Persist the report** — write it to `.docs/security-audit/` (see Reporting) in addition to printing it; a report that only lives in the chat leaves no trail for the next audit to compare against.
|
|
@@ -47,14 +47,14 @@ Zero-click: find the first actionable roadmap item and tackle it, **no prompts**
|
|
|
47
47
|
### Task survey (empty OR unresolved)
|
|
48
48
|
|
|
49
49
|
Recommend from the index; **do not auto-pick**.
|
|
50
|
-
- **Read only `wiki/work/tasks/index.md`** (canonical active list: bullet lines `- [TASK-
|
|
50
|
+
- **Read only `wiki/work/tasks/index.md`** (canonical active list: bullet lines `- [TASK-NNNN — Title](TASK-NNNN-slug.md) — one-line summary · status`). Do NOT read individual task files, `grep`, `bash`, or aggregate across `wiki/work/tasks/` — the index exists to prevent exactly that. The only per-file read is the chosen task in Step 1.
|
|
51
51
|
- Missing `index.md` / no active-item bullets → STOP: `Task index at wiki/work/tasks/index.md is empty or missing. Add tasks with /task-add, or invoke /tackle <path-or-slug> directly.` Do not scan every file.
|
|
52
52
|
- `index.md` carries no progress columns — it lists title + one-line summary + `status` only, and `status` now directly distinguishes `todo` / `in-progress` / `pending-uat` (see [lifecycle](../tasks/lifecycle.md)) — no need to infer UAT-awaiting state from file existence. If a bullet points at a task file that no longer exists (moved/archived), note the drift in one sentence and skip it — don't pre-emptively fix the index.
|
|
53
53
|
- Empty active list → STOP: "No active tasks to tackle".
|
|
54
|
-
- Present the active items as a compact table (`TASK-
|
|
54
|
+
- Present the active items as a compact table (`TASK-NNNN` · title · status). Below it, a **Recommendation** ranking top 1–3 by priority, using `status` alone:
|
|
55
55
|
1. `status: in-progress` — finish what's started.
|
|
56
56
|
2. `status: todo`, lowest-numbered first.
|
|
57
|
-
- Tasks at `status: pending-uat` are excluded from recommendations and listed under `**Awaiting UAT**:` — `mcp__serena__list_dir` on `wiki/work/uat/` for the matching `UAT-
|
|
57
|
+
- Tasks at `status: pending-uat` are excluded from recommendations and listed under `**Awaiting UAT**:` — `mcp__serena__list_dir` on `wiki/work/uat/` for the matching `UAT-NNNN-*` file; if found, suggest `/uat-walk wiki/work/uat/UAT-NNNN-<slug>.md`; if none found (implementation finished but `/uat-generate` never ran), suggest `/uat-generate wiki/work/tasks/TASK-NNNN-<slug>.md` instead.
|
|
58
58
|
- Progress counts, `[BLOCKED]`/`[FAILED]` flags, and per-step state are **not** in `index.md` by design — they live in the task files. This no-args survey deliberately ranks on `status` + UAT presence alone rather than re-reading every task file; use `/task-audit` when the full progress/blocker picture is needed. (Design note: the survey was simplified to `index.md`'s real bullet schema rather than expanding `index.md` with Progress/UAT/Flags columns, which would violate the "active items only, flat list" convention in `wiki/conventions.md`.)
|
|
59
59
|
- Use `AskUserQuestion` (top rec first, labelled `(Recommended)`; up to 2 more; `header` = number-slug). If input was unresolved, prefix one line noting it. Do NOT proceed to Step 1 until the user chooses.
|
|
60
60
|
|
|
@@ -3,7 +3,7 @@ name: task-add
|
|
|
3
3
|
description: Create a structured, execution-ready task file in wiki/work/tasks/
|
|
4
4
|
category: planning
|
|
5
5
|
model: claude-sonnet-5
|
|
6
|
-
argument-hint: <task description> [--decision DEC-NNNN#DM] [--roadmap ROADMAP-
|
|
6
|
+
argument-hint: <task description> [--decision DEC-NNNN#DM] [--roadmap ROADMAP-NNNN]
|
|
7
7
|
disable-model-invocation: false
|
|
8
8
|
user-invocable: true
|
|
9
9
|
---
|
|
@@ -42,8 +42,8 @@ If no decision reference: skip this step entirely.
|
|
|
42
42
|
### Step 3: Parse and validate roadmap reference (only if `$ARGUMENTS` contains `--roadmap` or a `ROADMAP-` token)
|
|
43
43
|
|
|
44
44
|
Detect:
|
|
45
|
-
- `ROADMAP-
|
|
46
|
-
- `--roadmap ROADMAP-
|
|
45
|
+
- `ROADMAP-NNNN` — bare token
|
|
46
|
+
- `--roadmap ROADMAP-NNNN` or `--roadmap NNN` — flag form
|
|
47
47
|
|
|
48
48
|
Strip the roadmap token from `$ARGUMENTS`.
|
|
49
49
|
|
|
@@ -59,7 +59,7 @@ If no roadmap reference: skip this step entirely.
|
|
|
59
59
|
|
|
60
60
|
Scan **all** task locations to find the next available number:
|
|
61
61
|
- `mcp__serena__list_dir` on `wiki/work/tasks/` and `wiki/work/tasks/archive/` (skip either that doesn't exist).
|
|
62
|
-
- Collect every `TASK
|
|
62
|
+
- Collect every `TASK-<digits>` prefix from filenames across **both** directories. Take `max + 1`, zero-pad the result to 4 digits. In a brand-new project the first task is `TASK-0001`; in this repo, continue from the current max (do not restart at 1). Collect the numeric value from every `TASK-<digits>-` prefix regardless of digit count — existing tasks are 3-digit, new ones are 4-digit — ignoring leading zeros when comparing.
|
|
63
63
|
- Also scan `wiki/work/tasks/index.md` for any reserved IDs not yet on disk.
|
|
64
64
|
- Never re-use a number — IDs are immutable references, and archived tasks keep their original number forever (terminal tasks move to `archive/`; they don't stay in `wiki/work/tasks/`).
|
|
65
65
|
|
|
@@ -89,17 +89,17 @@ Confirm with the user via `AskUserQuestion`.
|
|
|
89
89
|
|
|
90
90
|
### Step 7a: Re-verify next task number — IMMEDIATELY before writing
|
|
91
91
|
|
|
92
|
-
Re-run the scan from Step 4. If the number planned in Step 7 is now taken, silently bump to the new next-available number. **Never call `Write` before completing this re-scan.**
|
|
92
|
+
Re-run the scan from Step 4, collecting the numeric value from every `TASK-<digits>-` prefix regardless of digit count and zero-padding the result to 4 digits. If the number planned in Step 7 is now taken, silently bump to the new next-available number. **Never call `Write` before completing this re-scan.**
|
|
93
93
|
|
|
94
94
|
### Step 8: Create the task file
|
|
95
95
|
|
|
96
|
-
Create `wiki/work/tasks/TASK-
|
|
96
|
+
Create `wiki/work/tasks/TASK-NNNN-slug.md` using the `Write` tool.
|
|
97
97
|
|
|
98
98
|
**Frontmatter** (required):
|
|
99
99
|
```yaml
|
|
100
100
|
---
|
|
101
|
-
id: TASK-
|
|
102
|
-
aliases: [TASK-
|
|
101
|
+
id: TASK-NNNN
|
|
102
|
+
aliases: [TASK-NNNN]
|
|
103
103
|
title: "<task title>"
|
|
104
104
|
status: todo
|
|
105
105
|
created: YYYY-MM-DD
|
|
@@ -112,16 +112,16 @@ tags: []
|
|
|
112
112
|
---
|
|
113
113
|
```
|
|
114
114
|
|
|
115
|
-
Populate `depends_on`, `blocks`, and `parallel_safe_with` from Step 5 as lists of `TASK-
|
|
115
|
+
Populate `depends_on`, `blocks`, and `parallel_safe_with` from Step 5 as lists of `TASK-NNNN` IDs (empty list if none).
|
|
116
116
|
|
|
117
117
|
**Body structure**:
|
|
118
118
|
|
|
119
119
|
```markdown
|
|
120
|
-
# TASK-
|
|
120
|
+
# TASK-NNNN — Task Title
|
|
121
121
|
|
|
122
122
|
implements::[[DEC-NNNN#DM]] ← only when a decision reference was provided
|
|
123
|
-
depends_on::[[TASK-
|
|
124
|
-
blocks::[[TASK-
|
|
123
|
+
depends_on::[[TASK-NNNN]] ← one line per dependency from Step 5; omit entirely if none
|
|
124
|
+
blocks::[[TASK-NNNN]] ← one line per blocked task from Step 5; omit entirely if none
|
|
125
125
|
|
|
126
126
|
## Objective
|
|
127
127
|
|
|
@@ -149,14 +149,14 @@ Agent type annotations: valid types are `general-purpose`, `Explore`, `Plan`.
|
|
|
149
149
|
|
|
150
150
|
**Decision link** (only when Step 2 found an accepted decision reference): Insert `implements::[[DEC-NNNN#DM]]` as a typed link on the line immediately after the H1, before `## Objective`.
|
|
151
151
|
|
|
152
|
-
**Dependency links** (from the Step 5 data, no re-derivation needed): insert one `depends_on::[[TASK-
|
|
152
|
+
**Dependency links** (from the Step 5 data, no re-derivation needed): insert one `depends_on::[[TASK-NNNN]]` line per dependency and one `blocks::[[TASK-NNNN]]` line per blocked task, in the same position — immediately after `implements::` when it's present, or immediately after the H1 when it isn't. *Aside: these typed-link lines are additive to the existing `> **Depends on**:`/`> **Blocks**:` blockquote format, not a replacement, and creating them here does not backfill any pre-existing task file.*
|
|
153
153
|
|
|
154
154
|
### Step 9: Update the family index
|
|
155
155
|
|
|
156
156
|
Append to `wiki/work/tasks/index.md`:
|
|
157
157
|
|
|
158
158
|
```
|
|
159
|
-
- [TASK-
|
|
159
|
+
- [TASK-NNNN — Title](TASK-NNNN-slug.md) — one-line objective · todo
|
|
160
160
|
```
|
|
161
161
|
|
|
162
162
|
If the file does not exist, create it with a `# Tasks` heading and the list entry. Insert in numeric order.
|
|
@@ -166,7 +166,7 @@ If the file does not exist, create it with a `# Tasks` heading and the list entr
|
|
|
166
166
|
In the decision's `### Links` section, add or append a `Source task(s):` line:
|
|
167
167
|
|
|
168
168
|
```
|
|
169
|
-
- Source task(s): [[TASK-
|
|
169
|
+
- Source task(s): [[TASK-NNNN]] — **WIP** (added YYYY-MM-DD)
|
|
170
170
|
```
|
|
171
171
|
|
|
172
172
|
If no `### Links` section exists, create one before the closing `---` separator of that decision block. Use `Read` then `Edit` — never shell redirection.
|
|
@@ -176,7 +176,7 @@ If no `### Links` section exists, create one before the closing `---` separator
|
|
|
176
176
|
Read the roadmap file. Identify the last `## Phase N:` section (or any checklist section). Append a new `- [ ]` line:
|
|
177
177
|
|
|
178
178
|
```
|
|
179
|
-
- [ ] [[TASK-
|
|
179
|
+
- [ ] [[TASK-NNNN: <task title>]]
|
|
180
180
|
```
|
|
181
181
|
|
|
182
182
|
Update the roadmap's `updated:` frontmatter field to today's date. Use `Read` then `Edit`.
|
|
@@ -186,8 +186,8 @@ Update the roadmap's `updated:` frontmatter field to today's date. Use `Read` th
|
|
|
186
186
|
Append:
|
|
187
187
|
|
|
188
188
|
```
|
|
189
|
-
## [YYYY-MM-DD] task | TASK-
|
|
190
|
-
Created task TASK-
|
|
189
|
+
## [YYYY-MM-DD] task | TASK-NNNN <task title>
|
|
190
|
+
Created task TASK-NNNN: <one sentence summarising the objective>.
|
|
191
191
|
```
|
|
192
192
|
|
|
193
193
|
### Step 13: Refresh the hot cache
|
|
@@ -197,14 +197,14 @@ The new task is durable, cross-session-relevant wiki state. Run the **Hot Cache
|
|
|
197
197
|
### Step 14: Confirm completion
|
|
198
198
|
|
|
199
199
|
Report:
|
|
200
|
-
- Created file: `wiki/work/tasks/TASK-
|
|
201
|
-
- Task ID: `TASK-
|
|
200
|
+
- Created file: `wiki/work/tasks/TASK-NNNN-slug.md`
|
|
201
|
+
- Task ID: `TASK-NNNN`
|
|
202
202
|
- Status: `todo`
|
|
203
203
|
- Next steps:
|
|
204
204
|
|
|
205
205
|
```
|
|
206
|
-
To implement: /tackle wiki/work/tasks/TASK-
|
|
207
|
-
To generate tests: /uat-generate TASK-
|
|
206
|
+
To implement: /tackle wiki/work/tasks/TASK-NNNN-slug.md
|
|
207
|
+
To generate tests: /uat-generate TASK-NNNN
|
|
208
208
|
```
|
|
209
209
|
|
|
210
210
|
If linked to a roadmap, mention which roadmap was updated and suggest:
|
|
@@ -25,7 +25,7 @@ Analyse all active tasks: verify implementation completeness, auto-check unannot
|
|
|
25
25
|
|
|
26
26
|
Read `wiki/work/tasks/index.md` using the `Read` tool.
|
|
27
27
|
|
|
28
|
-
- Parse every active-item bullet line — format `- [TASK-
|
|
28
|
+
- Parse every active-item bullet line — format `- [TASK-NNNN — Title](TASK-NNNN-slug.md) — one-line summary · status`. Extract the `TASK-NNNN` ID and the linked file path (e.g. `wiki/work/tasks/TASK-001-project-registry-push.md`) for each.
|
|
29
29
|
- `index.md` lists active items only and carries no progress or flags columns — those are computed from each task file in Step 2.
|
|
30
30
|
- If the list is empty, report "No active tasks — nothing to audit." and STOP.
|
|
31
31
|
|
|
@@ -84,7 +84,7 @@ In the same file read, locate the dependency blockquote appearing **immediately
|
|
|
84
84
|
- Links follow the pattern `[NNN-slug](NNN-slug.md)` — extract the NNN-slug identifier from each link.
|
|
85
85
|
- A task with no dependency block at all is treated as having `Depends on: none`, `Blocks: none`, `Parallel-safe with: none`.
|
|
86
86
|
|
|
87
|
-
Going forward, task files should also carry one `depends_on::[[TASK-
|
|
87
|
+
Going forward, task files should also carry one `depends_on::[[TASK-NNNN]]` line per dependency and one `blocks::[[TASK-NNNN]]` line per blocked task, directly below the blockquote — these are additive typed links for Obsidian/Breadcrumbs graph visualization. `/task-audit`'s own parser continues to read only the blockquote above, unchanged.
|
|
88
88
|
|
|
89
89
|
### 2f. Build the Node Record
|
|
90
90
|
|
|
@@ -70,7 +70,7 @@ If the user says **No**, STOP.
|
|
|
70
70
|
```
|
|
71
71
|
Then append to `wiki/work/tasks/archive/index.md`:
|
|
72
72
|
```
|
|
73
|
-
| [[TASK-
|
|
73
|
+
| [[TASK-NNNN]] | <Title> | trashed | YYYY-MM-DD |
|
|
74
74
|
```
|
|
75
75
|
|
|
76
76
|
3. **For each related UAT file** (if any):
|
|
@@ -81,7 +81,7 @@ If the user says **No**, STOP.
|
|
|
81
81
|
```
|
|
82
82
|
- Append to `wiki/work/uat/archive/index.md`:
|
|
83
83
|
```
|
|
84
|
-
| [[UAT-
|
|
84
|
+
| [[UAT-NNNN]] | <Title> | trashed | YYYY-MM-DD |
|
|
85
85
|
```
|
|
86
86
|
|
|
87
87
|
### Step 5: Update Active Indexes
|
|
@@ -90,14 +90,14 @@ Remove the task's row from `wiki/work/tasks/index.md`. If there is a matching UA
|
|
|
90
90
|
|
|
91
91
|
Use `Read` then `Edit` — never `echo >>` or `sed`. If a row is already absent, note it and continue.
|
|
92
92
|
|
|
93
|
-
**Do NOT remove references from roadmaps, decisions, or other files** — `[[TASK-
|
|
93
|
+
**Do NOT remove references from roadmaps, decisions, or other files** — `[[TASK-NNNN]]` and `[[UAT-NNNN]]` IDs remain valid regardless of file location.
|
|
94
94
|
|
|
95
95
|
### Step 6: Append to wiki/log.md
|
|
96
96
|
|
|
97
97
|
Append one entry to `wiki/log.md`:
|
|
98
98
|
|
|
99
99
|
```
|
|
100
|
-
## [YYYY-MM-DD] task-trashed | TASK-
|
|
100
|
+
## [YYYY-MM-DD] task-trashed | TASK-NNNN <title> — archived to wiki/work/tasks/archive/
|
|
101
101
|
```
|
|
102
102
|
|
|
103
103
|
Use `Read` then `Edit` — never `echo >>`.
|