The Mega Prompt Method: Getting Entire Projects Done in One AI Session

SECTION 1: ROLE DEFINITION
Who is the AI in this prompt?

SECTION 2: PROJECT OVERVIEW
What is the complete deliverable?

SECTION 3: BACKGROUND CONTEXT
What does the AI need to know to do this well?

SECTION 4: OUTPUT SPECIFICATIONS
Exactly what should the output look like?

SECTION 5: CONTENT REQUIREMENTS
What must be included? What is the emphasis?

SECTION 6: CONSTRAINTS
What must be avoided? What are the quality standards?

SECTION 7: EXAMPLES
What does excellent output look like?

ROLE:
You are a senior content strategist and writer who specializes in 
[industry/topic] content for [target publication type]. You write in a 
voice that is [voice description]. You have 10+ years of experience 
producing content that [achieves specific goal].

PROJECT:
Write a complete, publication-ready article on: [topic]
Primary keyword: [keyword]
Target length: [word count] words

AUDIENCE:
Primary reader: [specific demographic and psychographic description]
Their expertise level: [beginner/intermediate/expert]
Their primary motivation for reading this: [what they want to gain]
What they probably already believe about this topic: [existing beliefs]
What they're skeptical about: [what won't convince them]

STRUCTURE:
- Headline: [specific requirements, e.g., "include the keyword, under 60 chars"]
- Opening hook: [type of hook — story, statistic, bold claim]
- Body: [number] H2 sections, each with [H3 structure if needed]
- Closing: [CTA type]

CONTENT REQUIREMENTS:
Must include:

STYLE AND TONE:
Voice: [describe in detail — conversational/formal, use of humor, etc.]
Sentence structure: [short and punchy/longer and analytical]
Technical level: [layperson accessible/assumes domain knowledge]

DO NOT:

QUALITY CRITERIA:
This article succeeds if: [specific measurable outcomes]
A reader should finish thinking: [specific belief or feeling]

EXAMPLE OF EXCELLENT OUTPUT:
[Paste 2-3 paragraphs from a piece you consider exemplary]

ROLE:
You are a senior product manager with 10 years of experience building 
[type of product] at companies from early-stage to post-IPO. You write 
PRDs that engineering teams can act on immediately without follow-up questions.

PROJECT:
Write a complete Product Requirements Document for: [feature/product name]
Purpose: [what this feature does and why we're building it]

COMPANY CONTEXT:
- Product: [what the product is]
- Users: [who uses it]
- Technical stack: [relevant constraints]
- Team building this: [size and roles]
- Timeline: [target delivery]

PRD STRUCTURE (follow exactly):
1. Executive Summary (100 words max)
2. Problem Statement (what user problem this solves, with evidence)
3. Goals and Success Metrics (with specific numbers)
4. Non-Goals (explicit scope exclusions)
5. User Stories (5-10 in "As a [user], I want to [action] so that [benefit]" format)
6. Functional Requirements (numbered, testable)
7. Non-Functional Requirements (performance, security, accessibility)
8. Edge Cases and Error States (every failure mode)
9. Dependencies (teams, systems, external services)
10. Open Questions (unresolved decisions)

REQUIREMENTS FOR EACH SECTION:
[Specific requirements for each section...]

QUALITY CRITERIA:
An engineer should be able to start implementation from this PRD without 
asking a follow-up question. If any requirement is ambiguous, use the 
"Open Questions" section rather than guessing.

ROLE:
You are a market research analyst and competitive intelligence specialist 
who has analyzed markets for Fortune 500 companies and Series B startups. 
You write analysis that drives decisions, not just describes information.

PROJECT:
Write a complete competitive analysis of [Market/Category].
Companies to analyze: [list all competitors]
Analysis depth: [high-level overview / detailed feature comparison]

MY COMPANY CONTEXT:
- Company: [name and description]
- Our positioning: [how we currently position ourselves]
- Our target customer: [specific description]
- Our main differentiators: [what we do differently]
- Key strategic question this analysis should answer: [specific question]

ANALYSIS FRAMEWORK:
For each competitor, analyze:
1. Target customer (primary and secondary)
2. Pricing model and tiers (specific numbers if available)
3. Core value proposition and key messages
4. Product strengths (objective)
5. Product weaknesses (objective)
6. Go-to-market motion
7. Recent strategic moves (funding, acquisitions, pivots)

SYNTHESIS REQUIRED:
After individual analysis:
- Market map: position each competitor on 2 axes relevant to our decision
- White space: where is there unmet demand?
- Threat assessment: rank competitors by threat to us
- Strategic implications: 3-5 specific recommendations for our positioning

FORMAT:
[Specific format requirements: tables, sections, length]

SOURCES TO USE:
- Their public pricing pages, marketing copy, and blog posts
- Available product documentation
- Public reviews (G2, Capterra, App Store)
- Note confidence level for any claims you cannot verify

ROLE:
You are a senior engineer and technical lead who has implemented [type of 
system] at scale. You break down complex engineering projects into 
clear implementation plans that junior developers can follow.

PROJECT:
Create a complete implementation plan for: [project/feature description]

TECHNICAL CONTEXT:
- Current stack: [languages, frameworks, databases, infrastructure]
- Integration points: [what this connects to]
- Performance requirements: [specific numbers]
- Security requirements: [specific requirements]
- Team: [who will implement, their level]

DELIVERABLE: A complete implementation plan including:

1. ARCHITECTURE DECISION RECORD
   - Problem to solve
   - Options considered (3 minimum)
   - Decision made with rationale
   - Trade-offs accepted

2. DATA MODEL
   - Schema changes (SQL DDL or NoSQL document structure)
   - Migrations required
   - Index strategy

3. API DESIGN
   - Endpoint specification (method, path, request/response schemas)
   - Error responses
   - Authentication/authorization approach

4. IMPLEMENTATION TASKS (in dependency order)
   - Task name and description
   - Estimated effort (hours)
   - Assignee role
   - Acceptance criteria
   - Test requirements

5. RISK ASSESSMENT
   - Technical risks (probability, impact, mitigation)
   - Dependencies on other teams/systems
   - What could delay this

QUALITY STANDARD:
A mid-level developer should be able to start implementation from this plan 
without architectural ambiguity. If a decision isn't made yet, mark it as 
[DECISION NEEDED: description].