sdlc-decide
SolidRecord an architectural decision as a machine-checkable invariant so an edit that breaks it is DENIED, not just discouraged. Use when the user runs /sdlc-decide, says "make this a rule / an invariant", "enforce this", "stop us breaking X", or after a retrospective proposes a standing rule that a linter can't catch.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- swapnil-agrim
- Repository
- swapnil-agrim/loopsmith
- Created
- 1 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
decision-log
Records durable technical decisions with their reasoning, and searches them before a settled question gets re-opened. Use when an architectural, scope, tooling or vendor choice is made or reversed, when someone asks "why is it like this", or before proposing an approach that may already have been rejected. Trigger: "log this decision", "why did we choose", "did we try", "have we decided", "record that we're not doing", "was this considered".
record
Keep durable architecture decisions and product specs in sync with the work happening in the conversation. AUTO-INVOKE when a request establishes or changes a long-lived architectural boundary, public contract, data ownership rule, operational invariant, or repo-wide convention with meaningful alternatives. Also invoke on explicit triggers: "record this", "create an ADR", "document this decision", "update the spec", "ADR for X". Run BEFORE coding when the decision is upfront, or AFTER landing when the right call only became clear during implementation. Do not create ADRs for simple features, local implementation choices, routine dependency changes, or bug fixes that do not establish a durable rule.
decision-lifecycle
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only. Never authors an ADR as its own judgment — every ADR carries explicit user attribution.