decision-check

To check historical decisions before committing, query decision archives, memory, and patterns files to surface prior context, flag contradictions against the proposed plan, and recommend whether to proceed, reconsider, or supersede.

New project goals contradict prior decisions and patterns when a proposed direction conflicts with archived rules or memory. Surfacing this historical context identifies direct or implicit contradictions and provides an actionable recommendation to resolve the tension.

The best way to surface decision history for a non-trivial choice is to cross-check the proposed direction against decision archives, patterns, memory, and long-term goals to generate a recommended path and flag any superseding opportunities.

You need to cross-check a proposed plan against memory and goals when you are about to decide something non-trivial, when a new direction sounds familiar, or when you sense tension with a prior call to ensure alignment with long-term goals.

Yes, you can use decision archives to flag risks and tensions with remembered rules by comparing the proposed direction against existing decisions, identifying implicit contradictions, and surfacing context to recommend whether to proceed or reconsider.

Decision-checking relies on reading existing decision archives, patterns, memory, and goals files to surface context. Without these inputs, the skill cannot compare proposed directions against historical rules or flag contradictions effectively.