From blog-workflow
Creates structural outline (sections, word estimates, code/diagram locations) from blog post spec at <path> using optional --template. Writes outline.md, updates links/table, self-reviews.
How this command is triggered — by the user, by Claude, or both
Slash command
/blog-workflow:plan <path> [--template name]post/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Post Plan Command
Create a structural outline from a post specification. The outline defines sections, word estimates, code example locations, and transitions.
## Tools
- `Read` - Load spec and template
- `Write` - Create outline
## Behavior
1. **Validate input**:
- Check spec exists at `{{path}}`
- Check spec status (can be `draft` or `approved`)
- Check outline doesn't exist (unless `--force`)
2. **Load outline template**:
- If `--template` flag provided, use that
- Otherwise, from `template` field in spec frontmatter
- Or default based on `content_type` from pha...Create a structural outline from a post specification. The outline defines sections, word estimates, code example locations, and transitions.
Read - Load spec and templateWrite - Create outlineValidate input:
{{path}}draft or approved)--force)Load outline template:
--template flag provided, use thattemplate field in spec frontmattercontent_type from phase.templates/outlines/<template>.mdTemplate preview (optional):
Generate outline following template structure:
Verify word estimates sum to target length (+/-10%)
Write outline: post/<phase-slug>/outline.md
Create bidirectional links:
parent in outline to ./spec.mdchildren in specUpdate Post Artifacts table in index.md
Self-review (structure check):
| content_type | Default Template | Alternatives |
|---|---|---|
tutorial | tutorial.outline.md | getting-started.outline.md, how-i-built.outline.md |
deep-dive | algorithm-deep-dive.outline.md | architecture-decision.outline.md, performance.outline.md |
experiment | experiment.outline.md | debug-error.outline.md |
explainer | first-look.outline.md | comparison.outline.md, library-evaluation.outline.md |
Created post outline: content/_projects/<slug>/post/<phase-slug>/outline.md
Template: {{template}}.outline.md
Sections: {{count}}
Total words: ~{{total}} (target: {{target}})
Section breakdown:
- Introduction: {{words}} words
- {{Section 1}}: {{words}} words
- {{Section 2}}: {{words}} words
- Conclusion: {{words}} words
Code examples: {{count}} locations marked
Diagrams: {{count}} locations marked
Self-review: {{passed|warnings}}
Next: Run `/blog/post/draft content/_projects/<slug>/post/<phase-slug>/outline.md`
| Condition | Error Message | Resolution |
|---|---|---|
| Spec doesn't exist | "Post spec not found at {{path}}" | Run /blog/post/spec first |
| Spec not approved | "Spec status is '{{status}}'. Review and approve first, or proceed anyway?" | Approve or confirm |
| Outline already exists | "Outline exists at {{path}}. Use --force to overwrite" | Use --force flag |
| Template not found | "Template '{{slug}}' not found in .templates/outlines/" | Verify template exists |
| Word estimate mismatch | "Outline total ({{N}}) differs from spec target ({{M}}) by >10%" | Adjust estimates |
# Normal outline creation
/blog/post/plan content/_projects/kubernetes-migration/post/tutorial-basics/spec.md
# Override template
/blog/post/plan content/_projects/kubernetes-migration/post/tutorial-basics/spec.md --template how-i-built
# Overwrite existing outline
/blog/post/plan content/_projects/kubernetes-migration/post/tutorial-basics/spec.md --force
npx claudepluginhub arustydev/agents --plugin blog-workflow/planCreates a step-by-step implementation plan from requirements or a PRD markdown file, then waits for user confirmation before any code changes.
/planBreaks project into small verifiable tasks with acceptance criteria, dependencies, checkpoints. Reads spec/codebase, presents plan for review, saves to tasks/plan.md and tasks/todo.md.
/planStarts Manus-style file-based planning: creates task_plan.md, findings.md, progress.md if missing, invokes planning skill, and guides through workflow.
/planInteractively builds Goal, Scope, Metric, and Verify command for an autoresearch run from provided goal description.
/planRestates requirements, assesses risks, creates step-by-step implementation plan with phases, dependencies, complexity estimates, and waits for user confirmation.
/planCaptures user intent, analyzes requirements, and generates a weighted execution plan saved to .claude/session-plan.md. Does not execute — plans are saved for review or later execution via /octo:embrace.