Coding Playbooks

5. Bug Triage

• Good for: ambiguous failures and regression hunting
• Best setup: codebase access, files, and a requested verification plan
• Example prompt:

Bug triage

Investigate this bug: [symptom]. First identify likely root causes from the codebase, then propose the smallest safe fix. Call out any risky assumptions and what should be tested after the change.

6. Feature Spec To Implementation Plan

• Good for: turning product ideas into engineering work
• Best setup: existing repo plus explicit constraints
• Example prompt:

Feature plan

Take this feature request: [request]. Inspect the current codebase and produce an implementation plan that names the affected areas, the lowest-risk approach, and the edge cases I should care about before building.

7. Repo Explainer

• Good for: onboarding or understanding an unfamiliar codebase
• Best setup: repo search plus architecture summary
• Example prompt:

Repo explainer

Explain how [system or feature] works in this repository. Focus on the request flow, the main files, the user-facing behavior, and the parts I should change if I want to extend it.

8. Test Plan Builder

• Good for: reducing regressions before shipping
• Best setup: changed files plus existing tests
• Example prompt:

Test plan

Given these proposed code changes, create a focused test plan. Separate the highest-risk regressions from lower-priority checks and suggest only the tests that materially improve confidence.