nauro-ship-tasklisted

Run the full planner -> executor -> reviewer -> tech-lead -> user-confirm -> push chain for a non-trivial code change against Nauro's bundled @nauro-* subagents. Gates on the user whenever the planner or tech-lead will file a Nauro decision; the executor never files. Runs @nauro-tech-lead Mode C between reviewer-APPROVE and the push gate to catch doctrine drift the reviewer missed. A prompt that carries a detailed implementation spec or a pasted handoff is still chain input, not license to implement directly. Invoke explicitly with the surface's nauro-ship-task command. Requires `nauro adopt --with-subagents` to have run.
Nauro-AI/nauro · ★ 6 · AI & Automation · score 76

Install: claude install-skill Nauro-AI/nauro

# Nauro ship task skill Orchestrate a non-trivial code change end-to-end using Nauro's bundled `@nauro-planner`, `@nauro-executor`, `@nauro-reviewer`, and `@nauro-tech-lead` subagents, with Nauro doctrine gates at every architectural choice. Take the user's task description from the prompt that invoked this skill. If they did not include one, ask for a one-paragraph description and wait for it before proceeding. ## Prerequisites This skill invokes the bundled `@nauro-*` subagents by name. They install via `nauro adopt --with-subagents` (or `nauro setup all --with-subagents`) and dispatch on Claude Code. If they are missing, or the current surface cannot spawn subagents, the chain cannot run; surface that to the user and stop. Do not reproduce the chain inline in the main session: the gates depend on the subagents' restricted tool access, and an inline imitation runs without those restrictions. The personal-subagent path (`@planner` / `@executor` / `@reviewer` without the `nauro-` prefix) is not a substitute either. The bundled subagents call Nauro's MCP tools by design, which is what makes the doctrine gates load-bearing. The bundled subagents follow the session's model — chain quality tracks the model the session runs. ## Execute the chain without waiting for the user to prompt each step Pause only at the two explicit gates marked GATE below. ## Pre-step — Doctrine triage before the planner spins up Before invoking `@nauro-planner`, the parent session confirms the p