sdlc-decide

Solid

Record 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.

Code & Development 6 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# sdlc-decide The registry behind LoopSmith's **only non-negotiable gate**. Every other guardrail here is discipline a model is asked to follow — and a model can talk itself past discipline, especially at 3am on iteration forty of an autonomous run. A registered invariant is different: the edit is refused by a script that does not negotiate. Registry: `.sdlc/decisions.json`. **Authoring it is the opt-in** — no registry, no behavior. ## What belongs in here (and what doesn't) The bar is narrow on purpose. A registry full of things that don't matter trains everyone to click through the prompt, and then it protects nothing. **Record it when all three hold:** 1. Breaking it causes real damage — corrupted data, a security hole, money spent, a silent wrong answer. Not "inconsistent with our style". 2. **Nothing else already catches it.** If a linter, type checker, schema, or CI job fails on it, that's your enforcement — a second copy just rots out of sync. This is for the rules that are invisible to tooling. 3. It's expressible as a **value constraint on a named thing in known files** — `timeout ≤ 30`, `verify_ssl == True`, `region in [...]`. A rule you cannot write as a comparison belongs in the north-star as prose, not here. **Don't record:** style preferences, anything a formatter owns, aspirations ("we should eventually…"), or a rule whose real enforcement is a code review. Those are north-star material — `.sdlc/context/north-star.md` — and `sdlc-plan-revie...

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

AI & Automation Listed

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".

0 Updated 2 days ago
makieali
Code & Development Solid

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.

502 Updated today
kdlbs
AI & Automation Solid

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.

137 Updated today
arbiterForge