plan-writing

Break down complex work into actionable tasks with verification criteria.

Updated Aug 27, 2026

Search Tags:#workflow #planning #verification #task-management #project-management #planning-framework

Ready to run

npx skills add https://github.com/thimmarques/gestao-inteligente --skill plan-writing-thimmarques

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/thimmarques/gestao-inteligente/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/thimmarques/gestao-inteligente --skill plan-writing-thimmarques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down complex work into small, actionable tasks with clear verification criteria to reduce ambiguity and accelerate delivery.

Core Features & Use Cases

Small, focused tasks: Each task is actionable, time-bound, and independently verifiable.
Clear verification: Defines how to confirm completion at the task level.
Logical sequencing: Identifies dependencies and critical path, enabling parallel work where possible.
Dynamic project-root naming: Encourages saving plan files at the project root named after the task for easy discovery.
Project-specific planning: Adapts to new projects, feature additions, or bug fixes with minimal boilerplate.

Quick Start

Create a new plan file at the project root named after your task and outline 5-10 verifiable tasks.

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 project features into actionable tasks with clear verification criteria?▼

To break down complex project features into actionable tasks, you create a plan file at the project root and outline 5-10 small, time-bound tasks. Each task includes specific verification criteria to independently confirm completion and reduce ambiguity.

What is the best way to structure a multi-step refactor plan to enable parallel work?▼

The best way to structure a multi-step refactor plan is to enforce task-level granularity and identify task dependencies. This logical sequencing maps the critical path, enabling parallel work where possible across your codebase.

Does this planning framework work for both new product initiatives and incremental bug fixes?▼

Yes, this planning framework works for new product initiatives and incremental bug fixes. It adapts to any project effort with minimal boilerplate, guiding both new features and refactors by enforcing a lightweight, project-specific workflow model.

How do I name and save plan files for easy discovery in a codebase?▼

To name and save plan files for easy discovery, you create a new file at the project root dynamically named after your specific task. This root-level naming convention ensures plans are immediately accessible within the codebase.

Why should I use a verifiable task planning workflow instead of standard task management?▼

You should use a verifiable task planning workflow to reduce ambiguity and accelerate delivery. Unlike standard task management, it enforces task-level granularity and requires defined verification criteria to confirm completion at the task level.

Can I apply this planning framework to multi-step initiatives across any codebase without dependencies?▼

Yes, you can apply this planning framework to multi-step initiatives across any codebase. It operates with no external dependencies, adapting to your project-specific workflow to organize complex work into verifiable steps.