test-driven-development

test-driven-development: Que hace este skill

test-driven-development is a reusable agent skill listed on skills.sh under obra/superpowers. skills.sh rank #127, installs 82.1K, GitHub stars 204.9K, first seen Jan 19, 2026.

Write tests first, watch them fail, then implement minimal code to pass. Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green Requires deleting any production code written before tests exist; no exceptions for "reference" or "adaptation" Emphasizes watching tests fail as proof they actually test the right thing; tests that pass immediately prove nothing Covers common rationalizations (testing after, manual verification, sunk cost) with concrete rebuttals and a verification checklist to confirm TDD was followed

Cuando usarlo

• Use this skill when the task matches the package name, repository context, or skills.sh topic: Agent workflows Testing.
• Prefer it when a repeatable workflow is better than a one-off prompt: setup, review, design, deployment, automation, research, media generation, or operational checks.
• For production work, read the linked repository and install command before allowing the agent to run scripts or modify files.

Como debe usarlo un agente

1. Confirm the user intent and whether this skill is the right fit.
2. Install or inspect the skill with the official command from skills.sh.
3. Read the local SKILL.md and only load extra files referenced by that skill.
4. Follow the skill's workflow, then verify the result with tests, screenshots, audits, or source-backed checks as appropriate.
5. Record any constraints, missing credentials, tool permissions, or security warnings before handoff.

Controles de calidad y seguridad

• Check repository ownership and source reputation: obra/superpowers.
• Review security audit signals before installing; skills.sh reports: Gen Agent Trust Hub Pass Socket Pass Snyk Pass.
• Never grant broad shell, browser, cloud, or deployment permissions without user approval.
• Treat generated output as draft until validated by the skill's own acceptance criteria.
• If the skill touches cloud resources, costs, credentials, customer data, or production deploys, require a human review step.

Fuentes e instalacion

• skills.sh page: https://www.skills.sh/obra/superpowers/test-driven-development
• Repository: https://github.com/obra/superpowers
• Install command: npx skills add https://github.com/obra/superpowers --skill test-driven-development

FAQ

Is test-driven-development an agent, a prompt, or a skill?
It is a skill: a reusable package of task-specific instructions and supporting files that an agent can load when the user's request matches the workflow.

Should I install it automatically?
Only after checking the repository, install command, audit status, and whether the user wants this capability in the current agent environment.

What makes it useful for AIDreamHub users?
It helps users discover practical agent capabilities from the open skills ecosystem and compare them by task, source, install count, and operational risk.