Add discovery step to /plan-issues skill #29
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
During vision/milestone/issue planning for Arcadia, we jumped from milestones directly to issues without understanding user workflows first.
Problem / Observation
The /plan-issues skill goes straight from 'understand the feature' to 'break down the work' without a formal discovery phase. This led to proposing issues 'out of thin air' that had to be reworked.
Suggested Improvement
Add a discovery step between understanding the feature and breaking down work:
Affected Files