@codewizard-dt/bootstrap 5.1.0 → 6.0.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 +11 -3
- package/bin/cli.js +16 -0
- package/lib/hooks/README.md +124 -3
- package/lib/hooks/claude-settings-guard.js +8 -2
- package/lib/prompts/README.md +1 -1
- package/lib/prompts/migrate-wiki.md +7 -7
- package/lib/scripts/README.md +111 -10
- package/lib/scripts/bootstrap-prefs-tui.js +1222 -0
- package/lib/scripts/install-global.sh +137 -6
- package/lib/scripts/migrate-project.sh +52 -10
- package/lib/scripts/rename-wiki-ids.js +232 -0
- package/lib/scripts/templates/CLAUDE-wiki.md +6 -6
- package/lib/scripts/templates/bootstrap-prefs-schema.json +11 -2
- package/lib/scripts/templates/settings-sandbox-unattended.json +36 -0
- package/lib/scripts/templates/settings-sandbox.json +7 -0
- package/lib/scripts/templates/wiki/conventions.md +12 -10
- package/lib/scripts/templates/wiki/dashboard.html +527 -23
- package/lib/scripts/templates/wiki/index.md +2 -2
- package/lib/scripts/templates/wiki/work/bugs/lifecycle.md +1 -1
- package/lib/scripts/templates/wiki/work/decisions/index.md +12 -4
- package/lib/scripts/templates/wiki/work/decisions/lifecycle.md +11 -9
- package/lib/scripts/templates/wiki/work/requirements/index.md +12 -4
- package/lib/scripts/templates/wiki/work/requirements/lifecycle.md +8 -8
- package/lib/scripts/templates/wiki/work/roadmaps/index.md +11 -3
- package/lib/scripts/templates/wiki/work/roadmaps/lifecycle.md +7 -5
- package/lib/scripts/templates/wiki/work/tasks/index.md +1 -1
- package/lib/scripts/templates/wiki/work/tasks/lifecycle.md +16 -8
- package/lib/scripts/templates/wiki/work/uat/lifecycle.md +3 -3
- package/lib/scripts/wiki-dashboard-server.js +98 -0
- package/lib/skills/README.md +27 -22
- package/lib/skills/_shared/ARCHIVE-WORK-ITEM.md +103 -0
- package/lib/skills/_shared/ID-RESOLUTION.md +142 -0
- package/lib/skills/_shared/SKILL-BOILERPLATE.md +50 -0
- package/lib/skills/adr-assess/SKILL.md +112 -0
- package/lib/skills/{decision-create → adr-create}/SKILL.md +27 -26
- package/lib/skills/adr-deprecate/SKILL.md +190 -0
- package/lib/skills/adr-extract/SKILL.md +255 -0
- package/lib/skills/{decision-finalize → adr-finalize}/SKILL.md +38 -38
- package/lib/skills/{decision-next → adr-next}/SKILL.md +20 -19
- package/lib/skills/{decision-walkthrough → adr-walkthrough}/SKILL.md +23 -29
- package/lib/skills/architecture-audit/SKILL.md +24 -3
- package/lib/skills/autopilot/SKILL.md +110 -0
- package/lib/skills/bootstrap-config/SKILL.md +1 -1
- package/lib/skills/bug-assess/SKILL.md +3 -3
- package/lib/skills/bug-close/SKILL.md +15 -26
- package/lib/skills/{bug-file → bug-create}/SKILL.md +25 -15
- package/lib/skills/bug-triage/SKILL.md +5 -19
- package/lib/skills/demo/SKILL.md +11 -11
- package/lib/skills/elevator-pitch/SKILL.md +1 -1
- package/lib/skills/extract-feature/SKILL.md +29 -87
- package/lib/skills/git-commit/SKILL.md +4 -4
- package/lib/skills/marp-slideshow/SKILL.md +2 -2
- package/lib/skills/port-feature/SKILL.md +28 -83
- package/lib/skills/power-mode/SKILL.md +42 -49
- package/lib/skills/prd-assess/SKILL.md +105 -0
- package/lib/skills/{req-compile → prd-compile}/SKILL.md +6 -13
- package/lib/skills/{req-create → prd-create}/SKILL.md +19 -19
- package/lib/skills/prd-deprecate/SKILL.md +173 -0
- package/lib/skills/{req-finalize → prd-finalize}/SKILL.md +20 -29
- package/lib/skills/primer/SKILL.md +2 -2
- package/lib/skills/research/SKILL.md +3 -3
- package/lib/skills/roadmap-assess/SKILL.md +20 -20
- package/lib/skills/roadmap-create/SKILL.md +23 -29
- package/lib/skills/roadmap-next/SKILL.md +16 -28
- package/lib/skills/security-audit/SKILL.md +3 -3
- package/lib/skills/tackle/SKILL.md +13 -15
- package/lib/skills/{task-audit → task-assess}/SKILL.md +34 -44
- package/lib/skills/task-close/SKILL.md +73 -0
- package/lib/skills/{task-add → task-create}/SKILL.md +44 -24
- package/lib/skills/uat-assess/SKILL.md +124 -0
- package/lib/skills/uat-auto/SKILL.md +9 -6
- package/lib/skills/uat-auto-plus/SKILL.md +2 -2
- package/lib/skills/{uat-generate → uat-create}/SKILL.md +10 -12
- package/lib/skills/uat-skip/SKILL.md +5 -9
- package/lib/skills/uat-walk/SKILL.md +2 -2
- package/lib/skills/uat-walk/UAT-CORE.md +29 -16
- package/lib/skills/update-docs/SKILL.md +1 -1
- package/lib/skills/usage-report/SKILL.md +52 -0
- package/lib/skills/usage-report/scripts/pricing.json +22 -0
- package/lib/skills/usage-report/scripts/usage-report.js +518 -0
- package/lib/skills/whats-next/SKILL.md +177 -0
- package/lib/skills/wiki-archive/SKILL.md +12 -23
- package/lib/skills/wiki-lint/SKILL.md +42 -5
- package/lib/skills/wiki-query/SKILL.md +1 -1
- package/lib/skills/wiki-rotate-log/SKILL.md +1 -1
- package/lib/skills/wiki-tidy/SKILL.md +6 -9
- package/package.json +1 -1
- package/lib/scripts/templates/wiki/work/decisions/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/requirements/archive/index.md +0 -10
- package/lib/scripts/templates/wiki/work/roadmaps/archive/index.md +0 -10
- package/lib/skills/req-extract-decisions/SKILL.md +0 -241
- package/lib/skills/req-retire/SKILL.md +0 -185
- package/lib/skills/req-update/SKILL.md +0 -265
- package/lib/skills/task-trash/SKILL.md +0 -115
- package/lib/skills/task-update/SKILL.md +0 -136
|
@@ -1,265 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: req-update
|
|
3
|
-
description: Amend an approved requirement with a tracked Amendment block (append-only); apply direct edits to drafts; set retired/superseded status; surface downstream decision/task impact
|
|
4
|
-
category: planning
|
|
5
|
-
model: claude-sonnet-5
|
|
6
|
-
argument-hint: <path/to/req.md, NNN-slug, or NNN> [optional change description]
|
|
7
|
-
disable-model-invocation: false
|
|
8
|
-
user-invocable: true
|
|
9
|
-
---
|
|
10
|
-
**Prereqs:** obey `wiki/guides/mcp-tools.md`; run /primer if not done this session.
|
|
11
|
-
|
|
12
|
-
# Update Requirement
|
|
13
|
-
|
|
14
|
-
Amend an existing requirement with a change. The mechanics depend on the requirement's status:
|
|
15
|
-
|
|
16
|
-
| Requirement Status | Behavior |
|
|
17
|
-
|--------------------|----------|
|
|
18
|
-
| `draft` | Apply edits directly in place — drafts are mutable |
|
|
19
|
-
| `approved` | Append an `## Amendment N` block; insert surgical `[amended N]` markers in affected sections; **never rewrite original prose** |
|
|
20
|
-
| `approved` (retiring) | Set `status: retired`, append reason to `## Notes`, update wiki index, append log entry — use `/req-retire` for a dedicated retirement flow |
|
|
21
|
-
| `retired` / `superseded` | Refuse general amendments — these requirements are no longer authoritative; suggest `/req-create` for new scope |
|
|
22
|
-
|
|
23
|
-
**Approved requirements are immutable in substance.** The amendment block is the audit trail. Original sections stay readable in their original form; markers point readers to the amendment that updated them. Amendments are themselves immutable once written — never edit a prior amendment block; append a new one.
|
|
24
|
-
|
|
25
|
-
**Check `wiki/work/requirements/lifecycle.md` first.** It defines the requirement format and status lifecycle; the `## Amendments` convention and the "Amendment Avoidance" anti-pattern this skill exists to prevent live there and in recent REQ files.
|
|
26
|
-
|
|
27
|
-
---
|
|
28
|
-
|
|
29
|
-
**Input**: $ARGUMENTS
|
|
30
|
-
|
|
31
|
-
---
|
|
32
|
-
|
|
33
|
-
## Step 1: Resolve the requirement file and parse change instructions
|
|
34
|
-
|
|
35
|
-
Parse `$ARGUMENTS`:
|
|
36
|
-
- **First token** — the file reference: `<path>`, `<NNN-slug>`, or `<NNN>`
|
|
37
|
-
- **Remaining text** — free-form change instructions describing what the user wants to amend
|
|
38
|
-
|
|
39
|
-
Resolution table:
|
|
40
|
-
|
|
41
|
-
| Input form | Resolution |
|
|
42
|
-
|------------|------------|
|
|
43
|
-
| `<path>` (e.g. `wiki/work/requirements/REQ-003-billing-portal.md`) | Use as-is |
|
|
44
|
-
| `<NNN-slug>` (e.g. `003-billing-portal`) | Search `wiki/work/requirements/` for `<NNN-slug>.md` (Serena `find_file`) |
|
|
45
|
-
| `<NNN>` (e.g. `3` or `003`) | Pad to 3 digits; search `wiki/work/requirements/` for files starting with that number; if ambiguous, list matches and ask the user via `AskUserQuestion` |
|
|
46
|
-
| Empty | List every requirement in `wiki/work/requirements/` and ask the user via `AskUserQuestion` to pick |
|
|
47
|
-
|
|
48
|
-
If the file cannot be located, **stop** and report — do not invent or create.
|
|
49
|
-
|
|
50
|
-
If the **change instructions are empty**, use `AskUserQuestion` to elicit them before proceeding. A `/req-update` invocation without a described change is malformed.
|
|
51
|
-
|
|
52
|
-
---
|
|
53
|
-
|
|
54
|
-
## Step 2: Read the requirement and check status
|
|
55
|
-
|
|
56
|
-
1. **Read** the requirement file with `Read`.
|
|
57
|
-
2. **Locate the `status:` field** in the YAML frontmatter.
|
|
58
|
-
3. **Branch on status:**
|
|
59
|
-
|
|
60
|
-
| Status | Action |
|
|
61
|
-
|--------|--------|
|
|
62
|
-
| `draft` | Continue to Step 3 (you will take the **direct-edit branch** in Step 4) |
|
|
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-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
|
-
|
|
67
|
-
**Retiring branch** (when the user indicates they want to mark the requirement as retired):
|
|
68
|
-
1. Ask for the retirement reason via `AskUserQuestion`
|
|
69
|
-
2. Set `status: retired` in frontmatter
|
|
70
|
-
3. Append reason to `## Notes` section: *"Retired YYYY-MM-DD: <reason>"*
|
|
71
|
-
4. Update `updated` in frontmatter to today's date
|
|
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-NNNN <title> — <reason>`
|
|
74
|
-
7. Skip to Step 10 (report)
|
|
75
|
-
|
|
76
|
-
---
|
|
77
|
-
|
|
78
|
-
## Step 3: Determine change scope and impact
|
|
79
|
-
|
|
80
|
-
Before any edit is applied, fully characterize the change. Use `AskUserQuestion` to gather (in this order):
|
|
81
|
-
|
|
82
|
-
1. **Affected sections** — which requirement sections does this change touch?
|
|
83
|
-
|
|
84
|
-
| Candidate section | Typical reason for amendment |
|
|
85
|
-
|-------------------|------------------------------|
|
|
86
|
-
| Problem Statement | New evidence reframes the problem |
|
|
87
|
-
| Goals | A goal added, removed, or rephrased |
|
|
88
|
-
| Non-Goals | Scope tightened or loosened |
|
|
89
|
-
| Personas | New persona discovered or one removed |
|
|
90
|
-
| User Stories | Story added, removed, or acceptance criteria changed |
|
|
91
|
-
| Success Metrics | Threshold or signal updated |
|
|
92
|
-
| Constraints | New regulatory or business constraint |
|
|
93
|
-
| Assumptions | Assumption invalidated |
|
|
94
|
-
| Open Questions | Resolution arrived |
|
|
95
|
-
| stakeholders | Reviewer set changed |
|
|
96
|
-
|
|
97
|
-
2. **Reason category** — pick one:
|
|
98
|
-
|
|
99
|
-
| Category | When applicable |
|
|
100
|
-
|----------|-----------------|
|
|
101
|
-
| `new evidence` | User research, support tickets, or analytics changed the picture |
|
|
102
|
-
| `scope clarification` | Original wording was ambiguous; this nails it down |
|
|
103
|
-
| `stakeholder request` | A named stakeholder asked for the change |
|
|
104
|
-
| `external constraint` | Legal, compliance, vendor change |
|
|
105
|
-
| `discovered ambiguity` | Implementation revealed an unanswered question |
|
|
106
|
-
|
|
107
|
-
3. **Downstream impact** — read the requirement's `## Linked Decisions` and `## Linked Tasks` tables.
|
|
108
|
-
- **If linked decisions exist:** list them and ask whether the change might invalidate any decision
|
|
109
|
-
- **If linked tasks exist:** list them and ask whether the change affects their scope
|
|
110
|
-
- If neither table has rows, skip — but still surface "no downstream artifacts" in the Step 10 report
|
|
111
|
-
|
|
112
|
-
---
|
|
113
|
-
|
|
114
|
-
## Step 4: Branch on status
|
|
115
|
-
|
|
116
|
-
### Branch A — `draft` requirement (direct-edit, mutable)
|
|
117
|
-
|
|
118
|
-
1. **Apply each distinct change with one `Edit` call.** Never bulk-rewrite.
|
|
119
|
-
2. **Update `updated`** in frontmatter to today's date.
|
|
120
|
-
3. If the change involves **adding or removing user stories, success metrics, or non-goals**, surface a one-line reminder: *"This requirement is still `draft`. When you're ready to approve, run `/req-finalize <path>` to re-audit completeness."*
|
|
121
|
-
4. **Skip Steps 5–8.** Proceed directly to Step 9 (downstream impact) and Step 10 (report).
|
|
122
|
-
|
|
123
|
-
### Branch B — `approved` requirement (amendment-only, append-only)
|
|
124
|
-
|
|
125
|
-
Approved requirements are immutable in substance. The original sections are not rewritten; instead:
|
|
126
|
-
|
|
127
|
-
- A new `## Amendment N` block is appended under the file's `## Amendments` heading
|
|
128
|
-
- Surgical `[amended N]` markers are inserted in the affected sections pointing to the amendment block
|
|
129
|
-
- The original prose stays readable in its original form
|
|
130
|
-
|
|
131
|
-
Determine **N**:
|
|
132
|
-
|
|
133
|
-
1. Scan the requirement for existing `## Amendment N` H2 blocks
|
|
134
|
-
2. `N` = (highest existing amendment number) + 1, or `1` if none exist
|
|
135
|
-
|
|
136
|
-
Continue to Step 5.
|
|
137
|
-
|
|
138
|
-
---
|
|
139
|
-
|
|
140
|
-
## Step 5: Compose the amendment block (approved-requirement branch only)
|
|
141
|
-
|
|
142
|
-
Draft the amendment block in your working context. Format:
|
|
143
|
-
|
|
144
|
-
```markdown
|
|
145
|
-
## Amendment N (YYYY-MM-DD)
|
|
146
|
-
|
|
147
|
-
- **Reason**: <reason category from Step 3>
|
|
148
|
-
- **Affected sections**: <comma-separated list from Step 3>
|
|
149
|
-
- **Stakeholders consulted**: <names or roles>
|
|
150
|
-
- **Downstream impact**: <decision/task IDs that may need review, or "none">
|
|
151
|
-
|
|
152
|
-
### Changes
|
|
153
|
-
|
|
154
|
-
| Section | Before (summary) | After (summary) | Rationale |
|
|
155
|
-
|---------|------------------|-----------------|-----------|
|
|
156
|
-
| Problem Statement | <one-line summary of original> | <one-line summary of amended> | <why> |
|
|
157
|
-
|
|
158
|
-
### Detailed Diff (optional)
|
|
159
|
-
|
|
160
|
-
<Free-form prose for the substance of the change.>
|
|
161
|
-
```
|
|
162
|
-
|
|
163
|
-
Rules:
|
|
164
|
-
- One row in the `### Changes` table per affected section
|
|
165
|
-
- `### Detailed Diff` is optional but recommended when the substance is non-trivial
|
|
166
|
-
- Use today's date in the H2
|
|
167
|
-
|
|
168
|
-
**Confirm the amendment-block content with the user via `AskUserQuestion` before writing.** Amendments are append-only and themselves immutable.
|
|
169
|
-
|
|
170
|
-
---
|
|
171
|
-
|
|
172
|
-
## Step 6: Apply surgical `[amended N]` markers (approved-requirement branch only)
|
|
173
|
-
|
|
174
|
-
For each affected section in the original requirement body, insert an inline marker pointing to the new amendment. **Do not rewrite the original prose.**
|
|
175
|
-
|
|
176
|
-
Marker patterns by section type:
|
|
177
|
-
|
|
178
|
-
| Section type | Marker pattern |
|
|
179
|
-
|--------------|----------------|
|
|
180
|
-
| Table row | Append `[amended N — see below]` to the relevant cell |
|
|
181
|
-
| Prose paragraph | Append `_(See [Amendment N](#amendment-N-yyyy-mm-dd).)_` at end of paragraph |
|
|
182
|
-
| Bulleted/numbered list item | Append `[amended N]` to the line |
|
|
183
|
-
|
|
184
|
-
Apply each marker with one `Edit` call. Use unique surrounding text in `old_string`.
|
|
185
|
-
|
|
186
|
-
---
|
|
187
|
-
|
|
188
|
-
## Step 7: Append the amendment block to the file (approved-requirement branch only)
|
|
189
|
-
|
|
190
|
-
1. **Read** the file again (state may have changed after Step 6's edits).
|
|
191
|
-
2. **Locate the `## Amendments` heading.**
|
|
192
|
-
- If the file still has the placeholder comment, append the new block beneath the comment
|
|
193
|
-
- If previous amendments exist, append the new block after the last existing `## Amendment` block
|
|
194
|
-
3. **Use `Edit`** to insert the block.
|
|
195
|
-
4. **Never** use `sed`, `echo >>`, `cat <<EOF`, or `Write` for a full-file rewrite. Only `Edit`.
|
|
196
|
-
|
|
197
|
-
---
|
|
198
|
-
|
|
199
|
-
## Step 8: Update `updated` and the wiki index
|
|
200
|
-
|
|
201
|
-
1. **Update the requirement's `updated` field** in frontmatter to today's date via `Edit`.
|
|
202
|
-
2. **Edit `wiki/work/requirements/index.md`** only if amendment-relevant columns changed (Title, Owner). Typically the index row stays stable for amendments.
|
|
203
|
-
|
|
204
|
-
Append to `wiki/log.md`:
|
|
205
|
-
|
|
206
|
-
```
|
|
207
|
-
## [YYYY-MM-DD] req-updated | REQ-NNNN <title> — Amendment N
|
|
208
|
-
```
|
|
209
|
-
|
|
210
|
-
---
|
|
211
|
-
|
|
212
|
-
## Step 9: Surface downstream impact
|
|
213
|
-
|
|
214
|
-
Print a tabular report listing every linked decision and linked task that might need review:
|
|
215
|
-
|
|
216
|
-
| Artifact | Type | Status | Suggested Action |
|
|
217
|
-
|----------|------|--------|------------------|
|
|
218
|
-
| `DEC-0007#D2` | linked decision | accepted | Review whether amendment invalidates the decision; if so, write a successor via `/decision-create` |
|
|
219
|
-
| `wiki/work/tasks/TASK-004-billing-checkout.md` | linked task | in-progress | Review whether amendment changes the task scope; if so, run `/task-update ...` |
|
|
220
|
-
|
|
221
|
-
If there are no linked artifacts, print: *"No downstream decisions or tasks linked. No further action."*
|
|
222
|
-
|
|
223
|
-
This skill **does not auto-update or auto-deprecate** downstream artifacts.
|
|
224
|
-
|
|
225
|
-
---
|
|
226
|
-
|
|
227
|
-
## Step 10: Report completion
|
|
228
|
-
|
|
229
|
-
Print a single tabular summary:
|
|
230
|
-
|
|
231
|
-
| Field | Value |
|
|
232
|
-
|-------|-------|
|
|
233
|
-
| File | `<path>` |
|
|
234
|
-
| Branch taken | `direct-edit (draft)`, `amendment (approved)`, or `retired` |
|
|
235
|
-
| Amendment number | `N` (or `—` for direct-edit/retired) |
|
|
236
|
-
| `[amended N]` markers added | count (or `—`) |
|
|
237
|
-
| Sections touched | comma-separated list |
|
|
238
|
-
| Downstream artifacts flagged | count |
|
|
239
|
-
| Log entry | appended to wiki/log.md |
|
|
240
|
-
| Suggested next steps | `/req-finalize ...` (drafts), `/task-update ...`, `/decision-create ...`, etc. |
|
|
241
|
-
|
|
242
|
-
---
|
|
243
|
-
|
|
244
|
-
## Output Formatting Rules (mandatory)
|
|
245
|
-
|
|
246
|
-
1. **Tables not bullets** — the amendment block's `### Changes` section, the downstream-impact report, and the completion summary are all tables
|
|
247
|
-
2. **Approved requirements are append-only in substance** — original sections must remain readable; markers point to amendments, they do not replace text
|
|
248
|
-
3. **Surgical `Edit` calls** — one `Edit` per distinct change; never bulk rewrites
|
|
249
|
-
4. **Never use `sed`, `echo >>`, `cat <<EOF`** — always `Edit`
|
|
250
|
-
5. **Amendments are themselves immutable** once written — never edit a prior `## Amendment N` block
|
|
251
|
-
6. **Refuse general amendments on `retired` / `superseded` status** — suggest `/req-create` for new scope
|
|
252
|
-
7. **Confirm amendment-block content** with the user via `AskUserQuestion` before writing
|
|
253
|
-
|
|
254
|
-
---
|
|
255
|
-
|
|
256
|
-
## CRITICAL Rules
|
|
257
|
-
|
|
258
|
-
1. **Approved requirements are immutable in substance** — appending amendments is the ONLY allowed change
|
|
259
|
-
2. **Original prose stays visible** — `[amended N]` markers point to amendments; they do not replace the original content
|
|
260
|
-
3. **Amendment blocks are themselves append-only** — never edit a prior amendment block
|
|
261
|
-
4. **Refuse on terminal statuses** (`retired`, `superseded`) — suggest `/req-create` for new scope
|
|
262
|
-
5. **Never auto-update downstream artifacts** — surface linked decisions and tasks for user review
|
|
263
|
-
6. **Never use `sed`/`echo >>`/`cat <<EOF`** — always `Edit`
|
|
264
|
-
7. **Maximum 3 sub-processes at a time** if delegating
|
|
265
|
-
8. **Always terminate processes when done**
|
|
@@ -1,115 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: task-trash
|
|
3
|
-
description: Trash a task and its related UAT files — moves them to archive/ and removes all active-index references
|
|
4
|
-
category: planning
|
|
5
|
-
model: claude-haiku-4-5-20251001
|
|
6
|
-
argument-hint: <path/to/task-file.md>
|
|
7
|
-
disable-model-invocation: false
|
|
8
|
-
user-invocable: true
|
|
9
|
-
---
|
|
10
|
-
**Prereqs:** obey `wiki/guides/mcp-tools.md` + `wiki/work/tasks/lifecycle.md`; run /primer if not done this session.
|
|
11
|
-
|
|
12
|
-
# Trash Task
|
|
13
|
-
|
|
14
|
-
Move a task file (and any related UAT files) to `archive/`, then remove all active-index references. No files are ever deleted — archiving is the terminal action.
|
|
15
|
-
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
**Task File**: $ARGUMENTS
|
|
19
|
-
|
|
20
|
-
---
|
|
21
|
-
|
|
22
|
-
## Instructions
|
|
23
|
-
|
|
24
|
-
### Step 1: Resolve the Task File
|
|
25
|
-
|
|
26
|
-
Parse `$ARGUMENTS` to locate the task file:
|
|
27
|
-
|
|
28
|
-
1. **If a file path is provided** (e.g., `wiki/work/tasks/3-user-auth.md`):
|
|
29
|
-
- Confirm the file exists (use Serena `find_file` or `list_dir`)
|
|
30
|
-
- If the file does not exist, STOP and report the error
|
|
31
|
-
|
|
32
|
-
2. **If a number-slug is provided** (e.g., `3-user-auth`):
|
|
33
|
-
- Search `wiki/work/tasks/` for `<number-slug>.md`
|
|
34
|
-
- If not found, check `wiki/work/tasks/archive/`
|
|
35
|
-
- If still not found, STOP and report the error
|
|
36
|
-
|
|
37
|
-
3. **If only a description or number is provided** (e.g., `user auth` or `3`):
|
|
38
|
-
- Search `wiki/work/tasks/` and `wiki/work/tasks/archive/` for a matching task file
|
|
39
|
-
- If ambiguous, list matches and ask the user to clarify
|
|
40
|
-
- If no match found, STOP and report the error
|
|
41
|
-
|
|
42
|
-
4. Determine which directory the task currently lives in (`wiki/work/tasks/` or `wiki/work/tasks/archive/`)
|
|
43
|
-
5. Extract the task's **number-slug identifier** (e.g., `3-user-auth` from `3-user-auth.md`)
|
|
44
|
-
|
|
45
|
-
### Step 2: Find Related UAT Files
|
|
46
|
-
|
|
47
|
-
Using the task's number-slug identifier, search for matching UAT files:
|
|
48
|
-
|
|
49
|
-
1. Check `wiki/work/uat/` for `<number>-<slug>.uat.md`
|
|
50
|
-
2. Check `wiki/work/uat/archive/` for `<number>-<slug>.uat.md`
|
|
51
|
-
3. Collect all matches — there may be zero, one, or multiple related UAT files
|
|
52
|
-
|
|
53
|
-
### Step 3: Confirm with the User
|
|
54
|
-
|
|
55
|
-
Before moving anything, use `AskUserQuestion` to confirm. Show:
|
|
56
|
-
|
|
57
|
-
- **Task file** to be trashed: `$ARGUMENTS`
|
|
58
|
-
- **UAT file(s)** to be trashed (list each, or "None found")
|
|
59
|
-
- Ask: **"Archive these files as trashed? (Yes/No)"**
|
|
60
|
-
|
|
61
|
-
If the user says **No**, STOP.
|
|
62
|
-
|
|
63
|
-
### Step 4: Set status and archive files
|
|
64
|
-
|
|
65
|
-
1. **Update `status: <current>` → `status: trashed`** in the task file frontmatter using `Edit`.
|
|
66
|
-
|
|
67
|
-
2. **Archive the task file** (Bash — `git mv` only):
|
|
68
|
-
```
|
|
69
|
-
git mv wiki/work/tasks/<file>.md wiki/work/tasks/archive/<file>.md
|
|
70
|
-
```
|
|
71
|
-
Then append to `wiki/work/tasks/archive/index.md`:
|
|
72
|
-
```
|
|
73
|
-
| [[TASK-NNNN]] | <Title> | trashed | YYYY-MM-DD |
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
3. **For each related UAT file** (if any):
|
|
77
|
-
- Update `status: <current>` → `status: trashed` in UAT frontmatter using `Edit`.
|
|
78
|
-
- Archive it (Bash — `git mv` only):
|
|
79
|
-
```
|
|
80
|
-
git mv wiki/work/uat/<UAT-file>.md wiki/work/uat/archive/<UAT-file>.md
|
|
81
|
-
```
|
|
82
|
-
- Append to `wiki/work/uat/archive/index.md`:
|
|
83
|
-
```
|
|
84
|
-
| [[UAT-NNNN]] | <Title> | trashed | YYYY-MM-DD |
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
### Step 5: Update Active Indexes
|
|
88
|
-
|
|
89
|
-
Remove the task's row from `wiki/work/tasks/index.md`. If there is a matching UAT row in `wiki/work/uat/index.md`, remove it too.
|
|
90
|
-
|
|
91
|
-
Use `Read` then `Edit` — never `echo >>` or `sed`. If a row is already absent, note it and continue.
|
|
92
|
-
|
|
93
|
-
**Do NOT remove references from roadmaps, decisions, or other files** — `[[TASK-NNNN]]` and `[[UAT-NNNN]]` IDs remain valid regardless of file location.
|
|
94
|
-
|
|
95
|
-
### Step 6: Append to wiki/log.md
|
|
96
|
-
|
|
97
|
-
Append one entry to `wiki/log.md`:
|
|
98
|
-
|
|
99
|
-
```
|
|
100
|
-
## [YYYY-MM-DD] task-trashed | TASK-NNNN <title> — archived to wiki/work/tasks/archive/
|
|
101
|
-
```
|
|
102
|
-
|
|
103
|
-
Use `Read` then `Edit` — never `echo >>`.
|
|
104
|
-
|
|
105
|
-
### Step 7: Report Completion
|
|
106
|
-
|
|
107
|
-
Report what was done:
|
|
108
|
-
|
|
109
|
-
| Field | Value |
|
|
110
|
-
|-------|-------|
|
|
111
|
-
| Task file | `wiki/work/tasks/<file>.md` → `wiki/work/tasks/archive/<file>.md` |
|
|
112
|
-
| UAT file(s) | `wiki/work/uat/<file>.md` → `wiki/work/uat/archive/<file>.md` (or "None") |
|
|
113
|
-
| Active index rows removed | task index, UAT index (as applicable) |
|
|
114
|
-
| Archive index rows added | task archive index, UAT archive index (as applicable) |
|
|
115
|
-
| wiki/log.md entry | yes |
|
|
@@ -1,136 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: task-update
|
|
3
|
-
description: Assess and modify an existing task's scope or steps
|
|
4
|
-
category: planning
|
|
5
|
-
model: claude-sonnet-5
|
|
6
|
-
argument-hint: <path/to/task.md, number-slug, or number> [optional instructions]
|
|
7
|
-
disable-model-invocation: false
|
|
8
|
-
user-invocable: true
|
|
9
|
-
---
|
|
10
|
-
**Prereqs:** obey `wiki/guides/mcp-tools.md` + `wiki/work/tasks/lifecycle.md`; run /primer if not done this session.
|
|
11
|
-
|
|
12
|
-
# Update Task
|
|
13
|
-
|
|
14
|
-
Assess an existing task file against the task spec and update it until it is execution-ready for `/tackle`.
|
|
15
|
-
|
|
16
|
-
---
|
|
17
|
-
|
|
18
|
-
**Input**: $ARGUMENTS
|
|
19
|
-
|
|
20
|
-
---
|
|
21
|
-
|
|
22
|
-
## Step 1: Resolve the Task File
|
|
23
|
-
|
|
24
|
-
Parse the first part of `$ARGUMENTS` to locate the task file. Any remaining text after the file reference is treated as **user instructions** for how to update the task.
|
|
25
|
-
|
|
26
|
-
1. **If a file path is provided** (e.g., `wiki/work/tasks/3-user-auth.md`):
|
|
27
|
-
- Confirm the file exists (use Serena `find_file` or `list_dir`)
|
|
28
|
-
- If the file does not exist, STOP and report the error
|
|
29
|
-
|
|
30
|
-
2. **If a number-slug is provided** (e.g., `3-user-auth`):
|
|
31
|
-
- Search `wiki/work/tasks/` for `<number-slug>.md`
|
|
32
|
-
- If not found, STOP and report the error
|
|
33
|
-
|
|
34
|
-
3. **If only a number is provided** (e.g., `3`):
|
|
35
|
-
- Search `wiki/work/tasks/` for a file starting with that number
|
|
36
|
-
- If ambiguous, list matches and ask the user to clarify
|
|
37
|
-
- If no match found, STOP and report the error
|
|
38
|
-
|
|
39
|
-
---
|
|
40
|
-
|
|
41
|
-
## Step 2: Read the Task Spec, Add-Task Command, and Task File
|
|
42
|
-
|
|
43
|
-
Read all three files:
|
|
44
|
-
1. `wiki/work/tasks/lifecycle.md` — the authoritative task file spec (frontmatter schema, ID/filename rules, status transitions)
|
|
45
|
-
2. `lib/skills/task-add/SKILL.md` — the full overview of how to structure a task (research process, execution-readiness criteria, agent annotations, level of detail required)
|
|
46
|
-
3. The resolved task file from Step 1
|
|
47
|
-
|
|
48
|
-
The `add-task` command defines what a well-structured task looks like. Use it as the lens for your assessment.
|
|
49
|
-
|
|
50
|
-
---
|
|
51
|
-
|
|
52
|
-
## Step 3: Assess Against the Spec
|
|
53
|
-
|
|
54
|
-
Evaluate the task file against every requirement in the spec. Check for:
|
|
55
|
-
|
|
56
|
-
### Structure Compliance
|
|
57
|
-
- [ ] Has `# NNN — Task Title` heading
|
|
58
|
-
- [ ] Has dependency block immediately after the title and before `## Objective`:
|
|
59
|
-
```markdown
|
|
60
|
-
> **Depends on**: [NNN-slug](NNN-slug.md) or `none`
|
|
61
|
-
> **Blocks**: [NNN-slug](NNN-slug.md) or `none`
|
|
62
|
-
> **Parallel-safe with**: [NNN-slug](NNN-slug.md) or `none`
|
|
63
|
-
```
|
|
64
|
-
If the block is missing entirely, add it during Step 5 — consult the active task index and ask the user to confirm the relationships (same process as `/task-add` step 3.5) before writing.
|
|
65
|
-
- [ ] Has `## Objective` with one-sentence description
|
|
66
|
-
- [ ] Has `## Approach` with 1-3 sentence summary
|
|
67
|
-
- [ ] Has `## Prerequisites` section (can be empty if none)
|
|
68
|
-
- [ ] Has `---` separator between Prerequisites and Steps
|
|
69
|
-
- [ ] Has `## Steps` with numbered `### N.` sections
|
|
70
|
-
- [ ] Ends with a verification section
|
|
71
|
-
|
|
72
|
-
### Execution Readiness (the critical part)
|
|
73
|
-
- [ ] **Every `### N.` section has `<!-- agent: TYPE -->` annotation** with a valid type (`general-purpose`, `Explore`, `Plan`)
|
|
74
|
-
- [ ] **Every actionable item uses `- [ ]` checkbox syntax**
|
|
75
|
-
- [ ] **Steps include specific file paths** to create or modify
|
|
76
|
-
- [ ] **Steps include function/component names** to implement
|
|
77
|
-
- [ ] **Steps have enough implementation detail** for an agent to execute without ambiguity or further research
|
|
78
|
-
- [ ] **Sub-details** as plain-text indented lines for acceptance criteria where needed
|
|
79
|
-
- [ ] Steps are grouped by logical area
|
|
80
|
-
- [ ] No vague steps like "implement feature X" without specifics
|
|
81
|
-
|
|
82
|
-
### Codebase Alignment
|
|
83
|
-
- [ ] Referenced file paths actually exist (or are clearly marked as "create new")
|
|
84
|
-
- [ ] Referenced function/component names match the codebase
|
|
85
|
-
- [ ] Approach is consistent with existing project patterns and conventions
|
|
86
|
-
|
|
87
|
-
---
|
|
88
|
-
|
|
89
|
-
## Step 4: Report Findings
|
|
90
|
-
|
|
91
|
-
Present a clear assessment to the user:
|
|
92
|
-
|
|
93
|
-
1. **Spec compliance**: List any structural issues (missing sections, wrong format)
|
|
94
|
-
2. **Execution readiness gaps**: List steps that are too vague for `/tackle` to execute — these are the most important findings
|
|
95
|
-
3. **Codebase misalignments**: Any references that don't match reality
|
|
96
|
-
|
|
97
|
-
If there are **user instructions** (text after the file reference in `$ARGUMENTS`), note how they relate to the findings.
|
|
98
|
-
|
|
99
|
-
---
|
|
100
|
-
|
|
101
|
-
## Step 5: Apply Updates
|
|
102
|
-
|
|
103
|
-
### If user instructions were provided
|
|
104
|
-
Apply the user's specific changes first, then fix any spec compliance issues found in Step 3.
|
|
105
|
-
|
|
106
|
-
### If no user instructions were provided
|
|
107
|
-
Fix all issues found in Step 3:
|
|
108
|
-
- Add missing structural sections
|
|
109
|
-
- Add `<!-- agent: TYPE -->` annotations to any sections missing them
|
|
110
|
-
- Flesh out vague steps with specific file paths, function names, and implementation detail
|
|
111
|
-
- Use Serena to explore the codebase and determine the correct paths, names, and patterns
|
|
112
|
-
- Use Context7 MCP for any library/framework documentation needed
|
|
113
|
-
- Convert plain list items to `- [ ]` checkbox syntax
|
|
114
|
-
|
|
115
|
-
### Research for updates
|
|
116
|
-
When adding specificity to vague steps, follow the `/research` workflow (see `lib/skills/research/SKILL.md`):
|
|
117
|
-
- **Internal (Phase 2)**: Use Serena's `get_symbols_overview`, `find_symbol`, and `search_for_pattern` to understand the codebase
|
|
118
|
-
- **External (Phase 3)**: Use Context7 MCP for library docs and Brave Search MCP for best practices and package recommendations
|
|
119
|
-
- Ground every update in actual codebase state — don't guess at file paths or function names
|
|
120
|
-
|
|
121
|
-
### Present changes before applying
|
|
122
|
-
Before writing the updated task file, present a summary of proposed changes and ask the user to confirm using `AskUserQuestion`.
|
|
123
|
-
|
|
124
|
-
After confirmation, update the task file using the **`Edit`** tool (or `Write` for a full rewrite). **Never** use `sed`, `awk`, `perl -i`, or `echo >>` — call `Edit` once per change, even if there are many. See `wiki/guides/mcp-tools.md` "Common anti-patterns".
|
|
125
|
-
|
|
126
|
-
---
|
|
127
|
-
|
|
128
|
-
## Step 6: Confirm Completion
|
|
129
|
-
|
|
130
|
-
Report:
|
|
131
|
-
- Number of issues found and fixed
|
|
132
|
-
- Any remaining concerns or trade-offs
|
|
133
|
-
- Suggest next steps:
|
|
134
|
-
```
|
|
135
|
-
To execute this task: /tackle <resolved-path>
|
|
136
|
-
```
|