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 — connect a change to its proof Disciplina owns engineering work from understanding the current system through verifying the requested result. Architecture assessment, implementation and debugging use different entry points into the same evidence loop. A review request produces findings; an implementation request authorizes the necessary reversible edits. ## Establish the decision Read the relevant code, callers, recent changes and accepted project decisions. Identify the current behavior, the requested difference and the smallest observation that distinguishes the two. Preserve working strengths and the project's vocabulary. For a material architecture choice, compare viable alternatives, including retaining the current design. Support recommendations with inspected source or explicit requirements. Separate a promising design from evidence that it has run in production. Use [architecture-decisions.md](references/architecture-decisions.md) for the decision record and [transactional-updates.md](references/transactional-updates.md) for changes to running code or mutable state. Ask only for information that changes the implementation or a real authority boundary. Existing authorization remains relevant. State small reversible assumptions and continue; do not require approval of a routine plan merely because