Draft a Technical Spec from Requirements
Turn a rough feature description into a structured technical spec outline.
Use case
Use at the start of building a non-trivial feature, to force out the design questions before writing code.
Customize
Performance, scale, deadline, etc.
Preview
I need to build: {feature_description}. Constraints: {constraints}. It needs to integrate with: {existing_systems}.
Draft a technical spec outline with sections for: Problem statement, Goals and non-goals, Proposed approach (with 1-2 alternatives briefly considered and why rejected), Data model changes if any, API/interface changes if any, Open questions, and Rollout/testing considerations. Keep each section concise — this is a planning document, not the implementation. Flag any place where you had to make an assumption because the requirements were ambiguous.Usage guidance
The "alternatives considered" section is worth keeping even when it feels like overhead — it's usually where the model surfaces a simpler approach you hadn't considered.
Example input
Feature: add the ability for users to export their data as CSV. Constraints: must work for accounts with 100k+ rows without timing out. Existing systems: REST API, Postgres, S3 for file storage.
Example output
## Problem Statement\n\nUsers currently have no way to export their data...
Last updated Jan 1, 2026
Related prompts
SWOT Analysis for Your Business
Generate a structured strengths/weaknesses/opportunities/threats analysis for a small business.
Plan My Week from a Task Dump
Turn a messy list of everything you need to do into a prioritized, day-by-day plan.