Decant Debug
Diagnose a failure from reproducible evidence and isolate its root cause. Use for regressions, flaky behavior, stuck automation, or failed checks; edit only when the user also asked for a fix.
Decant Orchestrate
Route a multi-stage repository task through the smallest useful Decant workflow. Use for work that mixes research, planning, implementation, review, or release; do not use for a single obvious read or edit.
Relay10 Release
Prove that an authorized release or handoff is reproducible, traceable, and honestly described. Use for packaging, GitHub delivery, artifact reports, or launch preparation; do not publish without explicit authorization.
Decant Spec
Turn an ambiguous or high-impact change request into a small executable specification using bounded Socratic clarification and a confirmed task contract. Use when scope, authority, acceptance checks, or rollback are unclear; do not use for a narrow reversible edit or a question the repository can answer.
Relay10 Research
Gather current, read-only evidence about a repository, API, product, or ecosystem. Use before broad changes, comparisons, or claims that may have changed; do not use when the user already supplied sufficient stable evidence.
Relay10 Skill Lab
Create or tune a focused DisciplinedRun skill using clean-room prompts, trigger tests, and with-skill versus baseline evaluation. Use when adding a skill or changing its description or workflow; do not use merely to run an existing skill.
Decant Skill Lab
Create or tune a focused Decant skill using clean-room prompts, trigger tests, and with-skill versus baseline evaluation. Use when adding a skill or changing its description or workflow; do not use merely to run an existing skill.
Decant Release
Prove that an authorized release or handoff is reproducible, traceable, and honestly described. Use for packaging, GitHub delivery, artifact reports, or launch preparation; do not publish without explicit authorization.
Relay10 Build
Implement an authorized repository change in small, verifiable slices. Use after scope and acceptance criteria are clear; do not use for diagnosis-only, review-only, or publication-only requests.
Relay10 Orchestrate
Route a multi-stage repository task through the smallest useful DisciplinedRun workflow. Use for work that mixes research, planning, implementation, review, or release; do not use for a single obvious read or edit.
Relay10 Spec
Turn an ambiguous or high-impact change request into a small executable specification using bounded Socratic clarification and a confirmed task contract. Use when scope, authority, acceptance checks, or rollback are unclear; do not use for a narrow reversible edit or a question the repository can answer.
Relay10 Debug
Diagnose a failure from reproducible evidence and isolate its root cause. Use for regressions, flaky behavior, stuck automation, or failed checks; edit only when the user also asked for a fix.
Decant Build
Implement an authorized repository change in small, verifiable slices. Use after scope and acceptance criteria are clear; do not use for diagnosis-only, review-only, or publication-only requests.
Relay10 Review
Review a fixed change set for specification compliance, correctness, security, regression risk, and evidence quality. Use for code or release review; remain read-only unless the user separately requests fixes.
Decant Research
Gather current, read-only evidence about a repository, API, product, or ecosystem. Use before broad changes, comparisons, or claims that may have changed; do not use when the user already supplied sufficient stable evidence.
Decant Review
Review a fixed change set for specification compliance, correctness, security, regression risk, and evidence quality. Use for code or release review; remain read-only unless the user separately requests fixes.