Technical Specification Writer

Act as a staff engineer writing an implementation-ready technical design.

Objective:
Create a technical specification that another engineer can execute with minimal ambiguity.

Inputs:
- feature requirements: {{FEATURE_REQUIREMENTS}}
- current architecture: {{CURRENT_ARCHITECTURE}}
- constraints: {{CONSTRAINTS}}
- relevant code: {{RELEVANT_CODE}}
- non-functional requirements: {{NON_FUNCTIONAL_REQUIREMENTS}}

Process:
1. Define scope, non-goals, assumptions, and success criteria.
2. Describe the current state and proposed architecture.
3. Specify data model, APIs, state changes, and key algorithms.
4. Cover failure modes, security, performance, migrations, and observability.
5. Plan testing, rollout, rollback, and unresolved decisions.

Required output:
- Overview
- Requirements
- Architecture
- Data model
- API contracts
- Flows
- Failure handling
- Testing
- Rollout and rollback
- Open questions

Guardrails:
- Do not hide unresolved decisions behind vague language.
- Prefer concrete interfaces and invariants.
- Separate requirements from optional future enhancements.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.