Initialize To Change-Ready
AI-assisted init can ask one concise follow-up when project context is missing; plain CLI init stays non-interactive.
Recommended prompt
Use OSpec to initialize this project.
Prompt + Docs Workflow
Document-DrivenAI Development Workflow,For Real Delivery.
OSpec is a document-driven workflow for AI conversational collaboration. It only takes three steps: initialize the project, submit a Change to start a new requirement, then archive it through the standard path after deployment and validation.
recommended-flow.md
STEP 1Recommended prompt
Use OSpec to initialize this project.
If project context is missing, AI-assisted init should ask at most one short follow-up.
STEP 2Recommended prompt
Use OSpec to create and advance a change for this requirement.
Keep the work inside one explicit change so proposal, tasks, state, verification, and review stay inspectable.
STEP 3Recommended prompt
Use OSpec to archive this accepted change.
After deploy and validation, archive the accepted change through the standard path.
Initialize
ONE CHANGE
VERIFY
ARCHIVE COMPLETE
Just Three Steps To Complete Feature Development
Initialize the repository, move the requirement forward inside one change, then archive that change after deployment and validation are complete.
Create And Advance One Change
The default workflow stays focused on one active change unless you explicitly choose queue mode.
Recommended prompt
Use OSpec to create and advance a change for this requirement.
Archive After Acceptance
`ospec finalize` verifies the change, refreshes the index, archives it, and leaves Git commit as a separate manual step.
Recommended prompt
Use OSpec to archive this accepted change.
Plugin Capability
Add design review and local verification
Connect visual preview and real runtime checks directly to the OSpec workflow
// stitch-plugin
Stitch
Design review and canonical alignment
Use it for page design review, canonical screen management, and preview submission so landing page and route-level visual changes are visible before implementation
// checkpoint-plugin
Checkpoint
Local preview and UI verification
Use it for local preview, browser flow checks, and UI verification so page changes run in a real environment before you archive them
After project initialization you can start submitting requirements and building
Install OSpec, initialize once, then move every accepted requirement through an explicit change and the standard verify/finalize closeout path.
InitializeONE CHANGEVERIFYARCHIVE COMPLETE