PRD: Design-Ready Copy Agent
Status: Draft — gathering requirements
Last updated: 2025-02-03
Context graph: See CONTEXT_GRAPH_APPROACH.md for how this agent contributes to our process knowledge.
1. Overview
Agent that produces design-ready copy for campaign collateral (e.g. one-pagers, 2-pagers) by pulling from campaign briefs and the case study library, splitting content into clear sections, and giving light design guidance so designers can drop text in without wading through long narrative.
2. Requirements (current)
| # | Requirement | Notes |
|---|---|---|
| 1 | Pull copy from the campaign brief | Source: campaign briefs in brainforge-vault. Field list TBD (user will provide examples). |
| 2 | Reference full library of case studies in brainforge-files | Path: brainforge-files repo → sales/case_studies (tree/main). |
| 3 | Split into multiple sections by asset type | Taxonomy: DESIGN_READY_COPY_TAXONOMY.md. Service 2-pager = §6 below; other archetypes (sprint, promo, guide, partner kit) = taxonomy. |
| 4 | Copy sections tight; light recommendations | One markdown file, clear headings. Recommendations = wording variations (design/layout variations = v2). |
3. Resolved (from Q&A)
- Campaign brief source: Campaign briefs in brainforge-vault; specific fields to be provided (examples later).
- Case study library:
brainforge-filesrepo, pathsales/case_studies(main). - Output format: One markdown file with clear section headings.
- Design recommendations (v1): Wording variations only; keep in same doc but in a separate section so designers can focus on copy and ignore the recommendations section. Design/layout variations deferred to next version.
4. Open questions (to resolve before build)
- Brief fields: Which campaign brief fields to pull; user will provide examples.
- Header examples: User will provide reference examples for punchy header variations.
- Access to brainforge-files: How will the agent read case studies? (e.g. same workspace with both repos, separate clone, API?)
5. Anti-pattern: What NOT to do
Principle: Designers don’t need to be told how to design. They need copy ready to drop into their design process — nothing more.
Do NOT include in the copy sections:
| Avoid | Why |
|---|---|
| Visual suggestions | ”Hero image”, “timeline diagram”, “2x3 grid”, “side-by-side comparison” — designer decides. |
| Layout / placement notes | ”Center of slide”, “right side”, “full background” — not copy. |
| Color / style notes | ”Red for before, green for after”, “brand colors” — designer owns this. |
| StoryBrand element labels | ”Character”, “Problem”, “Guide”, “Plan” — internal framing, not for the asset. |
| ”Notes for Designer” / design direction | ”Overall design direction”, “key visual elements”, “slide count” — fluff. |
| TBD placeholders as section titles | Use real copy or a neutral label; don’t leave “Title: TBD” in the doc. |
What the output SHOULD be: Section headings + the actual copy (headline, subheadline, body, bullets, CTA text, contact block). Tight. No layout, no visual suggestions, no design instructions in the copy section. Wording variations (if any) live in a separate section only.
Reference: User-provided “overblown” example (1-pager + deck with heavy visual/layout/StoryBrand notes) — do the opposite.
6. 2-pager section structure (canonical)
Teardown of the dbt 2-pager defines the fixed section order and rules. Copy only in each section; no layout or visual notes.
| Section | Purpose | Data source | Rules |
|---|---|---|---|
| 1. Header | Top-left hero | Campaign brief | Multiple variations (agent outputs 2–3 options). Punchy, succinct. User will provide reference examples for tone. |
| 2. Trusted by | Client logos | Case studies (brainforge-files) | Pull relevant clients by company type. Match to ICP in campaign brief. (e.g. dbt 2-pager → digitally native / software / dbt-powered: StackBlitz, Default, readme, Eden, Pool Parts.) |
| 3. KPI / metric highlight | One modular block | Campaign brief | One big metric (save X$, reduce time Y%, etc.) + 1–2 sentence takeaway: “Clients get this win.” Must be clear from brief. |
| 4. Process | ”Fast, low-risk way to fix [X]“ | Campaign brief | Visual of our process: time-box (e.g. 3–4 weeks), 3-step process (e.g. Audit → Roadmap → Deploy). Crisp, minimal text — step label + one line each. |
| 5. Menu of capabilities | What you get / what unlocks | Campaign brief + case study flavor | ”What do you actually get?” Capabilities / dream state client unlocks. Not the same as the top metric — bragging rights, specific wins. 4–6 items. |
| 6. Who this is for + Deliverables | Audience + what they get | Campaign brief | Cookie-cutter. Comes straight from brief. Same structure every time: audience (who) + deliverables list. |
| 7. Case study highlight | One proof nugget | brainforge-files case studies | Complex: Pick a case study that fits the campaign; pull out one nugget (narrative snippet or key result, e.g. “>85% reduction in lines of code”) to feature. Short. |
| 8. CTA | Call to action | Campaign brief | Punchy. Different per service line (not cookie-cutter). Headline + subheadline + button text. |
| 9. Follow-up / Let’s talk | Contact | Static | Standard, never change. Same copy every time (e.g. “Have follow-up questions? Let’s talk.” + contact cards). |
Order: 1 → 2 → 3 → 4 → 5 (page 1); 6 → 7 → 8 → 9 (page 2). Sections 3–5 are “three slides smushed into three sections” on page 1.
Other asset types: See DESIGN_READY_COPY_TAXONOMY.md for section structures for Sprint 1-pager, Seasonal promotion, Service guide, Partner/VC kit. Agent picks archetype from brief (or user), then uses that archetype’s section sequence.
7. Scope & constraints
TBD
8. Inputs & outputs
| Spec | |
|---|---|
| Inputs | Campaign brief (path or content); access to brainforge-files/sales/case_studies. |
| Output | Single markdown: (1) copy sections with clear headings, (2) separate section for wording variations. |
9. User & workflow
TBD
10. Out of scope / later
- Design and layout variations (v2).