Use when working inside AxiomNexus with generic upstream skills and you need the thinnest possible local layer to shape inputs and normalize outputs into evidence that `transition-executor` can turn into a valid `TransitionIntent`.
Use this skill as a thin local adapter, not as a replacement for upstream skills.
Choose the right generic upstream skill, pass the minimum Nexus-specific context into it, then normalize the result into evidence that can honestly support propose_progress, complete, or block.
Prefer the existing generic skills for the real work:
build-write-codecheck-final-verifytest-run-user-scenariosworkflow-build-execute-plancontrol-build-until-doneThis local skill exists only to adapt them to Nexus rules.
.agents/AGENTS.md.agents/skills/transition-executor/SKILL.mdREADME.mdsamples/transition-intent.schema.jsonsamples/execute-turn-output.schema.jsonbuild-write-code for one bounded code change with explicit verification.check-final-verify when the work is done and the remaining question is whether the contract and evidence really support a pass.test-run-user-scenarios when you need realistic operator, runtime, or agent scenarios to produce trustable evidence.workflow-build-execute-plan when a task ledger exists and the work should follow it.control-build-until-done when no task ledger exists and the done contract is already clear.Whichever upstream skill you choose, carry these Nexus facts alongside it:
Do not expand the upstream skill contract more than needed. Pass only the facts that change the honesty of the result.
After the upstream skill finishes, normalize the result into this evidence bundle:
changed_filescommand_resultsartifact_refsnotesresolved_obligationsdeclared_risksverification_gapsproposed_intent_kindIf the upstream output is missing one of these, do not invent it. Mark the gap.
complete: only when the contract-facing work is satisfied and evidence exists for that claim.propose_progress: use when meaningful work happened but completion would overclaim.block: use when required evidence, required surface, or required state is missing and continuing would be dishonest.scheduler once is the canonical operator path.run once <run_id> is the deterministic diagnostic path.complete, downgrade to propose_progress or block.Return a short adapter note with: