plan-writing

Decompose complex software work into small, verifiable tasks with dependencies.

Updated Aug 30, 2024
One-click install
npx skills add https://github.com/jfrometa/esquizo --skill plan-writing-jfrometa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/jfrometa/esquizo/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/jfrometa/esquizo --skill plan-writing-jfrometa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams decompose complex work into small, actionable tasks with clear verification criteria, enabling faster, more reliable delivery.

Core Features & Use Cases

  • Small, Focused Tasks: Each task should take 2-5 minutes and be independently verifiable.
  • Clear Verification: Define how you verify task completion.
  • Logical Ordering: Identify dependencies, parallel work, and ensure verification is the final phase.
  • Dynamic Naming: Plan files are saved at the PROJECT ROOT with descriptive names, never inside .claude/ or docs.

Quick Start

Create a new plan file named {task-slug}.md at the PROJECT ROOT and fill in the Task List with concrete actions and verifications.

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 software features into verifiable tasks?

To break down complex software features into verifiable tasks, you decompose work into small, independently verifiable units taking 2-5 minutes each, identifying dependencies and defining clear verification criteria for every step.

What is the best way to structure task planning for multi-step software projects?

The best way to structure task planning for multi-step projects is to apply a simple, repeatable plan structure with dynamic task naming, identifying parallel work and dependencies, ensuring verification is the final phase of execution.

How do you write a plan file for software refactoring and feature development?

To write a plan file for refactoring or feature development, create a new markdown file at the project root with a descriptive task slug name, then fill in the task list with concrete actions and verifications.

Where should I save project plan files for task planning workflows?

You should save project plan files at the project root with descriptive, dynamic names, never inside the .claude/ directory or docs folder, ensuring easy access for the entire team.

Can I use this task planning approach for large team project management scenarios?

Yes, you can use this task planning approach for team project management scenarios, as it enforces project-specific planning rules, logical ordering, and clear verification to guide team planning and execution reliably.

Why should each task in a software development plan take only 2 to 5 minutes?

Each task in a software development plan should take 2-5 minutes to ensure it is small, focused, and independently verifiable, which enables faster, more reliable delivery by simplifying tracking and validation.