A structured workflow system for Claude Code — from idea capture through build, review, and wrap-up. Includes an LLM-as-judge recurring recon sweep, browser automation, and QA pipeline.
Use for browser automation via agent-browser — defines session naming, screenshot/trace paths, and operation vocabulary used by /stories, /visual-review, and /review. Keywords - browse, browser, agent-browser, screenshot, scrape, automation.
Use when implementing a spec or design doc end-to-end. Accepts a spec number for full lifecycle tracking, or a design doc path to skip /claude-tweaks:specify and build directly from brainstorming output.
Use when capturing ideas that need specification later — brain dumps, half-formed features, things to not forget
Use when you need to challenge assumptions and remove bias from a problem statement before brainstorming. Takes an INBOX item or topic and produces a debiased problem framing.
Use when you want an architectural-depth pass on recently changed code — finds shallow modules (interface nearly as complex as implementation) and proposes deepening or collapsing them, ranked by leverage. Catches architecture entropy that line-level simplification misses. Works standalone or surfaced as a Next Action by /claude-tweaks:review and /claude-tweaks:reflect.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A structured workflow system for Claude Code — from idea capture through build, review, and wrap-up.
Claude Code is powerful but unstructured. claude-tweaks adds a complete development lifecycle: capture ideas, challenge assumptions, decompose into specs, build with quality gates, and learn from what was built. Every finding is explicitly resolved — nothing silently drops.
Recon v2 replaces the v1 mechanical-lens spine with an LLM-as-judge model: the LLM evaluates the repo against a criteria catalog, calling deterministic tool checks as evidence. Area-type routing, content-hash skip, hotspot priority, fingerprinting, and dedup are handled by deterministic helpers. The v1 subagent dance and plan-judgment / ingest-judgment phases are removed. Recon now runs as a scheduled Routine for continuous, hands-off coverage — no manual invocation needed.
/claude-tweaks:research adds citation-audited deep web research to the plugin. Four runtime modes trade depth for time:
As of v4.15.0 this delegates to Claude Code's built-in /deep-research Dynamic Workflow when available, with a lean inline fallback otherwise. Reports land under .claude-tweaks/research/.
Diagram Design companion plugin — a soft-hook integration with cathrynlavery/diagram-design (MIT, separately installed). Unlike Impeccable (wrapped via /claude-tweaks:design) or research (which delegates to the built-in /deep-research), diagram-design has no callable surface — it's a pure-skill plugin that auto-triggers from its YAML description. claude-tweaks adds contextual nudges at three lifecycle moments:
/specify Step 2.5d (new, all surfaces) — when the design doc describes state machines, schemas, multi-actor flows, decision trees, or layered architecture, the spec summary surfaces "consider a {type} diagram" with a suggested output path (docs/diagrams/{slug}.html). Un-gated from frontend — backend specs get architecture / ER / state diagrams too. Caps at 2 suggestions per spec./journeys Step 3.6 (new) — when a journey crosses 2+ personas, has 3+ named decision branches, or sequences 2+ external services, suggests the matching diagram type (swimlane / flowchart / sequence) before commit./review Lens 3i-diagram (extension) — when the diff added structural complexity but docs/diagrams/ has no matching file, emits one informational Lens 3i finding ("Visual documentation gap"). Mirrors the existing "doc-update missed" pattern.All three hooks are gated by diagram-integration: enabled in CLAUDE.md, written by /init Phase 0.95 (always offered — not frontend-gated). Disabled / missing flag = silent no-op everywhere. claude-tweaks never invokes the plugin directly; the user accepts conversationally and diagram-design's skill auto-triggers. Shared procedure lives at skills/_shared/diagram-integration-check.md — flag-read, signal→type mapping (10 types), canonical phrasing, output convention.
See CHANGELOG.md for earlier release notes (v4.6, v4.5, v4.2, v4.1) and v3→v4 upgrade guidance.
/plugin marketplace add thomasholknielsen/claude-tweaks-marketplace
/plugin install claude-tweaks@claude-tweaks-marketplace
/plugin install superpowers@claude-plugins-official
/claude-tweaks:init
SKILL ARTIFACT SUPERPOWERS USED
───── ──────── ────────────────
npx claudepluginhub thomasholknielsen/claude-tweaks-marketplace --plugin claude-tweaksHooks-based workflow orchestration for solo product development with Claude Code
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
HarnessFlow — From idea to shipped product: high-quality engineering workflows for AI agents. Spec-anchored SDD, gated TDD, evidence-based routing, independent reviews, and formal closeout.
Requirements-driven development workflow with quality gates for practical feature implementation
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and Beads integration
Compound Engineering workflow: PRD-driven sprints, isolated worktrees, hook-enforced safety, automated learning. Skills become /vini-workflow:plan, /vini-workflow:compound, etc.