Requirements Synthesis
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Inventory sources, stakeholders, dates, authority, and material limitations.
- Extract needs, outcomes, constraints, risks, dependencies, acceptance evidence, and unresolved questions.
- Normalize duplicates while preserving disagreements, source ownership, and context.
- Separate observed facts, reported needs, proposals, ratified decisions, rejected decisions, and estimates.
- Write requirements with actor, behavior, condition, outcome, priority, rationale, and acceptance evidence.
- Trace every material requirement back to one or more sources and flag unsupported additions.
- Identify conflicts that require a named decision owner rather than silently resolving them.
Boundaries
- Do not invent consensus, priority, scope, or acceptance criteria.
- Do not expose confidential source details in public outputs.
- Do not begin implementation or ratify requirements unless separately authorized.
Output
Return Source inventory, Findings, Requirement set, Traceability, Conflicts, Open questions, and Decisions needed.
1---2name: requirements-synthesis3description: Synthesize interviews, documents, issues, observations, and constraints into traceable requirements. Use when multiple sources must become a decision-ready scope without turning proposals or preferences into ratified facts.4license: MIT5---67# Requirements Synthesis89Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1011## Workflow12131. Inventory sources, stakeholders, dates, authority, and material limitations.142. Extract needs, outcomes, constraints, risks, dependencies, acceptance evidence, and unresolved questions.153. Normalize duplicates while preserving disagreements, source ownership, and context.164. Separate observed facts, reported needs, proposals, ratified decisions, rejected decisions, and estimates.175. Write requirements with actor, behavior, condition, outcome, priority, rationale, and acceptance evidence.186. Trace every material requirement back to one or more sources and flag unsupported additions.197. Identify conflicts that require a named decision owner rather than silently resolving them.2021## Boundaries2223- Do not invent consensus, priority, scope, or acceptance criteria.24- Do not expose confidential source details in public outputs.25- Do not begin implementation or ratify requirements unless separately authorized.2627## Output2829Return Source inventory, Findings, Requirement set, Traceability, Conflicts, Open questions, and Decisions needed.30
JovaniPink