plan-writing

Name: plan-writing
Availability: InStock
Author: marablemarcel

Convert ambiguous work into structured plans with verifiable tasks and outcomes.

Updated Jan 6, 2026

Search Tags:#workflow #planning #verification #task-management #project-management #product-management #plan-writing

Ready to run

npx skills add https://github.com/marablemarcel/Living-Lytics --skill plan-writing-marablemarcel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/marablemarcel/Living-Lytics/tree/main/living-lytics/.agent/skills/plan-writing
Command: npx skills add https://github.com/marablemarcel/Living-Lytics --skill plan-writing-marablemarcel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-writing addresses the challenge of turning vague, multi-step work into clear, actionable tasks with measurable outcomes, reducing miscommunication and delays.

Core Features & Use Cases

Task breakdown: decompose complex work into small, independently verifiable tasks with explicit outcomes.
Dependency-aware planning: order tasks to reveal critical path and enable parallel work where possible.
Verification-driven: each task includes a concrete verification criteria to ensure quality and progress.

Quick Start

Create a concise plan at the project root listing 5-7 tasks with verifiable outcomes and a final "Done When" criterion, saved as a {task-slug}.md file.

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 ambiguous software development work into verifiable tasks?▼

To break down ambiguous work into verifiable tasks, create a plan file at your project root listing 5-7 ordered tasks with explicit outcomes and a final Done When criterion. This simple structure reduces miscommunication by ensuring each task has measurable verification criteria.

What is verification-driven project planning?▼

Verification-driven planning is a task management approach where each decomposed task includes concrete verification criteria to ensure quality and track progress. It converts vague multi-step workflows into independently verifiable actions with explicit outcomes.

Can I use a structured plan for both feature development and code refactors?▼

Yes, you can use a structured plan for feature development, refactors, and bug fixes across software projects of varying sizes. The plan structure applies dependency-aware ordering to reveal critical paths and enable parallel work for any multi-step workflow.

How do I start writing a project plan with clear task dependencies?▼

Start writing a project plan by creating a concise markdown file at the project root. Save it as a task-slug.md file listing 5-7 tasks ordered by dependency, including project-specific assets when present, to reveal the critical path and enable parallel work.

What is the best way to structure a plan for multi-step software workflows?▼

The best way to structure a plan for multi-step workflows is to enforce a simple format with a Goal, verifiable Tasks, and a Done When section. This structure decomposes complex work into small, independently verifiable tasks with explicit outcomes.

Do I need external project management tools to track verifiable tasks?▼

You do not need external project management tools to track verifiable tasks. You can write a concise plan directly at the project root as a markdown file, utilizing dependency-aware ordering to manage progress without additional software requirements.