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
- ZoolCoder/findabletheir own version, first seen Nov 1, 2026
- RightBlogger/bloggingskillstheir own version, first seen Nov 1, 2026
- fliqrlabs/instagram-creator-skillstheir own version, first seen Nov 1, 2026
- codebywater/WB-OZON-AI-TEAMtheir own version, first seen Oct 25, 2026
- DRAZY/claude-skillstheir own version, first seen Sep 14, 2026
- marcus-at-localhost/market-context-kittheir own version, first seen Aug 21, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- fliqrlabs/instagram-creator-skills★ 5same name
- RightBlogger/bloggingskills★ 4same name
- codebywater/WB-OZON-AI-TEAM★ 2same name
- donatassimkus/claude-ai-skills★ 1same name
- DRAZY/claude-skills★ 1same name
- lumizone/social-content-os-claude-skill★ 0same name
- marcus-at-localhost/market-context-kit★ 0same name
- phoenixvn/claude-code-agency★ 0same name
- ZoolCoder/findable★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- buffer-schedulingSkill
- content-publishSkill
- content-repurposeSkill
- content-researchSkill
- content-scriptSkill
- contentSkill
- content-voiceSkill
- screenstudio-editSkill
- social-postSkill
- video-editSkill
- video-recordSkill
- video-setupSkill
- youtube-remotion-clipsSkill
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
- Distinctive: line 27
Write the promise as: “This helps [audience] go from [starting state] to [outcome] by [point of view or method].”
- Distinctive: line 37
remove material that does not serve the promise
- Distinctive: line 47
Use a stairstep for educational material:
- Distinctive: line 69
Do not plan every platform at once by default.
“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.
Files
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:
- remove material that does not serve the promise
- choose one central tension or claim
- separate creator experience from facts requiring research
- order prerequisites before dependent ideas
- 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:
- Anchor: what the audience already knows or feels
- Step: the new idea
- Proof: the example, result, story, or demonstration
- Objection: the next reasonable concern
- Landing: the memorable takeaway
- 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 source | Best when |
| Short vertical video | One fast idea, visual proof, or personal observation |
| Horizontal video | Depth, teaching, search, or durable reference |
| Written post | The argument works without performance or demonstration |
| Recording/transcript | Conversation 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.
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
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.

