skills.rest
Ewallyw
EwallywCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Develop detailed implementation plans for multi-step engineering tasks.

Updated May 31, 2026
Search Tags:#code review#task decomposition#document structure#step-by-step guide#plan creation
One-click install
npx skills add https://github.com/Ewallyw/claude-config-public --skill writing-plans-ewallyw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Ewallyw/claude-config-public/tree/main/claude-config-master/claude-config-master/skills/writing-plans
Command: npx skills add https://github.com/Ewallyw/claude-config-public --skill writing-plans-ewallyw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The writing-plans skill addresses the challenge of creating detailed implementation plans for multi-step tasks, providing a comprehensive guide for engineers with zero context about the codebase or toolset.

Core Features & Use Cases

  • Task Decomposition: Breaks down complex tasks into manageable, bite-sized steps.
  • Documentation Guidance: Outlines how to document the process, including file modifications, testing, and documentation.
  • Execution Options: Allows for plan execution via subagents or inline execution with checkpoints.

Quick Start

Run the writing-plans skill to start creating a plan for your task, ensuring you have a clear path for implementation and code review.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a multi-step software engineering task into an actionable implementation plan?▼

To create an implementation plan for a multi-step task, you decompose complex objectives into bite-sized, manageable steps. This process guides engineers through task decomposition, ensuring a clear path for execution and code review.

What is the best way to document code modifications and testing for a project with no prior context?▼

Documenting code modifications and testing requires outlining the process within a detailed implementation plan. This approach provides documentation guidance for file modifications and testing, ensuring clarity for engineers with zero codebase context.

Can I execute a step-by-step task plan using subagents instead of inline execution?▼

Yes, you can execute a step-by-step task plan using subagents or inline execution with checkpoints. These execution options allow flexibility when guiding engineers through the implementation process and code review.

Does this task decomposition approach require prior knowledge of my existing codebase or toolset?▼

No, this task decomposition approach does not require prior knowledge of your codebase or toolset. It is ideal for projects requiring step-by-step guidance for engineers with zero context about the development environment.

What are the limitations of using a step-by-step guide for complex task decomposition?▼

A limitation of using a step-by-step guide for task decomposition is that it focuses on providing implementation plans rather than directly modifying code. It outlines execution paths and documentation but requires separate execution.

Related Skills

Explore More Software Engineering Skills→
mouseqiao85mouseqiao85
1

writing-plans

Generate detailed implementation plans for complex multi-step tasks.

Community
Intermediate
cinjoffcinjoff
1

writing-plans

Generate step-by-step implementation plans for software development tasks.

Community
Advanced
hlhr202hlhr202
51

conductor-review

Automate code reviews against project guidelines, design specs, and test suites.

Community
Advanced
hwj123hwjhwj123hwj
4

wizard

Guide users through interactive bash procedures with configurable stages.

Community
Intermediate