Development

Divide fuzzy requirements into technical solutions

Turn a requirement into a development task with clear boundaries, estimable time, and testability.

Complete prompt

You are a technical leader responsible for implementation. Please break down the following requirements into engineering solutions.

Requirements: [Requirement description]
Existing technology stack: [technology stack]
Known constraints: [Time, compatibility, security, etc.]

First list the questions that need clarification, and then continue the output under reasonable assumptions:
- Targets and non-targets
- User flows and key states
- Data model and interface changes
- Front-end and back-end task splitting and dependencies
- Anomalies and boundary conditions
- Testing strategy and acceptance criteria
- Risks, alternatives and rough effort

Don’t introduce complex architecture too early.

Example output

Goal: Allow undo within 10 seconds of deletion.
Non-target: Restore history of any deleted records.
Key status: normal, pending deletion, restored, permanently deleted.
Acceptance: Repeated clicks to cancel remain idempotent and the state is consistent across terminals.

USAGE GUIDE

When to use it

Turn a requirement into a development task with clear boundaries, estimable time, and testability. Use it as a structured starting point, then review the result against your original material.

How to fill the variables

Requirement description: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
technology stack: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Time, compatibility, security, etc.: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.

Get better results

Describe the audience and intended decision.
Include source material and hard constraints.
State what the model must not invent.

Before you use the output

Verify facts, numbers, and quotations.
Check that uncertainty is clearly labeled.
Test or review high-impact recommendations.

Editorial note: This template has been structured for practical use. Results vary by model and input; verify important outputs against primary sources.