35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
|
# Agent Task: Triage Prototype Intake
|
||
|
|
|
||
|
|
## Goal
|
||
|
|
Turn a rough idea into a clear triage outcome: prototype card, merge, park, or reject.
|
||
|
|
|
||
|
|
## Context
|
||
|
|
`whynot-control` uses `PROTOTYPE_PIPELINE.md` to move ideas from raw capture into structured prototype exploration.
|
||
|
|
|
||
|
|
## Inputs
|
||
|
|
- One item from `inbox/` or an equivalent rough note.
|
||
|
|
- `PROTOTYPE_PIPELINE.md`
|
||
|
|
- `templates/prototype-card.md`
|
||
|
|
|
||
|
|
## Allowed Changes
|
||
|
|
- Create or refine a prototype card in `prototypes/`.
|
||
|
|
- Improve wording and structure of the input note.
|
||
|
|
- Recommend park, merge, or reject when a prototype card is not justified.
|
||
|
|
|
||
|
|
## Forbidden Changes
|
||
|
|
- Do not treat the idea as a committed product.
|
||
|
|
- Do not invent signal evidence that does not exist.
|
||
|
|
- Do not create beta, pricing, or public launch commitments.
|
||
|
|
|
||
|
|
## Expected Output
|
||
|
|
- One explicit triage outcome.
|
||
|
|
- If promoted to prototype, one draft prototype card with learning question, test, and expected signal.
|
||
|
|
|
||
|
|
## Acceptance Criteria
|
||
|
|
- The output states who might care, what is being tested, and the smallest useful next step.
|
||
|
|
- The outcome is one of: prototype card, merge, park, or reject.
|
||
|
|
|
||
|
|
## Human Approval Required For
|
||
|
|
- Promoting the idea beyond prototype exploration.
|
||
|
|
- Making external commitments.
|