aico-subagent-driven

Execute implementation plan by dispatching fresh subagent per task. Each task gets: Implementer → Spec Review → Quality Review. Two-stage review ensures both correctness and quality. Use this skill when: - Have implementation plan with multiple independent tasks - Want automated execution with quality gates after each task - Tasks are mostly independent (not tightly coupled) - User asks to "execute the plan", "run the tasks", "auto implement" Prerequisites: Must have plan from aico-frontend-plan, aico-backend-plan, or aico-*-task-breakdown skill. Process: For each task: Dispatch Implementer → Spec Review (passes?) → Quality Review (passes?) → Next task Review order: ALWAYS spec compliance first, THEN code quality.

Jump to install

Repository: yellinzero/aico
Last source activity: February 12, 2026 at 05:32
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/yellinzero/aico --skill aico-subagent-driven

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

aico-backend-implement

Execute backend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "start coding" - Have task file (story-* or standalone-*) ready to execute - User asks to "use TDD", "write test first", or "test-driven" - User asks to "write tests", "add tests", "create tests" - Fixing bugs (write failing test first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - Task file in docs/reference/backend/tasks/ (story-* or standalone-*) - Read constraints.md and design spec before coding Flow: Read Task → Read Constraints → Execute Steps → Verify → Test → Update Status

2026-02-12

aico-backend-plan

Create or enhance backend tasks with detailed implementation steps. Supports TWO modes: MODE A: Enhance existing task (add detailed steps to task in file) MODE B: Create new standalone task file (can contain single or multiple tasks) IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /backend.plan command - User asks for "atomic steps", "step-by-step plan with verification" - Have a specific task and need implementation steps - User wants to create a standalone task file (not from story) - Need granular steps: Types → DB → Repository → Service → API → Tests DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: - MODE A: Update specific task section in file with Implementation Steps - MODE B: Create new standalone-{name}.md file with one or multiple tasks

2026-02-12

aico-backend-task-breakdown

Break down PM story into organized tasks in a single file following LAYERED ARCHITECTURE order: Types → Database → Repository → Service → API → Tests. UNIQUE VALUE: Creates single task file (story-{name}.md) containing all tasks for a story. Tasks are ordered by backend architecture layers. Use this skill when: - Running /backend.tasks command - User asks to "break down story", "create backend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task breakdown - Need tasks ordered by backend architecture layers (not random order) - Starting backend work and want organized task list Task order is CRITICAL: Types → Database → Repository → Service → API → Tests Output: Create single file docs/reference/backend/tasks/story-{name}.md with all tasks

2026-02-12

View all from this repository

name

aico-subagent-driven

description

Subagent-Driven Development

Process

1. Read plan, extract all tasks
      ↓
2. Create task list with TaskCreate for all tasks
      ↓
3. For each task:
   a. Dispatch Implementer Subagent
   b. Implementer: implement and test
   c. Dispatch Spec Reviewer (matches spec?)
   d. Spec issues? → Implementer fixes → re-review
   e. Dispatch Quality Reviewer (code quality?)
   f. Quality issues? → Implementer fixes → re-review
   g. Mark task complete
      ↓
4. All tasks complete → Final review → Done

Review Order is Critical

Spec Compliance Review FIRST
        ↓
    ✅ Passes
        ↓
Code Quality Review SECOND

Why: No point reviewing code quality if it doesn't meet spec.

Subagent Prompts

Implementer

Provide FULL task text (don't make subagent read file)
Provide context (where task fits in plan)
Require TDD and self-review

Spec Reviewer

Check: Does implementation match spec exactly?
Missing anything? Added anything extra?

Quality Reviewer

Check: Tests, readability, error handling, performance, security
Rate issues as Critical/Important/Minor

aico-subagent-driven

Install options

Review the source files

Subagent-Driven Development

Process

Review Order is Critical

Subagent Prompts

Implementer

Spec Reviewer

Quality Reviewer

Subagent-Driven Development

Process

Review Order is Critical

Subagent Prompts

Implementer

Spec Reviewer

Quality Reviewer

Key Rules

Red Flags

Common Mistakes

aico-subagent-driven

Source facts

Install options

Review the source files

More from this repository

More from this repository

Subagent-Driven Development

Process

Review Order is Critical

Subagent Prompts

Implementer

Spec Reviewer

Quality Reviewer

Subagent-Driven Development

Process

Review Order is Critical

Subagent Prompts

Implementer

Spec Reviewer

Quality Reviewer

Key Rules

Red Flags

Common Mistakes