decisions

To log project decisions, this skill captures non-trivial choices involving alternatives, dependencies, and architectural trade-offs from conversations, appending them to a centralized claude_session/DECISIONS.md file to preserve context and rationale.

Maintaining a decision log for feature delivery handoffs is done by persisting session choices to a central markdown file, enforcing a consistent '### <date> — <title>' entry format to ensure accountability and preserve context across project transitions.

Preventing duplicate decision log entries is handled by scanning existing decisions before writing, applying guarded write operations and idempotent initialization to ensure no redundant records are appended to the file.

This decision logging approach works without external project management dependencies, operating entirely within the local session environment to capture and persist design choices directly to a markdown file.

Documenting architectural boundaries in a session decision log is appropriate during brainstorming, feature delivery, or explicit requests, specifically when choices involve design trade-offs, dependencies, or alternative approaches that impact project scope.

Using a markdown decision log to track design trade-offs across project sessions is fully supported, as the skill initializes a persistent file to capture and centralize choices, ensuring context survives beyond a single conversation.