plan-writing

Break complex engineering work into actionable plans with verification criteria.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill plan-writing-capaas2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/capaas2/Site-teste --skill plan-writing-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you break down larger engineering or product tasks into small, actionable steps with clear verification so work stays organized and easy to execute.

Core Features & Use Cases

  • Task Decomposition: Splits features, refactors, and bug fixes into a short sequence of focused tasks.
  • Verification Guidance: Defines how each step can be checked so progress is measurable and less ambiguous.
  • Practical Planning: Useful when you need a concise implementation plan for multi-step work, such as adding authentication, refactoring a module, or shipping a new feature.

Quick Start

Ask for a short implementation plan for your task with clear steps and verification criteria.

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 feature implementation into actionable steps?

To break down feature implementation, you decompose the work into a short sequence of focused tasks with explicit verification criteria. This ensures each step has a simple, testable outcome to keep execution organized and measurable.

What is the best way to plan a multi-step software refactoring task?

Planning a multi-step software refactoring task involves splitting the work into ordered, focused tasks with dependency awareness. Each step gets defined verification guidance so progress remains measurable and less ambiguous throughout the process.

How do I create an implementation plan for a bug fix with testable outcomes?

Creating an implementation plan for a bug fix requires prioritizing tasks and defining simple testable outcomes for each step. This approach ensures the fix is verifiable and execution stays ordered and focused.

Can I use this planning method for large engineering tasks without dependencies?

Yes, this planning method works for large engineering tasks without dependencies by applying task prioritization and dependency awareness. It breaks the work into concise, actionable plans regardless of external library constraints.

When do I need verification criteria for a software task breakdown?

You need verification criteria for a software task breakdown when executing multi-step work like adding authentication or shipping a new feature. Defining how each step is checked makes progress measurable and reduces ambiguity.