nano-mode

Replace the eight-phase SDD pipeline with a four-step inline workflow.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill nano-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nano-mode
Source: https://github.com/JNZader/javi-ai/tree/main/own/skills/nano-mode
Command: npx skills add https://github.com/JNZader/javi-ai --skill nano-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SDD-lite for small changes. Quick, inline decision-making replaces the full SDD pipeline for minor updates.

Core Features & Use Cases

  • Replaces the eight-phase SDD with four fast steps: Challenge, Plan, Build, Review.
  • Ideal for single-file edits, bug fixes with clear scope, and small refactors under 100 LOC.
  • Enables consistent, audit-friendly change workflows without sub-agents.

Quick Start

Describe the tiny change you want to make and let Nano Mode guide the four-step inline workflow (Challenge, Plan, Build, Review).

Frequently Asked Questions about nano-mode

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

FAQPage Schema
How do I handle small code changes without running a full planning pipeline?

Small code changes can be handled using an inline four-step workflow that replaces the full SDD pipeline. This approach uses Challenge, Plan, Build, and Review phases to guide single-file edits and quick fixes while enforcing scope control.

What is the best way to plan a single-file edit or lightweight config tweak?

The best way to plan a single-file edit is using a four-step inline workflow that provides structured steps and documented outputs. It enables rapid validation for lightweight config tweaks without requiring sub-agents or the full eight-phase SDD process.

Can I use an inline workflow for bug fixes with clear scope?

Yes, an inline workflow is ideal for bug fixes with clear scope and small refactors under 100 LOC. It provides consistent, audit-friendly change handling through four fast steps: Challenge, Plan, Build, and Review.

When should I use a four-step inline workflow instead of the full SDD pipeline?

You should use a four-step inline workflow instead of the full SDD pipeline when dealing with minor updates, single-file edits, or quick fixes. It replaces the eight-phase SDD with fast inline decision-making where rapid validation matters.

Does the inline SDD-lite workflow support small refactors under 100 LOC?

Yes, the inline SDD-lite workflow supports small refactors under 100 LOC. It performs inline four-step handling with structured steps and documented outputs, ensuring consistent and audit-friendly workflows for minor updates.