implement

Implement story contracts via test-first red/green/refactor workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mbaho10/claude-code-skills-9arm-workspace --skill implement-mbaho10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/mbaho10/claude-code-skills-9arm-workspace/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/mbaho10/claude-code-skills-9arm-workspace --skill implement-mbaho10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a story plus a contract into working, tested code. The discipline ensures tests drive the implementation, guarding against changing an agreed API and ensuring a complete, green suite before declaring done.

Core Features & Use Cases

  • Test-first discipline drives development: write the failing test before code.
  • Contract adherence ensures APIs and cross-boundary boundaries remain stable.
  • Red/Green/Refactor workflow guides incremental, safe delivery with continuous validation.

Quick Start

Describe the acceptance criteria, write the failing test, implement the minimal code to make it pass, and run the full test suite to confirm all tests pass.

Frequently Asked Questions about implement

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

FAQPage Schema
What is test-first development and how does it enforce contract adherence?

Test-first development requires writing failing tests before implementation code, enforcing contract adherence by validating APIs and cross-boundary boundaries before declaring a story done.

How do I turn acceptance criteria into working tested code?

Describe the acceptance criteria, write a failing test, implement minimal code to pass it, and run the full test suite to validate contract adherence and confirm all tests are green.

Can I use this workflow for both frontend and backend development?

Yes, this test-first workflow applies to frontend and backend development where acceptance criteria exist and cross-boundary contracts must be honored across the stack.

Why does my test suite need to pass completely before declaring a story done?

Running the full test suite ensures complete green validation, guarding against breaking existing functionality or changing an agreed API before the implementation is declared done.

What is the red/green/refactor workflow for incremental code delivery?

The red/green/refactor workflow guides incremental delivery by writing a failing test, implementing minimal passing code, and refactoring safely with continuous test suite validation.