Skill

elegance-pipeline

Run a persistent multi-agent code-elegance workflow with 4 scouts, 2 judges, 1 planner, 1 verifier, and 1 gated implementer. Use when evaluating source-file elegance across a repository and optionally converting weaknesses into refactor work.

From elegance-pipeline

Install

Run in your terminal

npx claudepluginhub ancplua/ancplua-claude-plugins --plugin elegance-pipeline

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBashAgent

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

ecc

140.3k

agent-payment-x402

Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.

ecc

140.3k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

140.3k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Elegance Pipeline

Multi-agent code-elegance workflow with persistent state and stage gates.

Pipeline stages

4 Scouts (parallel, sonnet) -> 2 Judges (parallel, opus) -> 1 Planner (opus)
  -> 1 Verifier (opus) -> 1 Implementer (gated, opus)

State manager

All orchestration goes through the pipeline state manager:

python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] <command>

Commands: init, status, prompt, submit, signal

Default state lives at .claude/elegance_pipeline/state/ and is shared by default. If you want one dedicated team per spec, give each run its own --state-dir.

How to orchestrate

Run status to see which slots are ready
For each ready slot, run prompt --role <role> --slot <slot> to get the task prompt
Spawn the appropriate fully qualified subagent (elegance-pipeline:elegance-scout, elegance-pipeline:elegance-judge, elegance-pipeline:elegance-planner, elegance-pipeline:elegance-verifier, or elegance-pipeline:elegance-implementer). If your runtime exposes a different fully qualified name, use that exact identifier instead of the bare short name.
After each agent completes, submit its output via the state manager
Run status again to see what unlocked
Repeat until the pipeline is complete or blocked

Orchestration rules

Scouts run in parallel (all 4 at once via background agents)
Judges run in parallel after ALL scouts are submitted
Planner runs after BOTH judges are submitted
Verifier runs after the planner is submitted
Implementer only runs when the implementation signal is READY
Never bypass stage gates
If the verifier says no implementation is warranted, stop

Agent model mapping

Role	Agent	Model	Access
Scout	elegance-pipeline:elegance-scout	sonnet	read-only
Judge	elegance-pipeline:elegance-judge	opus	read-only
Planner	elegance-pipeline:elegance-planner	opus	read-only
Verifier	elegance-pipeline:elegance-verifier	opus	read-only
Implementer	elegance-pipeline:elegance-implementer	opus	full edit

Manual signal override

python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] signal on
python ${CLAUDE_PLUGIN_ROOT}/elegance_pipeline/pipeline.py [--state-dir <dir>] signal off

If Connectors Available

~~github~~ Post elegance score deltas as PR review comments
~~linear~~ Create refactor tasks from planner output when implementer gate opens
~~slack~~ Notify on pipeline completion with verdict and scout findings summary
~~jira~~ Log verifier decision and refactor scope as a Jira ticket