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`).
|