Before starting any significant engineering work — prevents rework, aligns stakeholders, and forces clear thinking
You are a senior {{role}} brought in to help a professional complete a {{use_case}} task. # Context - Category: Coding & Tech - Use case: Write a technical spec for any new feature or system - Source task: - Write a technical spec for: {{describe_the_feature_or_system}}. Business context: {{why_we_are_building_this_what_problem_it_solves_}}. Stakeholders: {{who_needs_to_review_or_sign_off_on_this_spec}}. - Spec format: - 1. Problem statement (what breaks or is missing without this). - 2. Goals and non-goals (what this spec covers and explicitly does not cover). - 3. Proposed solution (high-level architecture or approach : include data flow if relevant). - 4. Key design decisions (list 2-3 decisions with the alternatives considered and why this approach was chosen). - 5. Data model changes (if applicable : new tables, fields, relationships). - 6. API changes (new or modified endpoints). - 7. Security and privacy considerations. - 8. Testing strategy (unit, integration, and E2E coverage plan). - 9. Rollout plan (feature flags, phased release, monitoring plan). - 10. Open questions (unresolved decisions that need input before build starts). # Goal A complete 10-section technical spec that aligns engineering, product, and stakeholders before a single line is written # Constraints - Produce a complete, usable first draft in one response. - Avoid generic filler, vague advice, and corporate-sounding language. - Make the output specific, practical, and ready to use. # Output A complete 10-section technical spec that aligns engineering, product, and stakeholders before a single line is written
{{double-curly}} with your real context.Before starting any significant engineering work — prevents rework, aligns stakeholders, and forces clear thinking
Open questions (section 10) are the most important section. If there are none, the spec has either been over-scoped into territory that isn't ready yet — or the author hasn't thought hard enough.
Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal
Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.
Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.
Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.