docs(sdlc): memory that's a process rule = /sdlc gap

ROADMAP.md

@@ -24,6 +24,7 @@ Add entries when a candidate is mid-evidence (one signal exists but doesn't yet
 | Default to Opus 4.6 1M context (not 200K) | Maintainer hit this: project `settings.json` pinned `claude-opus-4-6` (200K) instead of the `/model` default which gives 1M on Max. Users should get 1M by default; allow opt-out to 200K. Pair with `CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=30` for 1M. | Second user reports same config trap OR #403 model-config cleanup lands | 2026-07-11 | v1.82.0 session 2026-06-11 |
 | Confidence Ramp Pattern for SDLC skill | **TRIGGER FIRED 2026-06-11.** Workflow: Opus researches issues → batch-consult Fable advisor → build 95%+ confidence task list → `/goal` churn. Trialing on #395/#403/#391 model-config batch. If clean (no CI failures, no review findings), graduate to wizard doc as a new SDLC phase. | Model-config batch ships clean | 2026-07-11 | v1.82.0 triage session 2026-06-11 |
 | Advisor auto-fallback in SDLC skill | **TRIGGER FIRED 2026-06-11.** When `advisor()` fails, the SDLC skill should automatically spawn a Fable subagent as fallback — proved in v1.82.0 triage (batch-reviewed 4 issues, caught #395 already fixed). Currently this pattern lives only in private memory; needs to be in `skills/sdlc/SKILL.md` so every project gets it. Also: auto-try advisor before every plan, not just when user asks. | Confidence ramp trial ships clean | 2026-07-11 | v1.82.0 triage session 2026-06-11 |
+| Detect process-rule memories in /feedback or /setup | Users saving memories like "always run tests" are patching /sdlc gaps with private memory. /feedback or /setup could detect `type: feedback` entries with process-rule patterns and suggest contributing back to /sdlc instead. | Maintainer runs memory audit and finds ≥3 process-rule memories | 2026-08-11 | v1.83.0 session 2026-06-12 |
 | Memory audit + repo efficiency pass with Fable | Run Memory Audit Protocol on private memory files — promote portable lessons, delete stale entries. Then: Fable batch-review the full repo (SKILL.md files, hooks, wizard doc) for efficiency, dead code, stale references, and consolidation opportunities. Goal: build a 95% confidence task list of cleanup items that can be worked in parallel. | Next triage session | 2026-07-11 | v1.82.0 triage session 2026-06-11 |
 | ~~Sync AI Setup Lanes to Claude-family sibling wizards~~ | **DONE 2026-06-11.** gdlc v0.3.0, rdlc v0.7.0 shipped with AI Setup Lanes v2. Cowork plugin port in PR #410. Originally: `claude-gdlc-wizard` (v0.2.2) and `claude-rdlc-wizard` (v0.6.1) have stale 69-70 line AI_SETUP_LANES.md vs sdlc-wizard's 217 lines. Missing: 3-lane structure (Premium/Saver/Lite), advisor fallback escalation, Fable effort guidance, usage signals, autocompact cross-ref. Each needs a tailored port — gdlc is game-dev domain, rdlc is research domain. Codex/xdlc/ldlc out of scope (different ecosystem). When people run `/update` in those repos they should get the same Premium lane experience. | Next release of either sibling | 2026-07-11 | v1.82.0 triage session 2026-06-11 |
 

cowork/skills/sdlc/SKILL.md

@@ -255,7 +255,7 @@ Per-user memory at `~/.claude/projects/<proj>/memory/` accumulates private learn
 - `type: project` → manual review (mixed state + portable lesson)
 - `type: feedback` → manual review (mixed personal preference + portable rule)
 
-**Destinations for promote entries** (no new files): tool/platform gotchas → `SDLC.md` `## Lessons Learned`. Testing → `TESTING.md`. Tool quirks tied to a skill → that `SKILL.md`. Process rules → `CLAUDE.md`.
+**Destinations** (no new files): gotchas → `SDLC.md`. Testing → `TESTING.md`. Skill quirks → that `SKILL.md`. Process rules → `/sdlc`. **Memory that's a process rule = /sdlc gap — use /feedback.**
 
 **Tracking:** `promoted_to: <path>` in the memory file's YAML frontmatter; later audits skip already-promoted entries.
 

skills/sdlc/SKILL.md

@@ -255,7 +255,7 @@ Per-user memory at `~/.claude/projects/<proj>/memory/` accumulates private learn
 - `type: project` → manual review (mixed state + portable lesson)
 - `type: feedback` → manual review (mixed personal preference + portable rule)
 
-**Destinations for promote entries** (no new files): tool/platform gotchas → `SDLC.md` `## Lessons Learned`. Testing → `TESTING.md`. Tool quirks tied to a skill → that `SKILL.md`. Process rules → `CLAUDE.md`.
+**Destinations** (no new files): gotchas → `SDLC.md`. Testing → `TESTING.md`. Skill quirks → that `SKILL.md`. Process rules → `/sdlc`. **Memory that's a process rule = /sdlc gap — use /feedback.**
 
 **Tracking:** `promoted_to: <path>` in the memory file's YAML frontmatter; later audits skip already-promoted entries.
 

tests/test-memory-audit-protocol.sh

@@ -46,7 +46,7 @@ test_protocol_section_exists() {
 
 test_protocol_subsections_present() {
     local missing=""
-    for keyword in "When to run" "Rule-based denylist" "Destinations for" "Tracking" "Human gate"; do
+    for keyword in "When to run" "Rule-based denylist" "Destinations" "Tracking" "Human gate"; do
         if ! grep -qF "$keyword" "$SKILL"; then
             missing="${missing:+${missing}, }$keyword"
         fi