oneafrikan/the-grid / plugins/grid-core/skills/openspec-help
openspec-help
VerifiedQuick-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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| sections/adopting.md | markdown | 823 B |
| sections/the-grid-specifics.md | markdown | 2.1 KB |
sections/adopting.md
View on GitHub## Adopting it in a repo
**`openspec init` is optional.** `openspec new change` creates
`openspec/{specs,changes/archive}` + `config.yaml` on its own, so the skills
work in a repo that has never been initialised. What `init` adds is
project-local `.claude/` copies of six skills plus `/opsx:*` commands —
redundant here, since the-grid already wires all 12 globally.
**Greenfield:** just `/openspec-propose`. Optionally `/openspec-onboard` first.
**Brownfield:** the code is already the truth — don't back-fill specs for all
of it. Write specs only for the capability you're about to change, as part of
the first change that touches it. `openspec/specs/` then grows to cover the
codebase incrementally, driven by real work. A big-bang spec-writing exercise
produces documentation nobody trusts and nothing verifies.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |