ruver-feature-deliverylisted

Use when delivering a Linear ticket, bug, or chore end-to-end (implementation through draft PR with CI green) via /ruver-feature-delivery or /ruver-fd, or when resuming a run whose HANDOFF.md exists under $RUVER_ROOT/.ruver-feature-delivery/. Spine: grill-with-docs → spec → tickets → implement(tdd) → review. User-facing chat in Brazilian Portuguese. Unslop. Never write .ruver-* inside a repo.
ruverd/skills · ★ 1 · AI & Automation · score 67

Install: claude install-skill ruverd/skills

# Ruver feature delivery Orchestrator. Speak to the user in Brazilian Portuguese. Unslop. **No product code on the main thread.** Load now: - [GRAPH.md](GRAPH.md) - [STATE.schema.md](STATE.schema.md) - [ROUTING.md](ROUTING.md) - [VOICE.md](VOICE.md) - [PSTACK.md](PSTACK.md) - [DECISION_POLICY.md](DECISION_POLICY.md) - `ruver-bus` [DISK.md](../../graphs/ruver-bus/DISK.md) Spine (Matt Pocock + pstack, not Superpowers): ``` grill-with-docs → to-spec → to-tickets → implement(/tdd) → code-review ``` Adapted grill: [GRILL.md](GRILL.md). ASK the user only as a last resort. ## Quick start ```text /ruver-fd DEV-1212 /ruver-fd DEV-1212: extra note /ruver-fd null crash in MembersTable /ruver-fd resume /ruver-fd … --no-pr ``` Linear branch `feature/dev-xxxx` (or Linear `gitBranchName`). ## Orchestrator loop **Resume:** read STATE + HANDOFF, **RECONCILE** (git/gh vs STATE, see HANDOFF.md), continue at the current node. If `waiting_user`, the user message is the ASK answer. Do not re-init. Do not re-run mcp_context / triage / grill branches that are already settled. **Fresh:** 1. Init STATE under `$RUVER_ROOT/.ruver-feature-delivery/`. 2. `mcp_context` then `triage`. Critical MCP down → STOP. Do not invent. 3. Walk GRAPH. Grill / spec / tickets on the main thread. Spawn **one** node subagent at a time for implement / review / diagnose / tester / quality / shipper. 4. Never merge. Draft PR only from `shipper`. 5. Near context limit → `handoff`. ## Paths | path / scope | When