plan-writing

Name: plan-writing
Availability: InStock
Author: Nishchay

Structure work into actionable task plans with explicit verification criteria.

Updated Feb 2, 2026

Search Tags:#planning #refactoring #bug fixing #verification #task decomposition #dependency mapping

Ready to run

npx skills add https://github.com/nishchaydev/emitra --skill plan-writing-nishchaydev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/nishchaydev/emitra/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/nishchaydev/emitra --skill plan-writing-nishchaydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague work into a clear, dependency-aware plan with explicit verification so tasks finish correctly the first time.

Core Features & Use Cases

Small, focused tasks: Keeps each step independently verifiable (typically 2–5 minutes).
Clear verification criteria: Defines exactly how to confirm each task is done and what “expected output” looks like.
Logical ordering with verification last: Identifies dependencies, highlights critical path, and ensures Phase X: verification happens at the end.
Dynamic plan naming: Saves plans as {task-slug}.md in the project root with safe naming rules (no docs/temp/.claude placement).

Quick Start

Provide the task you want to execute (feature, refactor, or bug fix) and ask the AI to produce a short plan with tasks that each include a one-line “→ Verify:” criterion and a final “Done When” checklist.

Frequently Asked Questions about plan-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break a complex software refactoring task into verifiable steps?▼

Task decomposition breaks refactoring work into independently verifiable steps, typically 2–5 minutes each, with explicit dependency mapping and a final verification phase to ensure correctness.

What is the best way to create a dependency-aware plan for fixing complex bugs?▼

A dependency-aware plan for bug fixing identifies critical paths and orders tasks logically, ensuring that each step includes a one-line verification criterion and a final checklist to confirm completion.

How do I structure feature implementation plans with explicit verification criteria?▼

Feature implementation plans structure work by defining actionable tasks with specific expected outputs, sequencing them based on dependencies, and applying deterministic verification last to reduce ambiguity.

Where should task plan files be saved in a project directory?▼

Task plan files should be saved directly in the project root using a safe dynamic naming convention like {task-slug}.md, avoiding placement in docs, temp, or .claude directories.

Does task decomposition work for short, specific project-aware tasks?▼

Task decomposition suits short, specific project-aware tasks by keeping each step independently verifiable and ensuring the final phase strictly applies deterministic verification before completion.