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
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Source inventory, Findings, Requirement set, Traceability, Conflicts, Open questions, and Decisions needed.
Example
Synthetic example; not an observed client result.
Input: One interview requests immediate deletion; another requires seven-year retention.
Output: Record the conflict and responsible decision owner. Do not silently choose one requirement or label the combined scope approved.
1---2name: synthesize-requirements3description: "Combines interviews, documents, and issues when asked to turn conflicting inputs into requirements; traces each requirement to evidence and keeps unresolved decisions visible."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/synthesize-requirements7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-operations"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Requirements Synthesis1617Use 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.1819## Workflow20211. Inventory sources, stakeholders, dates, authority, and material limitations.222. Extract needs, outcomes, constraints, risks, dependencies, acceptance evidence, and unresolved questions.233. Normalize duplicates while preserving disagreements, source ownership, and context.244. Separate observed facts, reported needs, proposals, ratified decisions, rejected decisions, and estimates.255. Write requirements with actor, behavior, condition, outcome, priority, rationale, and acceptance evidence.266. Trace every material requirement back to one or more sources and flag unsupported additions.277. Identify conflicts that require a named decision owner rather than silently resolving them.2829## Boundaries3031- Do not invent consensus, priority, scope, or acceptance criteria.32- Do not expose confidential source details in public outputs.33- Do not begin implementation or ratify requirements unless separately authorized.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Source inventory, Findings, Requirement set, Traceability, Conflicts, Open questions, and Decisions needed.4041## Example4243Synthetic example; not an observed client result.4445Input: One interview requests immediate deletion; another requires seven-year retention.4647Output: Record the conflict and responsible decision owner. Do not silently choose one requirement or label the combined scope approved.