skills.rest
AnthonyCongHieu
AnthonyCongHieuCOMMUNITY
Explore all skills by this author →
GitHub

plan-writing

Break complex work into verifiable tasks with dependencies and final verification.

Updated Aug 22, 2025
Search Tags:#planning#verification#task-management#project-management#work-breakdown#planning-templates
One-click install
npx skills add https://github.com/AnthonyCongHieu/voice_tool --skill plan-writing-anthonyconghieu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/AnthonyCongHieu/voice_tool/tree/main/voice_tools_v1/.agent/skills/plan-writing
Command: npx skills add https://github.com/AnthonyCongHieu/voice_tool --skill plan-writing-anthonyconghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan writing helps teams break complex work into small, verifiable tasks with clear dependencies and verification criteria, reducing miscommunication and scope creep.

Core Features & Use Cases

  • Clear task breakdown into actionable steps
  • Verification criteria and dependency ordering
  • Guidelines for project-root planning and naming consistency

Quick Start

Plan and save a new task as a markdown file in the PROJECT ROOT, e.g., create auth-feature.md that captures a specific action and verification.

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 feature development into verifiable tasks?▼

Complex feature development breaks down into small, verifiable tasks with clear dependencies and deterministic checks. Using structured work breakdown templates ensures each actionable step has a specific outcome and final verification criteria.

What is the best way to manage task dependencies for a multi-step refactoring project?▼

Managing task dependencies for a multi-step refactoring project requires ordering tasks sequentially with clear verification criteria. Structured planning enforces dependency ordering and deterministic checks to prevent scope creep and ensure consistent project outcomes.

How do I structure project planning files for consistent work breakdown?▼

Project planning files are structured as markdown files stored directly in the project root directory. Enforcing project-root plan storage with consistent naming captures specific actions and verifications for each task.

Does work breakdown planning work for multi-team projects?▼

Work breakdown planning works for multi-team projects by applying structured task decomposition across teams. Clear dependency ordering and task-specific verification criteria reduce miscommunication and ensure deterministic checks across all units.

Why do I need verification criteria in my task management templates?▼

Verification criteria in task management templates are needed to enforce deterministic checks on task-specific outcomes. Defining these checks during work breakdown reduces scope creep and ensures each actionable step meets its final verification requirements.

Related Skills

Explore More Product & Management Skills→
NeKon69NeKon69
1

user.project_root

Resolve the project root directory by searching upward for marker files.

Community
Basic
roderikroderik
2

subagent-driven-development

Dispatch fresh subagents per task to execute implementation plans with two-stage reviews.

Community
Advanced
liujiarui0918liujiarui0918

using-task-list

Create, track, and update tasks with dependencies and statuses.

Community
Intermediate
OpenCovenOpenCoven
20

beads

Manage project tasks and dependencies using the bd CLI.

Official
Intermediate