OperationsEngineerEngineering Manager

Technical Spec

Create a Technical Spec tailored to your inputs.

Share:XWhatsAppLinkedIn

Prompt template

Open in ChatGPTOpen in Claude
You are a senior software architect. Generate a comprehensive technical specification document in Markdown for the following feature or system.

Feature Name: {{feature_name}}
Feature Description: {{feature_description}}
{{spec_type}}
{{user_stories}}
{{technical_requirements}}
{{out_of_scope}}
{{tech_stack}}
{{security_considerations}}
{{success_metrics}}

Create a detailed technical specification with these exact sections:
1. ## Overview — summary of the feature, version, status, and stakeholders
2. ## User Stories — list of user stories in "As a... I want... so that..." format
3. ## Technical Requirements — functional and non-functional requirements
4. ## API Design — endpoint definitions, request/response schemas, error codes (if applicable)
5. ## Out of Scope — explicit list of what is NOT included in this version
6. ## Security Considerations — security requirements and threat mitigations
7. ## Success Metrics — measurable KPIs with targets and measurement methods

Use Markdown formatting with headers, tables, code blocks, and checkboxes where appropriate. Be specific, measurable, and actionable.

Fill the 9 fields below to customize.

Customize before copy

Fill these — your prompt updates live.

Stays in your browser. Nothing sent anywhere — we don't run a server for this.

Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.

Sample

Example output

What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.

# Technical Specification: Feature Name

**Version:** 1.0.0
**Date:** ${new Date().toISOString().split("T")[0]}
**Status:** Draft

---

## 1. Overview

This technical specification describes the design and implementation details for the feature. It covers user stories, technical requirements, API design, and success metrics.

**Spec Type:** Feature Specification
**Stakeholders:** Engineering, Product, Design

---

## 2. User Stories

- As a user, I want to perform the core action so that I achieve the primary goal.
- As an admin, I want to configure settings so that I can customize the behavior.
- As a developer, I want clear API contracts so that I can integrate reliably.

---

## 3. Technical Requirements

### Functional Requirements

- **FR-001:** The system shall accept valid input and produce the expected output.
- **FR-002:** The system shall validate all input fields before processing.
- **FR-003:** The system shall return appropriate error messages for invalid input.
- **FR-004:** The system shall support concurrent requests without data corruption.

### Non-Functional Requirements

- **NFR-001:** Response time shall be under 2 seconds for 95th percentile of requests.
- **NFR-002:** The system shall handle up to 1,000 requests per minute.
- **NFR-003:** Uptime shall be 99.9% or higher.
- **NFR-004:** All data at rest shall be encrypted.

---

## 4. API Design

### Endpoint

\
Related

You might also like

API Documentation

Create a API Documentation tailored to your inputs.

Operations

Bug Report Formatter

Create a Bug Report Formatter tailored to your inputs.

Operations

Changelog Writer

Create a Changelog Writer tailored to your inputs.

Operations

Agency Agreement

🇮🇳

Draft a Agency Agreement tailored to your inputs.

Legal & Contracts

Made with KLI — extracted from real tools, shared free. krakelabsindia.com