From iyu
Execute a single development phase. For iterative multi-cycle work, use `/iyu:run-cycle`.
npx claudepluginhub iyulab/claude-plugins --plugin iyuThis skill uses the workspace's default tool permissions.
Execute a single development phase. For iterative multi-cycle work, use `/iyu:run-cycle`.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Execute a single development phase. For iterative multi-cycle work, use /iyu:run-cycle.
Priority Order:
Outcomes: READY → proceed | NONE_PENDING → exit | BLOCKED → exit with info | NO_PLAN_FOUND → exit with guidance
/iyu:run "Add caching layer to API endpoints"
Flags: --dry-run (plan only) | --no-commit (skip commit)
Session context first. If nothing: search project files (stop at first found). If nothing found: exit — do not invent scope.
Before execution, evaluate scope against CLAUDE.md / README.md:
| Dimension | Question |
|---|---|
| Core Mission Fit | Serves core purpose? |
| Scope Alignment | Within library responsibility? |
| Pattern Consistency | Consistent with existing patterns? |
| Scope IN | Scope OUT | |
|---|---|---|
| Mission HIGH | PROCEED | ADAPT |
| Mission MED | ADAPT | PARTIAL |
| Mission LOW | PARTIAL | REJECT |
Latent discovery: While reading the codebase for alignment, actively look for related issues, inconsistencies, or improvements that should be addressed alongside the explicit task.
Skip conditions — ALL must be true to proceed directly to execution:
Investigation signals — ANY triggers this phase:
Steps:
If --dry-run, stop here.
Per-task: execute → test → complete.
Root cause mindset: When problems surface, ask "why" 5 times. Fix all instances, not just the trigger.
All tasks complete, tests passing, build succeeds.
Version rules: NEVER bump MAJOR — MINOR for features, PATCH for fixes.