gleicon

Design a target architecture for a new system — module boundaries, dependency rules, seams, and build order — from its requirements. Reports a blueprint; changes nothing.

Analyze an existing codebase's architecture and produce a sequenced refactoring plan — assess module boundaries, dependency structure, and layering, then lay out ordered, risk-tagged steps. Language-agnostic. Reports a plan; changes nothing.

Turn a goal or another command's output into an ordered task roadmap.

Find the root cause of a failure with the scientific method — reproduce, isolate, fix, then prove it.

Interview the user relentlessly about a plan or design until reaching shared understanding.

Run an extremely strict maintainability + single-source-of-truth review of code changes — abstraction quality, file sprawl, spaghetti-condition growth, and duplicate/competing implementations. Reports findings by default; `--fix` applies the mechanical, unambiguous ones — structural/code-judo restructurings rest on judgment and stay reported.

Drive implementation with tests, one vertical slice at a time.

Activate pragmatic testing mode for this session.

Compress long prose into a short extractive summary with the local tldt binary (no LLM cost) before adding it to context. Use for long articles, web pages, transcripts, docs, or pasted prose you only need the gist of. Do NOT use when the exact/verbatim text matters: code, config, logs to grep, or anything you will quote or edit.