skills.rest
dsonyy
dsonyyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-creating

Create detailed implementation plans through interactive codebase research and iterative refinement.

Updated Mar 28, 2026
Search Tags:#planning#software design#task breakdown#implementation plan#technical specification#codebase research#verification criteria
One-click install
npx skills add https://github.com/dsonyy/dotfiles --skill plan-creating-dsonyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-creating
Source: https://github.com/dsonyy/dotfiles/tree/main/skills/plan-creating
Command: npx skills add https://github.com/dsonyy/dotfiles --skill plan-creating-dsonyy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans without understanding the actual codebase leads to vague specs, missed edge cases, and scope creep. This Skill guides an AI through a structured, research-driven planning process that grounds every decision in real code before writing anything down. ## Core Features & Use Cases - Codebase-Grounded Research: Spawns parallel research agents (codebase-locator, codebase-analyzer, codebase-pattern-finder) to find relevant files, trace data flow, and return file:line references before planning begins. - Iterative Plan Development: Builds plans in stages—context gathering, research, outline approval, detailed writing, and review—so users can course-correct at each step. - Structured Plan Template: Produces plans with phases, specific file changes, code snippets, and success criteria split into automated verification (test commands, type checks) and manual verification (UI checks, edge cases). - Use Case: A developer receives a ticket to add session management to an API. The Skill reads the ticket and related code, researches existing auth patterns, presents design options, then writes a phased plan with exact files to modify and commands to verify each phase. ## Quick Start Ask the AI to create an implementation plan for your ticket or feature description, providing any relevant file paths or issue references.

Frequently Asked Questions about plan-creating

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

FAQPage Schema
How do I create an implementation plan from a ticket?▼

Provide the ticket description or file path, and the process reads all referenced files fully, then spawns research agents to locate relevant code and analyze current implementation. It presents findings and questions before drafting a phased plan with specific file changes.

What should a good software implementation plan include?▼

A solid plan includes current state analysis, desired end state, explicit out-of-scope items, phased changes with exact file paths and code snippets, and success criteria split into automated verification (test and lint commands) and manual verification steps.

How does codebase research improve implementation planning?▼

Research agents find relevant source files, trace data flow, and identify existing patterns with file:line references before planning starts. This prevents plans based on wrong assumptions and surfaces constraints and edge cases early.

Can the plan include unresolved open questions?▼

No. The process explicitly forbids finalizing a plan with open questions. When uncertainties arise, planning stops so the question can be researched or clarified with the user, ensuring the final plan is complete and actionable.

When should I not use a detailed implementation plan?▼

Skip detailed planning for trivial changes like typo fixes, single-line edits, or well-understood repetitive tasks. The multi-step research and review process is designed for features, refactors, and database changes where mistakes are costly.

Related Skills

Explore More Software Engineering Skills→
unblockedunblocked
13

headless-enrich-ticket

Gather context and attach structured enrichment documents to issue tracker tickets.

Official
Advanced
corticalstackcorticalstack
1

implement-plan

Executes phased implementation plans from flow/plans with verification pauses between phases.

Community
Intermediate
docs-plusdocs-plus
88

grill-with-docs

Validates project plans against CONTEXT.md glossaries and ADRs to catch terminology mismatches.

Official
Intermediate
dhaneshdhanesh
8

manifold-m-quick

Automate lightweight three-phase code change workflows for bug fixes and small features.

Community
Intermediate