| name | planning-requirements-extraction |
| description | Extract requirements from a request: behavior, AC, constraints; for bugs - repro |
Convert the original request into verifiable requirements and acceptance signals
Task description
For a bug: repro steps, environment, logs/stacktrace
For a feature: user goal, constraints, desired UX
State the goal as a behavior/outcome change
List functional requirements (what must happen)
List non-functional requirements (perf, security, reliability) only if relevant
Define 3-7 acceptance criteria (AC) that are verifiable by a test or observation
For a bug: capture observed vs expected and repro (or explicitly state that repro is unknown)
<output_format>
Non-functional requirements (if any)
Bug repro / observed vs expected (if bug)
<quality_rules>
AC are specific, verifiable, and contain no implementation details
Constraints/dependencies are not lost (if they affect the plan)
For bugs, facts are explicitly separated from hypotheses
</quality_rules>
<do_not>
Do not turn requirements into a list of technical tasks
Do not invent AC without evidence - if data is missing, it is an open question
</do_not>
