@dzhechkov/skills-feature-adr 1.3.18 → 1.3.20
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dzhechkov/skills-feature-adr",
|
|
3
|
-
"version": "1.3.
|
|
3
|
+
"version": "1.3.20",
|
|
4
4
|
"description": "Adaptive Feature Development skill pack for Claude Code — 11-step pipeline with Complexity Router (S/M/L/XL), ADR-driven architecture, 15 agentic-qe skills, multi-agent fleet QE. Supports --full-qe, --full-qe-extended, --with-learning, and --knowledge-extractor modes.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"skills-feature-adr": "./bin/cli.js"
|
|
@@ -216,7 +216,7 @@ After Step 8 (or Step 9 for L/XL) completes, verify:
|
|
|
216
216
|
| `{COMPLEXITY_TIER}` | Step 0 | All steps | S/M/L/XL |
|
|
217
217
|
| `{ACTIVE_STEPS}` | Step 0 | Orchestrator | list[int] |
|
|
218
218
|
| `{TIME_BUDGET}` | Step 0 | All steps | dict |
|
|
219
|
-
| `{LEARNED_PATTERNS}` | Step 0 | Step 1 (brief); Steps 8-9 do their own namespace recalls | list[pattern] (Direct modes
|
|
219
|
+
| `{LEARNED_PATTERNS}` | Step 0 | Step 1 (brief); Steps 8-9 do their own namespace recalls | list[pattern] (dz recall = ALL modes; aqe adds semantic in Direct modes) |
|
|
220
220
|
| `{REQUIREMENTS}` | Step 1 | Steps 2-9 | structured |
|
|
221
221
|
| `{RESEARCH_FINDINGS}` | Step 2 | Steps 3-5 | structured |
|
|
222
222
|
| `{ADR_DECISIONS}` | Step 3 | Steps 3.5-7 | list[ADR] |
|
|
@@ -343,9 +343,19 @@ Step 0 (Complexity Router) checks:
|
|
|
343
343
|
3. If flag + installed → set `{AGENTIC_QE_MODE}` = `direct` or `direct-extended`
|
|
344
344
|
4. If flag present but not installed → WARN and fall back to reference mode
|
|
345
345
|
|
|
346
|
-
### Pattern memory loop (
|
|
346
|
+
### Pattern memory loop (self-learning — runs in ALL modes)
|
|
347
347
|
|
|
348
|
-
|
|
348
|
+
**Self-learning is MANDATORY on EVERY `/feature-adr` run — including plain `/feature-adr` without any
|
|
349
|
+
`--full-qe` flag and outside ultracode.** The **dz durable loop runs UNCONDITIONALLY** (no MCP, no
|
|
350
|
+
`fleet_init` needed): **Step 0** `dz recall "<domain terms>"` → fold the top patterns into
|
|
351
|
+
`{LEARNED_PATTERNS}` → apply in Step 1; **Step 8** `dz teach "<durable lesson>"` for each real lesson;
|
|
352
|
+
each step records the live panel via `dz statusline --fa-record`. This half NEVER depends on the mode.
|
|
353
|
+
|
|
354
|
+
The **agentic-qe MCP layer below is an ADDITIONAL enrichment, active only in Direct modes**
|
|
355
|
+
(`--full-qe` / `--full-qe-extended`, needs `fleet_init`) — it adds semantic in-session recall on top of
|
|
356
|
+
the always-on dz loop.
|
|
357
|
+
|
|
358
|
+
When `{AGENTIC_QE_MODE}` = `direct` | `direct-extended`, the pipeline ALSO runs a recall → store cycle
|
|
349
359
|
over agentic-qe's MCP pattern memory (`namespace: "learning"`, `fleet_init` first):
|
|
350
360
|
|
|
351
361
|
- **Step 0** — `memory_query("patterns/feature-adr/*")` **plus** `dz recall --json` over the durable
|
|
@@ -364,7 +374,7 @@ observed live), so it serves fast in-session semantic recall; the dz lexical sto
|
|
|
364
374
|
(`dz teach`/`dz recall`) is the durable half that survives to the next day. All calls are
|
|
365
375
|
non-blocking — an error or empty result never stalls the pipeline. This layer is
|
|
366
376
|
**distinct from the Keysarium reward layer** installed by `--with-learning`: it uses agentic-qe MCP
|
|
367
|
-
memory + the dz store, is
|
|
377
|
+
memory + the dz store, is UNCONDITIONAL for the dz half (recall/teach/fa-record run in every mode) and Direct-mode-only for the aqe-MCP half, and never touches `.keysarium/memory/`.
|
|
368
378
|
|
|
369
379
|
**Live learning panel (`dz statusline`).** The pipeline **drives** the panel: at each pattern-memory-loop
|
|
370
380
|
step above it records its live state via `dz statusline --fa-record …`, so `dz statusline` can surface
|