Menu
Walk a first-time user through one real cospec change end to end, narrating each step.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Run the apply gate for a change and implement its tasks, obeying the gate's exit code.
Archive a completed change — validate, merge specs, verify, and fan blockers out.
Archive a batch of completed changes in dependency order, one cospec archive call at a time.
Resume a partially-built change and finish its remaining artifacts.
Investigate the codebase or a spec question without writing implementation code.
Author every remaining artifact on an already-scaffolded change in one pass, then validate.
| name | cospec-onboard |
| description | Walk a first-time user through one real cospec change end to end, narrating each step. |
| license | MIT |
| compatibility | Requires the cospec CLI (@aligned-team/cospec). |
| metadata | {"author":"cospec","generatedBy":"cospec@0.5.1","contentHash":"sha256:c0acf01721c99e0b50950041c4080c330b709e81b07ef095b69784b1bedc7960"} |
Walk a first-time user through one real cospec change, end to end, narrating each step before running it. This is a tutorial: explain, then do, then show the result, then pause for the user before continuing. Stop gracefully at any point the user wants to.
All work goes through cospec. Never call openspec directly.
cospec doctor
Confirm cospec is set up in this repo (schemas present, no drift). Explain
what doctor checked before moving on.
Look for something genuinely small in this repo: a TODO/FIXME comment, a
one-line docs fix, or the shape of a recent small commit
(git log --oneline -10). Explain why a small task is the right first change to
onboard with. If nothing small is at hand, ask the user for one — do not
manufacture busywork.
Steer toward chore or docs — three short artifacts, not the full feat
treatment — unless the task the user picked is genuinely a feature or fix.
Explain the tradeoff (lighter type, fewer artifacts, faster loop) before asking
the user to confirm the type.
cospec new <type> <slug>
Show the printed artifact plan and explain what each artifact is for. Pause: confirm the user wants to continue before authoring anything.
For each artifact in the plan, in order:
cospec instructions <artifact> --change <slug> --json
Explain what the instructions ask for, write the artifact, show the user what you wrote, and pause before moving to the next artifact.
cospec validate <slug> --strict
Explain what this checks. Fix anything it flags, narrating the fix, then re-run until clean.
cospec apply <slug> --json
Explain the exit code before acting on it: 0 clear (proceed to implement), 2
blocked (a required artifact or a hard blocker — stop and explain which), 3
soft-blocked (confirm with the user, then re-run with --allow-soft).
Work through tasks.md, checking off each box as you finish it. If the type
plans a verification.md, fill in each row's observed result as you go rather
than leaving it for later. Pause after implementation to show the user the diff
before archiving.
cospec archive <slug>
Explain what just happened: the change validated, its spec deltas merged (or were skipped), the move was verified on disk, and any blocker boxes fanned out to sibling changes.
Tell the user they have now run the full cospec loop once end to end, and point
at /cospec:propose (or /cospec:new plus /cospec:ff or /cospec:continue)
for their next real change.