@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,17 +1,17 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: bug-
|
|
3
|
-
description:
|
|
2
|
+
name: bug-create
|
|
3
|
+
description: Create a new bug report in wiki/work/bugs/ with required-on-report fields and append it to the bug index
|
|
4
4
|
category: planning
|
|
5
5
|
model: claude-sonnet-5
|
|
6
|
-
argument-hint: <short bug description>
|
|
6
|
+
argument-hint: <short bug description> [--knowledge <slug>]
|
|
7
7
|
disable-model-invocation: false
|
|
8
8
|
user-invocable: true
|
|
9
9
|
---
|
|
10
10
|
**Prereqs:** obey `wiki/guides/mcp-tools.md` + `wiki/work/bugs/lifecycle.md`; run /primer if not done this session.
|
|
11
11
|
|
|
12
|
-
#
|
|
12
|
+
# Create Bug
|
|
13
13
|
|
|
14
|
-
Create a new bug file in `wiki/work/bugs/` with status `
|
|
14
|
+
Create a new bug file in `wiki/work/bugs/` with status `open`. Gather every required-on-report field before writing — a bug without reliable reproduction is a complaint, not a bug.
|
|
15
15
|
|
|
16
16
|
---
|
|
17
17
|
|
|
@@ -53,17 +53,15 @@ For each missing required-on-report field, use `AskUserQuestion`. Batch related
|
|
|
53
53
|
|
|
54
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
|
+
**Knowledge exception** (optional, non-required): if `$ARGUMENTS` contains `--knowledge <slug>` or a bare slug matching an existing page filename (without extension) in `wiki/knowledge/concepts/` or `wiki/knowledge/sources/`, use `mcp__serena__find_file` to search for `<slug>.md` (try the slug as given, and with `.md` appended if not already present) in those two directories. **If found**: store `(knowledge_file_path, knowledge_slug)` for Step 6. **If not found**: warn the user (e.g. "Knowledge page '<slug>' not found in wiki/knowledge/concepts/ or wiki/knowledge/sources/ — continuing without a knowledge link.") and continue — never block bug filing on a missing knowledge page. If no knowledge reference was given, skip this exception entirely (no `relates_to::` line is written in Step 6).
|
|
57
|
+
|
|
56
58
|
If the user cannot supply reliable Steps to Reproduce, STOP and tell them:
|
|
57
59
|
|
|
58
|
-
> Cannot file this bug yet — Steps to Reproduce are required. Capture a deterministic trigger first (a failing test, a screencast, a server log timestamp), then re-run `/bug-
|
|
60
|
+
> Cannot file this bug yet — Steps to Reproduce are required. Capture a deterministic trigger first (a failing test, a screencast, a server log timestamp), then re-run `/bug-create`.
|
|
59
61
|
|
|
60
62
|
### Step 4: Determine the Next Bug Number
|
|
61
63
|
|
|
62
|
-
|
|
63
|
-
- `mcp__serena__list_dir` on `wiki/work/bugs/` and `wiki/work/bugs/archive/` (skip either that doesn't exist)
|
|
64
|
-
- Collect every `NNNN-` prefix; take `max + 1`; zero-pad to 4 digits.
|
|
65
|
-
- Also scan `wiki/work/bugs/index.md` for any reserved IDs not yet on disk.
|
|
66
|
-
- Never re-use a number — IDs are immutable references.
|
|
64
|
+
Allocate the next ID per `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Number allocation (family: `wiki/work/bugs/`, prefix: `BUG-`, also scan `index.md` for reserved IDs).
|
|
67
65
|
|
|
68
66
|
Derive the slug from the title: lowercase, hyphen-separated, 2–5 words, ≤ 60 chars. Describe the **symptom**, not the suspected cause (e.g., `login-fails-on-safari`, not `safari-cookie-handler-bug`).
|
|
69
67
|
|
|
@@ -78,13 +76,13 @@ Ask the user to confirm via `AskUserQuestion` ("File this bug? Yes / Edit / Canc
|
|
|
78
76
|
|
|
79
77
|
### Step 5a: Re-verify next bug number — IMMEDIATELY before writing
|
|
80
78
|
|
|
81
|
-
|
|
79
|
+
Repeat § Number allocation step 6 (same family and prefix as Step 4); never call `Write` before completing it.
|
|
82
80
|
|
|
83
81
|
### Step 6: Write the Bug File
|
|
84
82
|
|
|
85
83
|
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:
|
|
86
84
|
|
|
87
|
-
- `Status:
|
|
85
|
+
- `Status: open`
|
|
88
86
|
- `Priority: —` (filled in triage)
|
|
89
87
|
- `Assignee: —` (filled in triage)
|
|
90
88
|
- `Tags: —` (filled in triage)
|
|
@@ -94,6 +92,18 @@ Use `Write` to create `wiki/work/bugs/BUG-NNNN-<slug>.md`, following the frontma
|
|
|
94
92
|
- `aliases: [BUG-NNNN]` — mirrors this file's own id: field so Obsidian's wikilink resolver can find it by short ID (ROADMAP-008)
|
|
95
93
|
- Leave `Root Cause Analysis`, `Resolution`, and `Related` sections present but empty (the templated placeholder line under each `>` quote is fine)
|
|
96
94
|
|
|
95
|
+
**Knowledge link** (only when the Step 3 exception resolved a knowledge reference): insert `relates_to::[[<slug>]]` as a typed link directly under the `# BUG-NNNN — <title>` H1 heading, before the body prose begins. Bug files have no other typed-link line near the top, so this is a new line, not an insertion alongside an existing one:
|
|
96
|
+
|
|
97
|
+
```markdown
|
|
98
|
+
# BUG-NNNN — <title>
|
|
99
|
+
|
|
100
|
+
relates_to::[[<slug>]]
|
|
101
|
+
|
|
102
|
+
<body prose begins here>
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
If no knowledge reference was given or resolved, omit the line entirely — do not write an empty placeholder.
|
|
106
|
+
|
|
97
107
|
### Step 7: Update the Bug Index
|
|
98
108
|
|
|
99
109
|
Append a bullet line to `wiki/work/bugs/index.md` (active items only — a flat list, no table). Insert in numeric order. Entry format (documented at the top of `index.md`):
|
|
@@ -104,14 +114,14 @@ Append a bullet line to `wiki/work/bugs/index.md` (active items only — a flat
|
|
|
104
114
|
|
|
105
115
|
`<status>` is the status you set in Step 6; `<priority>` is `—` until triage. If the index still shows the placeholder line (`_(none yet)_`), replace it with the new line.
|
|
106
116
|
|
|
107
|
-
Use
|
|
117
|
+
Use one targeted `Edit` call. Edit only — see `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Edit hygiene.
|
|
108
118
|
|
|
109
119
|
### Step 8: Report Completion
|
|
110
120
|
|
|
111
121
|
Print:
|
|
112
122
|
- Created file: `wiki/work/bugs/BUG-NNNN-<slug>.md`
|
|
113
123
|
- Bug ID: `BUG-NNNN`
|
|
114
|
-
- Status: `
|
|
124
|
+
- Status: `open`
|
|
115
125
|
- Next step:
|
|
116
126
|
|
|
117
127
|
```
|
|
@@ -23,16 +23,7 @@ Walk an existing bug through triage: confirm reproducibility, assign priority/as
|
|
|
23
23
|
|
|
24
24
|
### Step 1: Resolve the Bug File
|
|
25
25
|
|
|
26
|
-
|
|
27
|
-
- `BUG-NNNN` (e.g. `BUG-0042`)
|
|
28
|
-
- `NNNN` (e.g. `0042` or `42`)
|
|
29
|
-
- `NNNN-slug` (e.g. `0042-csv-export`)
|
|
30
|
-
- Full path (e.g. `wiki/work/bugs/BUG-0042-csv-export.md`)
|
|
31
|
-
|
|
32
|
-
Resolution order:
|
|
33
|
-
1. If full path: confirm with `mcp__serena__find_file`.
|
|
34
|
-
2. Otherwise normalize to a `BUG-NNNN*` pattern and search `wiki/work/bugs/` via `mcp__serena__find_file`.
|
|
35
|
-
3. If not found, STOP and report the error.
|
|
26
|
+
Resolve the file per ~/.claude/skills/_shared/ID-RESOLUTION.md — family: bugs · scope: active · ambiguous: interactive · empty: not found → STOP and report the error
|
|
36
27
|
|
|
37
28
|
Read the bug file in full.
|
|
38
29
|
|
|
@@ -87,7 +78,7 @@ If the required field is absent, ask via `AskUserQuestion` and refuse to proceed
|
|
|
87
78
|
|
|
88
79
|
### Step 6: Apply Updates
|
|
89
80
|
|
|
90
|
-
Edit the bug file
|
|
81
|
+
Edit the bug file (Edit only — see `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Edit hygiene):
|
|
91
82
|
|
|
92
83
|
1. Flip `status:` to the new value.
|
|
93
84
|
2. Set `priority:`, `assignee:`, `tags:`, `impact:`, `workaround:` as gathered.
|
|
@@ -99,23 +90,18 @@ Edit the bug file using `Edit` (never `sed`/`echo`/`awk`):
|
|
|
99
90
|
Read `wiki/work/bugs/index.md`. Apply changes with `Edit`:
|
|
100
91
|
|
|
101
92
|
- **Start work / Defer**: find the row for this bug and update the `Status` column text. Do not move the file.
|
|
102
|
-
- **Reject**:
|
|
93
|
+
- **Reject**: the active-index row removal is performed by Step 7a.
|
|
103
94
|
|
|
104
95
|
#### Step 7a: Archive-Move for Reject Outcomes
|
|
105
96
|
|
|
106
|
-
For `wontfix`, `duplicate`, and `cannot-reproduce` outcomes only
|
|
107
|
-
|
|
108
|
-
1. `Bash`: `git mv wiki/work/bugs/NNNN-slug.md wiki/work/bugs/archive/NNNN-slug.md`
|
|
109
|
-
2. `Edit`: (active index row already removed in Step 7 above)
|
|
110
|
-
3. `Edit`: append to `wiki/work/bugs/archive/index.md`: `| [[BUG-NNNN]] | <title> | <status> | YYYY-MM-DD |`
|
|
111
|
-
4. `Edit`: append to `wiki/log.md`
|
|
97
|
+
For `wontfix`, `duplicate`, and `cannot-reproduce` outcomes only. Read `~/.claude/skills/_shared/ARCHIVE-WORK-ITEM.md` now, then run its Procedure: `family: bugs`, `terminal_status: <wontfix|duplicate|cannot-reproduce>`, `log: skip` — Step 9 writes the single log entry. Step 6 has already flipped the status (the bug file needed its `## Resolution`/`## Related` edits before the move), so the procedure's status flip is a no-op.
|
|
112
98
|
|
|
113
99
|
For active outcomes (Start work / Defer), skip this step entirely — the file stays at `wiki/work/bugs/NNNN-slug.md`.
|
|
114
100
|
|
|
115
101
|
### Step 8: Cross-Linking
|
|
116
102
|
|
|
117
103
|
- If outcome is **Duplicate**: open the canonical bug file and append a line to its `## Related → Related bugs:` section listing this bug ID. Use `Edit`.
|
|
118
|
-
- If outcome is **Start work now**: ask whether to spawn a fix task via `/task-
|
|
104
|
+
- If outcome is **Start work now**: ask whether to spawn a fix task via `/task-create`. If yes, suggest the command — do not invoke it automatically.
|
|
119
105
|
|
|
120
106
|
### Step 9: Append Log Entry
|
|
121
107
|
|
package/lib/skills/demo/SKILL.md
CHANGED
|
@@ -11,7 +11,7 @@ user-invocable: true
|
|
|
11
11
|
|
|
12
12
|
# Demo
|
|
13
13
|
|
|
14
|
-
Audit the project's features, produce a **2-3 minute demo run book** at
|
|
14
|
+
Audit the project's features, produce a **2-3 minute demo run book** at `wiki/demo/runbook.md`, then generate a **Marp slideshow** from it at `wiki/demo/runbook.slides.md`.
|
|
15
15
|
|
|
16
16
|
---
|
|
17
17
|
|
|
@@ -27,7 +27,7 @@ Audit the project's features, produce a **2-3 minute demo run book** at `.docs/d
|
|
|
27
27
|
|
|
28
28
|
Use Serena MCP to explore the project. Never use `bash` commands for file exploration.
|
|
29
29
|
|
|
30
|
-
Start by reading Serena memories and the project's README, manifest, and
|
|
30
|
+
Start by reading Serena memories and the project's README, manifest, and `wiki/index.md` for planning context. Then browse the source tree and use `mcp__serena__get_symbols_overview` on key files to discover what the project actually does — routes, commands, exported functions, UI entry points.
|
|
31
31
|
|
|
32
32
|
Compile a **feature inventory** — a flat list of distinct, user-visible capabilities. For each feature note what it does and how to trigger it (a click path, a command, or a code example). Aim for around a dozen features; collapse trivial variations into a single entry.
|
|
33
33
|
|
|
@@ -39,7 +39,7 @@ Before designing the narrative, collect every stated requirement so the demo can
|
|
|
39
39
|
|
|
40
40
|
**Check for requirements documents in this order:**
|
|
41
41
|
|
|
42
|
-
1. `wiki/work/requirements/` — read every non-retired PRD file (
|
|
42
|
+
1. `wiki/work/requirements/` — read every non-retired PRD file (decide by each file's `status:`, never by location; retired PRDs stay in place, and any legacy holding folder is skipped). Extract:
|
|
43
43
|
- User stories / personas
|
|
44
44
|
- Functional requirements
|
|
45
45
|
- Success metrics / acceptance criteria
|
|
@@ -47,7 +47,7 @@ Before designing the narrative, collect every stated requirement so the demo can
|
|
|
47
47
|
|
|
48
48
|
2. `wiki/work/decisions/` — scan accepted ADR decisions for capabilities they mandate or prohibit.
|
|
49
49
|
|
|
50
|
-
3. Any other requirements
|
|
50
|
+
3. Any other requirements-like pages in `wiki/knowledge/sources/` (ingested source summaries not already captured as formal requirements).
|
|
51
51
|
|
|
52
52
|
Produce a **requirements checklist** — a flat list of discrete, testable requirements drawn from those sources. Each entry should be one line, e.g. `REQ-01: User can sign up with email and password`. If no requirements documents exist, note that explicitly and continue.
|
|
53
53
|
|
|
@@ -75,7 +75,7 @@ End with a single closing sentence pointing to next steps or where to learn more
|
|
|
75
75
|
|
|
76
76
|
## Phase 4 — Write the Run Book
|
|
77
77
|
|
|
78
|
-
Create
|
|
78
|
+
Create `wiki/demo/` if it doesn't exist. Write `wiki/demo/runbook.md` using this template:
|
|
79
79
|
|
|
80
80
|
```markdown
|
|
81
81
|
# Demo Run Book — {Project Name}
|
|
@@ -145,7 +145,7 @@ Fill every placeholder with real project content. The run book must be self-cont
|
|
|
145
145
|
|
|
146
146
|
Invoke the `marp-slideshow` skill on the run book you just wrote:
|
|
147
147
|
|
|
148
|
-
> **Delegate to `/marp-slideshow
|
|
148
|
+
> **Delegate to `/marp-slideshow wiki/demo/runbook.md wiki/demo/`**
|
|
149
149
|
|
|
150
150
|
The deck must use a **GitHub dark style** — set the front-matter to a dark background (`#0d1117`) with light text (`#c9d1d9`) and accent color (`#58a6ff`). Write every slide as if you are speaking directly to a stakeholder: tell the story, don't transcribe the run book. One clear idea per slide; no bullet dumps. Speaker notes contain the verbatim spoken line from the run book.
|
|
151
151
|
|
|
@@ -153,11 +153,11 @@ If the `marp-slideshow` skill is not available, write the deck directly: use `ma
|
|
|
153
153
|
|
|
154
154
|
**Architecture diagrams**: If the project has a meaningful architecture worth showing (layered systems, data flows, service dependencies), follow this two-track approach — one format per destination:
|
|
155
155
|
|
|
156
|
-
- **Run book (Markdown)** — embed a fenced `mermaid` block directly in
|
|
156
|
+
- **Run book (Markdown)** — embed a fenced `mermaid` block directly in `wiki/demo/runbook.md` at the appropriate section. Keep each diagram small — no more than six or seven nodes. One layer per diagram.
|
|
157
157
|
- **Slides (SVG image)** — never embed a raw Mermaid code block in the slides. Instead:
|
|
158
|
-
1. Write the raw Mermaid source (no markdown wrapper) to
|
|
159
|
-
2. Render it to SVG via Bash: `npx @mermaid-js/mermaid-cli mmdc -i
|
|
160
|
-
3. Reference the rendered SVG in the slide: ` to `wiki/demo/<name>.mmd` (e.g. `architecture.mmd`, `data-flow.mmd`).
|
|
159
|
+
2. Render it to SVG via Bash: `npx @mermaid-js/mermaid-cli mmdc -i wiki/demo/<name>.mmd -o wiki/demo/<name>.svg`
|
|
160
|
+
3. Reference the rendered SVG in the slide: ``
|
|
161
161
|
|
|
162
162
|
One diagram per slide. Name `.mmd` files after their content (e.g. `system-overview.mmd`, `data-flow.mmd`).
|
|
163
163
|
|
|
@@ -168,7 +168,7 @@ One diagram per slide. Name `.mmd` files after their content (e.g. `system-overv
|
|
|
168
168
|
Print a short summary to the user:
|
|
169
169
|
|
|
170
170
|
- **Run book** — path, word count, and step count
|
|
171
|
-
- **Slideshow** — path, slide count, and render command (`npx @marp-team/marp-cli@latest
|
|
171
|
+
- **Slideshow** — path, slide count, and render command (`npx @marp-team/marp-cli@latest wiki/demo/runbook.slides.md`)
|
|
172
172
|
- **Requirements coverage** — table of all requirements, each marked Covered / Gap / Undocumented
|
|
173
173
|
- **Gaps** — requirements with no demo step, and features that exist but couldn't be cleanly demo'd
|
|
174
174
|
|
|
@@ -36,7 +36,7 @@ Use Serena MCP tools to explore the target project. You are looking for the stor
|
|
|
36
36
|
- **The best features** — identify the 2-3 features that are most impressive, most useful, or most surprising. Look for things with real numbers (command counts, time saved, steps eliminated), elegant abstractions, or capabilities that competitors don't have. These are the things you'd demo first to a skeptic.
|
|
37
37
|
- **The best part** — something that makes a developer or user think "oh that's clever."
|
|
38
38
|
|
|
39
|
-
Check: `package.json` (name, description), existing `README.md`, the top-level directory structure, and any
|
|
39
|
+
Check: `package.json` (name, description), existing `README.md`, the top-level directory structure, and any planning docs in `wiki/` (e.g. `wiki/index.md`, `wiki/work/requirements/`) or `CLAUDE.md` files for stated goals.
|
|
40
40
|
|
|
41
41
|
### 2. Write the pitch
|
|
42
42
|
|
|
@@ -35,7 +35,7 @@ The output document is formatted to be a valid "source project" for `/port-featu
|
|
|
35
35
|
3. **Clarifying questions** — ask before proceeding if any are ambiguous:
|
|
36
36
|
- **Output location**: Should the extracted module live as a subdirectory within this project (e.g., `packages/<module-name>/`) or as a stub for a new standalone repo? (Default: subdirectory)
|
|
37
37
|
- **Constraints**: Any hard constraints — must stay in the same language, no new dependencies, must preserve the current public API for backward compatibility?
|
|
38
|
-
- **Supplementary output**:
|
|
38
|
+
- **Supplementary output**: Is this extraction substantial enough to warrant a roadmap (multiple ordered steps) via `/roadmap-create`, or small enough for a single task via `/task-create`? Default to a roadmap once Phase 5's extraction steps exceed ~3 steps or missing test coverage must be backfilled first.
|
|
39
39
|
|
|
40
40
|
---
|
|
41
41
|
|
|
@@ -224,110 +224,52 @@ Classify each source file by porting effort:
|
|
|
224
224
|
|
|
225
225
|
---
|
|
226
226
|
|
|
227
|
-
## Phase 6:
|
|
227
|
+
## Phase 6: Produce the Extraction Roadmap
|
|
228
228
|
|
|
229
|
-
### 6a.
|
|
229
|
+
### 6a. Present the Full Analysis
|
|
230
230
|
|
|
231
|
-
|
|
231
|
+
Present the complete assessment in the conversation as structured tables/sections — this is working analysis for the roadmap and any task files, not a standalone persisted document:
|
|
232
232
|
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
proposed-module-path: <packages/<module-name> OR external repo name>
|
|
242
|
-
---
|
|
243
|
-
|
|
244
|
-
# Extraction Plan: <Feature Name>
|
|
245
|
-
|
|
246
|
-
> **Feature**: <feature description>
|
|
247
|
-
> **Extracted from**: `<absolute project path>`
|
|
248
|
-
> **Proposed module**: `<module path>`
|
|
249
|
-
> **Overall effort**: <Low / Medium / High / Very High>
|
|
250
|
-
> **Summary**: <One sentence on what this extraction involves.>
|
|
251
|
-
|
|
252
|
-
## Source Feature Inventory
|
|
253
|
-
|
|
254
|
-
<Phase 3 inventory — this section is read by /port-feature when this module is the source>
|
|
255
|
-
|
|
256
|
-
## Coupling Analysis
|
|
257
|
-
|
|
258
|
-
<Phase 2d coupling map table>
|
|
259
|
-
|
|
260
|
-
## Interface Specifications
|
|
261
|
-
|
|
262
|
-
<Phase 4a interface table>
|
|
263
|
-
|
|
264
|
-
## Proposed Module Structure
|
|
265
|
-
|
|
266
|
-
<Phase 4b directory tree with annotations>
|
|
267
|
-
|
|
268
|
-
## Technology Mapping
|
|
269
|
-
|
|
270
|
-
<Phase 4c table>
|
|
271
|
-
|
|
272
|
-
## Complexity Breakdown
|
|
273
|
-
|
|
274
|
-
<Phase 5c table>
|
|
233
|
+
- **Source Feature Inventory** — Phase 3 inventory (this is what must ultimately land in the extracted module's own `README.md` per Phase 4b — that file, not a wiki doc, is what `/port-feature` reads)
|
|
234
|
+
- **Coupling Analysis** — Phase 2d coupling map table
|
|
235
|
+
- **Interface Specifications** — Phase 4a interface table
|
|
236
|
+
- **Proposed Module Structure** — Phase 4b directory tree with annotations
|
|
237
|
+
- **Technology Mapping** — Phase 4c table
|
|
238
|
+
- **Complexity Breakdown** — Phase 5c table
|
|
239
|
+
- **Gap Analysis** — Phase 5a current-project changes + 5b missing test coverage
|
|
240
|
+
- **Extraction Steps** — ordered, dependency-respecting steps; for each: title, effort (Direct/Adapt/Rewrite), files affected (extract to target, create/move/refactor), what to do, and definition of done (tests pass, imports resolve, no references to old path)
|
|
275
241
|
|
|
276
|
-
|
|
242
|
+
### 6b. Decide: Roadmap or Single Task
|
|
277
243
|
|
|
278
|
-
|
|
244
|
+
- **≤3 extraction steps, no missing test coverage flagged in 5b** → skip the roadmap. Go straight to `/task-create "Extract <feature name> into standalone module"`, carrying the full step detail into the task's steps, then skip to Phase 7.
|
|
245
|
+
- **>3 steps, missing test coverage to backfill first, or the user asked for a roadmap in Phase 0** → continue to 6c.
|
|
279
246
|
|
|
280
|
-
|
|
247
|
+
### 6c. Delegate to `/roadmap-create`
|
|
281
248
|
|
|
282
|
-
|
|
249
|
+
> **Delegate to `/roadmap-create Extract <feature name> into standalone module`**
|
|
283
250
|
|
|
284
|
-
|
|
251
|
+
Feed `/roadmap-create`'s own Socratic Q&A from the analysis already gathered, rather than making the user re-derive it from scratch:
|
|
285
252
|
|
|
286
|
-
|
|
287
|
-
|
|
288
|
-
|
|
289
|
-
|
|
290
|
-
|
|
291
|
-
|
|
292
|
-
|
|
293
|
-
**Definition of done**: <How to know this step is complete — tests pass, imports resolve, no references to old path>
|
|
294
|
-
|
|
295
|
-
---
|
|
296
|
-
|
|
297
|
-
### Step 2: <title>
|
|
298
|
-
|
|
299
|
-
… (repeat for each step)
|
|
300
|
-
|
|
301
|
-
---
|
|
302
|
-
|
|
303
|
-
## Suggested Next Actions
|
|
304
|
-
|
|
305
|
-
- To create a task from this plan: `/task-add "Extract <feature name> into standalone module"`
|
|
306
|
-
- To port this module into another project after extraction: `/port-feature <proposed-module-path> <feature name>`
|
|
307
|
-
- If an interface decision is still open: <frame the specific decision clearly>
|
|
308
|
-
```
|
|
309
|
-
|
|
310
|
-
### 6b. Optionally Create a Task File
|
|
311
|
-
|
|
312
|
-
If the user requested a task file (or the plan is concrete enough to execute immediately):
|
|
313
|
-
|
|
314
|
-
```
|
|
315
|
-
/task-add "Extract <feature name> into standalone module"
|
|
316
|
-
```
|
|
253
|
+
| Elicitation | Answer to supply |
|
|
254
|
+
|---|---|
|
|
255
|
+
| Goal | The one/two-sentence extraction summary + overall effort verdict from 5c |
|
|
256
|
+
| Phases | Group the ordered Extraction Steps from 6a into 2-5 execution-flavored phases (e.g. "Backfill tests", "Define interfaces", "Extract core", "Wire adapters") — never one phase per step |
|
|
257
|
+
| Owner | Ask the user if not already known |
|
|
258
|
+
| Linked PRD/ADRs | Any `wiki/work/requirements/` or `wiki/work/decisions/` entries found during Phase 2a |
|
|
317
259
|
|
|
318
|
-
|
|
260
|
+
Each Extraction Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-create --roadmap ROADMAP-NNNN <step title>` (or automatically when `/roadmap-next` runs).
|
|
319
261
|
|
|
320
262
|
---
|
|
321
263
|
|
|
322
264
|
## Phase 7: Report to User
|
|
323
265
|
|
|
324
|
-
After
|
|
266
|
+
After the roadmap (or single task) is created:
|
|
325
267
|
|
|
326
|
-
1. State the path
|
|
268
|
+
1. State what was created: the roadmap path (`wiki/work/roadmaps/ROADMAP-NNNN-slug.md`) or the single task command run
|
|
327
269
|
2. Give a one-line effort verdict (e.g., "High effort — 3 interfaces to design, 2 rewrites, 1 missing test suite")
|
|
328
270
|
3. List the top 3 extraction steps in brief
|
|
329
271
|
4. Call out the single biggest coupling risk or blocker
|
|
330
|
-
5. Suggest the most useful next action (
|
|
272
|
+
5. Suggest the most useful next action (`/roadmap-next ROADMAP-NNNN`, an interface decision to make, or `/port-feature` handoff once the module's own `README.md` is written)
|
|
331
273
|
|
|
332
274
|
---
|
|
333
275
|
|
|
@@ -338,7 +280,7 @@ After writing the plan file:
|
|
|
338
280
|
3. **No speculation** — every coupling point listed must be grounded in what you actually read from the codebase (Serena tool results), not assumed
|
|
339
281
|
4. **Interfaces for everything** — every `infra`, `direct-external`, `internal-coupling`, and `config` dependency must have a corresponding interface in the plan; none may be left as a concrete import in the extracted module's `core/`
|
|
340
282
|
5. **SOLID enforced** — each SOLID principle (SRP, OCP, LSP, ISP, DIP) must be explicitly addressed in Phase 4a; call out any violations with a mitigation
|
|
341
|
-
6. **port-feature compatibility** — Phase 3 inventory must match exactly the format `/port-feature` Phase 1c expects; the
|
|
283
|
+
6. **port-feature compatibility** — Phase 3 inventory must match exactly the format `/port-feature` Phase 1c expects; the extracted module's own `README.md` (Phase 4b) must be usable as a "source project" spec
|
|
342
284
|
7. **Brave Search rate limit** — 50 requests/second, parallel searches allowed (applies during Phase 1 research)
|
|
343
285
|
8. **Maximum 3 concurrent sub-processes** at a time
|
|
344
286
|
9. **Always terminate all processes when done** (dev servers, type checkers, long-running commands)
|
|
@@ -64,7 +64,7 @@ Scan every line this commit **adds or modifies** for comments more verbose than
|
|
|
64
64
|
- If it explains a genuinely non-obvious *why* (a workaround, a hidden constraint, a subtle invariant) but spans more lines or words than necessary, rewrite it to the single shortest sentence that preserves that reason.
|
|
65
65
|
- Preserve the comment's position (same line for a trailing comment, same location for a block comment) and its language's comment syntax — only the wording and line count change.
|
|
66
66
|
|
|
67
|
-
Use `Edit` per file for every change —
|
|
67
|
+
Use `Edit` per file for every change. Edit only — see `~/.claude/skills/_shared/SKILL-BOILERPLATE.md` § Edit hygiene.
|
|
68
68
|
|
|
69
69
|
## Step 3: Assess Changes
|
|
70
70
|
|
|
@@ -257,7 +257,7 @@ git-commit "[no-bump] Fix the login redirect"
|
|
|
257
257
|
|
|
258
258
|
```bash
|
|
259
259
|
git-commit "[patch] Fix UAT verdict logic for edge-case test skips"
|
|
260
|
-
git-commit "[minor] Add /task-
|
|
260
|
+
git-commit "[minor] Add /task-assess skill with dependency graph and wave output"
|
|
261
261
|
git-commit "[major] Rename all skills to noun-first convention, drop legacy verb-first aliases"
|
|
262
262
|
```
|
|
263
263
|
|
|
@@ -265,14 +265,14 @@ git-commit "[major] Rename all skills to noun-first convention, drop legacy verb
|
|
|
265
265
|
|
|
266
266
|
```bash
|
|
267
267
|
git-commit "Fix UAT verdict logic for edge-case test skips"
|
|
268
|
-
git-commit "Add /task-
|
|
268
|
+
git-commit "Add /task-assess skill with dependency graph and wave output"
|
|
269
269
|
```
|
|
270
270
|
|
|
271
271
|
### Writing a good single-line subject
|
|
272
272
|
|
|
273
273
|
If the change feels too complex to summarize in one line, **make the subject more descriptive** — do not reach for a multi-line body. Aim for ~70–100 characters but go longer if it adds real information. Lead with the *what* and the *why* on the same line, separated by a colon when helpful:
|
|
274
274
|
|
|
275
|
-
- ✅ `[minor] Require research for every test type in /uat-
|
|
275
|
+
- ✅ `[minor] Require research for every test type in /uat-create with checkpoint gate`
|
|
276
276
|
- ✅ `[patch] Allow standard tools for markdown editing; ban bash exploration commands`
|
|
277
277
|
- ✅ `Allow standard tools for markdown editing; ban bash exploration commands` (no bump this run — the subject still carries its weight)
|
|
278
278
|
- ❌ `Update commands` (too vague — and vague is vague with or without a prefix)
|
|
@@ -21,7 +21,7 @@ The first whitespace-separated token is the **input path** (required). An option
|
|
|
21
21
|
|
|
22
22
|
**Output path resolution rules** (apply in order):
|
|
23
23
|
|
|
24
|
-
1. **No output path provided** → write to
|
|
24
|
+
1. **No output path provided** → write to `wiki/marp/<input-stem>.slides.md` (create `wiki/marp/` if it doesn't exist). Do **not** place the deck next to the input file.
|
|
25
25
|
2. **Output path provided** → always normalize the filename so it ends in `.slides.md`, even if the user didn't say so:
|
|
26
26
|
- `deck` → `deck.slides.md`
|
|
27
27
|
- `deck.md` → `deck.slides.md` (strip the trailing `.md`, then append `.slides.md`)
|
|
@@ -190,7 +190,7 @@ Before calling `Write`, mentally verify:
|
|
|
190
190
|
- [ ] Speaker notes (HTML comments) are present where the source had context that didn't fit on-slide
|
|
191
191
|
- [ ] Footer / header are short (one line, no Markdown that breaks YAML — wrap in quotes if it contains `:` or `#`)
|
|
192
192
|
- [ ] Output filename ends in `.slides.md` (always — append/normalize even if the user-supplied path didn't include it)
|
|
193
|
-
- [ ] If the user did **not** supply an output path, the deck is written to
|
|
193
|
+
- [ ] If the user did **not** supply an output path, the deck is written to `wiki/marp/<input-stem>.slides.md` (not next to the source)
|
|
194
194
|
|
|
195
195
|
## Phase 5 — Write & Confirm
|
|
196
196
|
|
|
@@ -33,7 +33,7 @@ Assess a specific feature or area of functionality in an external (source) proje
|
|
|
33
33
|
- Confirm the source directory exists: use `mcp__serena__find_file` or Bash `ls <source-path>` to verify it is accessible
|
|
34
34
|
|
|
35
35
|
3. **Clarifying questions** (ask before proceeding if ambiguous):
|
|
36
|
-
-
|
|
36
|
+
- Is this port substantial enough to warrant a roadmap (multiple ordered steps spanning several files/integration points) via `/roadmap-create`, or small enough for a single task via `/task-create`? Default to a roadmap once Phase 3's porting steps exceed ~3 steps or touch more than one integration point.
|
|
37
37
|
- Is there a preferred output level of detail (high-level steps vs. file-by-file implementation plan)?
|
|
38
38
|
- Are there any known constraints (e.g., "must stay in TypeScript", "no new dependencies")?
|
|
39
39
|
|
|
@@ -201,107 +201,52 @@ List risks that could complicate the port:
|
|
|
201
201
|
|
|
202
202
|
---
|
|
203
203
|
|
|
204
|
-
## Phase 4: Produce the Port
|
|
204
|
+
## Phase 4: Produce the Port Roadmap
|
|
205
205
|
|
|
206
|
-
### 4a.
|
|
206
|
+
### 4a. Present the Full Analysis
|
|
207
207
|
|
|
208
|
-
|
|
208
|
+
Present the complete assessment in the conversation as structured tables/sections — this is working analysis for the roadmap and any task files, not a standalone persisted document:
|
|
209
209
|
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
# Port Plan: <Feature Name>
|
|
220
|
-
|
|
221
|
-
> **Source**: `<source-path>`
|
|
222
|
-
> **Feature**: <functionality description>
|
|
223
|
-
> **Overall effort**: <Low / Medium / High / Very High>
|
|
224
|
-
> **Summary**: <One sentence on what this port involves.>
|
|
225
|
-
|
|
226
|
-
## Source Feature Summary
|
|
227
|
-
|
|
228
|
-
<Condensed version of the Source Feature Inventory from Phase 1c>
|
|
229
|
-
|
|
230
|
-
## Target Project Context
|
|
231
|
-
|
|
232
|
-
<Condensed version of the Target Project Profile from Phase 2d>
|
|
233
|
-
|
|
234
|
-
## Technology Mapping
|
|
235
|
-
|
|
236
|
-
<Table from 3a>
|
|
237
|
-
|
|
238
|
-
## Complexity Breakdown
|
|
239
|
-
|
|
240
|
-
<Table from 3b>
|
|
241
|
-
|
|
242
|
-
## Dependency Changes
|
|
243
|
-
|
|
244
|
-
<Table from 3c>
|
|
245
|
-
|
|
246
|
-
## Integration Points
|
|
247
|
-
|
|
248
|
-
<Bullet list from 3d>
|
|
210
|
+
- **Source Feature Summary** — condensed Phase 1c inventory
|
|
211
|
+
- **Target Project Context** — condensed Phase 2d profile
|
|
212
|
+
- **Technology Mapping** — table from 3a
|
|
213
|
+
- **Complexity Breakdown** — table from 3b
|
|
214
|
+
- **Dependency Changes** — table from 3c
|
|
215
|
+
- **Integration Points** — bullets from 3d
|
|
216
|
+
- **Risks** — table from 3e
|
|
217
|
+
- **Porting Steps** — ordered, dependency-respecting steps; for each: title, effort (Direct/Adapt/Rewrite), files affected (create/modify/delete), what to do, and definition of done
|
|
249
218
|
|
|
250
|
-
|
|
219
|
+
### 4b. Decide: Roadmap or Single Task
|
|
251
220
|
|
|
252
|
-
<
|
|
221
|
+
- **≤3 porting steps, single integration point** → skip the roadmap. Go straight to `/task-create "Port <feature name> from <source-path>"`, carrying the full step detail (files affected, what to do, definition of done) into the task's steps, then skip to Phase 5.
|
|
222
|
+
- **>3 steps, multiple integration points, or the user asked for a roadmap in Phase 0** → continue to 4c.
|
|
253
223
|
|
|
254
|
-
|
|
224
|
+
### 4c. Delegate to `/roadmap-create`
|
|
255
225
|
|
|
256
|
-
|
|
226
|
+
> **Delegate to `/roadmap-create Port <feature name> from <source-path>`**
|
|
257
227
|
|
|
258
|
-
|
|
228
|
+
Feed `/roadmap-create`'s own Socratic Q&A from the analysis already gathered, rather than making the user re-derive it from scratch:
|
|
259
229
|
|
|
260
|
-
|
|
261
|
-
|
|
262
|
-
-
|
|
263
|
-
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
|
|
267
|
-
**Definition of done**: <How to know this step is complete>
|
|
268
|
-
|
|
269
|
-
---
|
|
270
|
-
|
|
271
|
-
### Step 2: <title>
|
|
272
|
-
|
|
273
|
-
… (repeat for each step)
|
|
274
|
-
|
|
275
|
-
---
|
|
276
|
-
|
|
277
|
-
## Suggested Next Actions
|
|
278
|
-
|
|
279
|
-
- To create a task from this plan: `/task-add "Port <feature name> from <source-path>" --roadmap <if applicable>`
|
|
280
|
-
- To explore the source further: use Read on `<most important source file>`
|
|
281
|
-
- If a dependency decision is needed: <frame the specific decision>
|
|
282
|
-
```
|
|
283
|
-
|
|
284
|
-
### 4b. Optionally Create a Task File
|
|
285
|
-
|
|
286
|
-
If the user requested a task file (or if the plan is actionable enough to execute), suggest:
|
|
287
|
-
|
|
288
|
-
```
|
|
289
|
-
/task-add "Port <feature name> from <source-project-name>"
|
|
290
|
-
```
|
|
230
|
+
| Elicitation | Answer to supply |
|
|
231
|
+
|---|---|
|
|
232
|
+
| Goal | The one/two-sentence port summary + overall effort verdict from 3b |
|
|
233
|
+
| Phases | Group the ordered Porting Steps from 4a into 2-5 execution-flavored phases (e.g. "Dependencies", "Core port", "Integration", "Tests") — never one phase per step |
|
|
234
|
+
| Owner | Ask the user if not already known |
|
|
235
|
+
| Linked PRD/ADRs | Any `wiki/work/requirements/` or `wiki/work/decisions/` entries found during Phase 2a/2c |
|
|
291
236
|
|
|
292
|
-
|
|
237
|
+
Each Porting Step becomes one roadmap item — an inline placeholder (`- [ ] <step title>`) under its phase, per `/roadmap-create`'s item-format rules. **Do not embed the step's file list / what-to-do / definition-of-done in the roadmap item** — that detail belongs in the task file created for it via `/task-create --roadmap ROADMAP-NNNN <step title>` (or automatically when `/roadmap-next` runs).
|
|
293
238
|
|
|
294
239
|
---
|
|
295
240
|
|
|
296
241
|
## Phase 5: Report to User
|
|
297
242
|
|
|
298
|
-
After
|
|
243
|
+
After the roadmap (or single task) is created:
|
|
299
244
|
|
|
300
|
-
1. State the path
|
|
245
|
+
1. State what was created: the roadmap path (`wiki/work/roadmaps/ROADMAP-NNNN-slug.md`) or the single task command run
|
|
301
246
|
2. Give a one-line overall effort verdict (e.g., "Medium effort — 4 files to adapt, 1 rewrite, no new dependencies required")
|
|
302
247
|
3. List the top 3 porting steps in brief
|
|
303
248
|
4. Call out the single biggest risk or blocker
|
|
304
|
-
5. Suggest the most useful next action (
|
|
249
|
+
5. Suggest the most useful next action (`/roadmap-next ROADMAP-NNNN`, further exploration, or a specific dependency decision to make)
|
|
305
250
|
|
|
306
251
|
---
|
|
307
252
|
|