/f5-implement

description: Implement features and fix bugs with traceability
argument-hint: <feature|fix> [--tdd|--with-tests]
mcp-servers: context7, serena

/f5-implement - Unified Implementation Command

**Consolidated command** that replaces:

• `/f5-fix` → `/f5-implement fix`

Implement features and fix bugs with high quality, TDD support, and best practices.

ARGUMENTS

$ARGUMENTS

MODE DETECTION

| Pattern | Mode | Description | |---------|------|-------------| | `fix <bug-id\|desc>` | FIX | Bug fix workflow | | `fix list` | FIX_LIST | List all bugs | | `fix done <id>` | FIX_DONE | Mark bug as fixed | | `fix verify <id>` | FIX_VERIFY | Re-verify fix | | `<other>` (default) | IMPLEMENT | Feature implementation |

---

MODE: FIX (from /f5-fix)

`/f5-implement fix <bug-id|description>`

Structured workflow for fixing issues with traceability.

| Action | Description | |--------|-------------| | `<bug-id>` | Fix specific bug by ID | | `"<description>"` | Fix by description (creates new bug) | | `list` | List all bugs | | `done <bug-id>` | Mark bug as fixed | | `verify <bug-id>` | Re-verify after fix | | `list --status open` | Filter open bugs | | `list --severity high` | Filter by severity |

**Examples:**

/f5-implement fix BUG-001
/f5-implement fix "Hero image wrong size"
/f5-implement fix list
/f5-implement fix done BUG-001
/f5-implement fix verify BUG-001

---

MODE: IMPLEMENT (Default)

Implement features with high quality and auto-agent support.

STEP 0: PRE-FLIGHT CHECKS

0.1 Load Integration Config

# Load command integration settings from .f5/config/command-integration.yaml
INTEGRATION_CONFIG=".f5/config/command-integration.yaml"
if [ -f "$INTEGRATION_CONFIG" ]; then
  COMMAND_CONFIG=$(cat "$INTEGRATION_CONFIG" | yq '.command_integration.f5-implement')
fi

0.2 Check MCP Prerequisites

📋 **MCP Pre-flight Check**

Required MCPs:
  - context7: [✅ Available / ⚠️ Not available]

Optional MCPs:
  - serena: [✅ Available / ○ Not configured]

{{#if MISSING_REQUIRED}}
⚠️ Missing required MCP: context7
Run: /f5-mcp install context7
Continuing with reduced capabilities...
{{/if}}

0.3 Load Developer Role

# Get developer role from config
ROLE=$(jq -r '.developer_role // "fullstack"' .f5/config.json 2>/dev/null)
echo "Developer Role: $ROLE"

# Get role-specific focus
case "$ROLE" in
  backend)
    FOCUS="API endpoints, services, repositories"
    AGENTS="code_generator, api_designer"
    ;;
  frontend)
    FOCUS="Components, hooks, state"
    AGENTS="code_generator"
    ;;
  fullstack)
    FOCUS="Full feature implementation"
    AGENTS="code_generator, api_designer"
    ;;
  *)
    FOCUS="General implementation"
    AGENTS="code_generator"
    ;;
esac

0.4 Prepare Auto-Invoke Agents

🤖 **Agents to Auto-Invoke**

Based on role ($ROLE) and project settings:

| # | Agent | Purpose | Condition |
|---|-------|---------|-----------|
| 1 | ⚡ code_generator | Generate production-ready code | Always |
| 2 | 🧪 test_writer | Write comprehensive tests | TDD mode OR production |
| 3 | 📝 documenter | Generate documentation | Production only |

Focus: $FOCUS

0.5 Execute with Auto-Agents

**Step 1: MCP Enhancement (if available)**

If context7 available:
  → Fetch relevant documentation for detected stack
  → Apply latest patterns and best practices
  → Check for security advisories

**Step 2: Code Generator Agent**

⚡ Invoking code_generator...
  - Focus: {{FOCUS}}
  - Patterns: From .f5/memory/
  - Stack: {{DETECTED_STACK}}
  - Traceability: REQ-XXX comments

**Step 3: Test Writer Agent (conditional)**

{{#if TDD_MODE OR PROJECT_TYPE == 'production'}}
🧪 Invoking test_writer...
  - Coverage target: 80%
  - Include edge cases: true
  - Test naming: descriptive
{{/if}}

**Step 4: Documenter Agent (conditional)**

{{#if PROJECT_TYPE == 'production'}}
📝 Invoking documenter...
  - Inline documentation
  - API docs if applicable
  - README updates if needed
{{/if}}

FLAGS

| Flag | Description | |------|-------------| | `--tdd` | Use TDD workflow (red-green-refactor) | | `--with-tests` | Generate unit tests alongside implementation | | `--with-it` | Generate integration tests alongside implementation | | `--with-all-tests` | Generate UT + IT + E2E stubs | | `--security` | Security-focused implementation with extra guards | | `--performance` | Performance-focused implementation with optimization | | `--scaffold` | Generate module structure only (no implementation) | | `--dry-run` | Preview changes without writing files |

Flag Examples

# Standard implementation
/f5-implement user-registration

# With TDD workflow
/f5-implement user-registration --tdd

# Security-focused (auth, encryption, guards)
/f5-implement authentication --security

# Performance-focused (caching, optimization)
/f5-implement product-listing --performance

# Generate structure only
/f5-implement order-management --scaffold

# Generate with unit tests
/f5-implement payment-processing --with-tests

# Generate with integration tests
/f5-implement order-api --with-it

# Generate all test types (UT + IT + E2E stubs)
/f5-implement checkout-flow --with-all-tests

IT Auto-Detection Rules

When using `--with-it` or `--with-all-tests`, Claude auto-detects the appropriate integration test type:

| Implementation Type | IT Type Needed | Auto-trigger | |---------------------|----------------|--------------| | API Controller/Route | `api` | Yes | | Repository/DAO | `database` | Yes | | External Service Client | `service` | Yes | | MCP Integration | `mcp` | Yes | | Multi-component Feature | `flow` | Yes |

**Detection Logic:**

it_auto_detection:
  api:
    triggers:
      - "*.controller.ts"
      - "*.router.ts"
      - "*.route.ts"
      - "*.handler.ts"
    test_command: "/f5-test-it api"

  database:
    triggers:
      - "*.repository.ts"
      - "*.dao.ts"
      - "*.entity.ts"
    test