nano

Create scoped implementation plans with per-file changes and verification steps.

204|14|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/garagon/nanostack --skill nano-garagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nano
Source: https://github.com/garagon/nanostack/tree/main/plan
Command: npx skills add https://github.com/garagon/nanostack --skill nano-garagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about nano

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

FAQPage Schema
How do I create an implementation plan for complex code changes touching multiple files?

Create an implementation plan for complex code changes by classifying the scope as Small, Medium, or Large, then generating per-file change listings, ordered implementation steps, and independent verification criteria before coding begins.

What is the best way to prevent scope creep when refactoring a module?

Prevent scope creep during module refactoring by generating verifiable implementation plans with product and technical specs, running architecture checkpoints, and saving artifacts to a sprint journal for continuous scope-drift detection.

When do I need to generate specifications for a new feature?

Generate specifications for a new feature when scope classification determines the effort is Medium or Large, requiring product specs, technical specs, and architecture checkpoints to surface unknowns and risks.

How do I identify risks and unknowns before starting a software engineering sprint?

Identify risks and unknowns before a software engineering sprint by applying scoping and risk-assessment processes that produce a measurable implementation plan naming every file to change and independent verification criteria per step.

Can I use this for small bug investigations that only touch one or two files?

This scoping tool is designed for non-trivial work touching three or more files, automatically adapting outputs for Small, Medium, and Large scopes, but is not intended for single-file bug investigations.