Specification Mastery

Advanced Prompt Patterns for Documentation

The prompt engineering patterns that consistently produce better documentation output — with templates you can apply immediately.

Prompt Patterns That Work

General prompting advice ("be specific," "give context") is a starting point. This lesson goes further — documenting the specific prompt patterns that reliably produce high-quality documentation output.

Pattern 1: The Context Dump

Before any substantive documentation task, front-load all context in a structured block.

text
CONTEXT:
Company: [Name]
Product: [Description in 2 sentences]
Stage: [Pre-seed / Seed / Series A / Bootstrapped]
Team: [Size and composition]
Target customer: [Specific description]
Current state: [What exists today]
Goal: [What you want to achieve with this document]
Audience: [Who will read this document]

TASK:
[The specific document or section you want]

The context dump means you don't have to repeat yourself across multiple prompts in the same session.

---

Pattern 2: The Role Framing

Tell Claude what perspective to write from.

text
Write this as a [senior product manager / experienced startup attorney /
Series B CFO / senior solutions engineer] who is [describing constraint].

Examples:

text
Write this sales playbook section as a VP of Sales who has closed $10M+ in B2B SaaS
deals and is coaching a first-time sales rep on enterprise objection handling.
text
Write this architecture decision record as a principal engineer who is skeptical
of adding new infrastructure dependencies and needs to be convinced by the
trade-off analysis.

Role framing surfaces perspectives and concerns you might not have considered.

---

Pattern 3: The Output Format Specification

Tell Claude exactly what format you want before the content.

text
Format requirements:
- Use H2 for main sections, H3 for subsections
- Use tables for comparison data
- Use numbered lists for sequential processes
- Use bullet points for non-sequential items
- Each section must be under 200 words
- End each section with a "Key Takeaway" line

This prevents the default Claude behavior of writing long prose paragraphs when you need structured reference material.

---

Pattern 4: The Completeness Check

After generating a document, ask Claude to audit it:

text
You just wrote [document name]. Now review it as a skeptical reader who:
1. Will challenge any claim that isn't supported by evidence
2. Will ask "so what?" after every bullet point
3. Will flag any section where the recommendation is vague
4. Will note any section where a critical piece of information is missing

Provide a numbered list of specific improvements.

---

Pattern 5: The Multi-Audience Rewrite

The same document often needs to serve multiple audiences.

text
I have the following technical specification section:
[paste section]

Rewrite this three times:
1. For a non-technical CEO who needs to understand the business impact
2. For an engineering lead who needs to understand the implementation decisions
3. For a customer success manager who needs to explain this to a customer

Keep each version under 150 words.

---

Pattern 6: The Devil's Advocate

Before finalizing any strategic document, ask Claude to argue against it:

text
Here is my business plan / pitch deck / product spec:
[paste document]

Play devil's advocate. If you were:
1. An investor who decided NOT to invest, what are your top 3 reasons?
2. A competitor who heard this plan, what would you exploit?
3. A skeptical board member, what questions would you ask?

Be specific, not generic. Reference the actual content of the document.

This is one of the highest-value documentation prompts — it stress-tests your document before a real audience does.

---

Pattern 7: The Gap Finder

text
Here is a [document type] I've written:
[paste document]

Identify all gaps — information that should be present but isn't.
For each gap, explain:
1. Why it matters
2. What a reader will think when they notice it's missing
3. What questions I should answer to fill it in

---

Pattern 8: The Version for Different Lengths

text
I have a full-length [document]. Generate three versions:
1. Executive summary (150 words max)
2. One-page overview (400 words max)
3. Full detail version (existing document — just re-confirm it's complete)

Each version should stand alone without requiring the others.

---

Combining Patterns

The most powerful prompts combine multiple patterns:

text
[CONTEXT DUMP — company, product, audience]

ROLE: Write as a VP of Product with 10 years of experience shipping B2B SaaS products.

FORMAT: Use H2 sections, bullet points for requirements (no prose paragraphs),
tables for trade-off comparisons.

TASK: Generate a product requirements document for [feature].

After generating the document, run a completeness check: identify the top 5 gaps
and what information I need to fill them in.

Key Takeaways

  • Context dumps frontload information so you don't repeat yourself
  • Role framing surfaces domain-specific perspectives and blind spots
  • Format specification ensures output is immediately usable, not a wall of prose
  • The devil's advocate and gap finder prompts are the highest-value QA passes for any documentation

---

Try It Yourself: Take any document you've already generated using earlier lessons in this tutorial. Apply the devil's advocate pattern. How many of the objections Claude raised are ones you hadn't considered? Use the output to strengthen the weakest sections.