alexion/skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: route consume knowledge to two channels (#9-#14)

Browse Source 
Reworks the consume skill around two acceptance axes and two destinations,
implementing the six issues filed from the first real consume run as one design.

- Add trigger-ability as a second acceptance axis alongside generalizes, with
  its two premises; a pull-channel note now requires both (#9).
- Give consume a push channel — the target's own CLAUDE.md — for knowledge that
  fails an axis but is still useful: specific residue or proactive rules (#10).
- Name the general-lesson/specific-residue split and route each half (#12).
- Make the step-5 plan report a complete ledger with a per-note trigger line,
  push write-set, ref-fixes, flagged-not-authored, and drops (#13).
- Extend project cleanup to reconcile CLAUDE.md (capture-gated removal/trim) and
  fix references to deleted files wherever they land (#11).
- Encode a branch-owned output location: project notes flat under
  01 sources/claude/projects/, honoring any pre-existing grouping (#14).

Records the resolved vocabulary in .claude/CONTEXT.md and the two-channel write
decision in .claude/adr/0001.

Closes #9
Closes #10
Closes #11
Closes #12
Closes #13
Closes #14
This commit was merged in pull request #15.
This commit is contained in:
alexion
2026-07-24 22:22:28 -04:00
parent 8c17f3aeb8
commit 52fc449824
4 changed files with 140 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
skills/consume/project.md
View File

@@ -7,6 +7,8 @@ Reached from step 1 of [`SKILL.md`](SKILL.md) when the target is a directory con
The source code is the truth for *what* the project is and does now.
Read it thoroughly enough to understand its current state and to surface the reusable ideas it embodies — techniques, patterns, decisions, gotchas.
A gotcha usually carries two separable things — a transferable principle and a concrete repo-specific answer — so surface both.
Step 4 of SKILL.md routes the principle to the pull channel and the residue to the target's push channel.
`.claude/spec/` and `.claude/tasks/` are the record of *why* — the reasoning, trade-offs, and intent behind what the code became.
They are the richest source of the generalizable lessons, and cleanup destroys them, so mine their reasoning now or lose it.
@@ -16,8 +18,18 @@ Together these are the raw material the writing logic generalizes; extracting th
Done when you understand the project's current state from its source and have mined its specs and tasks for the reasoning behind it.
## Output location
Project notes land flat under `01 sources/claude/projects/`, this branch's own area within the vault write boundary.
This is the source-type carve — other consume source types get their own sibling areas later, so project output never mixes with them.
Keep the area flat by default and never reorganize it.
If the user has already grouped some notes into subfolders under `projects/`, write a new note into the matching group rather than at the top level.
## Cleanup
After the notes are written (step 6 of SKILL.md), delete the spec and task files that were present under `.claude/spec/` and `.claude/tasks/` when you read the project in step 2 — the scaffolding this run consumed.
A file added after that read is not swept up.
Leave the now-empty `.claude/spec/` and `.claude/tasks/` directories in place, along with everything else under `.claude/`.
Deleting those files can strand references to them.
Scan the target for pointers to each file about to be deleted — in `CLAUDE.md`, `CONTEXT.md`, ADRs, and sibling specs — and fix or remove each one, following the pointer wherever it lands rather than checking `CLAUDE.md` alone.