594fccc80a
Plugin pairs with Symphony — Composer's output (issues in the project's tracker) is Symphony's input. State-aware /composer command walks the user through 11 phases: concept, users (with workflow probing for hidden actors), requirements/NFR/IA, design system, interaction design, flows, mocks, architecture, stories, roadmap, load. Each phase produces a reviewable artifact in docs/planning/ (or, for design and interaction, a project-local skill — see below). Architecture is intentionally LAST, after the spec is complete. Mocks are JSX/TSX regardless of final stack and pass a "text feasibility" audit — every visible string is categorized (static/computed/authored), computed strings are traced to source data, and any string implying an unspecified feature halts the commit. Design system and interaction design are produced as PROJECT-LOCAL SKILLS in .claude/skills/<slug>-design-system/ and .claude/skills/<slug>-interaction-design/, not as docs in docs/planning/. Skills auto-load via description matching whenever UI work happens; a reference doc gets read once and drifts out of context. The mocks skill imports tokens directly from the design-system skill for a single source of truth across mocks and (eventually) real code. ui-system is currently a PLACEHOLDER — captures the minimum needed for mocks to proceed with <TBD: ...> markers as a return-pass worklist. Full interview specification is the next pass. Council touchpoints baked in: PM/skeptic/end-user after requirements, end-user/a11y after mocks, full architecture council after architecture, plus auto-additions (legal-triage on regulated data, privacy-advocate on PII, finance-controller on money flows). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
18 lines
937 B
Markdown
18 lines
937 B
Markdown
---
|
|
description: Continue product discovery for this project. State-aware — reads docs/planning/ and picks up at the first missing or stale artifact. Run on a fresh project to start from "I want an app that…"; run again later to resume.
|
|
---
|
|
|
|
Invoke the `composer` skill. It will:
|
|
|
|
1. Look for `docs/planning/` in the project root. Create it if absent.
|
|
2. Detect which phase artifacts exist (`concept.md`, `users.md`, `requirements.md`, etc.).
|
|
3. Resume at the first missing or stale phase.
|
|
4. Run the appropriate interview, write the artifact, sign off with the user, advance.
|
|
|
|
Phases that touch the design or interaction system delegate to the `ui-system`
|
|
skill. The mock phase delegates to `composer-mocks`.
|
|
|
|
The skill is conversational — it asks one focused question at a time and waits
|
|
for the user. To skip ahead or jump back, use `/composer-status` or one of the
|
|
phase-specific commands (`/composer-mock`, `/composer-load`).
|