plan-writing

Create implementation plans from feature specifications with steps, risks, and dependencies.

Updated Aug 27, 2026

Search Tags:#risk-management #dependency-mapping #spec-to-plan #plan-writing #feature-planning #implementation-plans

Ready to run

npx skills add https://github.com/pjordan/claude-toolkit --skill plan-writing-pjordan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/pjordan/claude-toolkit/tree/main/skills/examples/plan-writing
Command: npx skills add https://github.com/pjordan/claude-toolkit --skill plan-writing-pjordan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform ambiguous specifications into precise, actionable implementation plans, reducing ambiguity and aligning stakeholders.

Core Features & Use Cases

Atomic, testable steps: break work into small, independent tasks.
Risk and dependency mapping: surface risks, dependencies, and plan sequencing.
Checkpoints and traceability: define milestones tied back to requirements and acceptance criteria.
Use Case: Given a feature spec, generate a plan with tasks, owners, and success criteria.

Quick Start

Provide a feature specification or scope, then ask the skill to generate a detailed implementation plan outlining steps, risks, dependencies, and acceptance criteria.

Frequently Asked Questions about plan-writing

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

FAQPage Schema

How do I turn feature specifications into actionable implementation plans?▼

To turn feature specifications into implementation plans, provide the feature spec to generate a detailed breakdown of atomic steps, risks, dependencies, and acceptance criteria. This reduces ambiguity by decomposing work into testable tasks and mapping dependencies.

What is the best way to map dependencies and risks when planning a software migration?▼

Mapping dependencies and risks during migration planning involves sequencing tasks and surfacing potential blockers. The generated implementation plan enforces dependency mapping and risk identification to align stakeholders and ensure smooth coordination across components.

How do I break down a large refactor into atomic, testable steps?▼

Breaking down a large refactor into atomic, testable steps requires decomposing the scope into small, independent tasks. The plan enforces step decomposition, defines milestones tied to acceptance criteria, and establishes checkpoints to trace progress back to requirements.

Can I generate rollback strategies and checkpoints for feature planning?▼

Yes, generating rollback strategies and checkpoints is supported during feature planning. The plan defines specific milestones for validation and includes rollback strategies to mitigate risks, ensuring traceability back to the original requirements.

Does implementation planning work for coordinating work across multiple components?▼

Implementation planning works for coordinating work across multiple components by mapping dependencies and sequencing tasks. It aligns stakeholders by providing a structured breakdown of work, owners, success criteria, and traceability to requirements.