feature-implement

Dispatch wave-ordered feature tasks to domain agents with dependency tracking.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill feature-implement-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implement
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/feature-implement
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill feature-implement-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Execute wave-ordered implementation plan by dispatching tasks to domain agents. Use after /feature-plan produces a plan. Use for "implement feature", "execute plan", "start building", or "/feature-implement". Do NOT use without a plan or for ad-hoc coding tasks.

Core Features & Use Cases

  • Dispatch tasks to domain agents (golang-general-engineer, typescript-frontend-engineer, etc.)
  • Execute wave-ordered plans with dependency tracking
  • Handle deviations with tiered escalation
  • Run wave checkpoints (tests) between waves

Quick Start

Load a validated plan and run /feature-implement to execute it.

Frequently Asked Questions about feature-implement

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

FAQPage Schema
How do I execute a wave-ordered feature implementation plan with multiple agents?

Dispatch tasks to domain agents for wave-ordered feature implementation. This Skill requires a validated plan in .feature/state/ and uses python3 scripts/feature-state.py to enforce wave order, track dependencies, and run iterative checkpoints.

What is the best way to orchestrate domain agents for feature development?

Orchestrate feature implementation by dispatching tasks to domain agents like golang-general-engineer. It manages wave-based plans with dependency tracking, plan validation, and tiered deviation handling.

Do I need a formal plan artifact before starting feature implementation?

Yes, you must generate a formal plan artifact in .feature/state/plan/ first. This Skill dispatches tasks to domain agents based on that plan and does not support ad-hoc coding without a validated plan.

Can I run tests between implementation waves?

Yes, the Skill runs wave checkpoints between implementation waves. It enforces wave order, verifies task completion, and handles deviations with tiered escalation before moving to the next wave.

Why does feature implementation fail when dispatching tasks without a validated plan?

Feature implementation fails without a validated plan because the Skill requires a formal plan artifact in .feature/state/plan/. It enforces wave order, tracks dependencies, and dispatches tasks to domain agents based on that plan.