skill-writing-plans

Create zero-context implementation plans for multi-step software development tasks.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/burgebj/claudeoctopus --skill skill-writing-plans-burgebj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-writing-plans
Source: https://github.com/burgebj/claudeoctopus/tree/main/.claude/skills/skill-writing-plans
Command: npx skills add https://github.com/burgebj/claudeoctopus --skill skill-writing-plans-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning multi-step feature requirements into detailed implementation plans that engineers can execute without prior codebase context.

Core Features & Use Cases

  • Zero-Context Planning: Creates comprehensive plans with exact files, implementation steps, testing instructions, and verification criteria.
  • TDD-Oriented Task Breakdown: Structures work into small actions with failing tests, implementation steps, validation, and commits.
  • Use Case: When a team needs to implement a complex feature, use this Skill to generate a precise plan that another engineer or agent can follow independently.

Quick Start

Ask the skill to create an implementation plan for the specified feature or requirements.

Frequently Asked Questions about skill-writing-plans

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

FAQPage Schema
How do I create an implementation plan for complex feature development?

To create an implementation plan for feature development, you structure multi-step requirements into zero-context tasks with exact file paths, testing instructions, and verification criteria. This ensures engineers can execute complex features independently without prior codebase knowledge.

What is zero-context planning in software engineering?

Zero-context planning is a process that generates comprehensive implementation steps including exact files, validation checkpoints, and commit guidelines. It allows any engineer or agent to execute multi-step software development tasks independently without needing prior familiarity with the codebase.

How do I break down a refactoring task using TDD?

To break down a refactoring task using TDD, you structure work into small actions starting with failing tests, followed by implementation steps, validation, and commits. This ensures each code modification is verified independently before progressing to the next task.

Can I use task breakdown plans for delegation workflows?

Yes, task breakdown plans are designed for delegation workflows by providing precise execution-ready steps with file paths and verification safeguards. Another engineer or agent can follow these structured plans independently to complete the assigned software engineering tasks.

What's the best way to structure code planning for multi-step tasks?

The best way to structure code planning for multi-step tasks is to sequence them with exact file paths, testing instructions, verification steps, and execution safeguards. This structured task sequencing prevents context loss and ensures reliable implementation across complex engineering scenarios.