ospec-change

Name: ospec-change
Availability: InStock
Author: henrydiaosi

Creates and advances OSpec changes from requirement intake to final archive.

106|15|Updated Mar 21, 2026

Search Tags:#workflow #requirements #verification #queue #change-management #stitch #ospec

Ready to run

npx skills add https://github.com/henrydiaosi/dorado --skill ospec-change-henrydiaosi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ospec-change
Source: https://github.com/henrydiaosi/dorado/tree/main/assets/global-skills/claude/ospec-change
Command: npx skills add https://github.com/henrydiaosi/dorado --skill ospec-change-henrydiaosi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage an active OSpec change without losing track of requirements, progress, validation, or closeout.

Core Features & Use Cases

Requirement intake and change matching for new work or continuing an existing change.
Queue-aware planning when the user explicitly wants ordered work items.
Progress, verification, and archive readiness guidance with plugin gate checks such as Stitch when enabled.
Use case: a developer asks to advance a bug fix from proposal through tasks, verification, and final finalize steps.

Quick Start

Use the ospec-change skill to advance the current active change for my project.

Frequently Asked Questions about ospec-change

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

FAQPage Schema

How do I manage an OSpec change from requirement intake to final archive?▼

To manage an OSpec change end to end, you advance the active change through requirement intake, proposal refinement, task tracking, implementation guidance, verification, and final closeout. This ensures progress, validation, and archive readiness are tracked continuously.

Can I use queue-driven work items for ordered OSpec change planning?▼

Yes, you can use queue-aware planning for ordered OSpec work items. When you explicitly want ordered work, the workflow matches requirements and coordinates proposal, tasks, and state documents to advance changes sequentially.

How does change verification work with plugin gates like Stitch?▼

Change verification applies plugin gate checks, such as Stitch when enabled, to enforce validation before closeout. It coordinates verification and review documents to ensure the active OSpec change meets archive readiness requirements.

Do I need an initialized OSpec project to advance a change?▼

Yes, you need an initialized OSpec project to advance a change. The workflow requires reading project metadata to coordinate proposal, tasks, state, verification, and review documents for requirement intake and final archive.

What is the best way to track implementation guidance for a single change?▼

The best way to track implementation guidance for a single change is by advancing the active OSpec change through task tracking and state coordination. This reads project metadata and enforces plugin gates to guide the work to final closeout.

Why does OSpec change management require coordinating multiple documents?▼

OSpec change management requires coordinating proposal, tasks, state, verification, and review documents to prevent losing track of requirements, progress, and validation. This coordination enforces plugin gates and ensures proper archive readiness for the active change.