plan-pillar — Claude Code command: what it does, how to install
plan-pillar builds a content pillar plan with hero assets, derivative pieces, and a distribution schedule. Saves task dependencies and KPIs directly to JSON.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/plan-pillar.mdWhat plan-pillar does
The command generates a full content blueprint through five stages: brief intake, hero asset definition, derivative mapping, owner assignment, and distribution hooks. It accepts --theme, timeline --window, and target --channels, with optional flags for personas and KPI goals.
Execution defaults to the pipeline pattern for sequential delivery. When distribution prep runs alongside creative drafting, it shifts to the diamond pattern. The resulting dependency graph, stages, and metrics are written to .claude/plans/plan-<timestamp>.json.
Built-in guardrails monitor delivery issues. If deliverable delays or QA defects breach twice within 48 hours, escalation triggers notify the Editorial Director, Creative Producer, and Marketing Director.
What it helps with
- map derivative content formats from a flagship asset
- generate a content pillar schedule for specific channels
- save campaign tasks and dependency graphs to
.claude/plans - set up escalation paths for missed approvals or QA defects
Example prompts for the agent
- /content-pipeline-orchestration:plan-pillar --theme "AI readiness" --window 8w --channels "blog,video,webinar"
- /content-pipeline-orchestration:plan-pillar --theme "Product Security" --window 4w --channels "social,email" --goals "pipeline"
How to install plan-pillar
Manually: put the files in place
.claude/commands/plan-pillar.mdCall it with /plan-pillar. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan-pillar.mdCall it with /prompts:plan-pillar. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan-pillar.prompt.mdManually: put the files in place
.gemini/commands/plan-pillar.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan-pillar
How do I install plan-pillar in Claude Code?
Add the command file to .claude/commands/plan-pillar.md.
What does the plan-pillar command do?
It creates a content pillar blueprint covering flagship hero assets, channel derivatives, task owners, and distribution rules.
Which orchestration patterns does the command support?
It defaults to pipeline for linear progression from brief to hero asset and distribution. When creative pods and distribution prep run in parallel, it applies the diamond pattern.
Source text
plan-pillar.md · Apache-2.0
--- name: plan-pillar description: Produces a content pillar blueprint with hero assets, derivatives, and distribution plan. usage: /content-pipeline-orchestration:plan-pillar --theme "AI readiness" --window 8w --channels "blog,video,webinar" --- # Command: plan-pillar ## Inputs - **theme** – content pillar topic. - **window** – program duration. - **channels** – comma-separated roster (blog, video, webinar, social, email, enablement). - **audiences** – optional persona/vertical list. - **goals** – optional KPIs (pipeline, subscribers, product adoption). ### GTM Agents Pattern & Plan Checklist > Derived from GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. - **Pattern selection**: Default to **pipeline** (brief → hero asset → derivatives → owners → distribution). Use **diamond** when creative pods and distribution prep can run in parallel; document the pattern in the plan header. - **Plan schema**: Save `.claude/plans/plan-<timestamp>.json` with objective, asset stages, task IDs, parallel groups, dependency graph, error handling, and success criteria (e.g., MQL, pipeline, share of voice). - **Tool hooks**: Reference `docs/gtm-essentials.md` stack (Serena for CMS/landing updates, Context7 for brand/legal docs, Sequential Thinking for retros, Playwright for QA of landing pages). - **Guardrails**: Define retry strategy (default 2) and escalation ladder (Editorial Director → Creative Producer → Marketing Director) for missed approvals or QA issues. - **Review**: Before execution, run the checklist in `docs/usage-guide.md#orchestration-best-practices-puerto-parity` to confirm agents, dependencies, deliverables. ## Workflow 1. **Brief Intake** – align on objectives, persona needs, proof assets, campaign tie-ins. 2. **Hero Asset Definition** – define flagship deliverables (ebook, webinar, video series) with requirements. 3. **Derivative Mapping** – outline derivative assets per channel with rough cadence. 4. **Resourcing & Owners** – assign writers, designers, reviewers, budgets, tooling. 5. **Distribution Hooks** – highlight promotion partners, paid support, enablement ties. ## Outputs - Pillar blueprint table (asset, format, owner, due date, CTA, dependency). - Creative brief package template per asset. - Initial distribution + amplification notes. - Plan JSON entry stored/updated in `.claude/plans` for audit trail. ## Agent/Skill Invocations - `editorial-director` – leads strategy + calendar. - `editorial-calendar` skill – enforces cadence + governance. - `asset-tracking` skill – maps resources + dependencies. ## GTM Agents Safeguards - **Fallback agents**: document substitutes (e.g., Creative Producer covering Distribution Lead) when specialists unavailable. - **Escalation triggers**: if asset delivery or channel guardrails (cadence, QA defects) breach twice within 48h, trigger escalation to Content + Growth leadership per GTM Agents playbook. - **Plan maintenance**: Every scope change (asset count, owner, channel) must update the plan JSON and change log to maintain parity with GTM Agents audits. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents