2.2 KiB
project branch
How consume reads a project target, and what it clears afterward.
Reached from step 1 of SKILL.md when the target's flat artifact project directory contains *-spec.md or *-task.md artifacts.
Read the source, mine the specs
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.
The artifact project's *-spec.md and *-task.md artifacts are the canonical 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.
But they are not current fact: where a spec or task disagrees with the source, the source wins, and where one describes work later abandoned or changed, the source is what actually happened.
Together these are the raw material the writing logic generalizes; extracting the generalized notes themselves is step 4 of SKILL.md, not this branch's job.
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 $(xdg-user-dir DOCUMENTS)/ai-artifacts/wiki/.
Do not create subdirectories there.
Cleanup
After the notes are written (step 6 of SKILL.md), delete the *-spec.md and *-task.md artifacts that were present in the flat artifact project directory when you read the project in step 2 — the scaffolding this run consumed.
A file added after that read is not swept up.
Deleting those files can strand references to them.
Scan the target and its artifact project directory for pointers to each file about to be deleted — in AGENTS.md, context artifacts, ADRs, and sibling specs — and fix or remove each one, following the pointer wherever it lands rather than checking the push channel alone.