Ospec
Run a document-driven OSpec workflow so AI-assisted changes start initialized, execute against specs, validate, and stay archive-ready.
Overview
ospec is an agent skill most often used in Build → pm (also Validate → scope, Ship → review) that runs a document-driven OSpec workflow with initialization, execution, validation, and archive readiness.
Install
npx skills add https://github.com/clawplays/ospec --skill SKILL.mdWhat is this skill?
- Document-driven OSpec workflow for AI-assisted development
- Change-ready initialization before implementation starts
- Structured execution phase aligned to written specs
- Validation step before treating work as complete
- Archive readiness so changes remain auditable and storable
- 4 named lifecycle phases: initialization, execution, validation, archive readiness
Adoption & trust: 581 GitHub stars.
What problem does it solve?
Your agent starts coding without a change-ready spec path, so AI-assisted work is hard to validate or archive consistently.
Who is it for?
Solo builders practicing spec-first or document-driven AI development who need explicit validation and archive gates.
Skip if: Quick throwaway prototypes where no written change spec or validation archive is desired.
When should I use this skill?
You are doing AI-assisted development that must follow a document-driven OSpec workflow from init through validation and archive.
What do I get? / Deliverables
You get a spec-backed change flow from initialized documents through executed work and validation, ending archive-ready for the next implementation or review step.
- Change-ready initialized spec artifacts
- Validated execution outcome
- Archive-ready change package
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
OSpec is shelved under Build → pm because it governs how specs become executed, validated change work—not one-off coding snippets. PM is the right subphase for change-ready initialization, execution discipline, validation gates, and archive readiness across a spec lifecycle.
Where it fits
Initialize OSpec documents so a proposed feature change is explicit before you let the agent touch code.
Execute implementation tasks strictly against the archived spec set for a SaaS module.
Run the validation phase to confirm the change matches docs before marking the work archive-ready.
How it compares
Workflow skill for OSpec document lifecycles—not a linter-only checker or a single-file code generator.
Common Questions / FAQ
Who is ospec for?
Indie developers and small teams using coding agents who want OSpec-style document discipline across initialization, execution, validation, and archiving.
When should I use ospec?
Use it in Validate scope when drafting change-ready docs, in Build pm when executing against those specs, and in Ship review when validating before you treat a change as done or archivable.
Is ospec safe to install?
Review the Security Audits panel on this Prism page; workflow skills may encourage filesystem or git use when archiving spec artifacts.
SKILL.md
READMESKILL.md - Ospec
Document-driven OSpec workflow for AI-assisted development with change-ready initialization, execution, validation, and archive readiness. # ospec { "name": "ospec", "description": "Document-driven OSpec workflow for AI-assisted development with change-ready initialization, execution, validation, and archive readiness." }