Best Claude Prompt for “Write a Technical Spec”

<context>
The goal is to create a comprehensive technical specification document for a new software feature. This document will serve as a blueprint for development, testing, and future maintenance. It needs to be detailed enough for engineers to understand the implementation requirements and for stakeholders to grasp the feature's scope and functionality.
</context>

<task>
As a Senior Software Architect, write a technical specification for [feature]. Provide thorough explanations and go beyond surface-level descriptions to ensure clarity and completeness.
</task>

<requirements>
*   **Clarity and Detail:** Ensure all technical aspects are clearly defined. Use precise language suitable for an engineering audience.
*   **Scope Definition:** Clearly outline the boundaries of the feature, specifying what is included and what is explicitly out of scope. This prevents scope creep and manages expectations.
*   **Functional Requirements:** Detail the specific behaviors and functionalities the feature must exhibit. Describe user interactions, system responses, and data flows.
*   **Non-Functional Requirements:** Include performance, security, scalability, and reliability considerations. These are crucial for a robust and maintainable system.
*   **Technical Design:** Outline the proposed architecture, data models, APIs, and any necessary integrations with existing systems.
*   **Error Handling:** Specify how errors and edge cases should be handled, including user feedback and system logging.
*   **Examples:** Include 2-3 concrete examples or use cases to illustrate complex functionalities or workflows. This aids understanding for all involved parties.
*   **Conciseness:** While detailed, avoid unnecessary jargon or overly verbose explanations. Focus on conveying essential technical information efficiently.
</requirements>

<format>
Structure the specification using the following sections:
1.  **Introduction:** Briefly describe the feature and its purpose.
2.  **Goals and Objectives:** State the primary aims of the feature.
3.  **Scope:** Define what the feature will and will not do.
4.  **Functional Requirements:** Detail the feature's behavior. Use bullet points for individual requirements.
5.  **Non-Functional Requirements:** Specify performance, security, etc.
6.  **Technical Design:** Describe architecture, data models, APIs, etc.
7.  **Error Handling and Edge Cases:** Outline proposed solutions.
8.  **Future Considerations (Optional):** Briefly mention potential future enhancements.

Before finishing, verify your response covers the technical specification for [feature] with sufficient detail and clarity.
</format>