planner_skill
- JavaScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill itou-daiki/easy_stat_edu --skill planner- SKILL.md3.2 KB
Overview
This skill is an expert planning specialist for implementing complex features and refactors. It produces detailed, actionable implementation plans that break work into small, testable steps and surface dependencies, risks, and success criteria. Use it proactively when a clear, low-risk roadmap is needed to guide development and reviews.
How this skill works
I analyze requirements, inspect the current code state, and outline architecture impacts. Plans include file-level changes, step-by-step actions, estimated complexity, and testing strategy. The output prioritizes dependency order, incremental delivery, and explicit mitigations for risks and edge cases.
When to use it
- Introducing a complex new feature that touches multiple modules
- Planning an architectural change or migration that requires phased rollout
- Designing a complex refactor to reduce technical debt without breaking behavior
- Estimating effort and breaking tasks for team planning or sprint work
- Creating a testing and rollout strategy for risky changes
Best practices
- Verify current files and state before writing the plan; reference exact file paths and function names
- Break work into small, verifiable steps with clear dependencies and acceptance criteria
- Prioritize minimal, incremental changes that preserve existing behavior
- Call out edge cases, error flows, and expected null/empty input handling
- Group related changes to reduce context switching and enable focused reviews
Example use cases
- Plan implementing a new payment flow that spans frontend, backend, and billing service
- Design a phased database schema migration with backward-compatible access layers
- Create a stepwise refactor to extract shared utilities from duplicated code
- Outline an incremental API versioning strategy and deprecation timeline
- Map out tests and CI changes needed for introducing feature flags
FAQ
Plans list specific file paths, functions to change, and precise actions. Code snippets are provided on request, but primary output focuses on actionable steps and dependencies.
How are risks and rollbacks handled?
Each risky step includes a risk rating and mitigation. Plans recommend rollback points, feature flags, and incremental testing to limit blast radius.