polyphony-dogfood-recovery

Reset residual state from polyphony dogfood root runs before re-launching.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-dogfood-recovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polyphony-dogfood-recovery
Source: https://github.com/PolyphonyRequiem/polyphony/tree/main/.github/skills/polyphony-dogfood-recovery
Command: npx skills add https://github.com/PolyphonyRequiem/polyphony --skill polyphony-dogfood-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators recover from a wedged or completed polyphony dogfood root run by wiping residual prior-run state so the root can be re-launched cleanly.

Core Features & Use Cases

  • Run state reset runbook: Drives a controlled reset of branches, PRs, worktrees, manifest entries, and run watermarks via the shipped reset workflow model.
  • Safety-first halting guidance: Prevents collisions by instructing how to stop the conductor before performing reset operations.
  • Edge-case operator gotchas: Documents manual recovery actions for dirty worktrees, .twig/config drift, hand-edited work-item state, and platform-ineligible “close” operations for completed PRs.

Quick Start

Run the reset preview for the affected root by executing: ./scripts/Invoke-PolyphonySdlc.ps1 -RootId <N> -Intent reset.

Frequently Asked Questions about polyphony-dogfood-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reset a stuck dogfood run in polyphony?▼

To reset a stuck dogfood run, execute the Invoke-PolyphonySdlc reset workflow with the target RootId to tear down residual branches, PRs, worktrees, and manifest artifacts, ensuring a clean baseline for re-launching the workflow.

What is a polyphony dogfood run reset and when do I need it?▼

A polyphony dogfood run reset is a recovery process that wipes residual prior-run state after a workflow wedges or completes. You need it when stale branches, PRs, or watermarks prevent safely re-launching the root run.

How do I stop the polyphony conductor before resetting run state?▼

You must explicitly halt any running polyphony conductor before performing reset operations to prevent state collisions. The Skill provides safety-first halting guidance to stop the conductor before executing the reset workflow.

What manual recovery steps are needed for dirty git worktrees during a run reset?▼

Manual recovery for dirty git worktrees involves addressing edge cases the automation cannot resolve, including hand-edited work-item state, `.twig/config` drift, and platform-ineligible close operations for completed PRs during the reset.

Does the polyphony reset workflow support idempotent run state teardown?▼

Yes, the reset workflow supports idempotent reset semantics through guarded invocation of Invoke-PolyphonySdlc, allowing safe repeated execution to reconcile branches, PRs, worktrees, manifest artifacts, and run-started-at watermark state.

Why does my polyphony dogfood root run fail to re-launch after completing?▼

Your dogfood root run fails to re-launch because residual prior-run state like stale branches, PRs, and manifest artifacts blocks dispatch. Resetting these elements via the reset workflow restores a clean baseline for re-launch.