funnel-planner

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: funnel-planner
description: >
  Plan a complete affiliate funnel from research to revenue. Triggers on:
  "plan my affiliate funnel", "create a funnel strategy", "affiliate business plan",
  "how to start affiliate marketing", "full funnel roadmap", "plan from scratch",
  "week by week affiliate plan", "chain skills together", "build my funnel",
  "affiliate marketing roadmap", "step by step affiliate plan", "onboarding plan".
license: MIT
version: "1.0.0"
tags: ["affiliate-marketing", "meta", "planning", "compliance", "funnel", "strategy"]
compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent"
metadata:
  author: affitor
  version: "1.0"
  stage: S8-Meta
---

# Funnel Planner

Plan a complete affiliate funnel from research to revenue by chaining Affitor skills into a week-by-week execution roadmap. Output is a Markdown plan with skill sequence, time estimates, and exact invocation prompts for each step.

## Stage

S8: Meta — Most affiliates fail because they skip steps or work out of order. Funnel Planner solves this by mapping the user's resources (time, channels, experience) to a personalized execution plan that chains S1-S7 skills in the right sequence. It's the onboarding wizard for affiliate marketing via AI agent.

## When to Use

- User is starting from scratch and wants a complete plan
- User asks "how do I start affiliate marketing?"
- User has a niche but no strategy
- User wants to know which skills to use and in what order
- User says "build me a funnel" or "plan my affiliate business"
- User wants a week-by-week roadmap
- Chaining: this skill recommends which other skills to run and in what order

## Input Schema

```yaml
niche: string                  # OPTIONAL — e.g., "AI tools", "fitness supplements"
                               # If not provided, S1 research will help identify one

product: string                # OPTIONAL — specific product if already chosen
                               # e.g., "HeyGen" or "Semrush"

experience_level: string       # OPTIONAL — "beginner" | "intermediate" | "advanced"
                               # Default: "beginner"

available_channels:            # OPTIONAL — platforms the user can use
  - string                     # e.g., ["blog", "twitter", "linkedin", "email"]
                               # Default: ["blog", "twitter"]

weekly_hours: number           # OPTIONAL — hours per week available
                               # Default: 5

goal: string                   # OPTIONAL — "first_commission" | "scale_to_1k" | "scale_to_10k"
                               # Default: "first_commission"
```

**Chaining context**: If S1 was run earlier, pull niche and product info from conversation. If the user has mentioned their channels or experience, use that context.

## Workflow

### Step 1: Assess Starting Point

Determine where the user is:
- **Has nothing**: Start from S1 (full funnel)
- **Has a product**: Skip S1, start from S2
- **Has content**: Skip S1-S2, start from S3 or S4
- **Has traffic**: Skip to S6 (analytics) or S7 (automation)

Ask clarifying questions only if truly ambiguous. Default to the most common case (beginner, starting from scratch).

### Step 2: Select Relevant Skills

Based on channels, experience, and goal, select 5-8 skills from S1-S7:
- **Beginner + blog + twitter**: S1 → S2 (viral-post-writer) → S3 (affiliate-blog-builder) → S5 (bio-link-deployer) → S6 (seo-audit)
- **Intermediate + email + blog**: S1 → S3 → S4 (landing-page-creator) → S5 (email-drip-sequence) → S6 (performance-report) → S7 (content-repurposer)
- **Advanced + all channels**: Full S1-S7 pipeline with S8 (compliance-checker) at each content step

### Step 3: Estimate Effort

For each selected skill, estimate time based on experience level:
- Beginner: 2-4 hours per skill
- Intermediate: 1-2 hours per skill
- Advanced: 30-60 minutes per skill

Fit into the user's `weekly_hours` to create a week-by-week schedule.

### Step 4: Create R