Drive deterministic Compozy techspec execution with resumable iterations and atomic git checkpoints.
npx skills add https://github.com/compozy/agh --skill cy-codex-loop
Please help me install this Agent Skill. Skill: cy-codex-loop Source: https://github.com/compozy/agh/tree/main/.agents/skills/cy-codex-loop Command: npx skills add https://github.com/compozy/agh --skill cy-codex-loop
cy-codex-loop solves the problem of reliably running long, multi-step Compozy techspecs across many agent restarts without losing progress, by detecting the current phase from durable state and the filesystem, executing exactly one phase action per iteration, and producing an atomic git checkpoint after each Phase B completion.
state.yaml plus .compozy/tasks/<slug>/ truth, then runs one deterministic action and stops for the next restart.mode=tasks, or advances deliverables via time-bounded slices in mode=free, keeping a checklist-backed progress model.state.yaml only via the provided scripts and writes workflow memory through cy-workflow-memory using the shared and per-iteration memory paths.commit-checkpoint.py so completed tasks/slices become restorable snapshots.delegation=frontend-docs, qualifying Phase B work can be delegated via compozy exec with strict no-commit and explicit cy-final-verify PASS evidence requirements.Use the cy-codex-loop skill for a feature slug that already has a .compozy/tasks/<slug>/_techspec.md and either _tasks.md + task_*.md files (for tasks mode) or no task graph (for free mode).
High-intent search queries and answers about installing and using this skill.
Resuming multi-step techspec execution after an agent restart requires detecting the current phase from durable state and the filesystem, running one deterministic action, and producing an atomic git checkpoint to preserve progress.
Managing long-running workflow state with git checkpoints involves updating a durable state file only via provided scripts and committing atomic snapshots after each completed task or time-bounded slice.
Running techspec tasks in free mode advances deliverables via time-bounded slices, while task mode executes task-by-task, with both modes keeping a checklist-backed progress model for the workspace.
Yes, starting agent orchestration with state machine phases requires an existing techspec file and either task graph files for tasks mode or no task graph for free mode in the workspace directory.
Yes, you can delegate frontend and docs work during quality assurance execution via a goal signature gate, requiring strict no-commit policies and explicit final verification PASS evidence.
A workflow loop stops after one phase action completes because it is designed to run exactly one deterministic action per iteration and then stop, ensuring safe restarts and consistent state transitions.
rhuangabrielsantosDecompose PRDs and TechSpecs into detailed markdown task files with metadata.
specvitalOrchestrate analyze, plan, execute, and commit in one automated run.
zb-ssStandardize workflow phase agent file operations and state tracking.
Devvraj10Execute post-merge scripts and sync workflows automatically.