implement

Execute gate-driven feature plans with TDD cycles and archival commits.

6|Updated Mar 19, 2026

Search Tags:#workflow #TDD #archival #milestones #implement #specs #gate-check

Ready to run

npx skills add https://github.com/nesquikm/dev-process-toolkit --skill implement-nesquikm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/implement
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill implement-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end feature work with structured phases, gating, and self-review loops to ensure auditable, high-quality software delivery.

Core Features & Use Cases

End-to-end workflow orchestration across Plan, Build, and Ship phases with deterministic gate checks.
Phase-driven execution including TDD cycles, spec reviews, and milestone archival.
Handles multi-milestone deliveries and integrated release planning with human approvals.

Quick Start

Start the end-to-end workflow by invoking the implement skill with a target milestone (e.g., M1) or a task description.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I orchestrate end-to-end feature work with built-in safety checks and milestone archival?▼

You orchestrate end-to-end feature work by invoking a structured workflow that applies gated reviews, TDD-style iteration, and bounded self-reviews across Plan, Build, and Ship phases. It aligns specs, executes gate-driven plans, and produces archival-ready commits.

What is gate-driven plan execution for multi-milestone software delivery?▼

Gate-driven plan execution is a deterministic workflow mechanism that enforces spec reviews, TDD cycles, and human approvals before advancing through delivery phases. It ensures complex multi-milestone tasks maintain plan alignment and produce auditable archival-ready commits.

How do I start a TDD workflow with spec alignment for a complex feature milestone?▼

Start a TDD workflow by providing a target milestone argument like M1 or a task description. The system resolves targets, reads specs, and initiates phase-driven execution featuring TDD cycles, spec reviews, and milestone archival.

Can I use this workflow for integrated release planning with human approvals?▼

Yes, this workflow handles multi-milestone deliveries and integrated release planning requiring human approvals. It coordinates complex feature work across structured phases with deterministic gate checks to ensure auditable software delivery.

What's the best way to ensure plan and spec alignment during complex feature implementation?▼

The best way to ensure plan and spec alignment is using a gated review workflow that reads specs, resolves targets, and executes a gate-driven plan with bounded self-reviews. This orchestrates end-to-end feature work with structured phases and archival-ready commits.

When should I use a phase-driven workflow with deterministic gate checks for software delivery?▼

Use a phase-driven workflow with deterministic gate checks for complex, multi-milestone tasks requiring formal archival, spec reviews, and human approvals. It is designed for auditable, high-quality software delivery rather than simple, single-step changes.