Before any significant engineering work — a good spec prevents rework, aligns stakeholders, and forces clear thinking.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: System Design & Architecture - Use case: Technical Specification Document - Source task: - Write a technical specification for {{feature_or_system_name}}. - Step 1: Problem & Context: describe the problem, why it matters, and the current state. - Step 2: Proposed Solution: high-level approach, key design decisions with alternatives considered, data model changes, API changes. - Step 3: Implementation Plan: phases, dependencies, open questions that need resolution, security and privacy considerations, testing strategy, and rollout plan. Format as a professional spec document with numbered sections. # Goal A complete technical spec with problem context, proposed solution, design decisions, implementation plan, and rollout approach. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output A complete technical spec with problem context, proposed solution, design decisions, implementation plan, and rollout approach.
{{double-curly}} with your real context.Before any significant engineering work — a good spec prevents rework, aligns stakeholders, and forces clear thinking.
The 'alternatives considered' section is what separates a spec from a plan — it shows you've thought critically, not just decided.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.