@dzhechkov/skills-feature-adr 1.3.5 β†’ 1.3.7

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 (2) hide show
  1. package/README.md +42 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -13,6 +13,8 @@ the [Keysarium](https://www.npmjs.com/package/@dzhechkov/keysarium) ecosystem.
13
13
  > **For your team:** the `features/<slug>/` folder this produces *is* the spec β€” reviewable in a PR,
14
14
  > onboarding doc for free, every decision captured as an ADR, and machine-checked back against the
15
15
  > code by the QE phase. See **[Spec-Driven Development](#spec-driven-development-sdd)** below.
16
+ >
17
+ > πŸ‘‰ **Onboarding a team? Start here:** [**Feature ADR β€” Team Onboarding**](https://github.com/djd1m/dz-harness-hub/blob/main/docs/feature-adr-team-onboarding.md) β€” a single read-top-to-bottom playbook (install β†’ first feature β†’ SDD mechanics β†’ model routing incl. Fable β†’ self-learning layers β†’ team PR workflow β†’ FAQ).
16
18
 
17
19
  ---
18
20
 
@@ -373,6 +375,45 @@ npx @dzhechkov/skills-feature-adr init --with-learning --knowledge-extractor
373
375
 
374
376
  ---
375
377
 
378
+ ## Self-Learning Layers
379
+
380
+ There are **three independent self-learning systems** that can sit under a Feature ADR run.
381
+ `--full-qe-extended` does **not** turn on learning by itself β€” it controls QE depth. Learning is a
382
+ separate, orthogonal concern. The three layers do **not conflict**: each is isolated by its own
383
+ storage path, its own learning signal, and its own consumer.
384
+
385
+ | Layer | Turn it on with | Learns from | Storage (distinct!) | Needs a DB? |
386
+ |-------|-----------------|-------------|---------------------|-------------|
387
+ | **A β€” feature-adr reward learning** | install flag **`--with-learning`** (or bundled with `@dzhechkov/keysarium`) | your **checkpoint responses** (`ΠΎΠΊ`=1.0 / minor=0.7 / rework=0.3 / restart=0.0) | `.keysarium/memory/*.json` | **No** β€” plain JSON files |
388
+ | **B β€” agentic-qe learning** | comes with `agentic-qe` (required by `--full-qe` / `--full-qe-extended`), initialized by `aqe init` | QE task **experiences** (ReasoningBank + dream scheduler) | `.agentic-qe/memory.db` + `patterns.rvf` | Self-contained (its own store) |
389
+ | **C β€” dz harness self-learning** | the `dz` CLI (`dz setup` / `dz teach` / `dz consolidate` / `dz recall`) | your **dz sessions** | `.dz/` (+ optional `.dz/agentdb.db` vector tier) | **Optional** β€” lexical works without one; agentdb only adds vector search |
390
+
391
+ ### Do they conflict? No β€” but observe one rule
392
+
393
+ - **No logical conflict:** different files, different signals, different readers β†’ no write
394
+ contention and no data clobbering. Enabling all three at once is fine; they're complementary.
395
+ - **Auto-dedup:** if `@dzhechkov/keysarium` is present, the installer **skips** `--with-learning`
396
+ (keysarium already ships layer A), so you can't accidentally double-install it.
397
+ - **⚠️ The one rule β€” one DB file per writer.** Layer C writes to SQLite **natively (better-sqlite3,
398
+ WAL)**; agentic-qe (layer B) can write **via sql.js (whole-file overwrite)**. Pointing *both* at
399
+ the **same** `.db` file risks corruption. By default they use **different files**
400
+ (`.agentic-qe/memory.db` β‰  `.dz/agentdb.db`), so out of the box you're safe β€” just never
401
+ hand-repoint one system's `AGENTDB_PATH` at the other's database.
402
+
403
+ ### Which to enable
404
+
405
+ - Writing features with this pipeline and want it to **learn from your feedback** β†’
406
+ `npx @dzhechkov/skills-feature-adr init --with-learning` (**no agentdb needed**).
407
+ - Running `--full-qe` / `--full-qe-extended` β†’ agentic-qe's learning already runs via its hooks.
408
+ - Living inside the `dz` harness and want cross-session memory β†’ `dz setup` (add agentdb only if you
409
+ want the vector tier).
410
+
411
+ > There is no single unified "what did the whole stack learn" view β€” each layer reports from its own
412
+ > store. That's the price of isolation (and the reason there are no cascading failures). Tune each
413
+ > where it lives.
414
+
415
+ ---
416
+
376
417
  ## Shared Skills
377
418
 
378
419
  Feature ADR uses these skills from `@dzhechkov/keysarium` (if installed):
@@ -420,6 +461,7 @@ npx @dzhechkov/skills-feature-adr init # Feature development
420
461
 
421
462
  ## Links
422
463
 
464
+ - **Team Onboarding playbook:** [docs/feature-adr-team-onboarding.md](https://github.com/djd1m/dz-harness-hub/blob/main/docs/feature-adr-team-onboarding.md)
423
465
  - **GitHub:** [https://github.com/dzhechko/product-keysarium-2026](https://github.com/dzhechko/product-keysarium-2026)
424
466
  - **Issues:** [https://github.com/dzhechko/product-keysarium-2026/issues](https://github.com/dzhechko/product-keysarium-2026/issues)
425
467
  - **npm:** [https://www.npmjs.com/package/@dzhechkov/skills-feature-adr](https://www.npmjs.com/package/@dzhechkov/skills-feature-adr)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dzhechkov/skills-feature-adr",
3
- "version": "1.3.5",
3
+ "version": "1.3.7",
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
  "main": "src/cli.js",
6
6
  "bin": {