implement

Name: implement
Availability: InStock
Author: fourthwiz

Convert development plans into tested code with commits and PRs.

2|1|Updated Mar 18, 2026

Search Tags:#git #workflow #testing #implement #code-generation #pull-requests

Ready to run

npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill implement-fourthwiz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/FourthWiz/claude_dev_workflow/tree/main/dev-workflow/skills/implement
Command: npx skills add https://github.com/FourthWiz/claude_dev_workflow --skill implement-fourthwiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a validated implementation plan into incremental, test-covered code changes while preserving project conventions and minimizing risk from ad-hoc edits.

Core Features & Use Cases

Plan-driven implementation: Reads the current-plan.md and executes tasks in order, making small, reviewable commits.
Safety and quality gates: Verifies gate checks, runs tests, and follows commit and PR conventions before advancing.
Session persistence: Updates workflow artifacts and session memory so other lifecycle skills can continue work seamlessly.

Quick Start

Invoke /implement and specify which task from current-plan.md to implement next so the agent writes code, adds tests, and prepares commits and a PR for review.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I turn a development plan into tested, production-ready code?▼

To turn a development plan into tested code, you execute tasks sequentially from a current-plan.md file, writing code, running tests, making small commits, and preparing pull requests. This ensures changes are incremental and reviewable.

What is the best way to generate code and prepare pull requests from a workflow plan?▼

Generating code and preparing pull requests from a workflow plan involves reading task specifications, verifying gate checks, writing the implementation, running tests, and following commit message guidelines before advancing to the next task.

Do I need a specific file format to start automated code implementation?▼

Yes, automated code implementation requires a ready task specified in a .workflow_artifacts/<task>/current-plan.md file. The agent reads this plan to execute tasks in order, write tests, and prepare commits safely.

How does plan-driven code implementation keep changes small and reversible?▼

Plan-driven implementation keeps changes small and reversible by executing tasks in order from a plan, making incremental reviewable commits, verifying safety gates, and updating session memory artifacts so other workflow skills can continue seamlessly.

Why does my code generation workflow require running tests before preparing a PR?▼

Running tests before preparing a PR is required to verify safety and quality gates, ensuring the implemented code changes from the plan are test-covered and preserve project conventions before advancing to the next task.