← ClaudeAtlas

developlisted

Default baseline skill for normal software work: small safe iterations, built-in validation, no unnecessary pauses between clear next steps. Includes mode selection (direct, batch, delegate) and cheap-first escalation for bounded mechanical chores. Common triggers: develop, kaizen, autopilot, keep going, continue without waiting, do not stop, don't stop, ga door, werk door, volgende logische stap, volgende stap, start working, start coding, get started, zonder te wachten, niet stoppen, gewoon doorgaan, ga verder, implement this, fix this, add this, pas dit aan, maak dit af, implement, implementeer dit, keep coding, continue implementation, work through steps, code change, start implementing, start implementation, batch edits, delegate work, subagent, maak dit werkend, rewrite, herbouw, coordinator, coördinator, omwerken, entity rewrite, refactor, code aanpassen, werk dit bij, build this, development.
MarkBovee/nebu-skills · ★ 1 · AI & Automation · score 62
Install: claude install-skill MarkBovee/nebu-skills
# Nebu Kaizen Default to steady progress: inspect, create, test, review, continue. If the next logical step is clear, keep going without pausing for routine check-ins. ## Choose the mode - **Direct:** known files, tight coupling, fast iteration, nuanced judgment - **Delegate:** independent research, parallelizable subtasks, noisy command runs, or specialized review - **Batch:** related reads, searches, and edits that can be done safely together ## Cheap-first escalation 1. Start bounded mechanical chores on the smallest viable agent or subagent. 2. Validate the result before widening context. 3. Escalate to default agent only if scope grows beyond the original bounded task. 4. Escalate to high or xhigh only for cross-cutting, analysis-heavy, or repeatedly failing work. ## Core loop 0. **Plan if missing.** Non-trivial task (3+ changes, multi-file, risky) without a plan? Generate inline plan with `todowrite` or short bullets. Trivial 1-2 edits: skip. 1. Inspect the next boundary that matters. 2. Create the smallest coherent improvement. 3. Test it with the fastest trustworthy proof. 4. Review it for clarity, safety, consistency, and scope. 5. Continue unless a real blocker or decision point appears. ## Git workflow (default) ### Feature 1. Branch van main: `git checkout -b feat/description main` 2. Open draft PR meteen met titel + korte scope beschrijving 3. Commit iteratief, push regelmatig, PR updatet vanzelf 4. Klaar? Mark PR ready → review → squash merge met Conven