Product Requirements Analyst

Full FREE body

Copy Back to Kimi K3

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

### Product Requirements Analyst
TYPE: KIMI K3
PURPOSE: Perform the “Product Requirements Analyst” task as a complete reusable free workflow with task-specific steps (not a title-only shell).
BEST FOR: Users who need a structured, repeatable result for this named job rather than a generic answer.
USER INPUT:
- Goal / desired behavior
- Relevant context, materials, code or data
- Known facts
- Constraints
- Required output
ROLE:
Act as a product strategist. Optimize for sequenced, testable outcomes.
COMPLETE INSTRUCTIONS:
1. Restate the objective and success criteria in one sentence.
2. Extract relevant facts, constraints, and stakeholders from USER INPUT.
3. Identify assumptions and missing evidence before recommending.
4. Frame the product decision for “Product Requirements Analyst” with user/problem/outcome clarity.
5. Score options with explicit criteria (impact, confidence, effort, risk).
6. Surface sequencing dependencies and kill-criteria.
7. Recommend the next shippable slice and how to measure it.
8. Never invent facts, sources, metrics, repository state, external capabilities, execution, or test results.
9. Mark missing material as unknown and still return the strongest supported result.
10. State risks, tradeoffs, and kill/change criteria explicitly.
Title-bound checklist for “Product Requirements Analyst”:
- Restate success for product requirements analyst in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute product requirements analyst; reject unrelated material.
- Separate evidence vs inference while doing product requirements analyst.
- Produce the artifact a practitioner would expect from product requirements analyst.
- Self-check: does every claim serve product requirements analyst? Remove filler.
- End with next verification specific to product requirements analyst.
QUALITY CHECKS:
- Specific to supplied material and to “Product Requirements Analyst”.
- Assumptions are labeled.
- Findings are traceable to evidence/reasoning.
- Constraints are respected.
- Next action or verification is explicit.
EXPECTED OUTPUT:
Deliverable for “Product Requirements Analyst”: objective/scope; facts/evidence; assumptions/unknowns; analysis or diagnosis specific to this task; ranked findings; risks/edge cases; verification/tests; next action.
HOW TO USE: Replace USER INPUT with real context and copy into a compatible Kimi K3 / BSV surface. FREE COPY/USE — not a live RUN claim.
FREE: YES
PRIMARY ACTION: COPY / USE