implement

# Implement Track Implement tasks from the active track's plan following the TDD workflow. `/draft:implement` is the **canonical implementation parent**. It owns the common execution loop and absorbs three adjacent commands when appropriate: - `/draft:status` - `/draft:coverage` - `/draft:revert` ## Red Flags - STOP if you're: - Implementing without an approved spec and plan - Skipping TDD cycle when workflow.md has TDD enabled - Marking a task `[x]` without fresh verification evidence - Batching multiple tasks into a single commit - Proceeding past a phase boundary without running the three-stage review - Writing production code before a failing test (when TDD is strict) - Assuming a test passes without actually running it **Verify before you mark complete. One task, one commit.** ## Constraints Draft skills are designed for single-agent, single-track execution. Do not run multiple Draft commands concurrently on the same track. --- ## Parent Contract `/draft:implement` owns four execution jobs: 1. **Build the next task** → baseline `/draft:implement` 2. **Show current execution state** → `/draft:status` 3. **Measure implementation completeness via coverage** → `/draft:coverage` 4. **Undo implementation safely** → `/draft:revert` Most developers should only need `/draft:implement` in the common path. ### Explicit Child Modes If the user invokes explicit child intent, route directly: - `/draft:implement status` → follow `/draft:status` - `/draft:implement cove...