# Product Roadmap Prioritizer Runbook

## Project Context To Prepare
- Project goal
- Current repository or workflow context
- Current context
- Goal
- Audience or stakeholder
- Constraints
- Available notes or data

## Input Template
Project:

Goal:

Current context:

Constraints:

Available files, notes, or data:

Expected output:
- Scoring method
- Ranked roadmap
- Capacity plan
- Cut list

## Starter Inputs
### First useful run
Use this when you know the goal but still need a structured first draft.

Rank 20 feature candidates for the next quarter with effort estimates.

Context:
- Current state:
- Constraints:
- Audience:
- Success criteria:

### Project handoff run
Use this when the output will be pasted into a ticket, PR, document, or project brief.

Goal: produce prioritized roadmap for a real project.
Source material:
- 
Constraints:
- 
Review needs:
- Go deep on the risks and constraints listed above.
- Mark assumptions.
- Flag missing context.

### Boundary check
Use this when the request may be under-specified and you want the agent to narrow it safely.

Choose the company strategy from a brainstorm list.

Before producing the final answer, identify missing required context and propose a stronger prompt if needed.

## Setup Context Notes
- Bring candidate items, scoring dimensions, strategy constraints, effort estimates, and dependencies.
- Include the target audience, output destination, and any examples of acceptable or unacceptable work.
- Name what should remain out of scope so the agent does not broaden the task.

## Good Input Example
스타트업이 다음 분기 기능 후보 20개를 줄여야 하는 상황

Goal: produce prioritized roadmap for a real project.
Constraints: keep the result specific, structured, and ready for handoff.

## Weak Input Example
Help me with Product Roadmap Prioritizer.

## Weak Input Diagnostics
### Help me with Product Roadmap Prioritizer.
- Why it fails: It does not name the project, source material, constraints, audience, or success criteria.
- Stronger input: Rank 20 feature candidates for the next quarter with effort estimates. Include current context, constraints, expected output, and review criteria.

### Make this better.
- Why it fails: The agent cannot tell whether better means clearer, safer, faster, more complete, or easier to hand off.
- Stronger input: Improve the output for 스타트업이 다음 분기 기능 후보 20개를 줄여야 하는 상황. Optimize for prioritized roadmap, keep assumptions explicit, and list the changes made.

## Expected Output Shape
- Scoring method: criteria, scales, and weights tied to the stated goals
- Ranked table with evidence, confidence, effort, and in or out
- Plan: capacity arithmetic, order, dependencies, and deadlines
- Cut list with a reason and what would bring each item back
- Risks and next actions, each with an owner role and a date or trigger

## Output Checklist
- Every goal, constraint, deadline, dependency, and stakeholder request is reflected in the ranking or sequence
- Scores quote the evidence; weak evidence is marked low confidence
- Capacity arithmetic is shown and adds up
- Each stakeholder gets a data-grounded reason for their item's position
- The method is not tuned to reach a predetermined answer

## Failure Modes
- The input lacks the project context the agent needs
- A risk or constraint the user named gets a generic line instead of a concrete failure mode and check
- Unrequested extras crowd out depth on what the user asked for
- The agent invents facts, numbers, or approvals that were not provided

## Handoff Tips
- Paste relevant project files, notes, or constraints before asking for the final output.
- Ask for a first draft, then request a stricter revision using the checklist.
- Keep the generated output with the project ticket, PR, proposal, or team document.