Framework Issue Format¶
Framework issues should be execution-ready.
Do not file vague complaints.
Required Fields¶
- title
- category
- summary
- observed friction
- observed quality signals
- why this is a framework problem
- session evidence
- desired behavior
- solution direction
- acceptance criteria
- related docs, commands, skills, or templates
- related issues or duplicates
- agent-ready implementation notes
Writing Rules¶
- describe the user pain concretely
- describe the quality failure concretely when one was observed
- keep the target fix scoped
- point to likely repo areas when known
- separate evidence from speculation
- make the acceptance criteria testable