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.
thienanblog · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add thienanblog/awesome-ai-agent-skills --skill run-reviewable-subtask-loop技能说明
name: run-reviewable-subtask-loop description: 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.
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
- 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.
- 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.
- 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.
- 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.
- 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. Never infer final-merge authorization from permission to implement or publish.
Initialize the series
Before the first edit:
- Read repository instructions, the implementation plan, relevant architecture and progress docs, workflow files, branch protection, and current Git state.
- Determine the intended base branch, integration branch, required branch prefix, local verification commands, review-request path, documentation rules, and merge behavior.
- Fetch configured remotes and explicitly compare the intended base with its fetched counterpart. If a clean, non-diverged base is behind, update it only with the repository-approved fast-forward operation. If freshness cannot be verified, or the base is dirty or diverged, report the exact state and obtain direction before editing from that base or changing history.
- Create or reuse the series integration branch only after its base is fresh enough under repository policy. Default to an ephemeral local branch from the intended protected base; use an established delivery branch only when required.
- Record the initial base and integration commit SHAs. Confirm the integration branch is not used by another worktree and starts clean.
- Agree on the subtask ledger, focused verification budget, publication path, Remote CI decision, and whether cleanup of this series' exact local branches is authorized. Use the lightweight plan mode unless the user requests durable artifacts or the work has a concrete multi-session recovery need. Disclose any push or review-request action that would automatically trigger Remote CI before taking it.
Use this normal topology:
intended base
└── series integration
└── one current local subtask branch
Keep the integration branch local until aggregate verification passes unless the user explicitly requests remote backup or collaboration requires it. Do not push subtask branches or open per-subtask review requests. During normal execution, keep at most one live subtask branch and start every subtask from the current verified integration tip.
Choose and maintain the plan artifacts
Before the first source edit, choose the lightest execution mode that preserves the required recovery boundary:
- Continuous execution (default): keep a compact ordered ledger in the conversation or an existing repository-owned progress surface and run the approved subtasks sequentially without creating temporary plan files.
- Durable subtask plans: create the master and subtask plans only when the user requests persisted plans or the series is expected to cross sessions and cannot be reconstructed reliably from Git and the existing ledger.
Do not issue a blocking question solely to resolve this choice. Treat
docs/plans as a repository-relative path when durable plans are selected, but
obey a higher-priority repository rule that requires another planning location
or forbids temporary tracked plans.
For durable subtask plans:
- Choose one collision-free task slug and create only these series-owned paths:
docs/plans/<task-slug>-00-master.mdanddocs/plans/<task-slug>-NN-<subtask-slug>.md, using zero-padded execution order forNN. Never overwrite an existing plan to reuse a name. - Put the agreed requirement baseline, initial base and integration SHAs, execution mode, subtask order, dependencies, status, branches, commits, verification, findings, an