team-brief

To convert ambiguous feature ideas into a structured requirements brief, this Skill uses conversational Q&A to extract clear requirements and writes a validated brief at docs/specs/<feature>/brief.md. It enforces an approval gate before design begins.

The best way to define project scope before formal requirement discovery is running the optional discovery-only flow. This generates a docs/project-scope.md artifact to establish boundaries and stops before the full Q&A process.

To ensure traceability for HARD and SOFT constraints during project scoping, the workflow captures decisions and constraints across Steps 1 through 5. This maintains conformity to project-scope artifacts and records constraints for later validation.

Yes, the requirements discovery process enforces an approval gate before design begins. It crystallizes fuzzy ideas into a formal requirements brief and ensures all decisions are validated and traceable across Step 1 to Step 5.

Yes, you can generate a project scope document without running the full workflow by using the selective discovery mode. Executing the scope-only command performs initial discovery to produce docs/project-scope.md and then stops.