ss-proposallisted

Use when you have a PRD or requirement description and need a complete technical proposal before writing any code. Filters the requirement down to this repository's boundary, analyzes the existing architecture and conventions, and produces a Markdown proposal covering architecture, data flow, key interfaces, alternatives, risks, and milestones — gated by a self-review and, when available, an independent reviewer pass.
lbk-open/super-spec · ★ 1 · AI & Automation · score 65

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

# Write Technical Proposal Generate a comprehensive technical proposal from a PRD or requirement description, for any repository shape — a backend service, a frontend app (Web, iOS, Android, Flutter), or a full-stack repository. **Scope note:** a proposal is a high-level design document. It answers *what* the change is, *why* it's the right approach, and *what contracts* it introduces or touches — architecture, data flow, key interfaces, alternatives and trade-offs, risks and rollback, milestones. It does not contain implementation detail: no file-by-file edit lists, no full method bodies, no step-by-step coding instructions. That level of detail is the `ss-plan` skill's job, which consumes this proposal as its input. **When not to use:** - Small bug fixes or config-only changes with no architecture decisions. - One-line code changes, typo fixes, or copy fixes. - Changes already fully specified in an existing proposal. **Announce at the start:** "Using the ss-proposal skill to generate the technical proposal." ## Inputs - A link to a requirement document that your document-reading tool can fetch, or a plain-text requirement description. If neither is available, ask the user for one. If the input is a document link, read its content with whatever document-reading tool is available in your environment. Otherwise treat the input as a plain-text requirement description directly. ## Hard Gates Before writing, verify each item. If any fails, stop and explain to the user: