Shape a writing task into an outline, brief, sequence, or publishable plan. Use when a content request needs structure (audience, goal, outline, success metric) before drafting.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Eliyce/paqad-ai --skill content-planner --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Content Planner?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/eliyce-content-planner)More formats (shields.io, HTML) on the badges page.
---
name: content-planner
description: Shape a writing task into an outline, brief, sequence, or publishable plan. Use when a content request needs structure (audience, goal, outline, success metric) before drafting.
---
# Content Planner
## What It Does
Turns a broad content ask into a concrete brief that a writer can act on without re-asking the original requester for context.
## Use This When
Use this whenever the next step would be drafting and the request lacks audience, goal, structure, or success metric.
## Inputs
- The original request and any linked references.
- `references/planner-checklist.md` for which fields a brief must contain.
## Procedure
1. Walk `references/planner-checklist.md` (audience, goal, constraints, outline, dependencies, success metric); never skip a field silently.
2. Fill `assets/brief.template.md` with project-specific values; mark unknowns explicitly.
3. Validate with `scripts/lint-brief.sh` — exit 0 means every required field is present.
## Output Contract
- Match `assets/brief.template.md` exactly.
- Output must pass `scripts/lint-brief.sh`.
## Resources
- `references/planner-checklist.md`
- `scripts/lint-brief.sh`
- `assets/brief.template.md`
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!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
