feature-implementation

name	feature-implementation
version	2.0.0
lifecycle	experimental
type	workflow
category	engineering
risk_level	medium
trust	supervised
description	End-to-end feature implementation workflow using WHY/WHAT/HOW framework — from requirements through context mapping, implementation, testing, and PR creation. Use when implementing a complete feature across multiple files.
metadata	{"openclaw":{"emoji":"📋","os":["darwin","linux","win32"]}}

Feature Implementation Workflow

Role

You orchestrate the complete lifecycle of implementing a feature — from understanding requirements through shipping a pull request. You coordinate agents through the WHY/WHAT/HOW framework, ensuring every step has clear intent, scope, and execution strategy.

When to Use

Use this skill when:

• Implementing a complete feature that spans multiple files
• The work requires context mapping, design, implementation, testing, and PR delivery
• Coordinating multiple agents or personas through a structured pipeline
• You need quality gates between phases to catch issues early

When NOT to Use

Do NOT use this skill when:

• Making a small bug fix or single-file change — use an engineering persona directly, because the 5-phase pipeline adds overhead that exceeds the change complexity
• Only need context mapping without implementation — use context-mapper workflow instead, because it produces reconnaissance output without the implementation phases
• Only need a plan without execution — use strategic-planner persona instead, because it produces implementation plans without running code

Workflow Phases

Phase 0: Context Mapping     → Understand the codebase
Phase 1: Requirements         → Capture WHY
Phase 2: Design               → Define WHAT
Phase 3: Implementation       → Execute HOW
Phase 4: Verification         → Validate against success criteria
Phase 5: Delivery             → Create PR with full documentation

Phase 0: Context Mapping

Agent: context-mapper Output: context_map.yaml

Before anything else, map the territory:

context_mapping:
  scan:
    - Project structure and conventions
    - Existing patterns for similar features
    - Test infrastructure and patterns
    - CI/CD