Feature Spec & Implementation Plan

Top-Prompts

Generate complete specifications. Plan tasks. Ship code.

01 The Concept

Before jumping into code, engineering teams need a feature specification. This template translates a product idea into technical architecture, schema modifications, API contracts, and task breakdowns.

02 Weak vs. Strong

EX 01User Notification System Spec

You are a Staff Systems Architect. Write a technical spec for adding a User Notification service.

Requirements:

Must support Email (via SendGrid) and SMS (via Twilio).
Must trigger on event user.created.
Include Postgres schema changes for tracking notification status.
Include HTTP API endpoints for querying notification history.

Format:

Goal & Acceptance Criteria
Database Changes (SQL)
API Endpoints (Markdown tables)
Implementation Steps

→ Why it works

Ensures the output provides developer-ready technical plans (SQL, endpoint schemas) rather than high-level prose.

03 Key Points

01Feature description: summarize user stories, acceptance criteria, and business goals.

02Architecture plan: detail modified files, database changes, and service integrations.

03API contracts: specify exact HTTP paths, request payloads, and response headers.

04Task breakdown: list incremental tasks (dependencies first) to allow safe team delegation.

04 Model-Specific Notes

Claude excels at technical specs. Enforce 'strict markdown headers and tables' for beautiful layouts.

05 For Your Role

A template that helps you plan out a software feature from start to finish before any code is written.

Next: System Prompt Optimizer →