https://specdd.ai/how-to/use-spec-sections/Spec-driven development section guides for Spec, Platform, Purpose, Structure, ownership, requirements, contracts, tasks, Done when, scenarios, examples, comments, paths, and globs.Hugoen-ushttps://specdd.ai/how-to/use-spec-sections/how-to-write-the-spec-section/https://specdd.ai/how-to/use-spec-sections/how-to-write-the-spec-section/Write the Spec section in a SpecDD .sdd file by naming the subject, placing it first, using an inline value, and keeping body text out of the section.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-platform-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-platform-section/Use the Platform section in SpecDD when language, runtime, framework, or environment context materially affects implementation or review.https://specdd.ai/how-to/use-spec-sections/how-to-write-the-purpose-section/https://specdd.ai/how-to/use-spec-sections/how-to-write-the-purpose-section/Write the Purpose section in SpecDD as a short implementation-neutral statement of why the specified subject exists.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-structure-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-structure-section/Use the Structure section in SpecDD to describe local files and directories at a useful level without turning specs into full inventories.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-owns-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-owns-section/Use the Owns section in SpecDD to declare the files, directories, symbols, concepts, or responsibilities governed by a spec.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-can-modify-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-can-modify-section/Use the Can modify section in SpecDD to define the files or paths that may be changed under a local spec.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-can-read-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-can-read-section/Use the Can read section in SpecDD to give files, specs, or docs as read-only context without granting edit permission.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-references-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-references-section/Use the References section in SpecDD for explicit related specs, contracts, symbols, or context without granting inherited authority.https://specdd.ai/how-to/use-spec-sections/how-to-write-must-rules/https://specdd.ai/how-to/use-spec-sections/how-to-write-must-rules/Write SpecDD Must rules as specific, outcome-focused requirements that describe required behavior without vague goals or implementation clutter.https://specdd.ai/how-to/use-spec-sections/how-to-write-must-not-rules/https://specdd.ai/how-to/use-spec-sections/how-to-write-must-not-rules/Write SpecDD Must not rules for plausible local boundaries, non-goals, and forbidden behavior without creating unrelated negative lists.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-forbids-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-forbids-section/Use the Forbids section in SpecDD to block dependencies, paths, modules, libraries, tools, or access patterns.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-depends-on-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-depends-on-section/Use the Depends on section in SpecDD to list allowed dependencies, collaborators, contracts, symbols, paths, or required context.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-exposes-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-exposes-section/Use the Exposes section in SpecDD to list public exports, endpoints, commands, components, events, interfaces, or observable capabilities.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-accepts-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-accepts-section/Use the Accepts section in SpecDD to document accepted inputs, request shapes, parameters, preconditions, or input states.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-returns-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-returns-section/Use the Returns section in SpecDD to document returned values, response shapes, result states, generated files, exit codes, or other observable outputs.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-raises-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-raises-section/Use the Raises section in SpecDD to document errors, exceptions, rejected states, or failure conditions a subject may raise or return.https://specdd.ai/how-to/use-spec-sections/how-to-use-the-handles-section/https://specdd.ai/how-to/use-spec-sections/how-to-use-the-handles-section/Use the Handles section in SpecDD to document cases, events, states, branches, errors, or conditions the subject must handle.https://specdd.ai/how-to/use-spec-sections/how-to-write-tasks/https://specdd.ai/how-to/use-spec-sections/how-to-write-tasks/Write SpecDD Tasks with valid task markers, optional IDs, local work scope, and status updates only after verification.https://specdd.ai/how-to/use-spec-sections/how-to-write-done-when/https://specdd.ai/how-to/use-spec-sections/how-to-write-done-when/Write SpecDD Done when criteria that define concrete completion signals for implementation, review, and verification.https://specdd.ai/how-to/use-spec-sections/how-to-write-scenario-blocks/https://specdd.ai/how-to/use-spec-sections/how-to-write-scenario-blocks/Write SpecDD Scenario blocks with named behavioral examples using Given, When, Then, And, and But steps.