plan-writing

Break down complex projects into task-level plans with dependencies and verification criteria.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Arbab1308/BrownlandBL-2 --skill plan-writing-arbab1308
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/Arbab1308/BrownlandBL-2/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/Arbab1308/BrownlandBL-2 --skill plan-writing-arbab1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structuring multi-step work into small, verifiable tasks with clear dependencies and criteria to improve clarity and delivery speed.

Core Features & Use Cases

  • Clear task breakdowns with explicit outcomes
  • Dependency-aware sequencing and risk identification
  • Verification criteria and progress visibility
  • Use cases: feature implementation, refactors, or any multi-step project

Quick Start

Create a plan file at the project root and begin detailing tasks with clear, 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 projects into structured task-level plans?

Breaking down complex projects involves structuring work into small, verifiable tasks with clear dependencies and explicit completion criteria. This approach improves clarity and delivery speed by ensuring each task has measurable milestones and explicit outcomes before moving forward.

What is the best way to sequence project tasks with dependencies for agile planning?

Sequencing tasks with dependencies requires mapping dynamic, project-specific relationships between work items. Dependency-aware sequencing identifies risks early and ensures that prerequisite tasks are completed before downstream work begins, providing clear progress visibility for multi-step projects.

How do I add verification criteria to a multi-step project plan?

Adding verification criteria means defining explicit completion checks for each task within your project plan. This ensures that every task has measurable outcomes and explicit checks, preventing ambiguous progress states and ensuring task-level work is fully verifiable.

Can I use this task planning framework for feature implementation and refactoring work?

Yes, this task planning framework works for feature implementation, refactors, or any multi-step project requiring measurable milestones. It structures work into clear task breakdowns with explicit outcomes, making it suitable for complex software development and agile project management.

Do I need a specific project management tool to use this planning framework?

No specific project management tool is required to use this planning framework. You create a plan file at the project root and begin detailing tasks with clear, verifiable outcomes, making it adaptable to your existing agile workflow and task planning environment.

Why does my multi-step project plan lack clear progress visibility and verifiable outcomes?

Your project plan lacks visibility because it is missing explicit completion checks and dependency-aware sequencing. Structuring work into small, verifiable tasks with clear dependencies and explicit outcomes resolves this by enforcing measurable milestones and dynamic naming for each project step.