Discover a feature
Read discovery, artifacts, memory, and safety before starting.
Procedure
- Confirm PWDEV Flow state exists or explain that
$flow-init is the prerequisite for persisted artifacts.
- Inspect applicable
AGENTS.md, repository structure, existing behavior, tests, product context, and active relevant memories without reading secrets.
- Classify the request as quick, standard, or product-level. Route bounded changes to
$flow-quick; route product problems to $flow-product when a PRD is needed.
- Interview one focused decision at a time using the minimum questions required by discovery.
- Separate confirmed facts, user decisions, repository observations, assumptions, and open questions.
- Research stack and domain pitfalls from repository evidence first. Use current primary sources when external facts may have changed.
- Write the context artifacts and set state to
DISCOVERING while questions remain.
- Present problem, actors, scope, rules, acceptance criteria, risks, and open questions for approval.
- On approval, mark the discovery gate
APPROVED and recommend $flow-design. Otherwise revise requirements or set BLOCKED with the missing decision.
Collaboration
Work inline by default. Use a read-only research worker only when the user explicitly requests parallel agent work, following collaboration. Keep the interview and approval gate in the primary conversation.
Output
Return STATUS, feature slug, requirements path, supporting context paths, gate result, and NEXT. Do not make architecture decisions during discovery.
1---2name: flow-discover3description: Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.4---56# Discover a feature78Read [discovery](../../references/discovery.md), [artifacts](../../references/artifacts.md), [memory](../../references/memory.md), and [safety](../../references/safety.md) before starting.910## Procedure11121. Confirm PWDEV Flow state exists or explain that `$flow-init` is the prerequisite for persisted artifacts.132. Inspect applicable `AGENTS.md`, repository structure, existing behavior, tests, product context, and active relevant memories without reading secrets.143. Classify the request as quick, standard, or product-level. Route bounded changes to `$flow-quick`; route product problems to `$flow-product` when a PRD is needed.154. Interview one focused decision at a time using the minimum questions required by [discovery](../../references/discovery.md).165. Separate confirmed facts, user decisions, repository observations, assumptions, and open questions.176. Research stack and domain pitfalls from repository evidence first. Use current primary sources when external facts may have changed.187. Write the context artifacts and set state to `DISCOVERING` while questions remain.198. Present problem, actors, scope, rules, acceptance criteria, risks, and open questions for approval.209. On approval, mark the discovery gate `APPROVED` and recommend `$flow-design`. Otherwise revise requirements or set `BLOCKED` with the missing decision.2122## Collaboration2324Work inline by default. Use a read-only research worker only when the user explicitly requests parallel agent work, following [collaboration](../../references/collaboration.md). Keep the interview and approval gate in the primary conversation.2526## Output2728Return `STATUS`, feature slug, requirements path, supporting context paths, gate result, and `NEXT`. Do not make architecture decisions during discovery.
pwdev-solucoes