implement

Execute track plan tasks using a test-driven development workflow.

39|6|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/mayurpise/draft --skill implement-mayurpise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/mayurpise/draft/tree/main/skills/implement
Command: npx skills add https://github.com/mayurpise/draft --skill implement-mayurpise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executing tasks from track plans using a structured, TDD-driven workflow helps teams enforce discipline and visibility during feature development.

Core Features & Use Cases

  • TDD-driven task progression: Load context, determine the next task, write tests, implement, and verify via red-green-refactor.
  • Progress tracking: Commit-based progress with plan/metadata updates to reflect task completion.
  • Use Case: A team follows a track's spec and plan to deliver features with traceable checkpoints and clear next steps.

Quick Start

Initialize the project context with /draft:init, create a new track with /draft:new-track "Your feature", review draft/spec/plan, and run /draft:implement to execute tasks.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I execute tasks from a track plan using TDD?

Test-driven development task execution loads project context, identifies the next pending task, writes tests, implements the feature, and verifies via red-green-refactor. It enforces track specifications and updates progress through commits and metadata.

Can I automate progress tracking for feature development commits?

Automated progress tracking records commit-based checkpoints and updates plan metadata to reflect task completion. This enforces track specifications and coordinates with the repository workflow to guide disciplined delivery with traceable next steps.

What is the best way to manage a test-driven development workflow?

A structured test-driven development workflow manages feature delivery by loading context, writing tests, implementing features, and verifying through red-green-refactor. It coordinates with the repository workflow to enforce track plans and record checkpoints.

Do I need a track plan and specifications before starting TDD task progression?

Track plans and specifications are required before TDD task progression. You must initialize the project context, create a new track, and review the draft spec and plan to provide the structured context needed for disciplined delivery.

How does test-driven development workflow automation handle task tracking?

Test-driven development workflow automation handles task tracking by determining the next pending task, implementing the feature, and updating progress through commits and metadata. It enforces track specifications and records checkpoints for traceable delivery.

Why does track management require commit-based progress updates?

Track management requires commit-based progress updates to reflect task completion accurately. This records traceable checkpoints, updates plan metadata, and coordinates with the repository workflow to enforce track specifications and guide delivery.