state-update

Update sprint state files and harness artifacts after decisive outcomes.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill state-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-update
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/state-update
Command: npx skills add https://github.com/thompson0012/agents-stack --skill state-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconciles decisive sprint outcomes by updating the durable project state to reflect the latest review or execution results.

Core Features & Use Cases

  • Applies to the active sprint by mutating the authoritative backlog and focus artifacts to reflect current reality.
  • Preserves evidence and routing information by maintaining references to harness artifacts and docs/archive as needed.
  • Queues explicit Compound work when applicable to enable learning and proper downstream actions.

Quick Start

Immediately reconcile the latest sprint outcome by running the state-update flow after a decisive review or execution result.

Frequently Asked Questions about state-update

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

FAQPage Schema
How do I reconcile sprint outcomes with durable project state after a review?

Reconcile sprint outcomes by running the state-update flow to mutate authoritative backlog and focus artifacts, ensuring the durable project state reflects the latest review or execution results.

What is the best way to update the active sprint backlog and focus artifacts?

Update the active sprint by mutating docs/live/tracked-work.json, current-focus.md, roadmap.md, and progress.md to reflect current reality while preserving evidence paths and routing information.

When do I need to queue explicit compound work during sprint reconciliation?

Queue explicit compound work during sprint reconciliation when decisive outcomes require learning and proper downstream actions, enabling subsequent processing after updating the durable state.

Does sprint state validation work against the project contract?

Sprint state validation works against the contract by ensuring all updates to durable project state propagate next actions correctly and maintain compliance during the reconciliation process.

How do I preserve evidence paths when updating project state files?

Preserve evidence paths by maintaining references to harness artifacts under .harness/<sprint-id>/ and docs/archive when mutating the authoritative backlog and focus artifacts during state updates.