tdd
Test-Driven Development
Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Cycle
RED — Write a failing test
Write a test that defines the expected behavior BEFORE writing any production code.
- The test MUST fail before you write production code
- If the test passes without any changes, your test is wrong — rewrite it
- The test should describe behavior, not implementation
GREEN — Write the minimum production code
Write the minimum production code to make the test pass.
- Do NOT write more than necessary
- Do NOT optimize
- Do NOT refactor
- Ugly code that passes is correct at this stage
More from scando1993/sugar
worktree
Git worktree lifecycle management. Use when creating, navigating, syncing, or cleaning up git worktrees for parallel development.
12ralph
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json.
12respond-review
Guidance for receiving and responding to code review feedback. Use when addressing PR review comments, incorporating reviewer suggestions, or managing review discussions.
12debug
Systematic debugging with hypothesis-driven investigation. Use when diagnosing bugs, errors, or unexpected behavior. Phases: Reproduce, Hypothesize, Investigate, Fix, Verify, Regression.
11prd
Generate a Product Requirements Document for a feature. Use when planning a feature, starting a project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
11finish
Branch finishing and PR preparation. Use when completing a feature branch, preparing a pull request, or cleaning up commit history.
11