Issue Crafting
Domain skill for creating high-quality GitHub issues that describe what should happen without prescribing how.
Iron Law
ISSUES DESCRIBE OUTCOMES, NEVER IMPLEMENTATIONS. If the issue says "how," rewrite it.
The moment an issue prescribes a method, it constrains the solution space and biases the implementer.
Solution-Agnostic Principles
Issues must describe outcomes, not implementations:
- Good: "Users can reset their password via email"
- Bad: "Add a rese
[Description truncada. Veja o README completo no GitHub.]