decision

Extract structured decision records from conversations and append them to 04-决策记录.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alexaundre/mycc --skill decision-alexaundre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision
Source: https://github.com/alexaundre/mycc/tree/main/.claude/skills/decision
Command: npx skills add https://github.com/alexaundre/mycc --skill decision-alexaundre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decisions made during development—architecture changes, bug fixes, API modifications, and configuration choices—are often lost or undocumented, making future analysis, debugging, and automated agent recovery difficult. This Skill extracts the essential context and rationale from the current conversation and turns it into a concise, machine-friendly decision record so future agents and team members can quickly understand why choices were made.

Core Features & Use Cases

  • Automatic extraction of title, date, type, status, scope, affected files, candidate options, chosen decision, abandoned alternatives, verification steps, and flip conditions from the active conversation.
  • Append to project records by adding structured entries to the project's 04-决策记录.md and updating the last-modified metadata, with special handling for auto-type entries.
  • Use cases: capture post-mortem fixes, document architecture refactors, record API contract changes, and log configuration or deployment decisions for future agents and audits.

Quick Start

Run the /decision command in the current conversation to extract a draft decision record and append it to the project's 04-决策记录.md for review or automatic commit.

Frequently Asked Questions about decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically capture technical architecture decisions from a conversation?

You can automatically capture technical architecture decisions by running the /decision command to extract context and rationale from the active conversation, which generates a structured decision record appended to the project's documentation.

What is a structured decision record and what fields should it include?

A structured decision record documents development choices by capturing fields including type, status, scope, affected files, candidate solutions, chosen decision, abandoned options, verification steps, and flip conditions for future analysis.

How do I document API changes and bug fixes for future agent recovery?

To document API changes and bug fixes for future agent recovery, extract the essential context from the development discussion and append it as a machine-friendly entry to the project's decision log file.

Can I log configuration and deployment decisions without manual formatting?

Yes, you can log configuration and deployment decisions with minimal manual confirmation by automatically extracting the decision context and appending structured entries directly to the project's decision record markdown file.

What is the best way to maintain a decision log for software architecture refactors?

The best way to maintain a decision log for architecture refactors is to append structured entries to a centralized markdown file, updating the last-modified metadata to ensure future agents and team members understand the rationale.

How does automated knowledge capture handle abandoned alternative solutions?

Automated knowledge capture handles abandoned alternatives by extracting candidate solutions from the conversation context and explicitly recording both the chosen decision and the abandoned options in the decision record.