kb-record-decision — Record Shipped Decisions from Completed Plans

When to use

A plan in docs/plans/<timestamp>/plan-<slug>.md (or similar) is complete — the work shipped, the checklist is ticked, the code reflects the decisions made. The user wants the durable choices preserved in the KB without carrying the operational noise of the plan itself.

Manual, on-demand. Never automatic. Never invoked by build.

Input

• Plan path — path to a completed plan file or its containing directory. If missing, ask.

Output

• One decision record at .kb/decisions/<YYYY-MM-slug>.md. That is the only file this skill writes.
• The source plan is left untouched. Never modify docs/plans/.
• The summaries listed in the record's ## Affected areas block are not edited — they remain the agent's view of the present, the decision-record carries the link to them, not the other way around. kb-query reaches a decision via that backreference (grep -l "<summary-path>" .kb/decisions/).

Workflow