implement

Execute scout, inner loop, and outer loop phases to implement approved specs.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mliudev/agent-workflows --skill implement-mliudev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/mliudev/agent-workflows/tree/main/skills/claude/implement
Command: npx skills add https://github.com/mliudev/agent-workflows --skill implement-mliudev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Autonomous implementation of approved specs to reduce back-and-forth and accelerate delivery.

Core Features & Use Cases

  • Scout, rolling inner loop, and outer loop phases orchestrate end-to-end feature implementation.
  • Evidence-driven validation, bounded task planning, and incremental delivery with per-slice reviews.
  • Automatic gating and reporting to ensure alignment with the QA plan.

Quick Start

Provide an approved spec and trigger the implement workflow to begin executing the next 1-3 tasks with evidence gathering.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I autonomously implement an approved spec end-to-end?

Autonomous spec implementation is orchestrated through scout, rolling inner loop, and outer loop phases. This pipeline executes 1-3 task slices with evidence gathering and bounded subagent delegation to deliver features incrementally.

What is evidence-driven validation in autonomous feature implementation?

Evidence-driven validation enforces bounded ownership and requires verified proof before gating or release. It ensures each implemented task slice aligns with the QA plan through automatic gating and incremental per-slice reviews.

How do I plan task slices for approved feature specs with a QA plan?

Task slices are planned in bounded 1-3 task increments during the rolling inner loop phase. Each slice undergoes evidence gathering and per-slice reviews before proceeding to the next implementation segment.

Do I need a predefined QA plan to use autonomous spec implementation?

Yes, a predefined QA plan is required. The implementation pipeline applies to features with an approved spec and QA plan, using both to guide evidence-driven validation and generate a final verified report.

What is the best way to orchestrate an autonomous implementation pipeline?

The best way to orchestrate an implementation pipeline is using scout, rolling inner loop, and outer loop phases. This approach reduces back-and-forth by applying bounded subagent delegation and automatic gating for incremental delivery.

When should I not use autonomous spec implementation?

You should not use autonomous spec implementation for features lacking a defined spec or QA plan. The pipeline requires approved specifications and bounded task planning to enforce evidence-driven validation and generate verified reports.