Initialize repositories and manage explicit changes through a document-driven OSpec workflow.
npx skills add https://github.com/henrydiaosi/dorado --skill ospec-henrydiaosi
Please help me install this Agent Skill. Skill: ospec Source: https://github.com/henrydiaosi/dorado/tree/main Command: npx skills add https://github.com/henrydiaosi/dorado --skill ospec-henrydiaosi
This Skill solves the chaos of ad hoc AI-assisted development by enforcing a document-driven workflow for initializing repositories, creating scoped changes, validating progress, and archiving accepted work consistently.
Use ospec to initialize this project and leave it in a change-ready state without creating the first change automatically.
High-intent search queries and answers about installing and using this skill.
Standardize AI-assisted software delivery by enforcing a document-driven workflow that initializes repositories with protocol files, manages scoped changes explicitly, and validates progress through verification and archive flows. This structured approach replaces chaotic ad hoc AI development.
Document-driven change management for AI development workflows uses tracked workflow files and explicit change containers to advance requirements, bug fixes, refactors, or documentation updates, ensuring disciplined validation and closeout before any change is considered complete and archived.
Initialize a repository into a change-ready state by using Node.js-based CLI commands to generate managed protocol files, baseline project knowledge docs, and AI guidance, leaving the project prepared for creating scoped changes without automatically generating the first change.
Yes, you can enforce design review and automated runtime checks during AI code generation by integrating plugin-aware delivery rules, specifically handling workflow gates through Stitch and Checkpoint plugins to block progress until required validations pass.
Yes, the document-driven workflow supports CLI tools, web apps, services, desktop apps, and protocol-only repositories, applying standardized change execution, project knowledge maintenance, and change state tracking across diverse software delivery scenarios.
Managing queued multi-change planning requires strict adherence to index maintenance and change state tracking; without consistent use of the Node.js-based CLI commands to manage protocol files, the document-driven verification and archive readiness flows will fail to enforce disciplined closeout.
clawplaysInitialize OSpec change-ready protocol shells and orchestrate gated execution workflows.
ruan-catArchive completed changes into dated folders under openspec/changes/archive.
Aurora-AIIntegrates Stitch MCP via API/CLI to generate landing pages and visual components from text prompts.
chohra-medConvert ticket tracker issues and ad-hoc plans into structured spec documents.
