Knowledge Management
Help AI Pick Up Where Your Project Left Off
Separate standing rules, current progress and decisions so the next conversation can check the facts.
Check the state when work starts repeating
I pause when AI rebuilds completed work, revives rejected plans or cites nonexistent files. Context may be involved, but unclear instructions or oversized tasks can also cause these failures.
I ask it to list completed work, confirmed decisions and the next step, then compare that account with actual files, tasks and decision records. A mistaken account should not drive the next round of work.
Give three kinds of information separate homes
I keep short standing rules in the project entry point, progress in a state record, and reasons for choices in a decision record. My CLAUDE.md and DECISIONS.md have distinct jobs.
“Edit only this directory” is a rule. “Two sources checked; the third is pending” is state. “We review recipient lists before sending” is a decision. Separating them makes their continuing relevance clearer.
Write rules with four fields
A usable rule specifies its trigger, required action, completion check and stopping point. “Be careful about quality” supplies none of those.
For example: “When updating the comparison, use only designated sources and attach source IDs. Mark conflicts and missing fields for review. Do not invent values. Check at least one row from each source before completion.”
Save a checked handoff before switching conversations
Have AI draft confirmed facts, completed work, unresolved issues, rejected plans and the files needed next. Check the draft before saving it so mistakes do not become durable memory.
The next conversation can load that handoff and necessary inputs instead of all history. A written instruction still needs a check that the tool actually read it.
Reuse only work that repeats reliably
I look for frequent work with stable steps and a fixed output format. I would inspect two or three instances before deciding that similar task names describe the same procedure.
My starting request is: “Based only on these examples, draft the use cases, required inputs, fixed steps, output format and stopping conditions. Return a draft; do not create files yet.” I confirm the procedure before saving it for reuse.