skills.rest
FourthWiz
FourthWizCOMMUNITY
Explore all skills by this author →
GitHub

plan

Generate detailed implementation plans with file paths, task sequencing, and testing strategies.

2|1|Updated Mar 18, 2026
Search Tags:#workflow#planning#task-decomposition#implementation-plan#testing-strategy#claude-opus#integration-analysis
One-click install
npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill plan-fourthwiz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/plan
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill plan-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

High-level requirements and vague requests often leave engineers guessing about scope, file locations, testing, and rollback plans. This Skill turns ambiguous or broad development requests into concrete, implementation-ready plans with explicit file paths, task decomposition, acceptance criteria, and risk controls so engineers can work without assumptions.

Core Features & Use Cases

  • Concrete task decomposition: Produces ordered tasks with specific files to create or modify, acceptance criteria, and effort estimates.
  • Integration and risk analysis: Maps integration points, failure modes, backward compatibility, coordination needs, and rollback strategies.
  • Testing & validation: Specifies unit, integration, and E2E test targets and edge cases for each task.
  • Session & artifact management: Reads workflow artifacts and code, appends cost and session state, and saves the current-plan to the task workspace for downstream phases.
  • Use cases: Planning a new feature, refactoring a service, coordinating a migration, or revising a plan after critic feedback.

Quick Start

Create a detailed implementation plan for adding a health-check endpoint to the payments service, including task breakdown, file paths, tests, integration considerations, and rollback steps.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague software requirements into an implementation plan with file paths and tasks?▼

To turn vague requirements into an implementation plan, decompose the request into ordered tasks specifying exact file paths to create or modify, acceptance criteria, and effort estimates. This removes assumptions by mapping concrete file-level changes and task sequencing for engineers.

What is the best way to plan a database migration with rollback strategies and integration analysis?▼

Planning a database migration requires mapping integration points, identifying failure modes, and defining backward compatibility and rollback strategies. Applying this task decomposition ensures coordination needs and risk mitigation are documented before implementation begins.

How do I create a testing strategy matrix for a new feature refactor?▼

Creating a testing strategy matrix involves specifying unit, integration, and end-to-end test targets alongside edge cases for each task. This ensures validation coverage matches the file-level changes and acceptance criteria defined in the implementation plan.

Do I need a strong model like Claude Opus to generate detailed task decomposition for software development?▼

Yes, generating detailed task decomposition for software development requires the strongest model available, such as Claude Opus. Advanced reasoning is necessary to analyze repository context, map integration points, and produce concrete implementation-ready plans.

How should I save workflow artifacts and session state when planning a software development task?▼

To save workflow artifacts and session state during software planning, append cost and session data to existing artifacts, then save the current-plan to the task workspace. This preserves the implementation context for downstream execution phases.

When should I not use an automated implementation plan for software engineering tasks?▼

You should not use an automated implementation plan for simple tasks that do not require concrete task decomposition, integration analysis, or file-level changes. It is designed for complex features, refactors, migrations, and bug fixes requiring detailed risk mitigation.

Related Skills

Explore More Software Engineering Skills→
blake-goodwynblake-goodwyn

interview

Guide structured interviews to surface non-obvious requirements and refine specs.

Community
Basic
cpp-for-everythingcpp-for-everything
1

writing-plans

Generate implementation plans with tasks, file mappings, and acceptance criteria.

Official
Intermediate
royhenengelroyhenengel

failure-backwards

Identify failure modes and generate avoidance strategies for a goal.

Community
Basic
YH-05YH-05
1

issue-creation

Create GitHub Issues from natural language and synchronize project files.

Community
Advanced