v0.16.0: knowledge pipeline — capture skill, explore→proposed/, lane discipline#8
Open
milstan wants to merge 1 commit into
Open
v0.16.0: knowledge pipeline — capture skill, explore→proposed/, lane discipline#8milstan wants to merge 1 commit into
milstan wants to merge 1 commit into
Conversation
…ne discipline The shared knowledge base wasn't getting updated because the cold-lane consolidator was deleted in 2026-05-01 with no replacement and no skill captured durable learnings except /relentless + /diagnose. Three skills referenced in the knowledge repo's README never actually existed (/knowledge-capture, /knowledge-dream) or wrote to the wrong lane (/knowledge-explore wrote directly to wiki/). This change wires the producer side; the consolidator side is restored in leadbay/knowledge in a parallel PR. - new /knowledge-capture: session-end durable-learning capture. Calls lb-learnings-log so the launchd sync ships entries into journal/ and the dream folds them into wiki/. Skip-on-no-discovery is the expected outcome for most sessions. - /knowledge-explore v3.0.0: rerouted from wiki/journey/, wiki/concept/, wiki/pitfall/ to proposed/<concept>/proposals/ with force_promote: true. The cold lane is the dream's exclusive domain — explore is a hot-lane producer like everything else. - lb-knowledge-write: added --force-promote to the proposed subcommand so /knowledge-explore can mark its evidence-heavy output for immediate promotion (the dream's quorum check is for accidental drift, not for deliberate live tours). - /knowledge-find: removed stale reference to a non-existent Stop hook. Teammates whose harness doesn't run UserPromptSubmit hook should wire /knowledge-find into their own session-start equivalent. The working-with-milan skill carries the full invocation protocol; mirror it in your team's equivalent skill. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The shared knowledge base hasn't been getting updated. Diagnosis:
.github/workflows/dream-light.yml+dream.yml) was deleted inleadbay/knowledgeon 2026-05-01 with no local replacement. Result:wiki/,glossary.md,index.md,log.mdfrozen for 25 days while 288 journal entries piled up underneath./knowledge-captureand/knowledge-dream— neither existed./knowledge-explore(the only skill that actively documents new surfaces) wrote directly towiki/, breaking the two-lane discipline that's enforced everywhere else./relentlessand/diagnoseever calledlb-learnings-log, so the journal pipeline was fed by exactly two skills.This PR fixes the producer side. The consolidator side is restored in a parallel PR on
leadbay/knowledge(re-adding the workflows).What
New
/knowledge-capture— session-end durable-learning capture. Callslb-learnings-logper insight; the launchd sync ships them tojournal/; the dream promotes. Skip-on-no-discovery is the expected outcome for most sessions. Hard cap of ~5 captures per session per the "would save a future agent 10 min" filter./knowledge-explorev3.0.0 — rerouted output fromwiki/journey/,wiki/concept/vocabulary.md,wiki/pitfall/toproposed/<concept>/proposals/...withforce_promote: true. Phase 6 (Persist) is now hot-lane only.lb-knowledge-write— added--force-promoteflag to theproposedsubcommand. Emitsforce_promote: truein the proposal frontmatter so the dream's light pass promotes it on the next push without waiting for cross-source quorum (which is meant to catch accidental drift, not penalise deliberate live tours)./knowledge-find— removed stale reference to a non-existentStophook.What's NOT here
The
working-with-milanskill that wires/knowledge-find→/knowledge-question→/knowledge-explore→/knowledge-captureinto explicit session-start / mid / end invocation points. That lives at~/.claude/skills/working-with-milan/on Milan's machine and isn't in any git repo. Each team member's equivalent skill should mirror the block.Adding
lb-learnings-logcalls to other skills (/ship,/qa,/codex,/retro, etc.). Deliberate — those are gstack-upstream skills and would drift on update. The right path is/working-with-<owner>invoking/knowledge-captureat session end.Test plan
bin/lb-knowledge-write proposed --force-promote ...emitsforce_promote: truein the YAML frontmatter.~/.leadbay-skills/setup --updateafter merge installsknowledge-capture/.leadbay/knowledgePR merges (restoring the dream workflows), invoke/knowledge-exploreagainst any small surface and verify aproposed/<concept>/...file is created and promoted bydream-light.🤖 Generated with Claude Code