writing-plans

Generate implementation plans with file structure, tasks, and execution steps.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/tunneleven/C4Flow --skill writing-plans-tunneleven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/tunneleven/C4Flow/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/tunneleven/C4Flow --skill writing-plans-tunneleven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed, step-by-step implementation plans for software development tasks, ensuring clarity and reducing ambiguity for engineers.

Core Features & Use Cases

  • Comprehensive Planning: Generates plans that include file structure, bite-sized tasks, and exact commands for implementation.
  • Contextualization: Assumes engineers have zero context for the codebase, providing all necessary information.
  • Use Case: Before starting a new feature, use this Skill to generate a plan that outlines every file to be modified, the specific code changes, and the testing steps required, ensuring a smooth development process.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user authentication feature.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create a detailed implementation plan for a software development task?

To create a detailed implementation plan, you need a structured breakdown of file modifications, bite-sized commit-ready tasks, and specific execution steps. This approach assumes zero prior context of the codebase, providing engineers with exact commands and testing requirements for smooth execution.

What's the best way to break down a complex feature into actionable development tasks?

The best way to break down a feature is decomposing it into bite-sized, commit-ready tasks that adhere to TDD, DRY, and YAGNI principles. This ensures each task includes specific code changes, file structure modifications, and testing steps, reducing ambiguity for engineers unfamiliar with the domain.

How does TDD integration improve software implementation planning?

TDD integration improves implementation planning by enforcing a test-first methodology within each bite-sized task. It ensures every file modification includes corresponding testing steps, reducing ambiguity and guaranteeing that all generated execution steps follow strict development principles before code is committed.

Can I generate a step-by-step coding plan for engineers unfamiliar with my codebase?

Yes, you can generate a step-by-step coding plan specifically designed for engineers with zero codebase context. The plan provides comprehensive contextualization, including exact commands, file structure changes, and necessary domain information, ensuring smooth development execution without prior familiarity.

When do I need a detailed task breakdown for software implementation?

You need a detailed task breakdown when starting a new feature that requires clear, context-rich instructions for engineers. It is essential when developers are unfamiliar with the codebase or problem domain, ensuring every file modification and testing step is explicitly outlined to reduce ambiguity.