writing-plans

Write implementation plans with bite-sized tasks, exact file paths, and complete code.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill writing-plans-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tapway/shogun-os/tree/main/skills/general/writing-plans
Command: npx skills add https://github.com/tapway/shogun-os --skill writing-plans-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Multi-step features often get implemented without a clear plan, leading to vague tasks, missing context, and inconsistent code. This Skill produces detailed implementation plans that assume the implementer has zero context for the codebase, so execution becomes obvious rather than guesswork. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute tasks, each with exact file paths, complete copy-pasteable code, and verification commands. - TDD-First Structure: Every coding task follows the full test-driven cycle: write failing test, verify failure, implement minimal code, verify pass, commit. - Execution Handoff: Saved plans integrate with subagent-driven-development for task-by-task delegation with two-stage review. - Use Case: Before building a new API endpoint, generate a plan that lists each file to create or modify, the complete code for each step, the exact pytest commands to run, and the expected output, then hand it to a subagent for execution. ## Quick Start Ask the agent to write an implementation plan for your feature after completing a brainstorming phase, and it will produce a task-by-task plan saved to docs/plans/.

Frequently Asked Questions about 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 tasks of 2-5 minutes each, with exact file paths, complete copy-pasteable code, and exact test commands with expected output. Start each coding task with a failing test, then implement the minimal code to pass it, and commit after every task.

What is the right task granularity for an implementation plan?

Each task should be 2-5 minutes of focused work covering one action, such as writing a failing test or adding a single model field. Avoid broad tasks like 'build authentication system'; split them into single-file, single-purpose steps.

Can I write an implementation plan without brainstorming first?

No. The workflow is a three-phase chain: brainstorm, plan, then execute. Writing a plan without clarifying user intent and constraints first produces plans built on wrong assumptions.

When should I not use a detailed implementation plan?

Skip it for single-line fixes, typos, and trivial tasks that are already fully understood. The plan is designed for multi-step features, complex requirements, and work delegated to subagents or junior developers.

How does the plan hand off to subagent execution?

After saving the plan to docs/plans/, execution uses subagent-driven-development: a fresh subagent is dispatched per task with full context, followed by a spec compliance review and a code quality review before proceeding.