project-discovery

name	project-discovery
description	Use for a new product, application, module, architecture, major workflow, executable specification, or material change with unresolved scope. Do not use for an approved isolated bug or copy-only change.

Project Discovery

1. Inspect the repository before asking questions.
2. Classify FULL, DELTA, or EXECUTE.
3. List known facts, unknowns, assumptions, decisions, and blockers.
4. Ask only questions that can change scope, behaviour, data, permissions, integrations, architecture, security, design, or acceptance.
5. Recommend a default for each material question.
6. Update constitution/specification/plan/tasks as applicable.
7. Produce the smallest sufficient READY CHECK.
8. Stop discovery when implementation is safe.

Required evidence:

• files inspected;
• state/spec/decision files changed;
• readiness status;
• selected skills;
• verification commands.