nauro-looplisted

Originate gated Delivery and Interview candidates, or coordinate selected Program Delivery as FRAME -> CHOOSE -> START -> ADVISE -> VERIFY -> ADVANCE. Human-named work bypasses candidate selection. Agent-originated work keeps read-only ORIENT, 1-3 candidates, mandatory human selection, reject-all, and no auto-pick path. Each Program slice uses at most one fresh direct-user Delivery task. Automatic launch requires surface lifecycle support to create, identify, inspect, and message that task; otherwise the coordinator returns one exact launch prompt and stops. Coordinator artifact review is advisory, and integration is verified independently. Synchronous non-program Delivery stays outside the Program state machine. Interview stays explicit and non-authoritative. Ordinary outputs create no automatic store artifacts; scheduled ORIENT retains its existing SELECT checkpoint and pointer writes as a narrow process-state exception. Installed by `nauro adopt --with-skills`.
Nauro-AI/nauro · ★ 10 · AI & Automation · score 70

Install: claude install-skill Nauro-AI/nauro

# Nauro loop skill Run gated work origination and coordinate selected Program Delivery. The Program state machine is `FRAME -> CHOOSE -> START -> ADVISE -> VERIFY -> ADVANCE`. The coordinator owns the verified frame, sequence, handoff, advisory review, integration verification, and next recommendation. It does not implement, approve, file project truth, push, create a pull request, merge, or start the next slice. User-named work enters as `HUMAN-SELECTED`. Agent-originated work keeps read-only ORIENT, 1-3 ranked Delivery and Interview candidates, mandatory SELECT, reject all, and no auto-pick path. Interview remains explicit, separate, and non-authoritative. Synchronous non-program Delivery stays outside the Program state machine and keeps the current `nauro-ship-task` chain. ## Authority boundary These are authority rules. MCP or shell write paths may exist, but they do not grant the coordinator authority to use them for Program Delivery. - The loop cannot automatically change project truth or file decisions. Ordinary prompts, Interview results, Delivery handoffs, and program handbacks create no automatic store artifacts. The scheduled ORIENT selection-checkpoint writes are the narrow exception: they create only the existing SELECT checkpoint and pointer through the filesystem and `nauro sync` mechanism defined below. A selected Interview returns candidate shared understanding only. After the interview, an explicitly approved `propose_decision`, `update_state`, or `flag