plan-writing

Organize complex work into structured, verifiable tasks with plan files.

132|22|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill plan-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/xenitV1/Antigravity-Workflows/tree/main/skills/plan-writing
Command: npx skills add https://github.com/xenitV1/Antigravity-Workflows --skill plan-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-writing organizes complex work into structured, verifiable tasks.

Core Features & Use Cases

  • Breaks work into small, independently verifiable tasks with explicit outcomes.
  • Defines dependencies and optimal ordering to reveal the critical path.
  • Works for feature development, refactoring, bug fixes, and other multi-step initiatives across teams.
  • Produces project-root plan files (e.g., {task-slug}.md) that document actions and verification steps.

Quick Start

Create a new plan at the project root by saving a file named {task-slug}.md. Each task entry should specify a concrete action and a verifiable outcome. Limit plans to 5-10 tasks and include a final "Done When" section to indicate completion.

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

Plan-writing organizes complex work into structured, verifiable tasks by creating a plan file at your project root with 5-10 independent tasks, each specifying a concrete action and verifiable outcome. Define dependencies, task order, and a final 'Done When' criterion so you can validate completion and track the critical path.

Can I use task planning for feature development, refactoring, and bug fixes?

Yes. Plan-writing works across feature development, refactoring, bug fixes, and multi-step initiatives. Each task entry specifies an action and outcome; dependencies reveal optimal ordering. Save plans as {task-slug}.md files at your project root so your team can reference and verify work independently.

What's the best way to document dependencies and task ordering in a project plan?

Plan-writing structures dependencies explicitly within each task entry and uses clear ordering to expose the critical path. This lets teams understand which tasks block others, prioritize work, and execute tasks in parallel where possible while maintaining visibility into the complete project flow.

How do I know when a planned task is actually complete?

Plan-writing requires a final 'Done When' section in each plan file that defines the verifiable completion criterion for that task. This makes task outcomes explicit and lets you and your team confirm completion against a concrete standard rather than subjective judgment.

Do I need special tools or setup to start writing project plans?

No. Plan-writing requires only a text editor and your project root directory. Create a markdown file named {task-slug}.md, list 5-10 tasks with actions and outcomes, define dependencies, and add a 'Done When' section. No additional dependencies or components are required.