builder-state

Persist and resume builder sessions by managing docs/builder-state.json state.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill builder-state
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: builder-state
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/builder-state
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill builder-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist and resume builder sessions by storing state in docs/builder-state.json and coordinating session activity like heartbeats, PRD claims, and story progress, enabling seamless recovery after interruptions.

Core Features & Use Cases

  • Persist and load builder state to enable resumability across sessions and restarts.
  • Coordinate events like session start, PRD claim, story progress, ad-hoc tasks, and heartbeat to keep state consistent.
  • Use case: If a session crashes mid-PRD, resume from the last completed story and rehydrate UI todos from docs/builder-state.json.

Quick Start

Initialize or resume a builder session by loading docs/builder-state.json, then update and persist state at each key event (start, claim PRD, start/complete stories, and heartbeat).

Frequently Asked Questions about builder-state

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

FAQPage Schema
How do I persist and resume a builder session after an interruption?▼

Builder session resumability is achieved by loading and updating docs/builder-state.json. The skill coordinates heartbeats, PRD claims, and story progress, allowing you to resume from the last completed story and rehydrate UI todos after a crash.

What is the best way to manage state for PRD claims and story progression?▼

State management for PRD claims and story progression uses event-driven updates to docs/builder-state.json. It coordinates session starts, story progress, and heartbeats to keep state consistent across tasks.

How do state management guardrails handle commit order and recovery paths?▼

State management guardrails enforce atomic writes and specific commit order to docs/builder-state.json. This ensures recovery paths remain reliable during session state updates and heartbeat management.

Can I coordinate ad-hoc tasks and heartbeats within builder state management?▼

Yes, builder state management coordinates events like ad-hoc tasks, session starts, PRD claims, and heartbeats. It updates docs/builder-state.json at each key event to maintain consistent session state.

How does atomic write enforcement protect builder session state?▼

Atomic write enforcement protects builder session state by ensuring updates to docs/builder-state.json are completed fully or not at all. This prevents partial data writes during interruptions, enabling reliable session recovery.

When do I need to initialize builder session state persistence?▼

You need to initialize builder session state persistence when starting a new builder session by loading docs/builder-state.json. This enables seamless recovery and state coordination for subsequent PRD and story tasks.