implement

Generate implementation plans and TDD cycles from validated specifications.

107|15|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill implement-rhuss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/rhuss/cc-superpowers-sdd/tree/main/skills/implement
Command: npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill implement-rhuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you through the entire implementation process, ensuring that every line of code is built directly from a validated specification using Test-Driven Development (TDD). It continuously checks for spec compliance, preventing deviations and ensuring the final code perfectly matches the intended design.

Core Features & Use Cases

  • Spec-Driven Planning: Generates a detailed implementation plan directly from your specification, breaking down requirements into actionable tasks.
  • TDD Enforcement: Guides you through the TDD cycle (test, fail, implement, pass, refactor) for each spec requirement.
  • Continuous Compliance: Regularly verifies that your code adheres to the spec, flagging any deviations for reconciliation.
  • Quality Gates: Integrates with code review and final verification skills to ensure all tests pass and spec compliance is 100% before completion.
  • Use Case: You have a validated spec for a user profile update API. This skill will generate a plan, guide you through writing tests first for authentication, validation, and data updates, and ensure your code always matches the spec.

Quick Start

To start implementing a feature from an existing spec, simply say: Implement the user profile API from the spec at specs/features/user-profile-api.md.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement code from a specification using test-driven development?

Test-driven development implements code by writing tests first for each spec requirement, then writing minimal code to pass those tests, and refactoring with green tests. This workflow ensures your implementation directly matches the specification and maintains compliance throughout.

What is spec-driven development and why does it matter?

Spec-driven development generates implementation plans directly from validated specifications, breaking requirements into actionable tasks. It prevents code drift by continuously verifying that your implementation adheres to the intended design, ensuring functional and technical requirements are met exactly.

How do I ensure my code stays compliant with the specification?

Continuous compliance verification checks that your code adheres to the spec at each development stage, flagging deviations for reconciliation. Quality gates integrate code review and verification steps to confirm all tests pass and spec compliance reaches 100% before completion.

Can I use this workflow for any type of feature development?

Spec-driven implementation works best when you have a validated specification already in place. The workflow applies to feature development across APIs, services, and components—anywhere a detailed spec exists to derive requirements, write tests, and verify compliance.

What's the difference between writing code first versus starting with a spec?

Writing code first risks deviating from requirements; spec-driven development inverts this by deriving your implementation plan and tests directly from a validated specification, ensuring every feature matches intended design and passes compliance checks.

Do I need to understand TDD before using this workflow?

The workflow guides you through the TDD cycle step by step, so prior TDD experience is not required. However, familiarity with writing automated tests and understanding the test-fail-implement-pass-refactor pattern helps you follow along more effectively.