pipeline
Manage the content pipeline and idea backlog. Use when checking pipeline status, evaluating pillar distribution, reviewing idea statuses, or planning content calendar. Includes idea template, pillar definitions, and frontmatter schemas.
When & Why to Use This Skill
The Pipeline skill is a comprehensive content management and editorial workflow system designed to streamline the journey from ideation to publication. It enables users to maintain a structured idea backlog, track content status in real-time, and ensure strategic alignment with predefined content pillars. By providing automated pipeline reporting, stale-item detection, and standardized templates, it helps creators and marketing teams maintain a consistent publishing rhythm while ensuring their content mix hits specific strategic targets.
Use Cases
- Content Strategy Alignment: Monitor and balance content distribution across specific pillars (e.g., Tech Strategy, AI Trends) to ensure the output matches long-term marketing goals.
- Editorial Calendar Management: Review the idea backlog and identify items ready for drafting to plan a consistent weekly publishing schedule.
- Workflow Optimization: Automatically identify 'stale' drafts that have been inactive for over 30 days to resolve bottlenecks in the production pipeline.
- Standardized Content Creation: Use integrated templates and frontmatter schemas to ensure every new idea or post contains the necessary metadata and structure for SEO and tracking.
| name | pipeline |
|---|---|
| description | Manage the content pipeline and idea backlog. Use when checking pipeline status, evaluating pillar distribution, reviewing idea statuses, or planning content calendar. Includes idea template, pillar definitions, and frontmatter schemas. |
Pipeline Skill
Manage the content pipeline from idea to publication.
When to Use
- Checking overall pipeline status (
/pipelinecommand) - Reviewing idea backlog and priorities
- Ensuring pillar distribution is on target
- Planning which ideas to draft next
- Creating new ideas with proper structure
Quick Reference
Idea statuses: idea → drafting → ready_for_projection → published → archived
Pillar targets:
- Technology Strategy: 30%
- Leadership & Management: 25%
- Execution & Delivery: 20%
- Founder Lessons: 15%
- Market & AI Trends: 10%
Context Files
context/pillars.md- Content pillar definitions and targetscontext/frontmatter.md- Frontmatter schemas for all file typescontext/workflow.md- Status flow and weekly rhythmcontext/memory.md- MCP Memory usage for author profile and voice queries
Templates
templates/idea.md- Idea file template with full frontmatter
Commands
/pipeline
Run the pipeline status script to see the current state of all content.
Usage:
npm run pipeline
Output includes:
Pipeline Status - Counts of ideas by status (idea, drafting, ready_for_projection, published, archived) plus totals for drafts, posts, LinkedIn posts, and newsletter issues.
Pillar Distribution - Active ideas by pillar with percentage vs target:
- ✓ = On target (within 10%)
- ⚠ = Under target (needs more ideas)
- ▲ = Over target (pause new ideas)
Stale Items - Ideas in "drafting" status for 30+ days (based on YYYY-MM in the id)
Suggested Next Actions:
- Ideas ready for drafting (have pillar and target_audience)
- Pillars needing more ideas (>10% under target)
- Drafts to review for publishing