test-driven-development

Use when creating or editing an aimee skill.

Use when diagnosing a failure, flaky behavior, or unexpected output before attempting a fix.

Use when a bounded subtask is summarization, mechanical review, fixture inspection, proposal triage, verification, or boilerplate.

Use when locating where a symbol, function, type, command, or constant is defined or referenced, instead of grep/find/read chains.

Use when you need a project fact, document, relationship, investigation note, or prior finding that may already be captured.

Use when deciding whether a task matches an available skill before starting work.

Use when tempted to add broad abstractions, future-proofing, or extra product surface beyond the requested change.

Use when waiting for servers, jobs, files, tests, queues, or external processes.

Use when evaluating reviewer feedback, review delegates, or suggested code changes.

Use before claiming work is done, fixed, passing, complete, or ready to merge.

Use before asking the user about infrastructure, preferences, conventions, prior decisions, or past incidents.