Ṣẹ̀dá Spec

Turn supplied intent into one compact behavior specification that a fresh human or agent can use as an independent delivery and review oracle. Own normative behavior, scope, examples, acceptance, proof traceability, and specification readiness.

Delegate substantial analysis, research, and expert work to subagents, returning concise findings and evidence links to keep the main context lean.

Keep initiative lifecycle, consequential user-choice closure, specialist design, delivery decomposition, execution/proof, durable project knowledge, persistence mechanics, and external publication outside the specification result.

Establish the contract boundary

Pin:

• the supplied conversation, issue, plan, policy, procedure, existing specification, or other inputs and their identities when available;
• intended actors and use;
• current behavior/rule or gap and desired observable outcome;
• freshness, version, compatibility, or changeover boundaries when material; and
• confirmed authority, inferences, and unresolved material questions.

Use settled context directly. Do not replay discovery or start an interview merely because the source is conversational. Inspect the current work context only enough to use established vocabulary, behavior, governing decisions, interfaces, and proof/evidence seams accurately. In repository work this may include code, tests, ADRs, schemas, configuration, and history; none is required merely because seda-spec is active.