Seeking Feedback: Handling Bug Fixes with OpenSpec

[glitch0111]

We're currently adopting OpenSpec for feature development and have been discussing how best to handle bug fixes within the same framework.
For feature development, the standard flow of Proposal → Design → Spec → Tasks works well. However, for bug fixes, we felt that following the full process might introduce unnecessary overhead. As a result, we're experimenting with a lighter approach.
Our Current Proposal
For bugs, instead of creating all four artifacts, we're considering using only:
Spec
Tasks
In this approach:
A bug-specific spec is created to capture the issue, expected behavior, and resolution details.
Implementation tasks are generated from the spec.
The bug fix is then implemented, potentially leveraging AI-assisted development workflows.
Our assumption is that bug fixes generally have a narrower scope and therefore may not require separate Proposal and Design phases.
Looking for Community Feedback
We'd love to hear from others who are using OpenSpec:
How are you handling bug fixes?
Do you follow the full Proposal → Design → Spec → Tasks workflow for bugs?
Have you adopted a lighter process similar to what we've described?
Are there any pitfalls or best practices we should consider?
Does anyone have a different or more effective approach?
We're still in the exploration phase and would greatly appreciate feedback, challenges, alternative perspectives, or examples from your organizations and teams.
Looking forward to a productive discussion and learning from the community's experiences.
Thank you!