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/the-grid-specifics.md
View on GitHub## the-grid specifics
- **All 12 wired globally** on every machine via `baseline-submodules.txt`
(`openspec` whole-repo entry, minus `-openspec/release-openspec`, which is
upstream's own maintainer release skill).
- **Hard CLI dependency.** Every skill declares `allowed-tools:
Bash(openspec:*)` and pulls its real instructions from `openspec instructions`
at runtime — the `SKILL.md` files are shells. Without the binary they
dead-end immediately:
```bash
npm install -g @fission-ai/openspec@1.12.0 # needs Node >= 20.19.0; matches repos/openspec
```
- **Default profile is `core`.** That controls which skills `init` scaffolds
locally — **not** which CLI commands work. Every command works under `core`.
- **Cut projects get the convention automatically** —
`project-factory/templates/_common/SPECS.md` lands on every seed *and* every
retrofit, so spec-driven is the default rather than a per-project decision.
- **Composed agents check for it** — `agent-factory/_core/AGENTS_base.md` adds a
boot-sequence check for `SPECS.md` / `openspec/`. All 28+ agents across
`core`, `grid`, `finance-desk` (and any private desk) honour the convention in
repos that have it, and ignore it in repos that don't.
- **Telemetry is on by default.** Opt out with `OPENSPEC_TELEMETRY=0`.
## Stores (beta, not adopted here)
A **store** is a standalone repo whose only job is planning — same `openspec/`
shape, registered per-machine by name, addressed with `--store <id>`. Solves
planning that spans several repos. the-grid has **not** adopted this; it's
tracked in issue #38 as an open decision. Don't reach for `--store` unless that
issue closes as adopt.
## Gotchas
- A proposal exists to be **rejected cheaply**. If review always rubber-stamps,
the convention is costing you and buying nothing.
- `update-change` revises the plan and never touches code. `apply-change` is the
one that writes code. Mixing them up produces a change whose artefacts and
implementation disagree.
- If implementation proves the spec wrong, update the **delta**, not the code
silently. Divergence between spec and code is the thing being prevented.
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 |