writing-plans

Name: writing-plans
Availability: InStock
Author: i-onlabs

Convert designs into detailed implementation plans with file paths and tests.

3|1|Updated Dec 21, 2025

Search Tags:#planning #tdd #documentation #implementation #engineering #workflows #task-management

Ready to run

npx skills add https://github.com/I-Onlabs/claude-code-skills --skill writing-plans-i-onlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/I-Onlabs/claude-code-skills/tree/main/writing-plans
Command: npx skills add https://github.com/I-Onlabs/claude-code-skills --skill writing-plans-i-onlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts high-level designs into concrete, task-level plans that engineers can implement without ambiguity, reducing rework and coordination overhead.

Core Features & Use Cases

Generates end-to-end implementation plans with exact file paths, code examples, and verification steps.
Supports zero-context scenarios by documenting dependencies, interfaces, and testing strategies.
Enables consistent, auditable development through standardized plan documents saved under docs/plans.

Quick Start

Ask the planner to create a complete implementation plan for a feature, including file paths, code examples, tests, and verification steps, and save it to docs/plans with a date stamp.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I convert designs into executable implementation plans?▼

Implementation planning for unfamiliar codebases involves documenting dependencies, interfaces, and testing strategies to enable zero-context development. It breaks work into precise steps with exact file touches so engineers can execute without ambiguity.

How do I create a step-by-step implementation plan for a new feature?▼

You create a step-by-step feature implementation plan by generating end-to-end tasks that include file paths, code examples, and verification steps. The standardized plan is then saved to docs/plans with a date stamp for traceable planning.

What is the best way to break development tasks into precise engineering steps?▼

The best way to break development tasks into precise steps is to generate task-level plans with exact file paths and verification tasks. This approach ensures consistent, auditable development through standardized plan documents saved under docs/plans.

Can I generate code-ready plans with testing strategies for an unfamiliar codebase?▼

Yes, you can generate code-ready plans with testing strategies for an unfamiliar codebase. The planning process supports zero-context scenarios by explicitly documenting dependencies, interfaces, and testing strategies alongside implementation steps.

Does this implementation planning approach support TDD workflows?▼

Yes, this implementation planning approach supports TDD workflows by integrating specific testing strategies and verification tasks into the generated plan. It ensures every implementation step has corresponding tests defined before coding begins.