plan-writing

Breaks down complex work into structured tasks with verification criteria.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ollieb89/orchestrator --skill plan-writing-ollieb89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/ollieb89/orchestrator/tree/main/.cursor/skills/plan-writing
Command: npx skills add https://github.com/ollieb89/orchestrator --skill plan-writing-ollieb89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a framework to break down work into clear, actionable tasks with dependencies, ownership, and verification criteria for efficient delivery.

Core Features & Use Cases

  • Small, focused tasks with independently verifiable outcomes
  • Clear planning principles to guide feature development, refactoring, or multi-step projects
  • Project-root naming conventions to generate and organize plan files

Quick Start

Create a plan file at the PROJECT ROOT with a slugged name (e.g., auth-feature.md) and outline 4–6 actionable tasks with verification checks.

Frequently Asked Questions about plan-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down complex feature development into actionable tasks?

Break down complex feature development by structuring work into small, focused tasks with clear dependencies, ownership, and independently verifiable outcomes. This approach ensures efficient delivery for multi-step software projects.

What's the best way to write a project plan file with verification criteria?

Write a project plan file at your project root using a slugged name like auth-feature.md. Outline 4–6 actionable tasks, ensuring each includes specific verification checks to meet project planning workflow requirements.

When do I need structured task planning for refactoring workflows?

You need structured task planning for refactoring workflows when work involves multiple dependent steps requiring clear ownership. It guides focused tasks with independently verifiable outcomes to ensure efficient delivery.

Can I use this approach for agile project management across software teams?

Yes, you can use this approach for agile project management across software teams. It applies clear planning principles to feature development, refactoring, or multi-step projects, ensuring tasks have verifiable outcomes.

What naming conventions should I follow for project plan files?

Follow project-root naming conventions for plan files by creating a slugged name, such as auth-feature.md. This ensures proper generation and organization of plan files within your project planning workflows.