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.
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.
$
Open Repositorynpm install -g @clawplays/ospec-clirecommended-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.
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.
Built For Explicit AI Collaboration
"Initialization should leave a repository change-ready, not half-bootstrapped or waiting on hidden scaffold decisions."
"The first change stays explicit, queue mode stays explicit, and closeout stays explicit through verify and finalize."
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