Agent skill · software engineering · thienanblog
run-reviewable-subtask-loop
Explicit-opt-in delivery specialist for executing a large plan, migration, refactor, or roadmap as sequential reviewable commits on one integration branch. Use only when directly requested or explicitly accepted after a project-development-mindset proposal; never infer activation from size, an internal plan, or the word subtask. Subtasks are not subagents; delegation and Remote CI require separate approval.
Why this skill is useful
Adds a detailed workflow for managing large implementation tasks with specific local and remote CI checks that the AI cannot generate on its own.
What it needs
About 11k tokens when loaded. Last updated 2026-08-05. 63 stars on the source repository.
What this skill does
Run Reviewable Subtask Loop Deliver a large change as ordered, recoverable commits on a local integration branch. Review and verify every subtask before integration, then run focused aggregate checks and use one agreed aggregate publication path. After the work is complete, let the user decide whether to run a broader or full local suite. Use task for the user's complete requested outcome, subtask for one independently reviewable and recoverable delivery unit, and phase only for an optional group of related subtasks. Do not use these terms interchangeably. Enforce consent boundaries 1. Apply this workflow only after the explicit opt-in described in the frontmatter. A routine implementation plan, silence, or a general request to start coding is not acceptance. 2. Treat a subtask as a delivery and recovery boundary, not a delegated worker. Perform implementation, self-review, verification, and finalization sequentially in the main conversation by default. 3. Do not infer delegation approval from terms such as subtask, phase, review, reviewer, parallelizable, execute the plan, or use this skill. Before any delegation, explain why it helps, its usage impact, and the proposed agent count and scope, maximum concurrency, and roles. Obtain explicit approval and ask again before expanding the approved count, concurrency, roles, or scope. 4. Treat Remote CI as a separate consent boundary. Reading repository workflow files is always local discovery; triggering remote jobs requires explicit authorization for the current series and trigger. Read references/remote-ci.md when Remote CI is required, requested, or could start automatically. 5. Treat planning as read-only except for exact temporary plan artifacts the user requested or the durable-plan mode selected under the criteria below. Create branches, commits, merges, pushes, review requests, or branch deletions only when the user's execution request or repository workflow authorizes them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thienanblog/run-reviewable-subtask-loop