decisions

Architectural decisions are retrieved by accessing memory or knowledge records stored in a decisions directory. The Skill reads historical decision files to ensure your current choices align with prior patterns, comparing context, options, and rationale before proceeding.

Document the context describing the problem, options considered, the decision made, rationale explaining why that choice was selected, and consequences of that decision. This structure enables future reference and maintains a traceable decision history.

Reference past decisions whenever you're making architectural choices, comparing implementation approaches, or questioning existing patterns. Checking prior decisions prevents inconsistency and helps you understand why previous paths were chosen or rejected.

Yes. The Skill supports globbing decision sets across projects, allowing you to maintain a centralized repository of architectural decisions and apply consistent patterns wherever they're relevant across your codebase.

Documenting a decision captures the reasoning and context behind your choice, creating a reference for future decisions and team members. Without documentation, the rationale disappears and consistency becomes harder to maintain.