stamina

Fan-out review adapter. Routes a high-blast-radius artifact (plan or PR) through multiple heterogeneous review passes and gates on consensus. Does not review; dispatches existing review skills (/simplify, /review, /review-senior, /safer:dogfood, /codex, /security-review for PRs; /safer:dogfood + /safer:review-senior + /codex for plans) and aggregates their verdicts. N is set by the blast-radius x reversibility table in PRINCIPLES.md > Durability. Two invocation modes: --plan <sub-issue-URL> and --pr <pr-URL>. Use when the caller (typically /safer:orchestrate Phase 5c) has decided the artifact warrants stamina. Do NOT self-invoke from the working modality; that is Principle 5 self-polishing.

Safety Notice

This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.

Copy this and send it to your AI assistant to learn

Install skill "stamina" with this command: npx skills add chughtapan/skillsmp-chughtapan-chughtapan-stamina

No markdown body

This source entry does not include full markdown content beyond metadata.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHub

Related Skills

Related by shared tags or category signals.

Coding

architect

Turn an approved spec into a module layout: named modules, public interfaces, data flow, error channels, dependency choices. Produces a design doc (markdown) plus interface-stub files (function signatures with `throw new Error("not implemented")` bodies) so downstream `implement-*` modalities can execute against a published contract. Use when a spec exists and the next question is "what shape of code." Do NOT use when no spec exists (send to `/safer:spec` first), or when the work is obviously one-module (send to `/safer:implement-junior`).

Repository SourceNeeds Review

-0chughtapan

General

implement-senior

Cross-module coordination WITHIN an approved architect plan. May refactor internals across modules, add private helpers that span modules, and reorganize file layouts when the plan authorizes it. May NOT introduce new modules, new architectural patterns, new public contracts outside the plan, or new deps. Use when the architect plan explicitly covers multi-module work and the implementer needs to coordinate across them. Do NOT use for one-module work (route to `/safer:implement-junior`) or for introducing new modules/deps (route to `/safer:implement-staff`).

Repository SourceNeeds Review

-0chughtapan

General

implement-staff

Introduce new modules, new public interfaces, and new package dependencies in service of an approved spec. Every change traces back to a spec line. Staff does not revise the spec. Use when the spec explicitly names new architectural territory (a new module, a new API, a new dep) and someone has to build it. Do NOT use when the work fits inside an existing module (route to `/safer:implement-junior`) or when the plan is multi-module but stays within existing modules (route to `/safer:implement-senior`).

Repository SourceNeeds Review

-0chughtapan

Coding

orchestrate

Decompose a multi-step intent into sub-tasks, classify each by modality, route each sub-task to the right modality skill, gate every handoff on a published artifact, and track the whole pipeline via GitHub issues. Use when a goal spans more than one modality (not just implementation, not just investigation, not just research) or when sub-tasks have dependencies that need sequencing. Do NOT use for single-modality work — invoke the modality directly. This skill is the VP of Engineering.

Repository SourceNeeds Review

-0chughtapan