F.F.E.W.S. Workflow Spec Generator

SKILL.md Preview

---
name: ffews-workflow-spec-generator
description: Use this skill when the user asks Claude to plan or spec a funnel, automation, campaign, or lead-capture system, or to map out the automation behind an offer. Trigger when the user mentions building a funnel, the full automation behind a launch, GoHighLevel or CRM builds, or phrases like 'give me the build spec for my lead funnel.' This skill helps produce a build-ready automation spec covering Forms, Funnels, Emails, Workflows, and Social.
compatibility: Claude.ai, Claude Desktop
---

# F.F.E.W.S. Workflow Spec Generator

## Purpose
Produce an automation build spec organized by the five F.F.E.W.S. components, so a vague 'I need a funnel' becomes a complete document where every moving part has a home. Covering the same five layers every time means nothing gets forgotten.

## When to Use This Skill
Use it to plan or document any funnel or marketing automation before or during a build.

## When Not to Use This Skill
Do not use it to write the copy inside the funnel (use the relevant copy skills) or to design CRM pipelines alone (use the pipeline skill). Do not use it before the offer and goal are clear.

## Required Inputs
- The offer and price.
- The traffic source.
- The goal of the automation (lead capture, sale, booking, nurture).
- The tools or platform in use.

## Workflow
1. Confirm inputs in one batch.
2. Spec Forms: every form, its fields, and where submissions go.
3. Spec Funnels: the page sequence and the path between pages.
4. Spec Emails: each automated email or sequence, its trigger, and its goal.
5. Spec Workflows (triggers, conditions, actions, tags, branching) and Social (retargeting, organic, DM automation).

## Output Format
Return the spec with a section per F.F.E.W.S. component (Forms, Funnels, Emails, Workflows, Social), each detailed enough to hand to a builder, plus a short flow summary at the top showing the path from traffic to goal.

## Quality Standards
- All five layers are covered; if one is minimal, it is marked 'none needed' rather than skipped, so the spec is provably complete.
- Workflow logic is concrete: trigger, condition, action for each step.
- Every component ties back to the single goal.
- Uses contractions, no em dashes, no hype.

## Edge Cases
If the platform is unknown, write the spec platform-agnostically and note where platform specifics are needed. If the goal is unclear, pin it down first; a funnel with no single goal cannot be specced cleanly.

## Safety and Limitations
Do not spec deceptive automations (fake scarcity timers, misleading opt-ins). Keep automations honest and compliant.

## Test Prompts
1. Spec the full funnel for my $497 course launch. Traffic is from a webinar, goal is sales, I'm on GoHighLevel. I want forms, pages, emails, workflows, and retargeting mapped out.
2. I need a complete build spec for a lead-capture funnel for my local cleaning business. Traffic from Facebook ads, goal is booked estimates. Map everything in F.F.E.W.S.
3. Map the automation for a free challenge funnel that leads into a paid membership. Cover the opt-in, the daily emails, the tags and branching, and the social follow-up.

Skill Details

Package Preview

Trigger Phrases

• "Spec the full funnel for my $497 course launch. Traffic is from a webinar, goal is sales, I'm on GoHighLevel. I want forms, pages, emails, workflows, and retargeting mapped out."
• "I need a complete build spec for a lead-capture funnel for my local cleaning business. Traffic from Facebook ads, goal is booked estimates. Map everything in F.F.E.W.S."
• "Map the automation for a free challenge funnel that leads into a paid membership. Cover the opt-in, the daily emails, the tags and branching, and the social follow-up."