skill-writing-plans

Creates zero-context implementation plans with bite-sized TDD tasks for multi-step features.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-writing-plans-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-writing-plans
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/skill-writing-plans
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-writing-plans-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step feature work often fails because plans are vague, tasks are too large, and engineers lack context about the codebase. This Skill produces implementation plans detailed enough that an engineer with zero context can execute them without assumptions. ## Core Features & Use Cases - Zero-Context Plan Format: Every task specifies exact file paths, complete code, exact commands, and expected output. - Bite-Sized Task Granularity: Each task is a single 2-5 minute action following a TDD cycle of failing test, minimal implementation, verification, and commit. - Octopus Integration: Plans can be executed sequentially, parallelized via orchestrate.sh tangle, or run through the full embrace workflow, with session-aware plan storage. - Use Case: Given a spec for user authentication, produce a plan where each task shows the exact test file, the failing test code, the implementation code, the test command with expected output, and the git commit message. ## Quick Start Ask the AI to create a zero-context implementation plan for your multi-step feature before writing any code.

Frequently Asked Questions about skill-writing-plans

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

FAQPage Schema
How do I write an implementation plan for a multi-step feature?▼

Break the feature into single-action tasks of 2-5 minutes each. For every task, specify exact file paths, write the failing test first, show the minimal implementation code, give the exact test command with expected output, and end with a commit step.

What is a zero-context implementation plan?▼

A zero-context plan assumes the executing engineer knows nothing about the codebase. It documents every file to touch, complete code snippets, exact commands, and verification steps so no assumptions or outside knowledge are required.

When should I create an implementation plan versus coding directly?▼

Create a plan for multi-step features with 3 or more tasks, complex refactoring, uncertain scope, or delegation to a subagent. Skip planning for single-task bug fixes or simple config changes.

How does test-driven development fit into implementation planning?▼

Each task follows a TDD cycle: write the failing test, run it to confirm failure, implement minimal code to pass, run the test to verify success, then commit. This keeps every step verifiable.

Can implementation plans be executed in parallel?▼

Yes. After creating a plan, independent tasks can be parallelized using the orchestrate.sh tangle command, or the full research-to-delivery workflow can run via orchestrate.sh embrace.