← ClaudeAtlas

ss-write-speclisted

Generates or updates OpenSpec delta specs under openspec/changes/<change-id>/ from a proposal, PRD, or plain-language requirement, bootstrapping the openspec/ skeleton first if the project doesn't have one yet. Use this to align capability specs with reviewers before writing a full execution plan, or to adjust deltas without regenerating the plan.
lbk-open/super-spec · ★ 1 · AI & Automation · score 65
Install: claude install-skill lbk-open/super-spec
# Write OpenSpec Delta Generate OpenSpec-compatible delta specs under `openspec/changes/<change-id>/`. This is a plumbing skill: day-to-day development normally goes through the `ss-plan` skill, whose Phase 0 runs this same logic automatically. ## When To Use - You need to align capability specs with reviewers before writing a full execution plan. - You need to adjust delta specs without regenerating the plan. - The `ss-coding` or `ss-create-pr` skill reported missing or invalid delta specs. ## Inputs | Input | Handling | |-------|----------| | A URL to a hosted doc (wiki, Confluence, Google Docs, etc.) | Fetch it with your document-reading tool, or an available doc-integration skill, and convert it to markdown | | A local markdown file | Read the file directly | | Plain text | Treat it as the requirement source | If none of these is available, ask the user for the proposal, PRD, or requirement text before continuing. **Language of the deltas:** write requirement and scenario prose in the same language as the input document (or the project's existing docs, if that's a clearer signal); default to English when neither gives a signal. `SHALL`/`MUST` keywords, code identifiers, and file paths always stay in English. ## 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 with