agentleFS
cuevaiocuevaio/skills/skills/content-production/content-plan/SKILL.md

content-plan

Skill2 starsChanged 41 days agoMITView on GitHub

Turn an idea, goal, source, product update, or loose topic into a production-ready content brief. Use when choosing the audience, angle, promise, point of view, channel, format, series structure, evidence, CTA, or deciding what content is worth making.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the promise as: “This helps [audience] go from [starting state] to [outcome] by [point of view or method].”

    line 27
  2. Distinctive:

    remove material that does not serve the promise

    line 37
  3. Distinctive:

    Use a stairstep for educational material:

    line 47
  4. Distinctive:

    Do not plan every platform at once by default.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Plan Content

Plan the smallest piece that delivers one useful change for one audience. Read CONTENT_STYLE.md when available so the angle belongs to the creator rather than to generic content advice.

Creator defaults

For this creator, read the saved creator style alongside the local profile. A useful idea or personal recommendation can be the entire job; do not force a sales angle, engagement question or formal lesson into it. Keep source-specific experiences separate from the creator's own claims.

1. Define The Job

Inspect supplied source material before asking questions. Extract known decisions and propose the missing ones:

  • Audience: a specific person and starting state
  • Problem: the tension, obstacle, desire, or question
  • Outcome: what changes after consuming the piece
  • Point of view: what the creator believes or recommends and why
  • Business job: teach, build trust, start conversation, announce, convert, or retain
  • Canonical format: the source of truth for later derivatives
  • Destination: platform and consumption context
  • CTA: the one next action that serves the audience and the business job

Write the promise as: “This helps [audience] go from [starting state] to [outcome] by [point of view or method].”

Point of view, business job, canonical format, destination, and CTA belong to the creator. Infer them only as clearly labelled proposals from existing evidence; treat explicit choices and delegated editorial judgment in the current request as authorization. Ask only when a material decision remains unresolved; a provisional brief can support reversible work. The job is clear when candidate ideas can be rejected for failing to serve it.

2. Expand, Then Contract

During expansion, collect arguments, demonstrations, stories, examples, objections, data needs, visual proof, and likely derivatives without arranging them.

During contraction:

  1. remove material that does not serve the promise
  2. choose one central tension or claim
  3. separate creator experience from facts requiring research
  4. order prerequisites before dependent ideas
  5. reserve secondary ideas for follow-ups or derivatives

For a series, give every piece its own complete promise. A series is not permission to publish fragments that only make sense together.

3. Build The Content Arc

Use a stairstep for educational material:

  1. Anchor: what the audience already knows or feels
  2. Step: the new idea
  3. Proof: the example, result, story, or demonstration
  4. Objection: the next reasonable concern
  5. Landing: the memorable takeaway
  6. Action: the natural next step

For opinion, story, or announcement content, preserve the same functions without forcing tutorial language: tension → context → point of view → evidence → implication → action.

4. Choose The Production Shape

Choose one canonical source and planned derivatives:

Canonical sourceBest when
Short vertical videoOne fast idea, visual proof, or personal observation
Horizontal videoDepth, teaching, search, or durable reference
Written postThe argument works without performance or demonstration
Recording/transcriptConversation or spontaneous explanation is the strongest raw material

Do not plan every platform at once by default. Name the canonical source, then list only derivatives with a distinct audience job.

5. Produce The Brief

# <Working title>

## Job
- Audience and starting state:
- Problem/tension:
- Outcome:
- Creator point of view:
- Business job:
- Promise:
- CTA:

## Production Shape
- Canonical format and platform:
- Target length:
- Planned derivatives:
- Why each derivative deserves to exist:

## Arc
| Beat | Function | Claim/story | Proof or visual | Objection | Landing |
| --- | --- | --- | --- | --- | --- |

## Evidence
- Known facts and sources:
- Claims requiring research:
- Personal claims requiring confirmation:
- Examples, quotes, or visual assets needed:

## Voice
- Style profile:
- Desired energy:
- Phrases or approaches to preserve:
- Approaches to avoid:

## Production
- Delivery mode: bullets / hybrid / script
- Capture or design needs:
- Privacy or permissions:
- Deadline and owner:

The planning gate passes when the creator has approved one audience, one promise, one point of view, one canonical format, destination, CTA, and visible proof. Every planned derivative must have a stated job rather than existing to fill a channel. Carry forward approval or delegated choices already present in the request. Otherwise label the brief proposed and identify unresolved decisions without blocking independent reversible work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.