implementation

Name: implementation
Availability: InStock
Author: tasai-lab

Coordinate subagent-driven implementation tasks with TDD workflows and Git-based context sharing.

Updated Aug 27, 2026

Search Tags:#git #workflow #implementation #parallel #subagent #code-review #ttd

Ready to run

npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill implementation-tasai-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/implementation
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill implementation-tasai-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow facilitates efficient, structured software implementation by coordinating subagent-driven teams after planning approval, ensuring speed and quality through concurrent execution and formal reviews.

Core Features & Use Cases

Orchestrates sequential, parallel, and team-based implementation strategies to fit project needs.
Enforces TDD-first cycles, review gates, and context sharing via Git commits to maintain alignment.
Use Case: When a plan is approved, launch a multi-agent implementation sprint with clear task dependencies and automated progress reporting.

Quick Start

Start from an approved plan and initiate the implementation phase using parallel subagents guided by a team structure.

Frequently Asked Questions about implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate parallel code implementation with subagents after plan approval?▼

You can coordinate parallel code implementation by launching subagent-driven teams that execute concurrent tasks. This workflow automates the transition from an approved plan to implementation using clear task dependencies and structured team strategies.

What is the best way to enforce a TDD workflow during multi-agent code execution?▼

The best way to enforce a TDD workflow during multi-agent execution is to apply enforced TDD-first cycles with formal review gates. This ensures subagents maintain code quality and alignment through structured test-driven progressions.

Can I use Git commits to share context between parallel subagent teams?▼

Yes, you can use Git commits to share context between parallel subagent teams. The implementation workflow uses Git-based context sharing to maintain alignment and track progress across concurrent development tasks.

Does this parallel implementation workflow support sequential task strategies?▼

Yes, this parallel implementation workflow supports sequential, parallel, and team-based task strategies. You can configure the execution strategy to fit specific project needs and task dependency requirements.

How do automated requirement-driven reviews work in a subagent implementation sprint?▼

Automated requirement-driven reviews work by enforcing formal review gates after subagent task execution. These reviews verify that parallel code outputs meet the approved plan requirements before merging progress.

When should I avoid using parallel subagent teams for software implementation?▼

You should avoid using parallel subagent teams for software implementation when your project lacks an approved plan or when task dependencies require strictly sequential execution without concurrent development branches.