writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

writing-clearly-and-concisely

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

22

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

22

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

22

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

20

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

20

using-superpowers

More from freeacger/loom