https://specdd.ai/how-to/spec-writing-technique/Spec-driven development spec-writing technique guides for writing small, explicit, maintainable, reviewable specs that preserve source-of-truth context.Hugoen-ushttps://specdd.ai/how-to/spec-writing-technique/how-to-write-good-specs/https://specdd.ai/how-to/spec-writing-technique/how-to-write-good-specs/Write good SpecDD specs for spec-driven development by keeping them local, specific, outcome-focused, constraint-oriented, and reviewable for humans and agents.https://specdd.ai/how-to/spec-writing-technique/how-to-keep-specs-small-and-maintainable/https://specdd.ai/how-to/spec-writing-technique/how-to-keep-specs-small-and-maintainable/Keep SpecDD specs small and maintainable in a spec-driven development workflow by preferring local specs, avoiding inventories, delegating child behavior, and adding detail only when it helps.https://specdd.ai/how-to/spec-writing-technique/how-to-choose-the-right-spec-level/https://specdd.ai/how-to/spec-writing-technique/how-to-choose-the-right-spec-level/Choose the right SpecDD spec level for spec-driven development by matching each rule to the smallest useful root, module, feature, service, model, adapter, API, component, or job scope.https://specdd.ai/how-to/spec-writing-technique/how-to-start-from-a-minimum-viable-spec/https://specdd.ai/how-to/spec-writing-technique/how-to-start-from-a-minimum-viable-spec/Start from a minimum viable SpecDD spec for spec-driven development with Spec and Purpose, then add ownership, behavior, boundaries, tasks, scenarios, and Done when only as needed.https://specdd.ai/how-to/spec-writing-technique/how-to-name-specdd-files/https://specdd.ai/how-to/spec-writing-technique/how-to-name-specdd-files/Name SpecDD files for spec-driven development using root-spec naming, same-basename matching, optional suffixes, existing project conventions, and consistent case rules.https://specdd.ai/how-to/spec-writing-technique/how-to-place-sdd-files-in-a-repository/https://specdd.ai/how-to/spec-writing-technique/how-to-place-sdd-files-in-a-repository/Place spec-driven development .sdd files beside the code, docs, workflows, or infrastructure they govern so context is local and discoverable.https://specdd.ai/how-to/spec-writing-technique/how-to-split-a-large-spec/https://specdd.ai/how-to/spec-writing-technique/how-to-split-a-large-spec/Split a large SpecDD spec into smaller local specs for spec-driven development by identifying ownership, child behavior, repeated parent constraints, unrelated tasks, and writable scope.https://specdd.ai/how-to/spec-writing-technique/how-to-avoid-duplicating-parent-constraints-in-child-specs/https://specdd.ai/how-to/spec-writing-technique/how-to-avoid-duplicating-parent-constraints-in-child-specs/Avoid duplicating inherited SpecDD constraints in a spec-driven development workflow by writing each rule once where it is owned and relying on inherited context.https://specdd.ai/how-to/spec-writing-technique/how-to-be-explicit-in-a-spec/https://specdd.ai/how-to/spec-writing-technique/how-to-be-explicit-in-a-spec/Make SpecDD specs explicit for spec-driven development by stating behavior, constraints, non-goals, dependencies, uncertainty, and completion criteria directly.https://specdd.ai/how-to/spec-writing-technique/how-to-convert-a-feature-idea-into-a-spec/https://specdd.ai/how-to/spec-writing-technique/how-to-convert-a-feature-idea-into-a-spec/Turn a rough feature idea into a reviewed SpecDD spec for spec-driven development by defining scope, behavior, boundaries, scenarios, tasks, and open questions.https://specdd.ai/how-to/spec-writing-technique/how-to-use-specs-as-a-source-of-truth/https://specdd.ai/how-to/spec-writing-technique/how-to-use-specs-as-a-source-of-truth/Use SpecDD specs as the durable source of truth for spec-driven development behavior, boundaries, tasks, and review instead of temporary prompts or scattered tickets.https://specdd.ai/how-to/spec-writing-technique/how-to-review-a-draft-spec-before-using-it/https://specdd.ai/how-to/spec-writing-technique/how-to-review-a-draft-spec-before-using-it/Review a draft SpecDD spec before implementation in a spec-driven development workflow by checking correctness, scope, authority, ambiguity, testability, and inherited constraints.https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-edge-cases/https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-edge-cases/Write SpecDD specs for edge cases in a spec-driven development workflow, including validation failures, empty states, retries, concurrency, time zones, rate limits, permissions, and degraded services.https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-backwards-compatibility/https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-backwards-compatibility/Write spec-driven development compatibility constraints for APIs, libraries, migrations, data contracts, CLI output, and user-facing behavior.https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-performance-constraints/https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-performance-constraints/Write spec-driven development performance constraints for latency, memory, throughput, query count, bundle size, build time, and resource usage without premature over-specification.https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-observability/https://specdd.ai/how-to/spec-writing-technique/how-to-write-specs-for-observability/Write spec-driven development observability requirements for logs, metrics, traces, alerts, audit events, dashboards, and sensitive data boundaries.