plan-writing

Breaks down development work into small, verifiable steps with dependencies.

6|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/paulojalowyj/openkit --skill plan-writing-paulojalowyj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/paulojalowyj/openkit/tree/main/.opencode/skills/plan-writing
Command: npx skills add https://github.com/paulojalowyj/openkit --skill plan-writing-paulojalowyj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing complex tasks by providing a structured methodology to break them down into small, verifiable, and logically ordered steps, ensuring clarity and efficient execution.

Core Features & Use Cases

  • Task Decomposition: Breaks down large initiatives into manageable tasks (2-5 minutes each).
  • Verification Criteria: Defines clear, independent ways to confirm task completion.
  • Dependency Management: Identifies task order and potential for parallel work.
  • Use Case: When starting a new feature development, use this skill to create a detailed plan with specific, actionable tasks, each with a clear verification step, ensuring all aspects of the feature are covered systematically.

Quick Start

Use the plan-writing skill to create a plan for adding a new user authentication feature to the web application.

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 a complex software feature into actionable tasks?

Task breakdown helps manage software complexity by dividing initiatives into small 2-5 minute steps. This structured planning ensures logically ordered execution with clear dependencies and independent verification criteria for each unit of work.

What is the best way to plan a refactoring project with clear verification steps?

Planning refactoring requires structured task decomposition with independent verification criteria for each step. This ensures every code modification is systematically confirmed before moving to the next dependent task.

How does dependency management work when planning agile task breakdowns?

Dependency management in agile task breakdowns identifies the specific execution order of tasks and highlights opportunities for parallel work. This ensures independently verifiable steps are logically sequenced to prevent development bottlenecks.

Can I use this task planning methodology for bug fixing workflows?

Yes, this task planning methodology is explicitly applicable to bug fixing workflows. It breaks down the resolution process into small, verifiable steps with clear dependencies, ensuring the root cause is addressed methodically.

Do I need any specific project management tools to implement this workflow planning?

No external project management tools are required as dependencies. The workflow planning operates by directing planning artifacts to specific documentation directories and using interactive user input to structure the breakdown.