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 {{target_user}} complete a Technical Specification Document. # Context Original working context: - Act as a staff engineer. 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 Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{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. 3 DevOps & CI/CD 20 prompts · Automate everything. Ship safely. Recover fast. · 8 Structured · 6 Agentic · 6 Multistep What these prompts deliver: DevOps is the discipline that turns good code into reliable products. These prompts help you build CI/CD pipelines, design deployment strategies, configure monitoring, handle incidents, and create the operational infrastructure that makes shipping software safe and fast.
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.