Keep the Brief focused on what the team will deliver while the Spec holds the architecture and implementation decisions needed to deliver it.
A Brief is the lean, business-facing account of what the team will deliver and why. Its Technical Spec is the engineering space for how that work can be implemented before Plan generation.
The separation keeps product intent readable while giving engineering decisions enough room. The Spec stays connected to the Brief and carries its settled technical direction into the Plan.
Open the Spec from a Brief to review the proposed technical approach. Hamster identifies open technical questions and presents decisions that need direction before the work can be planned.
Review the options and record the chosen direction in the Spec. The Spec can reuse decisions settled in related work instead of asking the same open questions again.
When an accepted edit changes the Brief, the Spec stays current with the revised intent. When the technical direction is ready, generate the Plan from the Brief and its Spec.
Accepted Brief edits update the product intent that the Spec supports.
The Plan turns the Brief and its Spec into executable Tasks.