Score8.4
Popularity68.0
Risklow
TierGold
Score breakdown
Usefulness9.0
Novelty9.0
Momentum8.0
Maturity8.0
Open-source/build8.4
Evidence8.0
Workflow potential9.5
Setup ease6.4
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for **teams running Claude Code on shared / production codebases** — espalier-engineering is the MIT Claude Code plugin that discovers the unwritten rules in your codebase and encodes them as machine-enforceable constraints, so AI-generated code lands on your conventions on the first try rather than the fifth. Useful for **engineering teams whose AI-generated code drifts from internal conve
Who should use it
**Teams running Claude Code on shared / production codebases** — espalier-engineering is the MIT Claude Code plugin that discovers the unwritten rules in your codebase and encodes them as machine-enforceable constraints, so AI-generated code lands on your conventions on the first try rather than the fifth**Engineering teams whose AI-generated code drifts from internal conventions** — the v0.8.0 requirements approval gate (Stage 2 PASS no longer authorizes Stage 3 coding) is the canonical answer to the "AI generated plausible-looking code that doesn't fit" failure mode, and the README reports rework cycles dropping from 3-5 rounds to typically 1**Teams running the full 10-stage pipeline** — `/espalier <requirement>` runs requirement → reqs review → coding sub-agent → code review (different sub-agent, different tool set) → tests → test review → push → CI verify → deploy verify → user confirmation, with every stage having a programmatic gate and rollback counters triggering human escalation**Teams running shorter bug-fix workflows** — `/espalier-fix <bug>` is the smaller pipeline variant**Multi-agent code review patterns** — the `harness-coder` (coding sub-agent) and `harness-reviewer` (different sub-agent, different tool set) separation is the canonical 'separate context for code and review' pattern**MIT-licensed engineering-rule pipelines** — plain MIT, no per-file carve-outs, no SaaS-embedding caveat, no commercial-use threshold**Teams adopting Claude Code on existing repos** — `/espalier-init` reads the codebase, extracts the patterns, and writes them down as rules, so a fresh Claude Code session immediately respects the codebase's conventions**Teams with strict gating requirements** — the `hooks/` directory ships programmatic gates (layer boundary check, pre-push gate, post-merge drift detect + backlink), so the framework enforces gates before code reaches CIEvaluation: `/plugin marketplace add Junhanliu-dev/espalier-engineering` + `/plugin install espalier-engineering@espalier-engineering` then `/espalier-init` to scan the repo. Then `/espalier <requirement>` to drive the full 10-stage pipeline, or `/espalier-fix <bug>` for a shorter fix path. For Stage 1 grilling: the framework counts ambiguity signals in the requirement (undefined terms, unstated actors, missing failure behaviour, unscoped edge cases) and asks only as many questions as the vagueness warrants. For the v0.8.0 approval gate: after Stage 1 + Stage 2, the pipeline STOPS and waits for explicit sign-off — Approve / Edit / Abort — before Stage 3 starts; non-TTY runs auto-approve so unattended pipelines never hang. For migrations: `/espalier-migrate` auto-detects install version and applies needed migrations. Note the small-author caveat: the project is a single-author effort (Zayhan / Junhanliu-dev), so bus-factor-1 risk applies
Who should skip it
Skip Junhanliu-dev/espalier-engineering if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
Junhanliu-dev/espalier-engineering is tracked by RepoRadar as a mit claude code plugin for engin in the Junhanliu-dev/espalier-engineering is the MIT Cl section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Junhanliu-dev/espalier-engineering leads on workflow potential (9.5) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Junhanliu-dev/espalier-engineering a composite score of 8.4 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 68.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
single-author Zayhan / Junhanliu-dev (bus-factor-of-1 risk — fine for early adoption; fork or mirror if your project depends on it long-term); the v0.8.0 requirements approval gate is interactive-only (a no-TTY run auto-approves so unattended pipelines never hang; but the sign-off UX requires a TTY for human review).
Evidence links
Closest alternatives / related signals
espalierespalier-engineeringjunhanliu-devzayhanclaude-code-pluginclaude-codeengineering-rulesrule-discovery
