embedded-implementation

Embedded Implementation

Overview

Execute implementation plan with two-stage review after each task.

Core principle: Fresh subagent per task + hardware validation + code quality review = high quality.

Context: Run after embedded-driver-design creates plan.

Two-Stage Review Process

Task Execution → Hardware Validator → Code Quality Reviewer → Commit
     ↓                ↓                     ↓
  Generate code    DMA/GPIO check        MISRA C check

Stage 1: Hardware Validator

• Use prompts/hardware-validator.md
• Checks: DMA <= 4092, interface config, init sequence

Stage 2: Code Quality Reviewer

• Use prompts/code-quality.md
• Checks: MISRA C, DRY, YAGNI, clean code

Process

1. Load Plan

read docs/embedded/plans/YYYY-MM-DD-<driver>-plan.md

Extract ALL tasks with full text and context.

2. Create Todo List

todowrite todos=[{task: "Task 1: Header file", status: "pending"}, ...]

3. Execute Per Task

For each task:

#### Task N Execution

1. Mark todo: in_progress

2. Get task text and context (already extracted)

3. Dispatch implementation (use prompts/driver-generator.md)
   - Generate code
   - Build verification

4. Stage 1 Review: Hardware Validator
   - Use prompts/hardware-validator.md
   - Check DMA, interface, init sequence
   
5. If Stage 1 FAILS:
   - Fix issues
   - Re-review
   - Don't proceed until APPROVED

6. Stage 2 Review: Code Quality
   - Use prompts/code-quality.md
   - Check MISRA C, DRY, YAGNI
   
7. If Stage 2 FAILS:
   - Fix issues
   - Re-review
   - Don't proceed until APPROVED

8. Both stages APPROVED:
   - Mark todo: completed
   - Commit changes

4. After All Tasks

Dispatch final review for entire implementation

5. Transition to Verification

All tasks complete. Invoking embedded-verification for build-flash-monitor loop.

REQUIRED: Invoke embedded-verification next.

Implementation Prompt

Use prompts/driver-generator.md for code generation: