By taipt1504
7-phase agentic workflow for Java/Spring Boot backends (over a pre-indexed codebase): discover → brainstorm → spec → plan → implement → review → learn, with complexity-tier fast lanes.
Generates two or more genuinely distinct solution options for a problem and recommends one. General-purpose ideation — any problem type (feature, bug, refactor, performance, design). Consumes the Discover phase's context + reuse decision; returns the candidate enforcement set for code tasks. Do NOT write code.
Persistence-layer correctness — JPA mappings, fetch strategies, migration safety (Flyway/Liquibase), transaction boundaries. Use in the Review phase, spawned by claudehut:review, on changes to entities, repositories, or migrations.
Read-only codebase query agent for the Discover phase. Use when you need to understand an unfamiliar area, locate where something is implemented, or map the modules a task will touch so candidate solutions adapt to this codebase. Do NOT use to write code or propose fixes — it only reports.
Executes the plan test-first under the project's conventions. Use in the Implement phase for multi-file changes that benefit from an isolated worktree. Honors every rule that auto-loads for the files it touches.
Extracts candidate learnings for the Learn phase and keeps the reuse index and committed memory index current. The deterministic merge/dedup/promote/prune is done by a script after you return. Carries project-scoped auto-memory.
Use to generate and weigh solution approaches for a problem, after discovery has grounded the context. Produces two or more genuinely distinct options scored on trade-offs, recommends one, and (for code tasks) assembles the enforcement set the rest of the workflow audits against. General-purpose ideation — works for any problem type; not tied to a specific stack.
Use in the Learn phase at the end of every task, before declaring done - dispatches the learner agent to record what was learned (conventions, pitfalls, reuse points, decisions) to the cross-session store and refresh the committed memory index, then closes the phase. Runs inline on the main thread (it owns the state write).
Use once per project before starting work (or when ClaudeHut reports no codebase index) to bootstrap ClaudeHut for a Java/Spring repository - detects the stack, generates the project memory + index + path-scoped rules, and wires the always-load @import slice. Invoked as /claudehut:init. Idempotent.
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also re-anchor mid-session with /claudehut:workflow.
Use as the FIRST phase of EVERY coding task, before brainstorming - grounds the work in the existing codebase (entry points, key types, structure) and proves whether something reusable already exists. Produces the reuse-scan artifact the write gate requires and the reuse DECISION (adopt / extend / new). Runs inline on the main thread; trivial tier uses the inline 3-grep variant. Skip ONLY for pure documentation/comment edits with zero production-code change.
Modifies files
Hook triggers on file write and edit operations
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.
v0.5.0 · a Claude Code plugin for Java / Spring Boot backend engineers.
ClaudeHut turns a single task description into a disciplined, seven-phase engineering loop — and enforces it with native Claude Code mechanisms (hooks, skills, subagents, path-scoped rules) rather than relying on the model to remember:
┌────────────────────────────────────────────────────────────────────┐
init → │ Discover → Brainstorm → Spec → Plan → Implement → Review → Learn │
(pre-index) └────────────────────────────────────────────────────────────────────┘
reuse-first ideation test-first evidence-first reinforced
A complexity triage (Phase 0) routes each task: trivial/small tasks skip the deliberation phases
(Brainstorm/Spec/Plan) through a gate-verified fast lane (≤2 files, no security/auth/migration paths —
checked deterministically, not by model judgment); the safety rails (reuse-scan, test-first, Review) are
never skipped in any tier.
/claudehut:init pre-indexes the codebase once (stack, structure, memory, rules) — indexing is a
prerequisite, not a phase. After that, you describe a task and the workflow drives every phase
automatically, gating progress so you can't skip reuse, skip tests, or claim "done" without a clean review.
The full design lives in .claude/docs/design/.
# from the marketplace
/plugin marketplace add claudehut/claudehut
/plugin install claudehut@claudehut-marketplace
# or load locally for a session
claude --plugin-dir /path/to/claudehut
ClaudeHut ships no MCP servers and prompts for no credentials. MCP is opt-in per project (see Components → MCP).
jq on PATH — the state CLI and gate hooks require it./claudehut:init # one-time: detect stack → build index + memory + path-scoped rules
<describe your task> # ClaudeHut triages complexity, then drives Discover → … → Learn automatically
The orchestrator skill (claudehut:claudehut-workflow) is injected at session start and routes each phase
to its skills and agents. You don't invoke the phases by hand — the workflow does. Everything it generates
lives under .claude/claudehut/ (index, memory, one tasks/NNNN-<slug>/ dir per task holding its
reuse-scan/spec/plan/review, per-session state, learnings) and
.claude/rules/ (the generated tech-stack standards).
| Phase | Skill | Drives | Output |
|---|---|---|---|
| Discover | discover | claudehut-explorer ∥ claudehut-reuse-scanner (one message, concurrent) | codebase grounding + the reuse-scan artifact (required in every tier) |
| Brainstorm | brainstorm | claudehut-brainstormer (opus, xhigh — fixed 6-step ideation pipeline: diverge ≥6 → cluster → score → premortem → recommend) | ≥2 structurally distinct options + the per-task enforcement set |
| Spec | write-spec | main thread | a templated spec (tasks/<id>/spec.md), user-approved before the gate arms |
npx claudepluginhub taipt1504/claudehut --plugin claudehutAdaptive 5-layer workflow Claude Code plugin for Java Spring backend — 1% pre-flight discovery, triage routing, two-stage review, subagent dispatch, auto-evolution
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
AI-powered development tools for code review, research, design, and workflow automation.