Product Requirements

Full FREE body

Copy Back to AutoGen

Pack body is English. UI language controls translate chrome labels only.

You are handling **Product Requirements** in AutoGen.

GOAL
[GOAL]

INPUTS
[INPUTS]

CONTEXT / ASSETS
[CONTEXT_OR_FILES]

CONSTRAINTS
[CONSTRAINTS]

EXECUTION
1. State the concrete objective and identify only missing information that would make execution unsafe or materially unreliable. Continue without blocking on optional details.
2. Inspect/analyze the supplied context before changing anything or drawing conclusions.
3. Use specialists only when useful; define roles, inputs, output contracts, handoffs, team topology, termination and maximum-turn safety bounds.
4. Keep evidence, assumptions and unknowns separate. Never invent files, source facts, tool results, metrics, test results or completed actions.
5. Produce the actual artifact for this task; do not return generic advice about how to do it.
6. Verify the artifact against [CONSTRAINTS] and the requested outcome before returning it.
7. For this use case specifically, ensure the result can convert a product idea into scoped, testable requirements and includes concrete validation or acceptance criteria.

TARGET-SPECIFIC RULE
Define speaker/action transitions, handoff artifacts, termination and a maximum-turn bound to prevent endless loops.

OUTPUT CONTRACT
RESULT: [completed | blocked]
DELIVERABLE: [AutoGen team specification with agents, instructions, handoffs, termination, artifacts and tests]
VALIDATION: [checks performed / evidence used]
ASSUMPTIONS: [material assumptions only]
REMAINING: [none, or exact unresolved issue]

PLACEHOLDERS
[GOAL] desired outcome
[INPUTS] raw task material
[CONTEXT_OR_FILES] repository, documents, data, workflow context or API constraints
[CONSTRAINTS] scope, format, safety, compatibility, privacy, budget or policy constraints