aico-subagent-driven_skill

Overview

This skill executes an implementation plan by dispatching a fresh subagent for each task and enforcing a two-stage review loop: spec compliance followed by code quality. Each task cycles through Implementer → Spec Review → Quality Review, with fixes applied by the same implementer until both reviews pass. It’s designed for automated, gated execution of multiple independent tasks in TypeScript projects.

How this skill works

The skill reads a provided plan, extracts tasks, and creates a todo list. For each task it dispatches an Implementer subagent that implements, tests, and commits changes. After implementation it runs a Spec Reviewer to verify exact compliance, and only if the spec passes it runs a Quality Reviewer to evaluate tests, readability, error handling, performance, and security. Issues are fixed by the same implementer and re-reviewed until approved before moving to the next task.

When to use it

• You have a multi-task implementation plan from a plan or task-breakdown skill.
• You want automated execution with enforced quality gates after each task.
• Tasks are mostly independent and can be implemented sequentially.
• You need strict spec adherence before any code-quality evaluation.
• You want reproducible, auditable task-by-task progress with reviews.

Best practices

• Always provide the full task text and relevant plan context to the Implementer subagent.
• Keep tasks decoupled so one task’s review or fixes don’t block unrelated tasks.
• Require TDD and self-review from the Implementer before dispatching reviewers.
• Never start Quality Review until Spec Review has explicitly passed.
• Address reviewer issues with the same Implementer and re-run the appropriate review loop.

Example use cases

• Execute a feature rollout broken into independent stories where each story needs exact spec compliance.
• Automate implementation of smaller modules or utilities across a TypeScript codebase with enforced reviews.
• Run a bulk set of refactors that must preserve behavior exactly, with a spec-first validation.
• Perform incremental improvements where each change must pass functional spec and then quality gates.
• Onboard a temporary team by dispatching reliable subagents to implement and review isolated tasks.