test-driven-development
This skill implements the red-green-refactor cycle for test-driven development, guiding developers through writing failing tests first, implementing minimal code to pass them, then refactoring while maintaining test coverage. Use it when building new features to ensure code quality, maintainability, and comprehensive test coverage from the start.
git clone --depth 1 https://github.com/ArchieIndian/openclaw-superpowers /tmp/test-driven-development && cp -r /tmp/test-driven-development/skills/core/test-driven-development ~/.claude/skills/test-driven-developmentSKILL.md
# Test-Driven Development ## The Cycle ### Red Write a test that describes the behavior you want. Run it. It should fail. ### Green Write the minimum code to make the test pass. ### Refactor Make the code good. Tests must still pass. ## Test Quality A good test: - Tests behavior, not implementation - Has one clear assertion - Has a descriptive name - Is independent - Is fast
Syncs agent daily memory and MEMORY.md to an Obsidian vault so notes are human-browsable. Use nightly or on demand.
Structured ideation before any implementation. Use when starting any non-trivial task.
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
Executes plans task-by-task with verification. Use when implementing a plan.
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
Crawls a new codebase to infer stack, conventions, and key invariants, then generates a PROJECT.md context file for the agent
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
Detects skill name shadowing and description-overlap conflicts that cause OpenClaw to trigger the wrong skill or silently ignore one when two skills compete for the same intent.