Imlazy Router
Classify the task into Quick/Standard/Heavy/Vault/Learn tier and route to the right workflow. Adaptively consults heuristics.log to refine borderline classifications.
Imlazy Write Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Imlazy Bootstrap
Bootstrap skill loaded on every session — detects /imlazy and "i am lazy" triggers, routes through imlazy-router for tier-aware execution
Imlazy Strategic Save
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
Imlazy Receive Review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Imlazy Write Skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Imlazy Planning
Create and execute implementation plans. Two modes — light (5-bullet inline plan) for Standard tier; full (plan doc + subagent-dispatched execution + per-task review) for Heavy tier
Tdd
Test-Driven Development with built-in completion gate — write failing test, watch it fail, write minimal code to pass, verify with evidence before claiming success
Debugging
Systematic root-cause investigation before any fix attempt. Four phases — Root Cause → Pattern Analysis → Hypothesis → Implementation. If 3+ fixes fail, question the architecture
Imlazy Request Review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Imlazy Backend
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Learn
Record router misclassifications to ~/.claude/imlazy/heuristics.log so the router adapts over time. Invoked by workflow skills on auto-escalation or on user feedback
Imlazy Wordpress
WordPress + ACF (Advanced Custom Fields) development — themes, plugins, hooks, blocks, field groups, security, REST API, and the full ACF ecosystem
Parallel Agents
Dispatch multiple subagents in parallel for independent tasks. Cache-friendly dispatch pattern — identical system prompts let the Anthropic prompt cache (5-min TTL) make 2nd-Nth dispatches nearly free
Imlazy
Use when you want tier-aware agent routing — detects task complexity, routes to Quick/Standard/Heavy/Vault workflows, and auto-dispatches the right agent. Trigger with /imlazy or "i am lazy" prefix.
Brainstorming
For Heavy-tier tasks only — turn ideas into specs through one-question-at-a-time dialogue, present design in sections, write spec doc, hand off to planning skill
Imlazy Finish Branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Imlazy Standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Code Review
Two roles — request a code review (dispatch reviewer subagent) and receive a code review (process feedback rigorously). Use after each task in planning full mode, before merge, or when stuck
Worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans — ensures an isolated workspace exists via native tools or git worktree fallback
Imlazy Subagents
Use when executing implementation plans with independent tasks in the current session