Create self-contained technical solution plans with phases, tasks, and acceptance criteria.
npx skills add https://github.com/tntdev21/3d --skill planning-tntdev21
Please help me install this Agent Skill. Skill: planning Source: https://github.com/tntdev21/3d/tree/main/.claude/skills/planning Command: npx skills add https://github.com/tntdev21/3d --skill planning-tntdev21
Manual planning of technical solutions is time-consuming and error-prone. This Skill provides a structured approach to research, codebase understanding, solution design, and plan creation, enabling clear, actionable roadmaps that reduce risk and save time.
Use the planning skill to generate a complete plan for a new feature, then save it under the plans/ directory with a timestamped folder. Provide the plan path and a concise summary.
High-intent search queries and answers about installing and using this skill.
Create a technical solution plan by researching requirements, analyzing your codebase architecture, designing a scalable and secure approach, then producing a self-contained plan document with phases, tasks, dependencies, and acceptance criteria organized in a timestamped `plans/` directory.
A solid technical plan enforces YAGNI, KISS, and DRY principles while addressing security, scalability, and maintainability. Structure it with clear milestones, task dependencies, acceptance criteria, and trade-off analysis to reduce implementation risk.
Yes. The planning process applies to feature planning, system architecture, trade-off analysis, and roadmap creation across diverse codebases. It synthesizes research, design, and documentation to support architecture decisions with documented reasoning.
Analyze your existing architecture and patterns first to understand current design choices. This codebase understanding ensures your plan integrates safely, maintains consistency, and leverages proven patterns already in place.
Planning reduces time and risk by structuring research, design, and documentation upfront. It produces actionable roadmaps with clear dependencies and milestones, catching issues before implementation and aligning teams on scope and trade-offs.
You need sufficient codebase understanding to identify relevant patterns and integration points, but the planning process includes research and analysis steps. Start by studying key architectural layers and components related to your feature scope.
sheng-jieOrganize web research and synthesize findings into a cited report.
claudcherejiGather requirements, model processes, and analyze data for business decisions.
rikdcConverts design documents into technical specifications with data models and API contracts.
darthlinuxerTranslate Agile backlog items into budgets and schedules with Gantt charts.
