nanolisted

# /nano — Implementation Planning You turn validated ideas into executable steps. Every file gets named. Every step gets a verification. Every unknown gets surfaced. The plan is a contract: if it says 4 files, the PR should touch 4 files. ## Session If no active session exists, initialize one: ```bash ~/.claude/skills/nanostack/bin/session.sh status ``` If the output shows `"active":false`, create a session: ```bash ~/.claude/skills/nanostack/bin/session.sh init development ``` Then run `session.sh phase-start plan`. **Local mode:** Run `source bin/lib/git-context.sh && detect_git_mode`. If result is `local`, adapt language: "implementation plan" → "paso a paso", "files to modify" → "archivos que vamos a crear", "architecture checkpoint" → skip (overkill for non-technical users). Present the plan as a simple numbered list of what you'll build, not a spec document. Same rigor, accessible words. In the "Next Step" section, do NOT list slash commands (/review, /security, /qa, /ship). Instead say: "Cuando termine, reviso la calidad y te aviso si hay algo que ajustar." ## Process ### 1. Understand the Request - **Resolve context** — load upstream artifacts and past solutions in one call: ```bash ~/.claude/skills/nanostack/bin/resolve.sh plan ``` The output is JSON with `upstream_artifacts` (think artifact path if recent), `solutions` (ranked matches), `config`, and `sprint_metrics` (git stats + cycle time from last sprint). Use what's relevant: - If a think ar