record-decision

To record project decisions as markdown files in git, this Skill auto-detects decision moments during a session, synthesizes a structured file, and commits it to the repository. This ensures decisions are captured automatically without manual documentation effort.

The best way to preserve architectural choices across branches is committing them as dated markdown files under the .knowledge/decisions directory. This integrates decisions into the PR workflow, making them auditable and persistent across all branch merges.

Auto-detecting decision moments works by observing the session context for scope decisions, architectural choices, or constraints. When a clear decision is identified, it automatically triggers the synthesis of a structured markdown file to capture the knowledge asset.

Yes, the knowledge distillery pipeline is required to capture decisions as verifiable knowledge. The Skill stores dated markdown files in the .knowledge/decisions directory, relying on this pipeline to preserve and audit decisions across project branches.

No, a PR workflow is essential because the Skill commits captured decisions to the .knowledge/decisions directory through it. Without the PR workflow, the decisions cannot be preserved as verifiable team knowledge assets across branches.

Recording decisions as verifiable knowledge matters because it creates auditable markdown files that document scope decisions and constraints. This prevents knowledge loss across team transitions and provides a historical record of architectural choices for future reference.