elixir-discipline

Enforce a mandatory pre-response discipline by announcing and applying sub-skills in strict order: elixir-tdd-enforcement, elixir-root-cause-only, elixir-verification-gate, elixir-no-shortcuts, elixir-no-placeholders. This ensures tests pass, root causes are traced, commands are verified, and no steps are skipped before any code change or claim.

Root-cause tracing prevents ad hoc fixes by requiring actual investigation before responding to Elixir/Phoenix debugging tasks. This structured process identifies the underlying issue rather than masking symptoms, reducing regressions and technical debt.

Run mandatory checks: verify test coverage exists and passes, trace the root cause of any reported issue, validate commands actually execute in context, avoid placeholder solutions, and reject shortcuts that skip verification steps. Announce which skill you're applying before proceeding.

No. The elixir-no-shortcuts skill explicitly blocks shortcuts in Elixir contexts. All pre-checks—tests, root-cause analysis, command verification, and placeholder rejection—must be applied in exact order before responding to any feature, fix, debug, or review task.

By enforcing tests-first workflows, strict verification, and rejection of placeholder code before responding to Elixir/Phoenix queries, this approach eliminates ad hoc fixes, ensures actual commands work, and guarantees root causes are addressed—raising code quality and reducing debugging cycles.