task-runner
Task Runner
Overview
Load the plan, scrutinize it, execute tasks in batches, and pause for architect review between batches.
Core principle: Batch execution with checkpoints for architect oversight.
Announce at start: "I'm applying the task-runner skill to execute this implementation plan."
The Prime Directive
NO PLAN EXECUTION WITHOUT CRITICAL REVIEW OF EACH TASK FIRST
No exceptions. No workarounds. No shortcuts.
Plans contain errors, ambiguities, and outdated assumptions. Every task must be critically examined before execution begins. Blindly following a plan is not "efficiency" -- it is investing time in incorrect work.
More from noobygains/godmode
fault-diagnosis
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
15task-planning
Use when you have a spec or requirements for a multi-step task, before touching code
15agent-messaging
Use when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents. Covers both subagent prompts and team-level messaging.
15intent-discovery
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
15quality-enforcement
Use when preparing code for commit, PR, or merge - covers linting, type safety, bundle budgets, coverage thresholds, complexity limits, dependency audit, and dead code detection
14pattern-matching
Use when contributing code to an existing project - guarantees that every new line mirrors the established conventions, naming schemes, architectural layering, directory layout, and stylistic choices already present in the codebase rather than drifting toward generic AI defaults
14