writing-plans

Generate implementation plans with exact file paths, code samples, and tests.

Updated Aug 27, 2026
Ready to run
npx skills add https://github.com/chriscarterux/chris-claude-stack --skill writing-plans-chriscarterux
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/chriscarterux/chris-claude-stack/tree/main/skills/writing-plans
Command: npx skills add https://github.com/chriscarterux/chris-claude-stack --skill writing-plans-chriscarterux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the knowledge gap between design completion and implementation by creating detailed, step-by-step engineering plans that require zero codebase context from developers.

Core Features & Use Cases

  • Zero-Context Implementation: Generate comprehensive plans assuming engineers have minimal domain knowledge of your codebase.
  • Bite-Sized Task Breakdown: Create granular 2-5 minute tasks with exact file paths, complete code examples, and verification steps.
  • Use Case: After finalizing a new authentication feature design, use this Skill to produce a complete implementation guide that any engineer can follow, including exact test cases, file modifications, and commit commands.

Quick Start

Use the writing-plans skill to create an implementation plan for adding user profile management to our application.

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 from a design?▼

An implementation plan translates completed designs into executable tasks by breaking work into granular steps with exact file paths, code samples, and verification procedures. This Skill generates comprehensive guides assuming engineers have minimal codebase context, enabling any team member to execute the work independently.

What should an implementation plan include for developers new to the codebase?▼

A complete implementation plan specifies exact file paths, provides runnable code examples, defines test suites with verification steps, and outlines review and deployment considerations. It eliminates knowledge gaps by removing assumptions about domain familiarity.

When do I need to move from design to a step-by-step implementation plan?▼

Use implementation planning after finalizing a design and before handing work to engineers. This stage bridges design intent and executable code, particularly valuable when team members lack context about specific features, architectures, or codebase conventions.

Can I break a large feature into bite-sized implementation tasks?▼

Yes. Implementation plans decompose features into granular 2-5 minute tasks, each with precise file modifications, complete code samples, and verification checkpoints. This structure lets engineers complete work in focused increments without context-switching.

How does a detailed implementation plan reduce onboarding friction?▼

By embedding exact file paths, runnable examples, and test definitions directly in task descriptions, implementation plans eliminate the need for new engineers to reverse-engineer intent or ask clarifying questions. Knowledge becomes self-contained in each task.