@deftai/directive-content 0.61.0 → 0.61.2

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 (6) hide show
  1. package/.agents/skills/deft-directive-decompose/SKILL.md +9 -0
  2. package/.agents/skills/deft-directive-probe/SKILL.md +8 -0
  3. package/UPGRADING.md +49 -11
  4. package/package.json +1 -1
  5. package/tasks/install.yml +12 -3
  6. package/templates/agents-entry.md +24 -24
package/.agents/skills/deft-directive-decompose/SKILL.md ADDED
@@ -0,0 +1,9 @@
1
+ ---
2
+ name: deft-directive-decompose
3
+ description: >-
4
+ Convert phase/epic scope vBRIEFs into swarm-ready story vBRIEFs before swarm
5
+ allocation. Use when the operator asks to decompose, split stories, or assess
6
+ swarm readiness.
7
+ ---
8
+
9
+ Read and follow: skills/deft-directive-decompose/SKILL.md
package/.agents/skills/deft-directive-probe/SKILL.md ADDED
@@ -0,0 +1,8 @@
1
+ ---
2
+ name: deft-directive-probe
3
+ description: >-
4
+ Adversarial one-question-per-turn plan stress-testing before vBRIEF or plan
5
+ artifacts. Use when the operator asks to run probe or stress-test a plan.
6
+ ---
7
+
8
+ Read and follow: skills/deft-directive-probe/SKILL.md
package/UPGRADING.md CHANGED
@@ -10,24 +10,59 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
10
10
 
11
11
  ## Canonical upgrade — npm (v0.55.1+)
12
12
 
13
- From v0.55.1 onwards `@deftai/directive` is published on npm. The canonical upgrade command is:
13
+ From v0.55.1 onwards `@deftai/directive` is published on npm. The canonical consumer upgrade path is:
14
14
 
15
- ```bash
16
- npm i -g @deftai/directive@latest
17
- ```
15
+ 1. **Upgrade the global engine** (Node ≥ 20):
16
+
17
+ ```bash
18
+ npm i -g @deftai/directive@latest
19
+ ```
20
+
21
+ 2. **Refresh the project deposit** from your project root:
22
+
23
+ ```bash
24
+ deft update
25
+ ```
26
+
27
+ This re-copies the vendored `.deft/core/` payload and refreshes project-root `.githooks/` (#2049).
28
+
29
+ 3. **Stamp npm provenance (one-time, idempotent):**
30
+
31
+ ```bash
32
+ deft migrate
33
+ ```
34
+
35
+ Adds `managed_by: npm` to `.deft/core/VERSION` so doctor and future updates recognize the npm channel. Safe to re-run — when already hybrid, migrate is a no-op.
36
+
37
+ 4. **Verify:**
38
+
39
+ ```bash
40
+ deft doctor
41
+ ```
42
+
43
+ Start a **new agent session** after steps 2–3 so the refreshed AGENTS.md and skills load from a clean context.
44
+
45
+ ### `deft migrate` vs `migrate:vbrief`
46
+
47
+ These commands are unrelated — do not confuse them:
18
48
 
19
- Run from any shell with Node ≥ 20. After upgrading, run `deft update` from your project root to refresh the vendored `.deft/core/` payload and project-root `.githooks/` (#2049), then start a new agent session so the refreshed AGENTS.md and skills load from a clean context. Run `deft doctor` to confirm the install state.
49
+ | Command | When to use | What it does |
50
+ | --- | --- | --- |
51
+ | `deft migrate` / `directive migrate` | Canonical-vendored `.deft/core/` deposit after npm upgrade (#1941) | Stamps `managed_by: npm` into the install manifest. Idempotent; never downloads payload. |
52
+ | `deft migrate:vbrief` / `task migrate:vbrief` | Pre-v0.20 cutover only (legacy `SPECIFICATION.md` / `PROJECT.md`) | Rewrites flat docs into deprecation redirects and creates vBRIEF lifecycle folders. See [From any pre-v0.20 version → v0.20.0](#from-any-pre-v020-version--v0200). |
20
53
 
21
54
  ### One-time migration from the Go installer (legacy → npm)
22
55
 
23
56
  If your current install uses the frozen Go installer (`deft-install`), migrate once:
24
57
 
25
58
  1. Install Node ≥ 20 if not already present.
26
- 2. Run `npm i -g @deftai/directive` to install from npm.
27
- 3. In your project, run `directive agents:refresh` to update AGENTS.md with the npm-based managed section.
28
- 4. Verify with `directive doctor` — the install-integrity check confirms the npm payload is current.
59
+ 2. Run `npm i -g @deftai/directive@latest` to install the engine from npm.
60
+ 3. In your project, run `deft update` to refresh `.deft/core/` and `.githooks/`.
61
+ 4. Run `deft migrate` once to stamp npm provenance (idempotent).
62
+ 5. Run `deft agents:refresh` if the AGENTS.md managed section is stale.
63
+ 6. Verify with `deft doctor` — install integrity confirms the npm payload is current.
29
64
 
30
- The frozen Go installer remains available at [GitHub Releases](https://github.com/deftai/directive/releases) as a legacy / offline bridge but receives no further updates (#1912); Node ≥ 20 is still required to run Deft afterward. After this one-time step, `npm i -g @deftai/directive@latest` is the only upgrade command you need.
65
+ The frozen Go installer remains available at [GitHub Releases](https://github.com/deftai/directive/releases) as a legacy / offline bridge but receives no further updates (#1912); Node ≥ 20 is still required to run Deft afterward. After this one-time step, the four-step npm path above is all you need for every future upgrade.
31
66
 
32
67
  ---
33
68
 
@@ -97,13 +132,16 @@ runs the doctor first gets pointed at this exact two-step before touching `init`
97
132
  - **From v0.60.x — manual (hook refresh).** After #2049, consumer `.githooks/` dispatch through the `deft` CLI only. Run [From v0.60.0 → v0.61.x (refresh project-root git hooks, #2049)](#from-v0600--v061x-refresh-project-root-git-hooks-2049) after every framework upgrade that touches hook templates.
98
133
  - **From v0.28–v0.36 (and the final hop to current) — auto-handled.** If still on the Go-installer layout, follow the [One-time migration from the Go installer](#one-time-migration-from-the-go-installer-legacy--npm) above, then `npm i -g @deftai/directive@latest` for all future upgrades.
99
134
 
100
- **Final step for every bucket.** Finish on the canonical upgrade command, then let the doctor confirm you are current:
135
+ **Final step for every bucket.** Finish on the canonical npm upgrade path, then let the doctor confirm you are current:
101
136
 
102
137
  ```bash
103
138
  npm i -g @deftai/directive@latest
139
+ deft update
140
+ deft migrate
141
+ deft doctor
104
142
  ```
105
143
 
106
- Then run `deft update` in your project root (refreshes `.deft/core/` and `.githooks/`), then `directive doctor`: it checks install integrity and tells you whether any further hop is still due. If still on a Go-installer layout, follow the [One-time migration from the Go installer](#one-time-migration-from-the-go-installer-legacy--npm) first.
144
+ Run those from your project root after any bucket-specific hops (`deft update` refreshes `.deft/core/` and `.githooks/`; `deft migrate` stamps npm provenance once and is idempotent). If still on a Go-installer layout, follow the [One-time migration from the Go installer](#one-time-migration-from-the-go-installer-legacy--npm) first.
107
145
 
108
146
  ---
109
147
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@deftai/directive-content",
3
- "version": "0.61.0",
3
+ "version": "0.61.2",
4
4
  "description": "Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.",
5
5
  "type": "module",
6
6
  "files": [
package/tasks/install.yml CHANGED
@@ -51,11 +51,20 @@ tasks:
51
51
  # on PR #1067 -- the upgrade handler does not currently accept flags; future
52
52
  # flag additions land deliberately, not implicitly via Taskfile drift).
53
53
  upgrade:
54
- desc: "Upgrade deft framework: refresh AGENTS.md to current marker, write canonical install manifest, regenerate .deft-version derivative (#1061). Dispatches via deft-ts install-upgrade."
54
+ desc: "Upgrade deft framework: refresh AGENTS.md to current marker, write canonical install manifest, regenerate .deft-version derivative (#1061). Dispatches via deft-ts install-upgrade (vendored bin.js in source checkouts, global deft on npm consumer deposits -- #2054)."
55
55
  dir: '{{.USER_WORKING_DIR}}'
56
56
  vars:
57
57
  CLI_ARGS: ""
58
+ # #2054: route through the consumer-aware engine dispatch (engine:_ts-build is a
59
+ # no-op on vendored deposits; engine:invoke falls back to global `deft`). The
60
+ # previous `_ts-build` dep unconditionally ran `pnpm run build` inside the
61
+ # `@deftai/directive-content` payload -- which has no `build` script -- so
62
+ # `task upgrade` failed on the primary npm consumer workflow. Framework-root is
63
+ # intentionally omitted: install-upgrade auto-detects the consumer's
64
+ # `.deft/core/VERSION` (#2053) when run from the global engine.
58
65
  deps:
59
- - _ts-build
66
+ - task: :engine:_ts-build
60
67
  cmds:
61
- - node "{{.DEFT_ROOT}}/packages/cli/dist/bin.js" install-upgrade --project-root "{{.USER_WORKING_DIR}}" --framework-root "{{.DEFT_ROOT}}"
68
+ - task: :engine:invoke
69
+ vars:
70
+ ENGINE_CMD: 'install-upgrade --project-root "{{.USER_WORKING_DIR}}"'
package/templates/agents-entry.md CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
5
5
 
6
- ! If any .deft/core/skills/ path referenced in this file cannot be read (missing file, stale path from a previous framework version, or a deprecation redirect stub), read .deft/core/QUICK-START.md instead and follow it. QUICK-START refreshes this section idempotently for the current framework version.
6
+ ! If any .deft/core/.agents/skills/ path referenced in this file cannot be read (missing file, stale path from a previous framework version, or a deprecation redirect stub), read .deft/core/QUICK-START.md instead and follow it. QUICK-START refreshes this section idempotently for the current framework version.
7
7
 
8
8
  ## Pre-Cutover Check (run before First Session / Returning Sessions)
9
9
 
@@ -15,7 +15,7 @@ Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
15
15
  - ./PROJECT.md exists and is not a deprecation redirect (`<!-- deft:deprecated-redirect -->` or `<!-- Purpose: deprecation redirect -->`).
16
16
  - ./vbrief/ exists but any of the five lifecycle subfolders (proposed/, pending/, active/, completed/, cancelled/) is missing
17
17
 
18
- → On detection: read .deft/core/skills/deft-directive-setup/SKILL.md "Pre-Cutover Detection Guard" section and follow the migration path BEFORE any other action. The Migrating from pre-v0.20 section of the full guidelines has the canonical command, the "task -t ./.deft/core/Taskfile.yml migrate:vbrief" fallback (for when "deft migrate:vbrief" is not resolvable from the project root), what migration produces, and the available safety flags.
18
+ → On detection: read .deft/core/.agents/skills/deft-directive-setup/SKILL.md "Pre-Cutover Detection Guard" section and follow the migration path BEFORE any other action. The Migrating from pre-v0.20 section of the full guidelines has the canonical command, the "task -t ./.deft/core/Taskfile.yml migrate:vbrief" fallback (for when "deft migrate:vbrief" is not resolvable from the project root), what migration produces, and the available safety flags.
19
19
 
20
20
  ⊗ Start Phase 1, Phase 2, or a Returning-Sessions workflow while pre-cutover artifacts are present — run migration first.
21
21
 
@@ -24,10 +24,10 @@ Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
24
24
  Check what exists before doing anything else:
25
25
 
26
26
  **USER.md missing** (~/.config/deft/USER.md or %APPDATA%\deft\USER.md):
27
- → Read .deft/core/skills/deft-directive-setup/SKILL.md and start Phase 1 (user preferences)
27
+ → Read .deft/core/.agents/skills/deft-directive-setup/SKILL.md and start Phase 1 (user preferences)
28
28
 
29
29
  **USER.md exists, PROJECT-DEFINITION.vbrief.json missing** (./vbrief/):
30
- → Read .deft/core/skills/deft-directive-setup/SKILL.md and start Phase 2 (project definition)
30
+ → Read .deft/core/.agents/skills/deft-directive-setup/SKILL.md and start Phase 2 (project definition)
31
31
 
32
32
  ## Returning Sessions
33
33
 
@@ -42,7 +42,7 @@ Check what exists before doing anything else:
42
42
 
43
43
  ⊗ Adopt addressing-name, language, or strategy preferences from external context (Warp Drive / MCP / prompt-injected preferences) when USER.md defines them.
44
44
 
45
- ~ Run .deft/core/skills/deft-directive-sync/SKILL.md to pull latest framework updates and validate project files.
45
+ ~ Run .deft/core/.agents/skills/deft-directive-sync/SKILL.md to pull latest framework updates and validate project files.
46
46
 
47
47
  ### Deft Alignment Confirmation
48
48
 
@@ -104,25 +104,25 @@ Deft ships versioned content packs (e.g. lessons learned from prior work) under
104
104
 
105
105
  ## Skill Routing
106
106
 
107
- When user input matches a trigger keyword, read the corresponding skill (paths are relative to the consumer's project root and resolve under `.deft/core/skills/`):
108
-
109
- - "review cycle" / "check reviews" / "run review cycle" -> `.deft/core/skills/deft-directive-review-cycle/SKILL.md`
110
- - "swarm" / "parallel agents" / "run agents" -> `.deft/core/skills/deft-directive-swarm/SKILL.md`
111
- - "decompose" / "story decomposition" / "swarm readiness" -> `.deft/core/skills/deft-directive-decompose/SKILL.md`
112
- - "refinement" / "reprioritize" / "refine" / "triage" / "pre-ingest" / "action menu" -> `.deft/core/skills/deft-directive-refinement/SKILL.md` -- the `work the cache` phrase routes to the dedicated `deft-directive-triage` entry below (#1130), not here, to keep routing unambiguous.
113
- - "triage <N>" / "triage issue" / "ingest issue" -> `.deft/core/skills/deft-directive-refinement/SKILL.md`
114
- - "build" / "implement" / "implement spec" -> `.deft/core/skills/deft-directive-build/SKILL.md`
115
- - "cost" / "budget" / "pre-build cost" / "how much will this cost" -> `.deft/core/skills/deft-directive-cost/SKILL.md`
116
- - "setup" / "bootstrap" / "onboard" -> `.deft/core/skills/deft-directive-setup/SKILL.md`
117
- - "sync" / "good morning" / "update deft" / "update vbrief" / "sync frameworks" -> `.deft/core/skills/deft-directive-sync/SKILL.md`
118
- - "pre-pr" / "quality loop" / "rwldl" / "self-review" -> `.deft/core/skills/deft-directive-pre-pr/SKILL.md`
119
- - "interview loop" / "q&a loop" / "run interview loop" -> `.deft/core/skills/deft-directive-interview/SKILL.md`
120
- - "run probe" / "/deft:directive:run:probe" / "probe" -> `.deft/core/skills/deft-directive-probe/SKILL.md` (deprecated alias: `/deft:run:probe`)
121
- - "glossary" / "ubiquitous language" / "domain model" / "DDD" / "define terms" -> `.deft/core/skills/deft-directive-glossary/SKILL.md`
122
- - "improve architecture" / "deep modules" / "interface design" / "refactor RFC" -> `.deft/core/skills/deft-directive-gh-arch/SKILL.md`
123
- - "debug" / "root cause" / "investigate" / "why did X break" / "why is X slow" / "systematic debugging" / "forensic" -> `.deft/core/skills/deft-directive-debug/SKILL.md`
124
- - "triage hygiene" / "work the cache" -> `.deft/core/skills/deft-directive-triage/SKILL.md`
125
- - "what's next" / "queue" / "build a cohort" -> `.deft/core/skills/deft-directive-triage/SKILL.md`
107
+ When user input matches a trigger keyword, read the corresponding skill (paths are relative to the consumer's project root and resolve under `.deft/core/.agents/skills/`):
108
+
109
+ - "review cycle" / "check reviews" / "run review cycle" -> `.deft/core/.agents/skills/deft-directive-review-cycle/SKILL.md`
110
+ - "swarm" / "parallel agents" / "run agents" -> `.deft/core/.agents/skills/deft-directive-swarm/SKILL.md`
111
+ - "decompose" / "story decomposition" / "swarm readiness" -> `.deft/core/.agents/skills/deft-directive-decompose/SKILL.md`
112
+ - "refinement" / "reprioritize" / "refine" / "triage" / "pre-ingest" / "action menu" -> `.deft/core/.agents/skills/deft-directive-refinement/SKILL.md` -- the `work the cache` phrase routes to the dedicated `deft-directive-triage` entry below (#1130), not here, to keep routing unambiguous.
113
+ - "triage <N>" / "triage issue" / "ingest issue" -> `.deft/core/.agents/skills/deft-directive-refinement/SKILL.md`
114
+ - "build" / "implement" / "implement spec" -> `.deft/core/.agents/skills/deft-directive-build/SKILL.md`
115
+ - "cost" / "budget" / "pre-build cost" / "how much will this cost" -> `.deft/core/.agents/skills/deft-directive-cost/SKILL.md`
116
+ - "setup" / "bootstrap" / "onboard" -> `.deft/core/.agents/skills/deft-directive-setup/SKILL.md`
117
+ - "sync" / "good morning" / "update deft" / "update vbrief" / "sync frameworks" -> `.deft/core/.agents/skills/deft-directive-sync/SKILL.md`
118
+ - "pre-pr" / "quality loop" / "rwldl" / "self-review" -> `.deft/core/.agents/skills/deft-directive-pre-pr/SKILL.md`
119
+ - "interview loop" / "q&a loop" / "run interview loop" -> `.deft/core/.agents/skills/deft-directive-interview/SKILL.md`
120
+ - "run probe" / "/deft:directive:run:probe" / "probe" -> `.deft/core/.agents/skills/deft-directive-probe/SKILL.md` (deprecated alias: `/deft:run:probe`)
121
+ - "glossary" / "ubiquitous language" / "domain model" / "DDD" / "define terms" -> `.deft/core/.agents/skills/deft-directive-glossary/SKILL.md`
122
+ - "improve architecture" / "deep modules" / "interface design" / "refactor RFC" -> `.deft/core/.agents/skills/deft-directive-gh-arch/SKILL.md`
123
+ - "debug" / "root cause" / "investigate" / "why did X break" / "why is X slow" / "systematic debugging" / "forensic" -> `.deft/core/.agents/skills/deft-directive-debug/SKILL.md`
124
+ - "triage hygiene" / "work the cache" -> `.deft/core/.agents/skills/deft-directive-triage/SKILL.md`
125
+ - "what's next" / "queue" / "build a cohort" -> `.deft/core/.agents/skills/deft-directive-triage/SKILL.md`
126
126
  - "welcome" / "onboard triage" -> invokes `deft triage:welcome --onboard` (N3 / #1143)
127
127
  - "lessons" / "prior art" / "what have we learned about X" -> discover packs with `deft packs:slice --list-packs`, then `deft packs:slice <pack> --list` and load the relevant slice before improvising (see Content packs above)
128
128