plan-writing

Structure complex work into verifiable tasks with dependency-aware sequencing.

27|5|Updated Apr 3, 2026

Search Tags:#planning #dependencies #verification #plan #task-management #project #root-structure

Ready to run

npx skills add https://github.com/Fandry96/k3-agentic-skills --skill plan-writing-fandry96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/Fandry96/k3-agentic-skills/tree/main/skills/plan-writing
Command: npx skills add https://github.com/Fandry96/k3-agentic-skills --skill plan-writing-fandry96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Writing breaks down complex work into small, verifiable tasks with clear outcomes, reducing ambiguity and scope creep.

Core Features & Use Cases

Small, focused tasks with explicit outcomes that are independently verifiable.
Dependency-aware sequencing that orders tasks and highlights prerequisites.
Verification-first approach ensuring each task has a clear done criteria and measurable results.
Use it for feature work, refactoring, or any multi-step project to maintain momentum and clarity.

Quick Start

Create a concise, task-level plan at the project root with clearly verifiable steps and dependencies, and verify each step before execution.

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?▼

Dependency-aware sequencing orders tasks by prerequisites, ensuring you complete required steps before starting dependent ones. This sequencing maintains momentum by highlighting exactly what must be finished before subsequent work begins.

What is the best way to prevent scope creep during feature development?▼

The best way to prevent scope creep is applying a verification-first approach that enforces clear done criteria and measurable results for each task. Explicitly defining outcomes before execution keeps feature development focused and boundaries clear.

Can I use this for refactoring and multi-step project planning?▼

Yes, you can use this for refactoring and any multi-step project planning scenarios. It applies to feature work by creating a concise, task-level plan at the project root with clearly verifiable steps and dynamic task ordering.

How does dependency-aware sequencing handle task ordering?▼

What are the limitations of managing tasks at the project root?▼

A limitation of managing tasks at the project root is that it requires creating concise, task-level plans rather than high-level overviews. You must define explicit outcomes and verification criteria for each step to maintain clarity and avoid ambiguity.