Output Specifications

An output specification defines what the final deliverable looks like before you start building it. Not roughly. Exactly. Section titles, word count targets per section, formatting conventions, citation style, header hierarchy, and the exact structure of any tables or comparison matrices. The specification is the contract between the pipeline and the stakeholder.

The prompt pattern: "The final deliverable must conform to this specification: [paste spec]. After drafting, compare your output against the specification section by section. Report any deviations." Claude will conform to detailed specifications reliably. It will interpret vague specifications creatively — and creativity in a deliverable pipeline means inconsistency.

## Output Specification: Competitive Brief

**Length:** 1200-1500 words
**Sections:**
1. Executive Summary (100 words, 3 sentences max)
2. Competitive Landscape (300 words, comparison table required)
3. Strengths & Vulnerabilities (400 words, SWOT format)
4. Recommended Positioning (200 words, 3 bullet points)
5. Sources (numbered list, minimum 5)

**Formatting:**
- Headers: ## for sections, ### for subsections
- Tables: pipe-delimited markdown
- Citations: inline [Source N] with numbered list at end
- Tone: analytical, not promotional