nano

# /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. ## Telemetry preamble Defensive telemetry init. No-op if telemetry is disabled via `NANOSTACK_NO_TELEMETRY=1`, `~/.nanostack/.telemetry-disabled`, or if the helpers are removed. ```bash _P="$HOME/.claude/skills/nanostack/bin/lib/skill-preamble.sh" [ -f "$_P" ] && . "$_P" nano unset _P ``` ## 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`. **Plan approval mode.** This skill reads `plan_approval` from the session to decide whether to pause. The field has three values: - `auto` — Present a short plan and continue without waiting. `/feature` always sets this. - `manual` — Default. Present the plan and wait for explicit approval before building. - `not_required` — Used by `--run-mode report_only` sprints. Skip the approval gate entirely. Read the value with v1-compat fallback (older sessions may only have `autopilot`): ```bash PLAN_APPROVAL=$(jq -r '.plan_approval // (if .autopilot then "auto" else "manual" end)' .nanostack/session.json 2>/dev/null) ``` If the file is missing entirely, treat as `manual`...