clarity-council

Diagnosis loop for hard bugs and performance regressions.

Analyze a git repository's history and produce an SVG treemap of file churn — area = lines changed, color = commit frequency.

Use when a git merge or rebase hits complex conflicts, or the user says "resolve conflicts" / "fix merge conflicts".

Score today's load (meetings, sensory demand, social events, deep work), flag burnout risk, and suggest what to drop or defer.

Decode messages into plain language with tone and intent analysis.

Two-axis review of the working diff since a fixed point — Standards (repo conventions and code smells) and Spec (matches the originating ticket).

Safely rebase the current branch onto its upstream target, auto-resolving trivial conflicts and prompting for complex ones.

Shared vocabulary and principles for designing deep modules — a lot of behaviour behind a small interface, placed at a clean seam.

Actively build and sharpen a project's domain model — challenge fuzzy terms, stress-test with scenarios, and write CONTEXT.md and ADRs inline as decisions…

Extract clean markdown from web pages using Defuddle CLI, stripping navigation and clutter to save tokens.

Use when the user needs to groom, refine, or clean up a product backlog.

Use when the user needs to identify and prioritize risky assumptions in a product idea, feature, or strategy.