Landing Page Draft

skill

Draft a full research-backed landing page (hero, sections, CTAs) as a file with a summary.

Download .md

Landing Page Draft

Draft a full, research-backed landing page — hero, sections, calls to action (CTAs) — and save it as a file with a short summary of what you produced.

When to use

  • A stakeholder asks for a new landing page for a product, offer, or campaign.
  • You need a research-grounded page draft before a designer or copy reviewer takes over.
  • An existing page needs a full rewrite rather than a small tweak.
  • A campaign launch requires a dedicated page and none exists yet.

Tools

  • read-file — pull in prior briefs, positioning notes, or an earlier draft to build on.
  • write-file — save the finished landing page draft as a file.
  • complete-task — close out the task with a structured summary of the draft.

Playbook

  1. Read the task brief carefully: product/offer, target audience, primary goal (signup, demo, purchase), and any brand voice constraints.
  2. If a prior brief, positioning doc, or earlier draft is referenced, pull it in with read-file so the draft builds on existing research rather than repeating it.
  3. Identify the core value proposition: the single sentence that explains why this audience should care right now.
  4. Draft the hero section: headline, subheadline, and primary CTA. The headline should state the outcome, not the feature.
  5. Draft supporting sections in a logical order: problem/pain, solution/how it works, proof (testimonials, stats, logos), objection handling (FAQ or risk reversal), and a final CTA section.
  6. Write every CTA as a specific action tied to the goal (for example "Start your free trial" rather than "Submit"), and repeat the primary CTA at least twice on the page.
  7. Assemble the full draft as clean markdown with clear section headings so it can be handed to a designer or copywriter without further interpretation.
  8. Save the complete draft using write-file, naming the file clearly after the product or campaign it serves.
  9. Finish with complete-task, summarizing the page's structure (sections included), the primary CTA used, and the file path where the draft was saved.

Failure modes

  • No brief or prior research provided -> do not invent product claims; note the gap and draft only what can be supported, flagging missing inputs in the summary.
  • Conflicting instructions (for example two different target audiences) -> pick the primary goal stated in the task, note the ambiguity in the summary, and proceed.
  • Draft grows too long or unfocused -> cut back to hero, three to five core sections, and one final CTA rather than padding with filler.
  • Unable to write the file -> stop, do not fabricate a save confirmation, and report the failure via complete-task as blocked.

Done when

  • A complete landing page draft (hero, body sections, CTAs) has been saved as a file via write-file.
  • The task is closed via complete-task with a summary of the page's sections and the file path.
  • No section relies on unstated or fabricated product claims beyond what the brief or prior research supports.