skills.rest
Pieter-1337
Pieter-1337COMMUNITY
Explore all skills by this author →
GitHub

plan

Generates structured implementation plans for software engineering tasks through collaborative codebase research.

Updated May 7, 2026
Search Tags:#planning#software engineering#refactoring#feature development#implementation plan#plan.md#codebase research
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill plan-pieter-1337
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/tsz-plan
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill plan-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code without a plan leads to wrong assumptions, missed edge cases, and wasted implementation effort. This Skill produces a thorough, ready-to-execute plan for features, bug fixes, and refactors before any code is written. ## Core Features & Use Cases - Codebase Research: Explores relevant files, patterns, and integration points so the plan is anchored in the actual code rather than assumptions. - Structured Plan Drafting: Produces a plan with goal, file-level changes, numbered actionable steps, tests, edge cases, and assumptions. - Collaborative Review: Iterates with the user on open decisions and vague steps, then saves the confirmed result to PLAN.md. - Use Case: Before adding a new authentication flow, use this Skill to map the existing middleware, draft step-by-step changes with exact file paths, and confirm the approach before implementing. ## Quick Start Ask the AI to help you plan a feature or refactor before implementing it, for example by saying "let's plan how to add token refresh to the auth module".

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan a software feature before writing code?▼

Start by clarifying the desired end state and constraints, then research the codebase to find affected files and integration points. Draft a structured plan with specific steps, tests, and edge cases, and review it with stakeholders before implementing.

What should a software implementation plan include?▼

A solid plan includes a one-sentence goal, the files to create or modify with full paths, numbered actionable steps, tests to write, edge cases to handle, and assumptions to confirm. Each step should be specific enough to execute without further clarification.

When should I plan instead of coding directly?▼

Plan first when a task is complex, touches multiple files or integration points, or when jumping straight to implementation would be risky. Simple, well-understood changes can often skip formal planning.

Where is the finished plan saved?▼

The plan is saved as a Markdown file, defaulting to PLAN.md in the project root, though you can choose a different location. It follows a fixed structure covering goal, context, files, steps, tests, edge cases, and assumptions.

What are the limitations of plan-first development?▼

Plans based on incomplete codebase research can contain wrong assumptions, so the research step is essential. Very small or exploratory tasks may not benefit from a full planning cycle and can be implemented directly.

Related Skills

Explore More Software Engineering Skills→
lllyyslllyys
27

triage

Categorize software issues into bugs, features, duplicates, and needs-info.

Community
Advanced
totvstotvs
115

writing-plans

Translate software specifications into step-by-step implementation plans with testing and commit guidance.

Official
Intermediate
imvanzenimvanzen

technical-context-discovery

Inspect repository rules and analyze codebase patterns before code changes.

Community
Advanced
Araara7Araara7

spike

Build throwaway prototypes to validate technical feasibility before committing to a real build.

Community
Intermediate