Persist crash-safe SDLC checkpoint state to YAML and verify resume routing.
npx skills add https://github.com/gleeb/ai-registry --skill sdlc-checkpoint
Please help me install this Agent Skill. Skill: sdlc-checkpoint Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/sdlc-checkpoint Command: npx skills add https://github.com/gleeb/ai-registry --skill sdlc-checkpoint
sdlc-checkpoint prevents SDLC workflow drift by persisting crash-safe checkpoint state and providing deterministic resume routing across planning and execution hubs.
.sdlc/*.yaml before each sub-agent dispatch, ensuring progress can be resumed after interruptions.verify.sh cross-references checkpoint state against real on-disk artifacts (including staging-doc progress) and recommends the next action..sdlc/dispatch-log.jsonl via dispatch-log for traceability and debugging.Load the sdlc-checkpoint skill and run checkpoint.sh continue after receiving a /sdlc-continue-checkpoint command.
High-intent search queries and answers about installing and using this skill.
Resume verification cross-references checkpoint state against real on-disk artifacts and staging-doc progress, recommending the next action. It writes coordinator, planning, and execution YAML before dispatch to prevent workflow drift across planning and execution hubs.
Crash-safe write-ahead checkpointing persists workflow state to `.sdlc/*.yaml` files before each sub-agent dispatch. It is needed when orchestrating multi-agent story planning and task execution to prevent workflow drift and enable deterministic continuation after interruptions.
Enable optional dispatch logging to write dispatch and response records to `.sdlc/dispatch-log.jsonl`. This provides dispatch-log correlation for deterministic continuation, traceability, and debugging across multi-agent story planning and task execution handoffs.
Yes, the git-integrated story lifecycle coordinates branch, commit, and merge boundaries for each story branch. This checkpointing approach enables consistent continuation of SDLC workflows and multi-agent task execution across different machines.
Yes, the `verify.sh` script cross-references checkpoint state against real on-disk artifacts, including staging-doc progress. It validates expected artifacts before resume and recommends the next action for verification-driven routing during task execution.
File-based YAML checkpointing limitations include reliance on local `.sdlc/*.yaml` files, requiring write-ahead updates before each sub-agent dispatch. It lacks distributed locking for concurrent multi-agent writes, making it best suited for sequential SDLC orchestration workflows.
alansmelloInitialize a Git repository with an initial commit in Bash or PowerShell.
adiomasSave session state and generate next-session.md for continuation.
michael-conradRoute plan creation through a six-step pipeline with Z3-verified state transitions.
ROLLED740Persist Codable items via an actor-backed repository with in-memory cache and atomic file writes.