skills.rest
BenWork17
BenWork17COMMUNITY
Explore all skills by this author →
GitHub

plan-writing

Structure work into actionable tasks with verification criteria and project-root plan artifacts.

Updated Jan 12, 2026
Search Tags:#productivity#verification#task-management#project-planning#software-engineering#plan-writing
One-click install
npx skills add https://github.com/BenWork17/VeXeViet --skill plan-writing-benwork17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/BenWork17/VeXeViet/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/BenWork17/VeXeViet --skill plan-writing-benwork17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Writing provides a framework to break down work into clear, actionable tasks with dependencies and verification criteria, enabling consistent planning and execution across projects.

Core Features & Use Cases

  • Small, focused tasks that are independently verifiable
  • Clear verification criteria and logical task ordering
  • Dynamic, project-root naming for plans and guidance on task structure
  • Principles for handling new projects, feature additions, and bug fixes

Quick Start

Create a new plan in the project root with a unique task slug and outline 5 actionable tasks with verifiable outcomes.

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 software engineering work into actionable tasks?▼

Plan-writing breaks down complex software engineering work into small, focused tasks with clear dependencies and verification criteria. This framework ensures consistent planning and execution across feature development, refactors, and multi-step projects.

What's the best way to define verification criteria for a project planning task?▼

Define verification criteria by outlining actionable tasks with independently verifiable outcomes. Plan-writing requires project-specific planning steps to ensure each task has concise, unique verification criteria before execution.

Do I need to store plan artifacts at the project root for feature development?▼

Yes, you should store plan artifacts at the project root. Plan-writing uses dynamic, project-root naming with a unique task slug to ensure concise, unique plans are organized effectively for feature development and bug fixes.

Can I use this plan-writing approach for both refactoring and bug fixes?▼

Yes, plan-writing applies to refactoring and bug fixes. It provides structured principles for handling new projects, feature additions, and bug fixes by creating tasks with logical ordering and clear verification criteria.

How many actionable tasks should a plan include to ensure clear execution?▼

A plan should outline 5 actionable tasks to ensure clear execution. Plan-writing guides you to outline tasks with verifiable outcomes, maintaining a focused and independently verifiable structure for your project planning artifacts.

Related Skills

Explore More Software Engineering Skills→
suriyelsuriyel
178

long-task-init

Scaffold project artifacts and decompose SRS requirements into verifiable features.

Community
Advanced
airclearairclear
2

conductor-implement

Execute Conductor track plan tasks sequentially and update documentation.

Community
Advanced
Luney-IndustriesLuney-Industries
4

plan-task

Fetch Jira or Linear tickets and create implementation plans with security checks.

Official
Advanced
simoabidsimoabid
1

plan-writing

Break down work into small, verifiable steps with dependencies and verification criteria.

Community
Intermediate