Skip to content

oneafrikan/the-grid / plugins/grid-core/skills/openspec-help

openspec-help

Verified

Quick-reference card for OpenSpec in the-grid (the 12 wired skills, spec format, CLI). Use when the user asks "how do I use openspec", "how do I add specs to this repo", "what are the openspec commands" or "which openspec skill do I want".

openspec-help

One-shot reference. Not a mode — display and stop.

OpenSpec is spec-driven development: proposals get written and reviewed before code exists, and the spec survives the session that produced it. Upstream is Fission-AI/openspec (MIT), tracked at repos/openspec.

The 12 skills

Normal path — start here:

SkillWhen
/openspec-exploreThinking out loud before committing to a direction. No artefacts written.
/openspec-proposeYou know what you want. Creates the change + all artefacts in one pass.
/openspec-apply-changeProposal reviewed and accepted — implement the tasks.
/openspec-verify-changeCheck the implementation actually matches the spec, before archiving.
/openspec-archive-changeFold the delta into openspec/specs/, move the change to archive/.

When the normal path doesn't fit:

SkillWhen
/openspec-new-changeStep-by-step artefact creation instead of propose's one-shot.
/openspec-continue-changePick up a change someone (or a past session) left half-built.
/openspec-ff-changeFast-forward — generate every artefact without stepping through.
/openspec-update-changeRevise an existing plan and keep its artefacts coherent. Never edits code.
/openspec-sync-specsPush a delta into main specs without archiving the change.
/openspec-bulk-archive-changeSeveral parallel changes finished at once.
/openspec-onboardGuided first cycle, narrated, on real work in your codebase.

Related, and not an openspec skill: /spec-scout audits adoption and reports spec↔code drift. Survey-only — it never writes specs.

Layout

openspec/
  specs/<capability>/spec.md     current truth — what the system does today
  changes/<change-id>/
    proposal.md                  what & why
    design.md                    how
    tasks.md                     implementation checklist
    specs/<capability>/spec.md   the DELTA — how the spec changes
  archive/                       completed changes

The distinction that matters: openspec/specs/ is present tense. openspec/changes/*/specs/ is a diff against it. Never hand-edit current truth as part of a change — write the delta, let archive or sync fold it in. That's the failure mode the whole convention exists to prevent.

Spec format

Plain markdown. No custom syntax.

## ADDED Requirements

### Requirement: Theme selection
The app SHALL let users switch between light and dark themes, defaulting to
the system preference.

#### Scenario: User toggles dark mode
- **WHEN** the user clicks the theme toggle
- **THEN** the app switches to dark mode and persists the choice

Headers are ADDED, MODIFIED, or REMOVED. Requirements use SHALL. Every requirement needs at least one WHEN/THEN scenario — one without is untestable and shouldn't merge.

Sections

Read a section only when its condition applies; do not preload them.

  • sections/adopting.md: read when asked how to adopt OpenSpec in a repo (init, greenfield, brownfield)
  • sections/the-grid-specifics.md: read when asked how OpenSpec is wired here, its CLI dependency, stores, or gotchas
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall