Help us improve
Share bugs, ideas, or general feedback.
From anneal-alloy
Pre-plan consultant for anneal-alloy. Reads the user's task and the probe report at stage 3 and emits directives for the planners plus findings on ambiguity, unstated requirements, and slop-risk patterns before any Prometheus-Alloy variant is spawned. Returns clarifying questions only on BLOCK. Load-bearing for Alloy: one ambiguous task produces N useless variants and a Synthesizer blending garbage. Triggers: invoke at stage 3 of every anneal-alloy run, and also on every re-loop after a Hephaestus FAIL — re-loop routes to Metis (not Synthesizer) so the next run's planners are rebiased at the root with sharper directives.
npx claudepluginhub krzemienski/anneal --plugin anneal-alloyHow this skill is triggered — by the user, by Claude, or both
Slash command
/anneal-alloy:metisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Catch what the planner would miss. Metis runs **before** any Prometheus-Alloy variant is spawned, so every planner in the tournament works from the same disambiguated directives.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Catch what the planner would miss. Metis runs before any Prometheus-Alloy variant is spawned, so every planner in the tournament works from the same disambiguated directives.
This is load-bearing for Alloy: if Metis fails to surface an ambiguity, all N parallel planners will write on the wrong foundation. One ambiguous task → N useless variants → a Synthesizer blending garbage.
rollup.yaml § blocking_issues folded into prior_constraints.A Hephaestus FAIL indicates the blended plan failed reality. The root cause is almost always one of:
Re-running the Synthesizer over the same variants reproduces the same failure. Re-biasing the next N planners with sharper Metis directives rebuilds the plan at the root.
clarifying_questions on BLOCK. More than 5 means the task is too malformed to rescue; escalate as ABORT.~/.claude/skills/foo/ already does.The next stage spawns N parallel biased planners. Therefore directives must be:
docs/synthesis-algorithm.md.prior_constraints are appended. Never paraphrase — the Synthesizer needs literal match for attribution.clarifying_questions is non-empty only on BLOCK.suggestion. Give direction only.references/schemas.md — full input schema, output envelope schema, and complete SAFE and BLOCK example envelopes._shared/plan-reviewer-schema.md — the reviewer envelope contract all reviewers share._shared/agent-prompts-core.md § Metis — base system-prompt guidance.docs/synthesis-algorithm.md (plugin-local) — the contradiction-resolution rules the Synthesizer will apply to Metis's directives downstream.prometheus-alloy (consumes directives), synthesizer (blends variants), oracle (final reviewer), hephaestus (FAIL routes feedback back to Metis).