decision-hold-lifecycle

Persist unresolved user decisions to the agent decisions file.

11|Updated Jul 2, 2026

Search Tags:#agent orchestration #user input #decision tracking #session recovery #workflow state #persistent holds

Ready to run

npx skills add https://github.com/romiluz13/auto-pi --skill decision-hold-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-hold-lifecycle
Source: https://github.com/romiluz13/auto-pi/tree/main/skills/decision-hold-lifecycle
Command: npx skills add https://github.com/romiluz13/auto-pi --skill decision-hold-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unresolved user decisions from being forgotten during task execution, context compaction, or session restarts by recording them as durable hold items.

Core Features & Use Cases

Decision Inventory: Captures each genuine user-dependent choice with a stable key, title, reason, and project path.
Durable Holds: Persists unresolved decisions to the agent's decisions file so they remain available across sessions.
Resolution Tracking: Keeps holds open until the user's answer is recorded, supporting idempotent updates and reliable follow-through.
Use Case: When implementation reveals a choice between cursor-based and offset-based pagination, record the decision as a hold so it can be surfaced and resolved before the work is considered complete.

Quick Start

Use the decision hold lifecycle skill whenever work uncovers an unresolved choice that requires the user's input.

Frequently Asked Questions about decision-hold-lifecycle

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

FAQPage Schema

How do I preserve unresolved user decisions during agent workflow state changes and session restarts?▼

Persist unresolved user decisions by recording them as durable hold items in an agent decisions file. This ensures open choices requiring user input remain available across context compaction and session restarts until they are resolved.

What is persistent decision tracking in agent orchestration and when do I need it?▼

Persistent decision tracking captures user-dependent choices with stable keys and durable storage. You need it when agent workflows discover open choices that require user input before implementation or completion can proceed.

How do I record and track unresolved user input choices so they are not lost during task execution?▼

Record each unresolved choice as a durable hold with a stable key, title, reason, and project path in the agent decisions file. The hold remains open until the user's resolution is recorded, supporting idempotent updates and reliable follow-through.

Can I recover unresolved workflow state and open decisions after a session restart?▼

Yes, durable holds persist unresolved decisions to the agent decisions file so they remain available across session restarts. Surfaced status checks and idempotent retry behavior ensure reliable session recovery and follow-through.

Does decision tracking with persistent holds support idempotent updates for repeated user input?▼

Yes, decision hold lifecycle supports idempotent updates by keeping holds open until the user's answer is recorded. This ensures repeated or retried user input resolves the decision reliably without duplicating workflow state.

What are the limitations of using a decisions file for persistent holds in agent workflows?▼

Persistent holds require stable decision keys and durable storage in the agent decisions file. They apply only to genuine user-dependent choices discovered during task execution, not to autonomous agent decisions that do not require user input.