What problem does it solve? Project decisions get lost in chat history or made inconsistently, causing scope drift, conflicting choices, and repeated debates. This Skill centralizes every decision in a structured decision_log.md with severity levels, owners, and status tracking. ## Core Features & Use Cases - Three-Tier Severity System: Classifies decisions as strategic (PM approval), technical (PL judgment), or operational (agent autonomy) with distinct approval workflows for each level. - Structured Decision Log: Assigns sequential D-numbers, records context, options, rationale, and impact scope in a decision_log.md template with summary tables and detailed entries. - Pending-to-Confirmed Flow: Manages decision states from pending to confirmed, synchronizing with CLAUDE.md sections and notifying affected agents. - Use Case: When a solo developer must choose between PostgreSQL and MongoDB mid-project, the Skill classifies it as a technical decision, documents the trade-offs, records the PL's choice as D-06, and propagates it to all related design documents. ## Quick Start Ask the assistant to record a new project decision, for example by saying "결정사항 기록해: 데이터베이스는 PostgreSQL로 확정" so it classifies the severity and appends it to decision_log.md.
