skills.rest
PedroGiudice
PedroGiudiceCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generate implementation plans with exact file paths, code examples, tests, and verification steps.

5|3|Updated Nov 4, 2025
Search Tags:#planning#documentation#execution#engineering#tasks#plan
One-click install
npx skills add https://github.com/PedroGiudice/Claude-Code-Projetos --skill writing-plans-pedrogiudice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/PedroGiudice/Claude-Code-Projetos/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/PedroGiudice/Claude-Code-Projetos --skill writing-plans-pedrogiudice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates comprehensive implementation plans that assume engineers have no context about the codebase, providing exact file paths, code examples, tests, and verification steps.

Core Features & Use Cases

  • Bite-sized plan steps: each task is 2-5 minutes.
  • Comprehensive coverage: file touch points, code, docs, and tests.
  • Save and handoff: plans saved to docs/plans with date-based naming.

Quick Start

Plan structure starts with a header and is saved to: docs/plans/YYYY-MM-DD-<feature-name>.md

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 engineers who don't know the codebase?▼

Implementation plans generated by this Skill provide comprehensive step-by-step guidance with exact file paths, code examples, tests, and verification steps—designed for engineers starting with zero context about your project structure.

What should be included in an engineering implementation plan?▼

Effective implementation plans cover all file touch points, inline code examples, documentation updates, test cases, and verification steps. This Skill structures each task as bite-sized steps completable in 2–5 minutes for faster execution and handoff.

Where are implementation plans saved and how are they organized?▼

Plans are saved to docs/plans/ with date-based naming (YYYY-MM-DD-<feature-name>.md), making them easy to archive, reference, and hand off to team members without requiring context briefings.

Can I use implementation plans for onboarding new engineers to a project?▼

Yes. Since plans assume zero codebase context and include exact file paths and code examples, they serve as effective onboarding documents that reduce ramp-up time and enable self-service learning.

How do I ensure implementation plans cover all necessary components?▼

This Skill generates comprehensive coverage by including file paths, code modifications, documentation, and test cases in each plan. The structured format ensures nothing is missed when executing or handing off work.

What's the best way to document engineering tasks for team execution?▼

Implementation plans break down work into detailed, self-contained steps with code examples and verification criteria. This approach eliminates back-and-forth questions and enables parallel task execution across distributed teams.

Related Skills

Explore More Product & Management Skills→
SwiftyJunnosSwiftyJunnos

prompt-enhancer

Analyze project context to generate structured requirement documents for development requests.

Community
Intermediate
sensei-hackersensei-hacker
4

finish-task

Generate commits, pull requests, and completion reports for finished code tasks.

Community
Intermediate
Vortex4047Vortex4047

code-documentation-doc-generate

Generate documentation plans and artifacts from code, configs, and comments.

Community
Advanced
heximaoheximao

plan

Create detailed step-by-step implementation plans with documentation and verification steps.

Community
Advanced