ss-sdd-implementing-task

What problem does it solve?

It prevents spec-driven implementers from drifting out of scope by enforcing a task-focused protocol, test-first by default, and strict commit hygiene so the final cross-cutting review sees clean, compliant work.

Core Features & Use Cases

• Stay in scope: Execute exactly the task’s listed steps—no refactors, no extra flags/config/env-var additions, no defensive generalization, and no unrelated bug fixes.
• Follow the TDD protocol by default: Write a failing test first, confirm the expected failure, implement the minimal change to pass, verify, then commit.
• Status reporting with leaf-skill discipline: Report NEEDS_CONTEXT or BLOCKED to the controller when information is missing instead of dispatching sub-subagents.
• Self-review for final-stage quality: Perform a disciplined pre-merge check since there is no per-task reviewer—only the single final cross-cutting code-quality review.

Quick Start

Use this skill when an SDD implementer subagent has been dispatched to implement exactly one task from a plan and you need a strict protocol for TDD, in-scope execution, self-review, and commit hygiene.