implement-feature

Orchestrate parallel coder agents through feature spec waves with review gates.

Updated May 20, 2026

Search Tags:#feature #code-review #implement #orchestrate #wave-based #coder-agents

Ready to run

npx skills add https://github.com/gelowzzz/plushyai --skill implement-feature-gelowzzz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/gelowzzz/plushyai/tree/main/.agents/skills/implement-feature
Command: npx skills add https://github.com/gelowzzz/plushyai --skill implement-feature-gelowzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates parallel feature implementation by dispatching coder agents to work in waves, coordinating tasks and reviews without writing code directly.

Core Features & Use Cases

Orchestrates wave-based parallel tasks by spawning coder agents for each task
Enforces code-review gates between waves and manages fix loops
Tracks progress via spec files and resumes where left off

Quick Start

To begin implementing a feature, trigger the implement-feature skill to orchestrate parallel coder agents through the feature spec waves.

Frequently Asked Questions about implement-feature

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

FAQPage Schema

How do I orchestrate parallel feature implementation with coder agents?▼

You can coordinate parallel feature implementation by dispatching coder agents based on feature specifications. The process supports wave-by-wave execution, applies code-review gates between waves, and manages iterative fix loops.

How does wave-based execution manage code reviews and fixes?▼

Wave-based execution enforces code-review gates between parallel coder agent tasks. It automatically manages iterative fix loops and tracks progress via spec files, allowing you to resume implementation exactly where it left off.

Do I need a specific folder structure for feature specification files?▼

Yes, feature specification files must be defined within the specs/{feature}/ folders. The orchestration process parses these spec files to spawn parallel tasks, perform reviews, and generate commit-ready wave summaries.

Can I track feature implementation progress and resume interrupted tasks?▼

Yes, the orchestration mechanism tracks progress via spec files and resumes where left off. This allows iterative feature implementation to recover from interruptions without losing completed wave execution or code review states.

What are the limitations of using coder agents for wave-based feature implementation?▼

The orchestration process dispatches coder agents but does not write code directly. It relies strictly on pre-defined specs/{feature}/ folders and requires manual or automated code-review gates to manage iterative fixes.