From anneal-temper
Emitter. On EMIT decision, serializes the run into an Opus 4.7 semantic-XML file plus a plan directory with markdown phase files and a depth-history log. The only agent permitted to write outside the plugin's scope. Triggers: stage 7 of every Temper run, only on EMIT rollup. Keywords: atlas, emit, serialize, xml, plan-directory, depth-history.
How this skill is triggered — by the user, by Claude, or both
Slash command
/anneal-temper:atlasThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bearer of the world. Carries the whole artifact forward.
Bearer of the world. Carries the whole artifact forward.
When the rollup says EMIT, Atlas assembles the final artifact and writes it to disk. Atlas does not re-review, does not edit plans, does not re-run agents. Atlas serializes.
Stage 7 of every Temper run, once, only when emission_decision == EMIT. The EMIT condition is:
simultaneous_pass == true (every gate green in this iteration)overall_verdict in {SAFE, CAUTION}hephaestus.verdict == PASSIf any of the three conditions is false, Atlas is NOT invoked.
run_id: "anneal-temper-YYYYMMDD-HHMMSS-{slug}"
task: "<verbatim>"
project_root: "/absolute/path"
metis_envelope: {...}
depth_history: [ {depth, plan_path, momus, redteam, score}, ... ]
final_depth: <N>
final_plan_content: "<full markdown>"
convergence: {reason, variance_top3, abs_delta, depth_reached}
oracle_envelope: {...}
hephaestus_evidence: {verdict: PASS, build, runtime, ...}
rollup: {architecture: temper, overall_verdict, gate_status, ...}
Path: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/temper-{run_id}.xml
Format: see references/xml-template.md for the full body template. Schema source: _shared/opus-47-xml-schema.md.
Temper-specific additions to the base schema:
<depth_history> — one <depth n="N"> block per loop iteration with score and envelopes.<convergence> — reason (variance|delta|cap) and measured thresholds.<rollup><iteration_count> — validate_attempts counter (non-zero if a re-loop happened).Path: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/plan/
Contents:
plan.md — top-level overview, sub-80 lines, links to each phase file.phase-00-*.md through phase-NN-*.md — detailed phase files derived from final_plan_content.fixtures/ — any fixtures generated during probe or planning (optional).Path: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/depth-history.json
{
"run_id": "anneal-temper-YYYYMMDD-HHMMSS-{slug}",
"depth_scores": [62.0, 78.0, 85.0],
"depth_cap": 3,
"convergence": {
"reason": "variance",
"variance_top3": 0.18,
"abs_delta": 7.0,
"depth_reached": 2
},
"depth_details": [
{
"depth": 0,
"plan_path": "depth-0-plan.md",
"momus_envelope": {...},
"redteam_envelopes": {...},
"score": 62.0
}
]
}
Plus per-depth plan snapshots under ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/depth-history/:
depth-0-plan.mddepth-1-plan.mddepth-N-plan.mdRun: {run_id}
Architecture: temper
Depth: {final_depth} of {depth_cap}
Scores: [s_0, s_1, ..., s_N]
Convergence: {reason}
Verdict: {overall_verdict}
Validate: PASS
Emitted: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/temper-{run_id}.xml
Plan: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/plan/
History: ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/depth-history.json
Next: open a fresh Claude Code session and run:
cat ${ANNEAL_RUNS_ROOT:-./.anneal/runs}/{run_id}/temper-{run_id}.xml | claude
<context>, <plan>, <review>, <validation>). Actionable query (<instructions>) at the bottom.<thinking_budget>xhigh</thinking_budget> at the end of the root envelope.python3 scripts/validate-xml.py <path>. If it fails, do NOT emit — surface the error.simultaneous_pass == false. The rollup's decision is authoritative.<thinking>) in the emission; the schema is a prompt, not a transcript.<anneal_run> per file.depth-history.json — downstream tooling depends on machine-readable convergence data.references/xml-template.md.references/xml-template.md — full XML body template with Temper additions._shared/opus-47-xml-schema.md — base schema._shared/plan-reviewer-schema.md — envelope serialization format for <review>.docs/convergence-rules.md — meaning of <convergence> fields.scripts/validate-xml.py — emission validator.npx claudepluginhub krzemienski/anneal --plugin anneal-temperGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.