speclisted

Turn a wireframe and everything already agreed into a written spec in traditional agile shape — an initiative broken into epics, epics into user stories with acceptance criteria, and themes as the labels that span them — presented as an interactive drill-down tree the user prunes, edits and annotates in the browser, with a plain-markdown spec generated from it. Use when the user wants a spec, an initiative or epic broken into user stories, acceptance criteria, to formalise what a wireframe or mockup does, or to review and edit a spec visually.
Cavalry-Collective/visual-stack · ★ 11 · Testing & QA · score 72

Install: claude install-skill Cavalry-Collective/visual-stack

A spec in traditional agile shape — the full Atlassian ladder, **initiative → epics → user stories**, with **themes as the labels that span them** — that opens **collapsed to headlines**: the initiative's goal, its epics, their story titles; one screen, no scrolling. Click a story for its acceptance criteria; click a criterion for how it will be verified. Themes are *"large focus areas that span the organization"* — **tags, not work items**: a catalog shown on the initiative, toggled onto the stories they span (auditability, performance, compliance). The complaint this fixes: a spec today is a long document nobody reads. ``` wireframe + product.md + the conversation ──► tree JSON ──► drill-down page ──► edits & notes ──┐ ▲ │ └────────── you apply it, reply in notes, regenerate ◄────────────────┘ │ specs/YYYY-MM-DD-<feature>.md ← generated every round ``` **The tree is the spec.** `.vstack/specs/<feature>.json` is the source of truth; the markdown under `specs/` is generated from it, never edited by hand. **There is no approve/reject** — the user changes what's wrong, and the change is the feedback. ## 1 · Draft the tree Read whatever exists — the wireframe (`design/<feature>.html` or wherever it lives), `specs/product.md`, `specs/requirements.md`, and the conversation. Then write `.