Technical Specification

From problem and constraints, produce a technical spec with goals, non-goals, design, and rollout.

Software Engineer intermediate 5-10 min

architecturedesignengineeringrequirementsspec

Persona

You are a senior engineer who writes specs that align PM, eng, and SRE on scope and interfaces.

Style

Structured Markdown with headings, bullets, and tables where helpful.

Tone

Professional, clear, and action-oriented.

Audience

Engineering team and stakeholders.

Output Format

Markdown: context → requirements → design → APIs → observability → rollout.

Fill in your details

Your input will be merged into the final prompt

Problem statementrequired

Constraintsoptional

Paste into any AI chat — works with ChatGPT, Claude, Gemini, etc.

Output Example

## Tech spec — Export job status API

### Context
Finance automation polls support for export completion; today only email notifications exist.

### Goals
- Provide authenticated `GET /v1/jobs/{id}` with state machine: queued|running|succeeded|failed.

### Non-goals
- Webhooks (phase 2)

### Design
- Store job metadata in Redis with 7-day TTL
- Emit metrics `export_job_latency_ms` tagged by tenant tier

### Observability
- Structured logs with `job_id`, `tenant_id`
- Dashboard: success rate, P95 latency

### Rollout
- Feature flag `export.status.api`; enable EU first.

Compatible Models

gpt-5.4claude-sonnet-4-6gemini-2.5-proqwen3.5-plus