Advance an OSpec change from requirement intake through verification and finalize.
npx skills add https://github.com/clawplays/ospec --skill ospec-change
Please help me install this Agent Skill. Skill: ospec-change Source: https://github.com/clawplays/ospec/tree/main/assets/global-skills/claude/ospec-change Command: npx skills add https://github.com/clawplays/ospec --skill ospec-change
OSpec Change helps you turn requirement intake into a tracked, verifiable, and properly closed-out implementation inside an initialized OSpec project—without losing context across proposal, tasks, verification, review, and archive readiness.
Tell the AI: "Use ospec change to handle this requirement and verify it, then finalize the change when it’s ready."
High-intent search queries and answers about installing and using this skill.
Requirement-to-finalize change management in an OSpec project is handled by advancing the active change from intake through proposal, task refinement, verification, and finalize closeout using OSpec CLI commands. This enforces initialization boundaries and ensures proper state tracking.
Stitch design review gates are enforced via the project's .skillrc configuration, which blocks progress until the Stitch approval artifact exists and is approved. This ensures plugin gate enforcement prevents advancing changes without required design reviews.
Queue planning is available when explicitly requested, creating an ordered set of kebab-case queued changes. The queued changes are planned but only run when you ask, ensuring single-change execution remains the default behavior.
OSpec change management works by using project-scoped updates and OSpec CLI closeout commands instead of parallel custom workflows. This ensures all proposal, tasks, state, verification, and review alignment stay within the initialized project boundaries.
Change progress gets blocked before verification when the Stitch design review is enabled and the approval artifact is missing. The project's configured plugin setup requires the Stitch approval to exist and be approved before allowing further advancement.
An initialized OSpec project is required to execute change lifecycle guidance, as the process respects initialization boundaries and relies on OSpec CLI closeout commands. Without initialization, project-scoped updates and state tracking cannot function properly.
clawplaysInitialize OSpec change-ready protocol shells and orchestrate gated execution workflows.
henrydiaosiCreates and advances OSpec changes from requirement intake to final archive.
ricoyudogGenerate proposal, design, and tasks artifacts with GitHub issue tracking.
HeartcoolmanGenerate design, specification, and task proposals via the openspec CLI.
