spec-handover

Topics in the source

• Handing over a spec

A spec agreed in the conversation is handed over as text, and it ends there: the user creates it from the dashboard. When the user asks you to create it, run aide create " " for each spec, with the description on standard input, --depends-on for each dependency and --acceptance-not-required unless the user wants acceptance ticked. It queues the create on the board as the New spec form does. Where aide answers that the project has no board, invoke /aide-create instead. Never the board's HTTP routes, aide-create-spec by hand, or the files written directly. 1. Ask first. Raise the choices the spec depends on — thresholds, scope, dependencies on other specs — before writing the text, not as a list of open questions after it. 2. Hand over four parts, always, in this order: Prosjekt (the project the spec belongs to), Tittel, Beskrivelse and Avhengigheter (Depends on). Beskrivelse is everything the New spec form's one Description field takes: a ## Problem section saying what is wrong, a ## Solution section saying what should be true afterwards, ## Out of scope when there is one, and last ## Acceptance criteria with the - AC-n: lines, each one sentence in one of the five EARS patterns the

This is an excerpt. Refer to the complete source and its current requirements.