103 件 ・ 関連度順
概要と使いどころ
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
日本語の概要は準備中です。原文の説明を表示しています。
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development workflow with Red-Green-Refactor cycle across languages
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.
日本語の概要は準備中です。原文の説明を表示しています。
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
日本語の概要は準備中です。原文の説明を表示しています。
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
日本語の概要は準備中です。原文の説明を表示しています。
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
日本語の概要は準備中です。原文の説明を表示しています。
Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.
日本語の概要は準備中です。原文の説明を表示しています。
Red-green-refactor scaffold for building new features with TDD. Write failing tests first, then implement to pass. Use when building new features test-first.
日本語の概要は準備中です。原文の説明を表示しています。
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
日本語の概要は準備中です。原文の説明を表示しています。
Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
日本語の概要は準備中です。原文の説明を表示しています。
Guides quality-first TDD for new behavior, bug fixes, and test changes. Selects the smallest test layer, proves a distinct regression risk, and runs bounded RED-GREEN-REFACTOR verification.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development workflow with philosophy guide - plan → write tests → implement → validate
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
测试驱动开发。当用户想以测试先行构建功能或修复 bug、提到 "red-green-refactor"，或想要集成测试时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Use when Java implementation work should be guided by Test-Driven Development, including maintaining a test list, choosing the next behavior, writing a failing test first, implementing only enough production code to pass, and refactoring while keeping tests green. This should trigger for requests such as Apply TDD; Use test-driven development; Drive this Java change with tests; Write the failing test first; Red-green-refactor this feature. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
Run complete TDD red-green-refactor cycle for a test
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development for substantive feature, bug-fix, and behavior-changing work. Use automatically when implementing features, fixing bugs, or changing behavior (red → green → refactor). Also use when the user mentions TDD, /tdd, /TDD, or red-green-refactor. Do not use for documentation-only, formatting-only, exact generated-mirror, or provenance-only changes.
日本語の概要は準備中です。原文の説明を表示しています。
TDD: enforce RED-GREEN-REFACTOR, tests before code.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD," "dev-QA pairing," "definition of done," "testability," "quality culture," "QA in sprint planning." Not for: writing the unit tests themselves — use unit-testing; automated PR test-quality review at scale — use ai-qa-review; multi-quarter QA direction or roadmap — use test-strategy. Related: unit-testing, ai-qa-review, test-strategy.
日本語の概要は準備中です。原文の説明を表示しています。