ss-reverse-speclisted

Reverse-engineers OpenSpec source-of-truth capability specs from an existing (brownfield) codebase, either as a full baseline sweep or for a single capability. Bootstraps the openspec/ skeleton first if the project doesn't have one yet. Use this to give a legacy repository a meaningful starting spec instead of an empty openspec/specs/ directory.
lbk-open/super-spec · ★ 1 · AI & Automation · score 65

Install: claude install-skill lbk-open/super-spec

# Reverse OpenSpec Baseline Generate source-of-truth specs under `openspec/specs/` from existing code. This is how a brownfield repository gets a meaningful capability snapshot instead of starting from an empty `openspec/specs/` directory. ## Inputs One of: - `--baseline` — scan the whole repository and generate specs for every capability found - a single capability name — generate or update just that one spec Optional: `--include <path>` / `--exclude <path>` to scope the scan. ## Step 0: Ensure the OpenSpec Skeleton Exists Check whether `openspec/specs/` and `openspec/changes/` already exist. If this repository has no OpenSpec structure yet, create it first by following `../ss-references/openspec-skeleton.md`, then continue below. If the skeleton already exists, skip straight to the requested mode. ## Modes | Mode | Trigger | Output | |------|---------|--------| | Baseline | `--baseline` | scan the repo, generate specs for every capability found | | Single capability | a capability name | generate or update one capability spec | ## Process: Baseline Mode ### Step 1: Discover Capability Candidates Collect signals from: - `README.md`, an application-overview doc, and `docs/` - controller / handler / route files - service / domain layer names - OpenAPI paths - database migration or DDL table names Cluster the candidates into kebab-case business noun phrases. For each candidate, list the evidence files that back it. ### Step 2: User Confirmation Gate Show the can