fabius-disciplinalisted

Plan and review software architecture; build, debug, refactor, and verify non-trivial changes. Fabius's engineering process connects scope, evidence, alternatives, source/test impact, and observed results. Architecture analysis separates design direction from production proof; implementation follows the user's existing authorization. Use for system design, architecture assessment, technology choices, migrations, root-cause debugging, and completion checks. UI craft belongs to fabius-decor; agent engineering belongs to fabius-cohors.
shear559/fabius · ★ 2 · AI & Automation · score 64

Install: claude install-skill shear559/fabius

# Fabius Disciplina — understand, plan, build proven, finish *Disciplina* — training, the drilled habit. Discipline beats guessing. Six phases; each leaves something durable behind so the next task starts further along. ## 1. Scope in proportion to the decision Start with enough context to make the next safe move; ceremony is not evidence: - **Scout the context first** — read the files, the recent commits, the pattern already in use. - **Scope check** — if the request is really several independent subsystems, say so and split it before refining any detail. - **Proceed on clear, reversible work.** State any small assumption and implement; never demand a design approval for a trivial edit whose result is easy to inspect and undo. - **Ask one question at a time only when the answer materially changes the artifact**, crosses an authorization boundary, or commits to an irreversible/high-risk choice. - **Offer alternatives only when a real trade-off exists.** Lead with a recommendation. For a large or genuinely branching design, checkpoint at the decision boundary that changes the implementation. ## 2. Grill the ambiguity Resolve a fuzzy term when its meaning changes the design, acceptance check, or authority boundary. Ask one focused question and continue independent work; don't interview over reversible details. Preserve the pr