Implementation Workflow

---
title: "Implementation Workflow"
description: "Build a feature end-to-end: plan the approach, set up the worktree and branch, implement incrementally with verification at every step, and know when to stop and re-plan. Use when the agent has been asked to build, implement, or ship a feature - the standard engineering loop from 'go' to 'ready for review'."
author: AgentArmory
license: Proprietary
---

# Implementation Workflow

Build features systemically: plan, implement incrementally, verify continuously, and know when to stop and re-plan. This is the core engineering loop every agent follows - from "go" to "ready for review" - and it is the entry point for the agentic SWE workflow family.

Research shows AI coding agents produce ~1.7x more issues than human-authored code (CodeRabbit, 2025), with the #1 failure being premature jumping to implementation without a plan (Stack Overflow, 2026). This skill counters both patterns.

## Table of Contents

- [When to Use](#when-to-use)
- [Triggers](#triggers)
- [Prerequisites](#prerequisites)
- [Methodology](#methodology)
- [Dos](#dos)
- [Don'ts](#don'ts)
- [Pitfalls](#pitfalls)
- [Nonsense Check](#nonsense-check)
- [Validate Before Shipping](#validate-before-shipping)
- [Cross-Skill Hints](#cross-skill-hints)

## When to Use

Use this skill when you need to build, implement, or ship a feature - the standard engineering loop from receiving the request to having the change ready for PR review.

Do NOT use for: debugging a failing test (use Systematic Debugging), migrating code between languages (use Code Migration and Refactoring), performance optimization (use Performance Profiling), or looking up a config (use the project's docs).

## Triggers

"implement", "build this", "create", "add a feature", "ship", "make it work", "get this done", "develop", "code this", "implement the change"

## Prerequisites

Before starting, ensure you have access to:
- The source repository (local clone or checkout)
- Project README and CONTRIBUTING.md (most have worktree/branch conventions)
- A test runner and build command
- The project's CI configuration (what gates must pass?)
- Any existing ground skills loaded: Task Decomposition, PR Review

## Methodology

### Phase 1: Understand Before Acting

Spend at least 20% of total budget time (more for complex features) on understanding before writing any code. Jumping straight to implementation is the #1 agent failure mode.