
planning
Universal planning for technical and non-technical projects. Domains: software implementation, business, personal, creative, academic, events. Capabilities: feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment. Actions: plan, architect, design, evaluate, breakdown, structure projects. Keywords: implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs. Use when: planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements.
- Installs
- 43
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/samhvw8/dotfiles --skill planning- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads planning automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Planning
Universal planning methodology for technical implementation and general project planning.
Mode Selection
| Project Type | Mode | Key Focus |
|---|---|---|
| Software/Technical | Implementation | Codebase analysis, architecture, code changes |
| Business/Personal/Creative | Project | Goals, milestones, resources, timeline |
Technical Implementation Planning
Use when: Planning software features, system architecture, technical solutions
Core Principles
Always honor YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
Workflow
-
Research & Analysis →
references/research-phase.md- Skip if: Provided with researcher reports
-
Codebase Understanding →
references/codebase-understanding.md- Skip if: Provided with scout reports
-
Solution Design →
references/solution-design.md -
Plan Organization →
references/plan-organization.md -
Task Breakdown →
references/output-standards.md
Output Structure
plans/
└── YYYYMMDD-HHmm-plan-name/
├── research/
├── reports/
├── scout/
├── plan.md
└── phase-XX-*.md
Requirements
- DO NOT implement code - only create plans
- Self-contained with necessary context
- Include code snippets/pseudocode when clarifying
- Provide options with trade-offs
- Detailed enough for junior developers
Project Planning (Non-Technical)
Use when: Business, personal, creative, academic, event planning
Domains
- Business: Product launches, marketing, process improvements
- Personal: Career development, learning, lifestyle changes
- Creative: Writing, art, content creation
- Academic: Research, thesis, study programs
- Events: Conferences, weddings, community events
Plan Format
Location: docs/plans/PLAN-YYYYMMDD-HHMM-{slug}.md
Frontmatter:
---
plan_id: PLAN-YYYYMMDD-HHMM-{slug}
title: [Project Name]
created: YYYY-MM-DD HH:MM
status: draft | active | completed | on_hold
category: business | personal | creative | academic | event
phase: planning | execution | monitoring | complete
priority: critical | high | medium | low
---
Required Sections
- Vision & Objectives - SMART goals, alignment
- Scope & Deliverables - In/out of scope, acceptance criteria
- Action Steps - Phased tasks with owners, durations
- Resources Required - People, budget, materials, tools
- Timeline & Milestones - Dates, checkpoints, Gantt
- Risks & Contingencies - Mitigation, early warnings
- Success Metrics - Measurable outcomes, completion criteria
Quick Templates
references/business-plan-template.mdreferences/personal-goal-template.mdreferences/generic-plan-template.md
Pre-Planning Protocol
ALWAYS execute before creating new plan:
- Check for active plan:
test -f docs/plan.md && cat docs/plan.md - If exists: Ask user to continue or create new
- If none: Proceed with new plan creation
Quality Standards
Technical Plans
- Consider long-term maintainability
- Address security and performance
- Validate against codebase patterns
- Research thoroughly when uncertain
Project Plans
- All 7 sections present
- Each step has owner and deadline
- Resources are realistic
- Risks have contingencies
- Metrics are SMART
Both Types
- Be thorough and specific
- Simple, understandable structure
- Action-oriented
- Clear next steps
References
Technical Implementation
references/research-phase.md- Research methodologyreferences/codebase-understanding.md- Codebase analysisreferences/solution-design.md- Architecture patternsreferences/plan-organization.md- Plan structurereferences/output-standards.md- Task breakdown standards
Project Templates
references/business-plan-template.mdreferences/personal-goal-template.mdreferences/generic-plan-template.md
Plan quality determines implementation success. Be comprehensive.
FAQ
What does the planning skill do?
Universal planning for technical and non-technical projects. Domains: software implementation, business, personal, creative, academic, events. Capabilities: feature planning, system architecture, goal setting, milestone planning, requirement breakdown, trade-off analysis, resource allocation, risk assessment. Actions: plan, architect, design, evaluate, breakdown, structure projects. Keywords: implementation plan, technical design, architecture, roadmap, project plan, strategy, goal setting, milestones, timeline, action plan, SMART goals, sprint planning, task breakdown, OKRs. Use when: planning features, designing architecture, creating roadmaps, setting goals, organizing projects, breaking down requirements.
How do I install planning?
Run npx skills add https://github.com/samhvw8/dotfiles --skill planning in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/planning/ (personal) or .claude/skills/planning/ (project).
Which AI agents can use planning?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is planning safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains planning?
It is published by samhvw8 in samhvw8/dotfiles. It has 43 recorded installs.
More from samhvw8/dotfiles
code-quality
samhvw8/dotfiles
Review, refactor, and debug code with verification before claiming done. Use when responding to review feedback, requesting a review, refactoring or reducing technical debt, root-causing a bug or failing test, or checking work before a merge, commit, or completion claim.
mise-expert
samhvw8/dotfiles
mise — the tool-version manager, env-var loader, and task runner that replaces asdf, direnv, and make. Use for anything touching mise.toml or .tool-versions: installing or pinning tools, choosing a backend (core, packslip, aqua, github, cargo, npm, pypi/pipx), env vars, tasks, lockfiles, trust prompts, auto-updates, CI setup, migrating from asdf/direnv/make/npm scripts or off ubi, and install failures — including attestation/cosign/SLSA verification errors.
frontend-development
samhvw8/dotfiles
Multi-framework frontend development. Frameworks: React 18+ (Suspense, hooks, TanStack), Vue 3 (Composition API, Pinia, Nuxt), Svelte 5 (Runes, SvelteKit), Angular (Signals, standalone). Common: TypeScript, state management, routing, data fetching, performance optimization, component patterns. Actions: create, build, implement, style, optimize, refactor components/pages/features. Keywords: React, Vue, Svelte, Angular, component, TypeScript, hooks, Composition API, runes, signals, useSuspenseQuery, Pinia, stores, state management, routing, lazy loading, Suspense, performance, bundle size, code splitting, reactivity, props, events. Use when: creating components in any framework, building pages, fetching data, implementing routing, state management, optimizing performance, organizing frontend code, choosing between frameworks.
infra-engineer
samhvw8/dotfiles
Comprehensive infrastructure engineering covering DevOps, cloud platforms, FinOps, and DevSecOps. Platforms: AWS (EC2, Lambda, S3, ECS, EKS, RDS, CloudFormation), Azure basics, Cloudflare (Workers, R2, D1, Pages), GCP (GKE, Cloud Run, Cloud Storage), Docker, Kubernetes. Capabilities: CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins), GitOps, infrastructure as code (Terraform, CloudFormation), container orchestration, cost optimization, security scanning, vulnerability management, secrets management, compliance (SOC2, HIPAA). Actions: deploy, configure, manage, scale, monitor, secure, optimize cloud infrastructure. Keywords: AWS, EC2, Lambda, S3, ECS, EKS, RDS, CloudFormation, Azure, Kubernetes, k8s, Docker, Terraform, CI/CD, GitHub Actions, GitLab CI, Jenkins, ArgoCD, Flux, cost optimization, FinOps, reserved instances, spot instances, security scanning, SAST, DAST, vulnerability management, secrets management, Vault, compliance, monitoring, observability. Use when: deploying to AWS
3d-graphics
samhvw8/dotfiles
3D web graphics with Three.js (WebGL/WebGPU). Capabilities: scenes, cameras, geometries, materials, lights, animations, model loading (GLTF/FBX), PBR materials, shadows, post-processing (bloom, SSAO, SSR), custom shaders, instancing, LOD, physics, VR/XR. Actions: create, build, animate, render 3D scenes/models. Keywords: Three.js, WebGL, WebGPU, 3D graphics, scene, camera, geometry, material, light, animation, GLTF, FBX, OrbitControls, PBR, shadow mapping, post-processing, bloom, SSAO, shader, instancing, LOD, WebXR, VR, AR, product configurator, data visualization, architectural walkthrough, interactive 3D, canvas. Use when: creating 3D visualizations, building WebGL/WebGPU apps, loading 3D models, adding animations, implementing VR/XR, creating interactive graphics, building product configurators.
github-search
samhvw8/dotfiles
Search GitHub with the gh CLI: find repositories, code, and issues/PRs, and see how open-source projects use a library. Use when looking for repos, usage examples, or reported bugs and workarounds on GitHub.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.