AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Test Driven Development

skill-a5c-ai-babysitter-test-driven-development · by a5c-ai

Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-a5c-ai-babysitter-test-driven-development

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-a5c-ai-babysitter-test-driven-development)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Test Driven Development? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Test-Driven Development

Overview

Enforces the TDD discipline in all CC10X BUILD workflows. The RED-GREEN-REFACTOR cycle is mandatory and cannot be skipped or deferred.

TDD Cycle

  1. RED: Write failing test first. Run with CI=true npm test or --run flag. Exit code MUST be 1.
  2. GREEN: Write minimal code to make test pass. Exit code MUST be 0.
  3. REFACTOR: Clean up implementation while keeping tests green. Exit code MUST remain 0.

Non-Negotiable Rules

  • Always use run mode (CI=true npm test or --run flag)
  • NEVER use watch mode (prevents hanging processes)
  • Use timeout guards (timeout 60s) as backup
  • Record exit codes as evidence at each phase
  • If tests fail 3 consecutive times in GREEN, report failure status
  • Never skip RED phase (failing test must exist before implementation)
  • Never defer tests to "later" -- TDD means tests first

Scope Discipline

  • If implementation requires >3 file changes, flag for scope review
  • Architectural choices require user approval unless pre-approved in plan
  • New dependencies require user approval

When to Use

  • Every feature implementation in BUILD workflow
  • Every bug fix in DEBUG workflow (regression test)

Agents Used

  • component-builder (primary consumer)
  • bug-investigator (regression tests)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.