@codewizard-dt/bootstrap 5.3.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.
Files changed (93) hide show
  1. package/README.md +11 -3
  2. package/bin/cli.js +16 -0
  3. package/lib/hooks/README.md +124 -3
  4. package/lib/hooks/claude-settings-guard.js +8 -2
  5. package/lib/prompts/README.md +1 -1
  6. package/lib/prompts/migrate-wiki.md +7 -7
  7. package/lib/scripts/README.md +111 -10
  8. package/lib/scripts/bootstrap-prefs-tui.js +1222 -0
  9. package/lib/scripts/install-global.sh +137 -6
  10. package/lib/scripts/migrate-project.sh +52 -10
  11. package/lib/scripts/rename-wiki-ids.js +232 -0
  12. package/lib/scripts/templates/CLAUDE-wiki.md +6 -6
  13. package/lib/scripts/templates/bootstrap-prefs-schema.json +11 -2
  14. package/lib/scripts/templates/settings-sandbox-unattended.json +36 -0
  15. package/lib/scripts/templates/settings-sandbox.json +7 -0
  16. package/lib/scripts/templates/wiki/conventions.md +9 -9
  17. package/lib/scripts/templates/wiki/dashboard.html +527 -23
  18. package/lib/scripts/templates/wiki/index.md +2 -2
  19. package/lib/scripts/templates/wiki/work/bugs/lifecycle.md +1 -1
  20. package/lib/scripts/templates/wiki/work/decisions/index.md +12 -4
  21. package/lib/scripts/templates/wiki/work/decisions/lifecycle.md +11 -9
  22. package/lib/scripts/templates/wiki/work/requirements/index.md +12 -4
  23. package/lib/scripts/templates/wiki/work/requirements/lifecycle.md +8 -8
  24. package/lib/scripts/templates/wiki/work/roadmaps/index.md +11 -3
  25. package/lib/scripts/templates/wiki/work/roadmaps/lifecycle.md +7 -5
  26. package/lib/scripts/templates/wiki/work/tasks/index.md +1 -1
  27. package/lib/scripts/templates/wiki/work/tasks/lifecycle.md +16 -8
  28. package/lib/scripts/templates/wiki/work/uat/lifecycle.md +3 -3
  29. package/lib/scripts/wiki-dashboard-server.js +98 -0
  30. package/lib/skills/README.md +27 -22
  31. package/lib/skills/_shared/ARCHIVE-WORK-ITEM.md +103 -0
  32. package/lib/skills/_shared/ID-RESOLUTION.md +142 -0
  33. package/lib/skills/_shared/SKILL-BOILERPLATE.md +50 -0
  34. package/lib/skills/adr-assess/SKILL.md +112 -0
  35. package/lib/skills/{decision-create → adr-create}/SKILL.md +26 -26
  36. package/lib/skills/adr-deprecate/SKILL.md +190 -0
  37. package/lib/skills/adr-extract/SKILL.md +255 -0
  38. package/lib/skills/{decision-finalize → adr-finalize}/SKILL.md +38 -38
  39. package/lib/skills/{decision-next → adr-next}/SKILL.md +20 -19
  40. package/lib/skills/{decision-walkthrough → adr-walkthrough}/SKILL.md +23 -29
  41. package/lib/skills/architecture-audit/SKILL.md +1 -1
  42. package/lib/skills/autopilot/SKILL.md +110 -0
  43. package/lib/skills/bootstrap-config/SKILL.md +1 -1
  44. package/lib/skills/bug-assess/SKILL.md +3 -3
  45. package/lib/skills/bug-close/SKILL.md +13 -27
  46. package/lib/skills/{bug-file → bug-create}/SKILL.md +10 -14
  47. package/lib/skills/bug-triage/SKILL.md +5 -19
  48. package/lib/skills/demo/SKILL.md +1 -1
  49. package/lib/skills/extract-feature/SKILL.md +3 -3
  50. package/lib/skills/git-commit/SKILL.md +4 -4
  51. package/lib/skills/port-feature/SKILL.md +3 -3
  52. package/lib/skills/power-mode/SKILL.md +42 -49
  53. package/lib/skills/prd-assess/SKILL.md +105 -0
  54. package/lib/skills/{req-compile → prd-compile}/SKILL.md +6 -13
  55. package/lib/skills/{req-create → prd-create}/SKILL.md +19 -19
  56. package/lib/skills/prd-deprecate/SKILL.md +173 -0
  57. package/lib/skills/{req-finalize → prd-finalize}/SKILL.md +20 -29
  58. package/lib/skills/primer/SKILL.md +2 -2
  59. package/lib/skills/research/SKILL.md +3 -3
  60. package/lib/skills/roadmap-assess/SKILL.md +20 -20
  61. package/lib/skills/roadmap-create/SKILL.md +19 -29
  62. package/lib/skills/roadmap-next/SKILL.md +16 -28
  63. package/lib/skills/security-audit/SKILL.md +1 -1
  64. package/lib/skills/tackle/SKILL.md +13 -15
  65. package/lib/skills/{task-audit → task-assess}/SKILL.md +34 -44
  66. package/lib/skills/task-close/SKILL.md +73 -0
  67. package/lib/skills/{task-add → task-create}/SKILL.md +25 -24
  68. package/lib/skills/uat-assess/SKILL.md +124 -0
  69. package/lib/skills/uat-auto/SKILL.md +9 -7
  70. package/lib/skills/uat-auto-plus/SKILL.md +2 -2
  71. package/lib/skills/{uat-generate → uat-create}/SKILL.md +10 -12
  72. package/lib/skills/uat-skip/SKILL.md +5 -9
  73. package/lib/skills/uat-walk/SKILL.md +2 -2
  74. package/lib/skills/uat-walk/UAT-CORE.md +29 -16
  75. package/lib/skills/update-docs/SKILL.md +1 -1
  76. package/lib/skills/usage-report/SKILL.md +52 -0
  77. package/lib/skills/usage-report/scripts/pricing.json +22 -0
  78. package/lib/skills/usage-report/scripts/usage-report.js +518 -0
  79. package/lib/skills/whats-next/SKILL.md +177 -0
  80. package/lib/skills/wiki-archive/SKILL.md +12 -23
  81. package/lib/skills/wiki-lint/SKILL.md +23 -13
  82. package/lib/skills/wiki-query/SKILL.md +1 -1
  83. package/lib/skills/wiki-rotate-log/SKILL.md +1 -1
  84. package/lib/skills/wiki-tidy/SKILL.md +6 -9
  85. package/package.json +1 -1
  86. package/lib/scripts/templates/wiki/work/decisions/archive/index.md +0 -10
  87. package/lib/scripts/templates/wiki/work/requirements/archive/index.md +0 -10
  88. package/lib/scripts/templates/wiki/work/roadmaps/archive/index.md +0 -10
  89. package/lib/skills/req-extract-decisions/SKILL.md +0 -241
  90. package/lib/skills/req-retire/SKILL.md +0 -185
  91. package/lib/skills/req-update/SKILL.md +0 -265
  92. package/lib/skills/task-trash/SKILL.md +0 -115
  93. package/lib/skills/task-update/SKILL.md +0 -136
@@ -32,7 +32,7 @@ open ──▶ triaged ──▶ in-progress ──▶ closed
32
32
  └──▶ wontfix | duplicate | cannot-reproduce
33
33
  ```
34
34
 
35
- - **open** — filed (`/bug-file`); required-on-report fields present.
35
+ - **open** — filed (`/bug-create`); required-on-report fields present.
36
36
  - **triaged** — priority/severity/assignee set (`/bug-triage`); decision to fix, defer, or reject.
37
37
  - **in-progress** — actively being fixed.
38
38
  - **closed** — fixed and verified (`/bug-close`): root cause + fix commit + regression test recorded.
@@ -1,12 +1,20 @@
1
1
  ---
2
2
  title: Decisions Index
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
- # Decisions — Active Items
6
+ # Decisions
7
7
 
8
- Lists **only active** Decision Groups — a group stays listed while at least one of its decisions is `proposed`. When every block is `accepted` or `superseded`, delete the group's line here — the file itself never moves; per-decision status lives in each block. See the [lifecycle](lifecycle.md).
8
+ Lists every Decision Group in two sections: **Active** and **Closed**. A group stays Active while at least one of its decisions is `proposed`. When every block is `accepted`, `deprecated`, or `superseded`, move the group's line from Active to Closed — the file itself never moves; per-decision status lives in each block. See the [lifecycle](lifecycle.md).
9
9
 
10
- Entry format: `- [DEC-NNNN — Title](DEC-NNNN-slug.md) — one-line summary · D1 proposed, D2 accepted, …`
10
+ ## Active
11
+
12
+ Entry format: `- [ADR-NNNN — Title](ADR-NNNN-slug.md) — one-line summary · D1 proposed, D2 accepted, …`
13
+
14
+ _(none yet)_
15
+
16
+ ## Closed
17
+
18
+ Entry format: `- [ADR-NNNN — Title](ADR-NNNN-slug.md) — one-line summary · D1 accepted, D2 superseded, …`
11
19
 
12
20
  _(none yet)_
@@ -1,13 +1,13 @@
1
1
  ---
2
2
  title: Decisions Lifecycle
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
6
  # Decisions Lifecycle
7
7
 
8
- Architecture Decision Records. Each file is a **Decision Group** containing one or more `## DM. <title>` decision blocks. ID scheme: **DEC-NNNN** (4-digit, zero-padded) for the group; **DEC-NNNN#DM** for an individual decision (e.g. `DEC-0001#D2`). Filename: `DEC-NNNN-slug.md`.
8
+ Architecture Decision Records. Each file is a **Decision Group** containing one or more `## DM. <title>` decision blocks. ID scheme: **ADR-NNNN** (4-digit, zero-padded) for the group; **ADR-NNNN#DM** for an individual decision (e.g. `ADR-0001#D2`). Filename: `ADR-NNNN-slug.md`. Existing `DEC-NNNN` items keep their IDs (resolved via `aliases:`) until the `npx … update` migration renames them.
9
9
 
10
- Active files are **never moved** after creation; per-decision state lives in each block's `status` field. When all decisions in a group are `accepted` or `superseded`, the group may be moved to [`archive/`](archive/) by `/wiki-archive`. The active set is tracked in [`index.md`](index.md) — a group stays listed while at least one of its decisions is `proposed`.
10
+ Files are **never moved** after creation; per-decision state lives in each block's `status` field. Finished groups are never moved — when all decisions in a group are `accepted`, `deprecated`, or `superseded`, the group stays in place and is listed under **Closed** in [`index.md`](index.md). A group stays listed under **Active** while at least one of its decisions is `proposed`.
11
11
 
12
12
  ## Frontmatter / per-decision schema
13
13
 
@@ -15,7 +15,7 @@ Group frontmatter:
15
15
 
16
16
  | Key | Required | Notes |
17
17
  |-----|----------|-------|
18
- | `id` | yes | `DEC-NNNN` |
18
+ | `id` | yes | `ADR-NNNN` (legacy `DEC-NNNN`) |
19
19
  | `title` | yes | decision-group title |
20
20
  | `created` / `updated` | yes | `YYYY-MM-DD` |
21
21
  | `tags` | yes | umbrella tags for the group |
@@ -24,19 +24,21 @@ Per-decision block (`## D1.`, `## D2.` …) metadata:
24
24
 
25
25
  | Field | Required | Notes |
26
26
  |-------|----------|-------|
27
- | Status | yes | `proposed \| accepted \| superseded` |
27
+ | Status | yes | `proposed \| accepted \| deprecated \| superseded` |
28
28
  | Date | yes | `YYYY-MM-DD` |
29
29
  | Deciders | yes | who decided |
30
30
  | Consulted / Informed | no | E-C-A-D-R inputs |
31
- | Supersedes | no | `DEC-NNNN#DM \| none` |
31
+ | Supersedes | no | `ADR-NNNN#DM \| none` |
32
32
  | Tags | yes | decision-area tags |
33
33
 
34
34
  ## Status transitions
35
35
 
36
36
  ```
37
37
  proposed ──▶ accepted ──▶ superseded
38
+ proposed / accepted ──▶ deprecated
38
39
  ```
39
40
 
40
- - **proposed** — drafted in a Decision Group (`/decision-create`); comparison tables + mermaid flowchart, no commitment.
41
- - **accepted** — finalized per-decision via `/decision-finalize` after an E-C-A-D-R audit. Siblings in the same group are untouched.
42
- - **superseded** — replaced by a later accepted decision; the new block sets `Supersedes:` and the old block is marked `superseded by DEC-NNNN#DM`. Both blocks updated atomically; old block preserved.
41
+ - **proposed** — drafted in a Decision Group (`/adr-create`); comparison tables + mermaid flowchart, no commitment.
42
+ - **accepted** — finalized per-decision via `/adr-finalize` after an E-C-A-D-R audit. Siblings in the same group are untouched.
43
+ - **superseded** — replaced by a later accepted decision; the new block sets `Supersedes:` and the old block is marked `superseded by ADR-NNNN#DM` (legacy `superseded by DEC-NNNN#DM` stays valid). Both blocks updated atomically; old block preserved. Set only by `/adr-finalize`.
44
+ - **deprecated** — withdrawn without a successor via `/adr-deprecate`; status-only — the block is preserved with a `> **Deprecated**` callout and the file never moves.
@@ -1,12 +1,20 @@
1
1
  ---
2
2
  title: Requirements Index
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
- # Requirements — Active Items
6
+ # Requirements
7
7
 
8
- Lists **only active** requirements (`draft`, `approved`). When an item leaves the active set (`retired`), delete its line here — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
8
+ Lists every requirement in two sections: **Active** (`draft`, `approved`) and **Closed** (`retired`). When a requirement is retired, move its line from Active to Closed — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
9
9
 
10
- Entry format: `- [REQ-NNNN — Title](REQ-NNNN-slug.md) — one-line summary · status`
10
+ ## Active
11
+
12
+ Entry format: `- [PRD-NNNN — Title](PRD-NNNN-slug.md) — one-line summary · status`
13
+
14
+ _(none yet)_
15
+
16
+ ## Closed
17
+
18
+ Entry format: `- [PRD-NNNN — Title](PRD-NNNN-slug.md) — one-line summary · retired`
11
19
 
12
20
  _(none yet)_
@@ -1,19 +1,19 @@
1
1
  ---
2
2
  title: Requirements Lifecycle
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
6
  # Requirements Lifecycle
7
7
 
8
- Requirements (PRDs) capture the problem, personas, user stories, success metrics, and non-goals for a body of work. ID scheme: **REQ-NNNN** (4-digit, zero-padded, globally unique). Filename: `REQ-NNNN-slug.md`.
8
+ Requirements (PRDs) capture the problem, personas, user stories, success metrics, and non-goals for a body of work. ID scheme: **PRD-NNNN** (4-digit, zero-padded, globally unique). Filename: `PRD-NNNN-slug.md`. Existing `REQ-NNNN` files keep their names until the `npx … update` migration renames them (the old ID is kept in `aliases:`).
9
9
 
10
- Active files are **never moved** after creation; state lives in the `status:` frontmatter field. Terminal items (`retired`) may be moved to [`archive/`](archive/) by `/wiki-archive`. The active set is tracked in [`index.md`](index.md).
10
+ Files are **never moved** after creation; state lives in the `status:` frontmatter field. Finished items are never moved — a terminal item (`retired`) stays in place and is listed under **Closed** in [`index.md`](index.md); `draft` and `approved` requirements are listed under **Active**.
11
11
 
12
12
  ## Frontmatter schema
13
13
 
14
14
  | Key | Required | Notes |
15
15
  |-----|----------|-------|
16
- | `id` | yes | `REQ-NNNN` |
16
+ | `id` | yes | `PRD-NNNN` (legacy `REQ-NNNN`) |
17
17
  | `title` | yes | short requirement name |
18
18
  | `status` | yes | `draft \| approved \| retired` |
19
19
  | `created` / `updated` | yes | `YYYY-MM-DD` |
@@ -21,7 +21,7 @@ Active files are **never moved** after creation; state lives in the `status:` fr
21
21
  | `stakeholders` | no | consulted/informed list |
22
22
  | `tags` | no | discovery only |
23
23
 
24
- Approved requirements are amended via append-only `## Amendment N` blocks, never edited in place.
24
+ Approved requirements are locked in substance; changes are made by editing the file directly (existing `## Amendment N` blocks are retained as history; no skill produces them). To supersede, create a new requirement with `/prd-create`, then `/prd-deprecate` the old one.
25
25
 
26
26
  ## Status transitions
27
27
 
@@ -29,6 +29,6 @@ Approved requirements are amended via append-only `## Amendment N` blocks, never
29
29
  draft ──▶ approved ──▶ retired
30
30
  ```
31
31
 
32
- - **draft** — under construction (`/req-create`); edited freely.
33
- - **approved** — completeness-audited and locked (`/req-finalize`); changes are append-only amendments (`/req-update`).
34
- - **retired** — superseded or no longer in force; preserved for history.
32
+ - **draft** — under construction (`/prd-create`); edited freely.
33
+ - **approved** — completeness-audited and locked (`/prd-finalize`); changes are made by editing the file directly (no amendment skill).
34
+ - **retired** — superseded or no longer in force; preserved for history; set via `/prd-deprecate` (status-only; the status keeps the name `retired`).
@@ -1,12 +1,20 @@
1
1
  ---
2
2
  title: Roadmaps Index
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
- # Roadmaps — Active Items
6
+ # Roadmaps
7
7
 
8
- Lists **only active** roadmaps (`active`). When a roadmap completes (`done`), delete its line here — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
8
+ Lists every roadmap in two sections: **Active** (`active`) and **Closed** (`done`). When a roadmap completes, move its line from Active to Closed — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
9
+
10
+ ## Active
9
11
 
10
12
  Entry format: `- [ROADMAP-NNNN — Title](ROADMAP-NNNN-slug.md) — one-line summary · N/M items checked`
11
13
 
12
14
  _(none yet)_
15
+
16
+ ## Closed
17
+
18
+ Entry format: `- [ROADMAP-NNNN — Title](ROADMAP-NNNN-slug.md) — one-line summary · done`
19
+
20
+ _(none yet)_
@@ -1,13 +1,15 @@
1
1
  ---
2
2
  title: Roadmaps Lifecycle
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
6
  # Roadmaps Lifecycle
7
7
 
8
8
  Execution-plan roadmaps: a goal, phases, and a hybrid checklist where each item is either a **task link** (`[TASK-NNNN](../tasks/TASK-NNNN-slug.md)`) or an **inline** checkbox item. ID scheme: **ROADMAP-NNNN** (4-digit, zero-padded). Filename: `ROADMAP-NNNN-slug.md`.
9
9
 
10
- Active files are **never moved** after creation; state lives in the `status:` frontmatter field. Terminal items (`done`) may be moved to [`archive/`](archive/) by `/wiki-archive`. The active set is tracked in [`index.md`](index.md).
10
+ Existing `ROADMAP-NNN` files created before 2026-09-13 keep their 3-digit names permanently; only IDs assigned after that date use 4 digits.
11
+
12
+ Files are **never moved** after creation; state lives in the `status:` frontmatter field. Finished items are never moved — a terminal item (`done`) stays in place and is listed under **Closed** in [`index.md`](index.md); the roadmaps still in progress are listed under **Active**.
11
13
 
12
14
  ## Frontmatter schema
13
15
 
@@ -18,8 +20,8 @@ Active files are **never moved** after creation; state lives in the `status:` fr
18
20
  | `status` | yes | `active \| done` |
19
21
  | `created` / `updated` | yes | `YYYY-MM-DD` |
20
22
  | `owner` | no | accountable person/role |
21
- | `linked_requirements` | no | `REQ-NNNN` back-links |
22
- | `linked_decisions` | no | `DEC-NNNN` back-links |
23
+ | `linked_requirements` | no | `PRD-NNNN` (or legacy `REQ-NNNN`) back-links |
24
+ | `linked_decisions` | no | `ADR-NNNN` (legacy `DEC-NNNN`) back-links |
23
25
  | `tags` | no | discovery only |
24
26
 
25
27
  ## Status transitions
@@ -28,5 +30,5 @@ Active files are **never moved** after creation; state lives in the `status:` fr
28
30
  active ──▶ done
29
31
  ```
30
32
 
31
- - **active** — at least one unchecked item remains. Items are added by editing the roadmap file directly, at creation via `/roadmap-create`, or via `/task-add --roadmap ROADMAP-NNNN` (auto-links a new task); task-linked items auto-check when their task completes.
33
+ - **active** — at least one unchecked item remains. Items are added by editing the roadmap file directly, at creation via `/roadmap-create`, or via `/task-create --roadmap ROADMAP-NNNN` (auto-links a new task); task-linked items auto-check when their task completes.
32
34
  - **done** — every checklist item is checked. Completion is implicit; flip `status` to `done` when the last box is ticked.
@@ -5,7 +5,7 @@ updated: 2026-06-11
5
5
 
6
6
  # Tasks — Active Items
7
7
 
8
- Lists **only active** tasks (`todo`, `in-progress`). When a task leaves the active set (`done`, `trashed`), delete its line here — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
8
+ Lists **only active** tasks (`todo`, `in-progress`, `pending-uat`). When a task leaves the active set (`done`, `trashed`), delete its line here — the file itself never moves; status lives in its frontmatter. See the [lifecycle](lifecycle.md).
9
9
 
10
10
  Entry format: `- [TASK-NNNN — Title](TASK-NNNN-slug.md) — one-line summary · status`
11
11
 
@@ -1,12 +1,14 @@
1
1
  ---
2
2
  title: Tasks Lifecycle
3
- updated: 2026-06-11
3
+ updated: 2026-09-20
4
4
  ---
5
5
 
6
6
  # Tasks Lifecycle
7
7
 
8
8
  Execution-ready task files with `## Steps` checklists. ID scheme: **TASK-NNNN** (4-digit, zero-padded). Filename: `TASK-NNNN-slug.md`. UAT test files mirror task naming (**UAT-NNNN**) and live in the sibling [`../uat/`](../uat/) family.
9
9
 
10
+ Existing `TASK-NNN` files created before 2026-09-13 keep their 3-digit names permanently; only IDs assigned after that date use 4 digits.
11
+
10
12
  Active files are **never moved** after creation; state lives in the `status:` frontmatter field. Terminal items (`done`, `trashed`) may be moved to [`archive/`](archive/) by `/wiki-archive`. The active set is tracked in [`index.md`](index.md).
11
13
 
12
14
  ## Frontmatter schema
@@ -15,7 +17,7 @@ Active files are **never moved** after creation; state lives in the `status:` fr
15
17
  |-----|----------|-------|
16
18
  | `id` | yes | `TASK-NNNN` |
17
19
  | `title` | yes | task title |
18
- | `status` | yes | `todo \| in-progress \| done \| trashed` |
20
+ | `status` | yes | `todo \| in-progress \| pending-uat \| done \| trashed` |
19
21
  | `created` / `updated` | yes | `YYYY-MM-DD` |
20
22
  | `depends_on` | no | `TASK-NNNN` IDs that must finish first |
21
23
  | `blocks` | no | `TASK-NNNN` IDs this one gates |
@@ -23,17 +25,23 @@ Active files are **never moved** after creation; state lives in the `status:` fr
23
25
  | `uat` | no | link to the matching `../uat/UAT-NNNN-slug.md` |
24
26
  | `tags` | no | discovery only |
25
27
 
28
+ **Dependency fields.** `depends_on`, `blocks`, and `parallel_safe_with` are YAML arrays of `TASK-NNNN` IDs (`[]` when empty) and are the **sole authoritative, machine-read** encoding of task dependencies (per DEC-0001#D4).
29
+ Edges should be symmetric: if A lists B in `blocks`, B lists A in `depends_on` — tooling flags asymmetry and never auto-corrects it.
30
+ A body `depends_on::[[TASK-NNNN]]` / `blocks::[[TASK-NNNN]]` typed-link line under the H1 is an optional mirror for graph views (Obsidian/Breadcrumbs) and is never read by tooling.
31
+ The legacy `> **Depends on**:` blockquote and `## Dependencies` body headings are not part of the schema.
32
+
26
33
  ## Status transitions
27
34
 
28
35
  ```
29
- todo ──▶ in-progress ──▶ done
30
- │ │
31
- └────────────┴──▶ trashed
36
+ todo ──▶ in-progress ──▶ pending-uat ──▶ done
37
+ │ │ │
38
+ └────────────┴──────────────┴──▶ trashed
32
39
  ```
33
40
 
34
- - **todo** — created by `/task-add`; not yet started.
41
+ - **todo** — created by `/task-create`; not yet started.
35
42
  - **in-progress** — being executed (`/tackle`). `/tackle` runs **static gates only** (typecheck, `bash -n`, lint, unit tests); runtime/E2E verification is the UAT phase.
36
- - **done** — implementation complete and its UAT passed (`/uat-walk` / `/uat-auto`) or was explicitly skipped (`/uat-skip`).
37
- - **trashed** — terminal; abandoned via `/task-trash` with the reason recorded in the file. The matching UAT is trashed alongside.
43
+ - **pending-uat** — implementation complete: every `## Steps` checkbox is checked and `/tackle` set this status. Awaiting verification — `/uat-create` if no UAT exists yet, then `/uat-walk` / `/uat-auto`. Still an active state (stays listed in `index.md`).
44
+ - **done** — verification finished — its UAT passed (`/uat-walk` / `/uat-auto`) or was explicitly skipped (`/uat-skip`).
45
+ - **trashed** — terminal; abandoned via `/task-close` with the reason recorded in the file. The matching UAT is trashed alongside.
38
46
 
39
47
  A task reaches **done** only when its UAT is all-pass or skipped — see the [UAT lifecycle](../uat/lifecycle.md).
@@ -33,15 +33,15 @@ pending ──▶ in-progress ──▶ passed
33
33
  │ ▲
34
34
  ├──▶ failed ───┘ (rerun after fixes)
35
35
  pending ──▶ skipped (/uat-skip — intentional skip, skeleton documents why)
36
- any ──▶ trashed (/task-trash — task abandoned; reason recorded)
36
+ any ──▶ trashed (/task-close — task abandoned; reason recorded)
37
37
  ```
38
38
 
39
- - **pending** — created by `/uat-generate`; not yet executed.
39
+ - **pending** — created by `/uat-create`; not yet executed.
40
40
  - **in-progress** — being walked (`/uat-walk`) or run headlessly (`/uat-auto`).
41
41
  - **passed** — every test `[x]`; the matching task flips to `done`.
42
42
  - **failed** — one or more `[FAIL: …]` markers after a full run; flips back to `in-progress` on rerun.
43
43
  - **skipped** — UAT deliberately not run (`/uat-skip`); the file records why.
44
- - **trashed** — terminal; the task was trashed (`/task-trash`); reason recorded in the file.
44
+ - **trashed** — terminal; the task was trashed (`/task-close`); reason recorded in the file.
45
45
 
46
46
  A task reaches **done** only when its UAT is `passed` or `skipped`. See the [tasks lifecycle](../tasks/lifecycle.md).
47
47
 
@@ -3,14 +3,24 @@
3
3
  // Zero-dependency static file server for the live wiki dashboard.
4
4
  // Serves the dashboard HTML client (bundled next to this script) and the
5
5
  // target project's wiki/ tree read-only over HTTP. Node builtins only.
6
+ // It also serves the /usage-report script's JSON at /api/usage by running a
7
+ // fixed, package-owned script with fixed arguments, never with request data.
8
+ // WIKI_DASHBOARD_USAGE_SCRIPT overrides the script path; when set, it is the
9
+ // only candidate (a missing file means /api/usage answers 404).
6
10
 
7
11
  const http = require('http');
8
12
  const fs = require('fs');
13
+ const os = require('os');
9
14
  const path = require('path');
15
+ const { execFile } = require('child_process');
10
16
 
11
17
  const DEFAULT_PORT = 4317;
12
18
  const MAX_PORT_ATTEMPTS = 10;
13
19
 
20
+ const USAGE_TIMEOUT_MS = 15000;
21
+ const USAGE_MAX_BYTES = 10 * 1024 * 1024;
22
+ const USAGE_CACHE_TTL_MS = 30000;
23
+
14
24
  // --- CLI arg parsing (simple/positional) --------------------------------
15
25
  // First non-flag arg = project directory (default process.cwd())
16
26
  // `--port <n>` OR a positional numeric arg = port (default 4317)
@@ -80,6 +90,88 @@ function serveFile(res, filePath) {
80
90
  });
81
91
  }
82
92
 
93
+ // --- /api/usage ----------------------------------------------------------
94
+ // An env override is authoritative: if set but missing, do not fall back.
95
+ function resolveUsageScript() {
96
+ const override = process.env.WIKI_DASHBOARD_USAGE_SCRIPT;
97
+ if (override) {
98
+ return fs.existsSync(override) ? override : null;
99
+ }
100
+ const candidates = [
101
+ path.join(__dirname, '..', 'skills', 'usage-report', 'scripts', 'usage-report.js'),
102
+ path.join(os.homedir(), '.claude', 'skills', 'usage-report', 'scripts', 'usage-report.js'),
103
+ ];
104
+ for (const candidate of candidates) {
105
+ if (fs.existsSync(candidate)) return candidate;
106
+ }
107
+ return null;
108
+ }
109
+
110
+ let usageCache = null; // { at, body } — keyed by time only, successes only
111
+ let usagePending = null; // callbacks waiting on the in-flight run (single-flight)
112
+
113
+ function runUsageReport(callback) {
114
+ const script = resolveUsageScript();
115
+ if (script === null) {
116
+ callback(new Error('usage-report-unavailable'));
117
+ return;
118
+ }
119
+ if (usageCache && Date.now() - usageCache.at < USAGE_CACHE_TTL_MS) {
120
+ callback(null, usageCache.body);
121
+ return;
122
+ }
123
+ if (usagePending) {
124
+ usagePending.push(callback);
125
+ return;
126
+ }
127
+ usagePending = [callback];
128
+
129
+ execFile(
130
+ process.execPath,
131
+ [script, '--project', projectDir],
132
+ { timeout: USAGE_TIMEOUT_MS, maxBuffer: USAGE_MAX_BYTES, windowsHide: true },
133
+ (err, stdout) => {
134
+ let failure = err;
135
+ if (!failure) {
136
+ try {
137
+ const parsed = JSON.parse(stdout);
138
+ if (parsed === null || typeof parsed !== 'object' || Array.isArray(parsed)) {
139
+ failure = new Error('unexpected usage-report output');
140
+ }
141
+ } catch (e) {
142
+ failure = e;
143
+ }
144
+ }
145
+ if (!failure) usageCache = { at: Date.now(), body: stdout };
146
+
147
+ const callbacks = usagePending;
148
+ usagePending = null;
149
+ callbacks.forEach((cb) => (failure ? cb(failure) : cb(null, stdout)));
150
+ }
151
+ );
152
+ }
153
+
154
+ // Bodies are fixed strings: never stderr, err.message, script path, or projectDir.
155
+ function sendUsageJson(res, status, body) {
156
+ res.writeHead(status, noCacheHeaders({ 'Content-Type': 'application/json' }));
157
+ res.end(body);
158
+ }
159
+
160
+ function serveUsageReport(res) {
161
+ const script = resolveUsageScript();
162
+ if (script === null) {
163
+ sendUsageJson(res, 404, JSON.stringify({ error: 'usage-report-unavailable' }));
164
+ return;
165
+ }
166
+ runUsageReport((err, body) => {
167
+ if (err) {
168
+ sendUsageJson(res, 500, JSON.stringify({ error: 'usage-report-failed' }));
169
+ return;
170
+ }
171
+ sendUsageJson(res, 200, body);
172
+ });
173
+ }
174
+
83
175
  function requestHandler(req, res) {
84
176
  if (req.method !== 'GET') {
85
177
  send(res, 405, 'Method Not Allowed');
@@ -123,6 +215,12 @@ function requestHandler(req, res) {
123
215
  return;
124
216
  }
125
217
 
218
+ // Usage report JSON (exact match; /api/usage/ and deeper paths stay 404).
219
+ if (urlPath === '/api/usage') {
220
+ serveUsageReport(res);
221
+ return;
222
+ }
223
+
126
224
  send(res, 404, 'Not Found');
127
225
  }
128
226
 
@@ -2,7 +2,7 @@
2
2
 
3
3
  One directory per Claude Code skill, each containing a `SKILL.md` (Skills directory format). `install-global.sh` copies this whole folder verbatim to `~/.claude/skills/`, which makes every skill below available as a `/slash-command` in any Claude Code session on the machine — not just in this repo.
4
4
 
5
- Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLAUDE.md`; a handful are general-purpose utilities unrelated to the wiki. `uat-walk/` is the one skill with an extra file beyond `SKILL.md` — `UAT-CORE.md`, a shared module of UAT walkthrough logic factored out so other UAT skills (`uat-auto`, `uat-auto-plus`) can reference it instead of duplicating it.
5
+ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLAUDE.md`; a handful are general-purpose utilities unrelated to the wiki. Two things sit beside the per-skill `SKILL.md` files: `uat-walk/UAT-CORE.md`, a shared module of UAT walkthrough logic factored out so other UAT skills (`uat-auto`, `uat-auto-plus`) can reference it instead of duplicating it, and the `_shared/` directory, which holds reference docs (for example `ARCHIVE-WORK-ITEM.md`, `ID-RESOLUTION.md`, and `SKILL-BOILERPLATE.md` — the Prereqs grammar, Edit hygiene, and Number allocation) that several skills point at instead of restating. `_shared/` has no `SKILL.md` and is not a slash command.
6
6
 
7
7
  ## Wiki operations
8
8
 
@@ -11,29 +11,31 @@ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLA
11
11
  | `wiki-ingest` | Process a source from `raw/` into the wiki — summary page, entity/concept updates, index + log entry |
12
12
  | `wiki-query` | Answer a question from the wiki with citations; auto-ingest relevant un-ingested `raw/` sources when coverage is missing; offer to file the answer back as a new page |
13
13
  | `wiki-lint` | Health-check the wiki — contradictions, stale claims, orphan pages, missing concept pages, missing cross-references, never-ingested raw sources |
14
- | `wiki-archive` | Batch-move terminal work items into `<family>/archive/`, update `archive/index.md`, log the operation |
14
+ | `wiki-archive` | Batch-move terminal tasks, UAT and bugs into `<family>/archive/`, update `archive/index.md`, log the operation (roadmaps, decisions and requirements close in place and are never archived) |
15
15
  | `wiki-rotate-log` | Rotate `wiki/log.md` into a timestamped archive file once it exceeds ~500 lines |
16
- | `wiki-tidy` | One-shot cleanup: lint, archive terminal items across all families, rotate the log if overgrown — phases confirmed in sequence |
16
+ | `wiki-tidy` | One-shot cleanup: lint, archive terminal tasks/UAT/bugs, rotate the log if overgrown — phases confirmed in sequence |
17
17
 
18
18
  ## Requirements
19
19
 
20
20
  | Skill | Purpose |
21
21
  |-------|---------|
22
- | `req-create` | Draft a new requirement (REQ-NNNN) via Socratic Q&A — problem, personas, user stories, success metrics, non-goals |
23
- | `req-finalize` | Run a completeness audit on a draft requirement, resolve gaps via Q&A, flip `status: draft → approved` |
24
- | `req-extract-decisions` | Extract Architecturally Significant Requirements from an approved requirement and propose Decision Group candidates |
25
- | `req-update` | Amend an approved requirement with a tracked, append-only Amendment block; direct edits for drafts |
26
- | `req-compile` | Compile a requirement into a running, self-verifying system — routes every claim to its cheapest re-runnable check |
27
- | `req-retire` | Retire a requirement — set `status: retired`, document why, move to `archive/`, log it |
22
+ | `prd-create` | Draft a new requirement (PRD-NNNN) via Socratic Q&A — problem, personas, user stories, success metrics, non-goals |
23
+ | `prd-finalize` | Run a completeness audit on a draft requirement, resolve gaps via Q&A, flip `status: draft → approved` |
24
+ | `prd-compile` | Compile a requirement into a running, self-verifying system — routes every claim to its cheapest re-runnable check |
25
+ | `prd-deprecate` | Deprecate a PRD — set `status: retired`, document why, move its index row to Closed, log it; the file never moves |
26
+ | `prd-assess` | Survey all active PRDs together — flag approved requirements with no downstream ADRs or tasks and stale drafts, detect blocking open decisions, and rank them into one prioritized list with a status update for each (read-only) |
28
27
 
29
28
  ## Decisions
30
29
 
31
30
  | Skill | Purpose |
32
31
  |-------|---------|
33
- | `decision-create` | Create a Decision Group file with one or more proposed decisions, table-only comparisons, and mermaid flowcharts |
34
- | `decision-finalize` | Finalize a single proposed decision — E-C-A-D-R audit, supersession check, flip to `accepted` |
35
- | `decision-walkthrough` | Walk a decision file decision-by-decision, confirming each architecture choice with the user via Q&A |
36
- | `decision-next` | Read-only — find the first accepted decision missing a task reference; suggest `/task-add` |
32
+ | `adr-extract` | Extract Architecturally Significant Requirements from a PRD (or any document), cross-check existing ADRs, and propose Decision Group candidates for `/adr-create` |
33
+ | `adr-create` | Create a Decision Group file with one or more proposed decisions, table-only comparisons, and mermaid flowcharts |
34
+ | `adr-finalize` | Finalize a single proposed decision — E-C-A-D-R audit, supersession check, flip to `accepted` |
35
+ | `adr-walkthrough` | Walk a decision file decision-by-decision, confirming each architecture choice with the user via Q&A |
36
+ | `adr-deprecate` | Deprecate a single accepted decision (no successor) — set `status: deprecated`, document why, move its index row to Closed, log it; the file never moves |
37
+ | `adr-next` | Read-only — find the first accepted decision missing a task reference; suggest `/task-create` |
38
+ | `adr-assess` | Survey all active ADRs together — surface proposed decisions and accepted decisions with no task, follow supersession chains, and rank decision blocks into one prioritized list with a status update for each (read-only) |
37
39
 
38
40
  ## Roadmaps
39
41
 
@@ -41,32 +43,33 @@ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLA
41
43
  |-------|---------|
42
44
  | `roadmap-create` | Create an execution-plan roadmap via short Socratic Q&A — goal, phases, hybrid task-link/inline checklist |
43
45
  | `roadmap-assess` | Survey all active roadmaps together — cross-roadmap dependencies, prioritized list, status update per roadmap |
44
- | `roadmap-next` | Point at the first unchecked item(s) in a single roadmap (argument required), grouped into parallelizable waves; auto-archive when fully checked |
46
+ | `roadmap-next` | Point at the first unchecked item(s) in a single roadmap (argument required), grouped into parallelizable waves; flips a fully checked roadmap to `done` and moves its index row to Closed (file stays in place) |
45
47
 
46
48
  ## Tasks
47
49
 
48
50
  | Skill | Purpose |
49
51
  |-------|---------|
50
- | `task-add` | Create a structured, execution-ready task file in `wiki/work/tasks/` |
51
- | `task-update` | Assess and modify an existing task's scope or steps |
52
- | `task-audit` | Generate a dependency graph of active tasks — what blocks what, what can run in parallel; flags unannotated implementations |
53
- | `task-trash` | Trash a task and its related UAT files — move to `archive/`, remove all active-index references |
52
+ | `task-create` | Create a structured, execution-ready task file in `wiki/work/tasks/` |
53
+ | `task-assess` | Generate a dependency graph of active tasks — what blocks what, what can run in parallel; flags unannotated implementations |
54
+ | `task-close` | Close out an abandoned task and its related UAT files — set status `trashed`, move to `archive/`, remove all active-index references |
54
55
 
55
56
  ## UAT (user acceptance testing)
56
57
 
57
58
  | Skill | Purpose |
58
59
  |-------|---------|
59
- | `uat-generate` | Generate UAT tests in `wiki/work/uat/` for a task |
60
+ | `uat-create` | Create UAT tests in `wiki/work/uat/` for a task |
60
61
  | `uat-walk` | Interactively walk a pending UAT file test-by-test with the user (shares logic via `UAT-CORE.md`) |
61
62
  | `uat-auto` | Non-interactively run every test in a pending UAT file and auto-judge verdicts (headless, fail-closed) |
62
63
  | `uat-auto-plus` | Autonomous-fix variant of `uat-auto` — diagnoses failures, fixes them, re-runs until green or attempts exhausted; for `--dangerously-skip-permissions` agents |
63
64
  | `uat-skip` | Skip UAT for a task — set UAT and task `status: skipped/done`, remove index rows, auto-checkoff the roadmap |
65
+ | `uat-assess` | Survey all active UATs together — group them by what each is waiting on (failing cases, partial walks, auto-runnable, manual-only cases, stubs), rank by what each unblocks, and give a status update with a suggested next command for each (read-only) |
66
+ | `whats-next` | Survey ALL open work across every family — tasks (in or out of a roadmap), UATs, bugs, roadmaps, ADR blocks and PRDs — and rank one prioritized do-next list with parallel waves (read-only) |
64
67
 
65
68
  ## Bugs
66
69
 
67
70
  | Skill | Purpose |
68
71
  |-------|---------|
69
- | `bug-file` | File a new bug report with required-on-report fields; append it to the bug index |
72
+ | `bug-create` | Create a new bug report with required-on-report fields; append it to the bug index |
70
73
  | `bug-assess` | Survey all active bugs together — batch-triage any still-open reports first, then rank the active set by priority, severity, and impact into a single prioritized fix order with a status update for each bug |
71
74
  | `bug-triage` | Set priority/assignee/tags/impact, then advance to `in-progress`, keep `triaged`, or reject (wontfix/duplicate/cannot-reproduce) and archive |
72
75
  | `bug-close` | Close an in-progress bug — record root cause and resolution, require a regression test, move to `archive/` |
@@ -85,7 +88,8 @@ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLA
85
88
  |-------|---------|
86
89
  | `now` | Plan and delegate a task to subagents (max 3 concurrent) |
87
90
  | `tackle` | Execute an outlined task file step-by-step with subagent delegation |
88
- | `power-mode` | Orchestrator for parallel agent teams — drives roadmap or task files through the full tackle → uat-generate → uat-auto pipeline |
91
+ | `power-mode` | Orchestrator for parallel agent teams — drives roadmap or task files through the full tackle → uat-create → uat-auto pipeline |
92
+ | `autopilot` | One unattended tick for `/loop 1h /autopilot` — if idle, `/whats-next` then `/power-mode` on the first drivable item; if no work is left, `/research` similar products against this codebase; if still none, create a roadmap from the newest research |
89
93
 
90
94
  ## Docs & quality
91
95
 
@@ -98,6 +102,7 @@ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLA
98
102
  | `demo` | Audit all project functionality and produce a 2-3 minute demo run book plus a Marp slideshow |
99
103
  | `gap-assess` | Audit actual vs. expected functionality; produce an approvable gap-assessment plan (subagent-delegated, runs in plan mode) |
100
104
  | `debug-logs` | Diagnose points of failure from session context, running processes, and log stores; produce ranked likely causes without applying fixes |
105
+ | `usage-report` | Locally parse session logs for per-project token/cost rollups by model and skill (offline, read-only) |
101
106
 
102
107
  ## Security
103
108
 
@@ -143,7 +148,7 @@ Most skills operate on the LLM Wiki (`wiki/`, `raw/`) described in the root `CLA
143
148
 
144
149
  ## Conventions
145
150
 
146
- - Every skill directory name matches its slash-command name (`lib/skills/req-create/` → `/req-create`).
151
+ - Every skill directory name matches its slash-command name (`lib/skills/prd-create/` → `/prd-create`).
147
152
  - Frontmatter in each `SKILL.md` (`name`, `description`, optional `category`/`model`) drives Claude Code's skill picker — the `description` is what decides relevance, so it should stay specific about triggers and scope.
148
153
  - Skills that read/write the wiki follow the family lifecycle files under `wiki/work/*/lifecycle.md` in the target project, not anything hardcoded here — this repo's own `wiki/` is just the reference instance.
149
154
  - New skills should be added as a new subdirectory with a `SKILL.md`, then listed in the appropriate table above and in the root `CLAUDE.md` Custom Commands table.