writing-plans

Generate multi-step implementation plans with exact file paths and code examples.

1.4k|129|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/shiwenwen/hope-agent --skill writing-plans-shiwenwen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/shiwenwen/hope-agent/tree/main/skills/writing-plans
Command: npx skills add https://github.com/shiwenwen/hope-agent --skill writing-plans-shiwenwen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing a good implementation plan is hard, especially when you must safely break down requirements into executable steps with exact file paths and complete code examples.

Core Features & Use Cases

  • Multi-step implementation planning: Produces comprehensive, bite-sized tasks that make execution straightforward from minimal prior context.
  • File-accurate, copy-paste-ready outputs: Specifies exact files to create/modify and includes complete code examples, verification commands, and expected results.
  • TDD + frequent commits workflow: Enforces a test-driven cycle per task (fail, verify, implement minimally, verify pass) and encourages incremental commits to reduce risk.

Use case: You’re handed a feature request like “add OAuth login,” but you don’t know the codebase layout—generate a step-by-step plan that guides you through tests, the smallest working implementation, and how to verify it.

Quick Start

Ask: “Use the writing-plans skill to produce an implementation plan for [feature] with exact file paths, complete code examples, and TDD steps for each task.”

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan with exact file paths and TDD steps?

To generate an implementation plan with exact file paths and TDD steps, provide your feature requirements to prompt a multi-step workflow. This produces a structured document containing copy-paste-ready code examples, verification commands, and bite-sized test-driven tasks.

What is the best way to turn ambiguous requirements into executable code plans?

Turning ambiguous requirements into executable code plans involves breaking down the feature request into deterministic, multi-step work. This process outputs exact file modifications, complete code examples, and expected test outcomes to guide straightforward execution.

How does test-driven development planning work for new features?

Test-driven development planning for new features enforces a cycle of writing failing tests, verifying the failure, implementing minimal code, and verifying the pass. This approach structures each task incrementally to reduce risk and encourage frequent commits.

Can I use implementation planning for delegating execution to subagents?

Yes, you can use implementation planning for delegating execution to subagents. The plan generates a deterministic document structure aligned to an execution handoff process, ensuring subagents receive exact file paths and complete code examples for safe write operations.

Do I need prior codebase context to create a multi-step implementation plan?

You do not need prior codebase context to create a multi-step implementation plan. The planning process navigates the repository to produce comprehensive, bite-sized tasks that make execution straightforward from minimal initial context.

What are the limitations of using Plan Mode for implementation planning?

A limitation of using Plan Mode for implementation planning is the gating for write safety, which restricts direct modifications during generation. This means the output is a structured plan document rather than direct, automated code commits to your repository.