plan-writing

Name: plan-writing
Availability: InStock
Author: tuyenht

Break down objectives into small, verifiable tasks with defined outcomes and sequencing.

Updated Jan 31, 2026

Search Tags:#workflow #planning #project management #verification #task breakdown #agile

Ready to run

npx skills add https://github.com/tuyenht/Antigravity-Core --skill plan-writing-tuyenht

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured approach to breaking down complex tasks into smaller, manageable, and verifiable steps, ensuring clarity and efficient execution.

Core Features & Use Cases

Task Decomposition: Divides work into small, focused tasks (2-5 minutes each) with clear outcomes.
Verification Criteria: Defines how each task's completion will be checked.
Logical Ordering: Ensures tasks are sequenced correctly, identifying dependencies and parallelizable work.
Use Case: When starting a new feature development, use this skill to create a detailed, step-by-step plan that guides the developer through implementation and verification.

Quick Start

Use the plan-writing skill to create a plan for adding a user login 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 software feature into actionable tasks?▼

Task breakdown involves decomposing project objectives into small, 2-5 minute focused steps with specific outcomes. This method ensures clarity by emphasizing specific project context and verifiable results over generic templates.

What is the best way to define verification criteria for project management tasks?▼

The best way to define verification criteria is to establish clear methods for checking each task's completion during decomposition. This ensures every small step in a work plan has a defined, testable outcome before sequencing begins.

How do I sequence tasks and identify dependencies for agile planning?▼

Sequencing tasks requires logically ordering the decomposed work steps to identify dependencies and parallelizable work. This ensures correct execution flow for new projects, feature additions, or bug fixes within an agile workflow.

Can I use this task breakdown approach for both new features and bug fixes?▼

Yes, you can use this task breakdown approach for new projects, feature additions, and bug fixes. It defines task outcomes, verification methods, and logical sequencing to ensure clarity and efficient execution across different development scenarios.

Why should I use specific project context instead of generic templates for work plans?▼

Using specific project context instead of generic templates ensures the work plan accurately addresses the unique requirements of your objective. It facilitates creating detailed, verifiable tasks that guide developers through actual implementation needs.