What problem does it solve?
This Skill turns ambiguous or under-scoped engineering requests into a measurable, verifiable implementation plan before any code is written so teams avoid scope creep, unexpected file changes, and fragile rollouts.
Core Features & Use Cases
- Scope classification: Automatically classifies work as Small, Medium, or Large and adapts the output accordingly.
- Per-file planning: Names every file to be changed and produces ordered implementation steps with independent verification criteria.
- Specs & checkpoints: Generates product and technical specs for medium/large efforts, runs architecture checkpoints, and surfaces unknowns and risks.
- Session and artifact integration: Integrates with local session tooling and saves plan artifacts to the sprint journal for scope-drift detection and review.
- Use case: Use when adding a new feature, refactoring a module, or investigating a bug that will touch multiple files.
Quick Start
Run the /nano command to generate a scoped implementation plan that lists every file to change, ordered steps, and verification criteria.