# Feature Requirements Analyst Runbook

## Project Context To Prepare
- Project goal
- Current repository or workflow context
- Feature goal
- User story
- Constraints
- Existing behavior

## Input Template
Project:

Goal:

Current context:

Constraints:

Available files, notes, or data:

Expected output:
- Requirements
- Acceptance criteria
- Edge cases
- Out of scope

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

Define requirements for installable-only filtering and quality score badges.

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 Requirements for a real project.
Source material:
- 
Constraints:
- 
Review needs:
- Call out assumptions.
- Flag missing context.
- End with concrete next actions.

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

Write requirements for an undefined AI platform pivot.

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

## Setup Context Notes
- Bring the feature goal, users, current behavior, constraints, and release boundary.
- 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
Feature goal: add role-specific starter packs to /install.
Users: developers, PMs, designers, operations owners.
Constraints: static data only, use existing agents and card components.
Expected output: requirements, acceptance criteria, edge cases, and out-of-scope notes.

## Weak Input Example
Add some recommendations to the install page.

## Weak Input Diagnostics
### Help me with Feature Requirements Analyst.
- Why it fails: It does not name the project, source material, constraints, audience, or success criteria.
- Stronger input: Define requirements for installable-only filtering and quality score badges. 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 Ticket writing. Optimize for Requirements, keep assumptions explicit, and list the changes made.

## Expected Output Shape
- A short summary of the recommended Requirements
- A clearly labeled Requirements section
- A clearly labeled Acceptance criteria section
- A clearly labeled Edge cases section
- A clearly labeled Out of scope section
- Assumptions and missing context separated from confirmed facts
- Risks, review checkpoints, and concrete next actions

## Output Checklist
- Includes Requirements
- Includes Acceptance criteria
- Includes Edge cases
- Includes Out of scope
- States assumptions separately from confirmed facts
- Lists concrete next actions
- Calls out risks or missing context

## Failure Modes
- The output does not define which user problem the feature solves
- Acceptance criteria do not mention empty or missing-agent states
- Scope creep introduces personalization or accounts

## 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.