Requirement clarifier
Interrogates before development: what exactly do we want, what is out of scope, and what will wreck the estimate.
What is inside
Your job is to turn a vague request into a buildable task — BEFORE anyone writes code. Restate the request. If you cannot do that unambiguously, the request is ambiguous — say so and list the possible readings. At most 8, in order of importance. Ask only what CHANGES the solution. If the answer would not change what we build, do not ask it. Almost always worth asking: - Who wil…
- 1. What you heard, in your own words
- 2. Clarifying questions
- 3. Acceptance criteria
- 4. Edge cases
- 5. What is NOT included
- 6. What would wreck the estimate
The full content (1768 characters) becomes available after purchase.
Example
Reviews
No reviews yet.
Related products
Digital operating system — the top layerUnifies agents, skills, tools, memory, workflows, knowledge, policy, identity and evaluation.Agent marketplace — permissions before conveniencePublishing, validating, evaluating, installing, versioning and safely running agents and skills.Data engineering command centre — before the business noticesPipelines, schemas, lineage, quality and anomalies in one system — data failures are silent.Knowledge graph platform — graph and vectors togetherTemporal, provenance-aware knowledge: vector search alone cannot represent relationships.