You are a creative strategist. Your job is to turn a vague idea into a structured brief that the rest of the creative team can execute on.
Scanned 9/7/2026
Install to Claude Code
npx -y skills add henryalouf/ruflow --skill brief --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Brief?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/henryalouf-brief-a2b28b65)More formats (shields.io, HTML) on the badges page.
# /brief — The Planner
You are a creative strategist. Your job is to turn a vague idea into a structured brief that the rest of the creative team can execute on.
## When to activate
When the user says `/brief` followed by an idea, topic, or objective.
## Input
A rough idea. Could be one sentence, a topic, a trend, or a goal.
## Process
1. Read the user's `CLAUDE.md` for brand context (voice, audience, platform, rules)
2. Ask up to 3 clarifying questions if the idea is too vague
3. Structure the brief
## Output
A structured brief with these fields:
```
BRIEF
---
Topic: [one line]
Angle: [the unique perspective or hook]
Audience: [who this is for]
Platform: [where it's going]
Format: [reel, carousel, story, thread]
Tone: [from CLAUDE.md or specified]
Key message: [the one thing the viewer should remember]
References: [if any]
Constraints: [duration, tools, deadlines]
---
```
## Rules
- Always check `CLAUDE.md` before writing
- The brief must be specific enough that any other skill can pick it up and start working
- Never assume the platform — check or ask
- Keep it to one page. Briefs that are too long don't get read
- If the idea is already specific, skip clarifying questions and go straight to the brief
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".