Turn a feature idea into user stories with acceptance criteria and risky assumptions
Load the parent idea, project goals, related entities — solutions, segments, hypotheses — and existing specs to understand what is already decided before writing anything.
Articulate the motivation for this change and the specific metric or outcome it is intended to move, anchored to the team current OKRs.
Describe what exists today and what is broken or missing, then describe the proposed solution with enough precision for engineering to estimate and start.
For every non-obvious choice, record why this option was chosen and what alternatives were rejected. This section is what makes the spec useful months later.