https://specdd.ai/how-to/getting-started/Beginner SpecDD how-to guides for starting spec-driven development, writing your first .sdd spec, and running a first spec-driven change.Hugoen-ushttps://specdd.ai/how-to/getting-started/how-to-start-with-spec-driven-development/https://specdd.ai/how-to/getting-started/how-to-start-with-spec-driven-development/Learn how to start with spec-driven development by writing intent before implementation, keeping specs near the work, and reviewing changes against a local contract.https://specdd.ai/how-to/getting-started/how-to-use-spec-driven-development-with-humans-and-agents/https://specdd.ai/how-to/getting-started/how-to-use-spec-driven-development-with-humans-and-agents/Learn how to use spec-driven development with humans and agents by keeping intent, ownership, boundaries, and completion criteria in local specs.https://specdd.ai/how-to/getting-started/how-to-move-from-vibe-coding-to-spec-driven-development/https://specdd.ai/how-to/getting-started/how-to-move-from-vibe-coding-to-spec-driven-development/Learn how to move from vibe coding to spec-driven development by turning vague prompts into local specs, bounded changes, and reviewable implementation contracts.https://specdd.ai/how-to/getting-started/how-to-use-specdd-in-10-minutes/https://specdd.ai/how-to/getting-started/how-to-use-specdd-in-10-minutes/Use spec-driven development in 10 minutes by installing the CLI, initializing a project, adding a root spec, writing one local .sdd file, and prompting an agent for a small change.https://specdd.ai/how-to/getting-started/how-to-write-your-first-sdd-spec/https://specdd.ai/how-to/getting-started/how-to-write-your-first-sdd-spec/Write your first SpecDD .sdd spec for spec-driven development by choosing a local target, defining purpose, ownership, requirements, boundaries, completion criteria, and one scenario.https://specdd.ai/how-to/getting-started/how-to-run-your-first-spec-driven-change-end-to-end/https://specdd.ai/how-to/getting-started/how-to-run-your-first-spec-driven-change-end-to-end/Run your first spec-driven development change end to end by defining behavior, adding completion criteria, prompting the task, implementing, testing, and reviewing against the spec.https://specdd.ai/how-to/getting-started/how-to-choose-your-first-specdd-use-case/https://specdd.ai/how-to/getting-started/how-to-choose-your-first-specdd-use-case/Choose your first spec-driven development use case by picking a small, valuable, local change where written intent, boundaries, and verification will reduce ambiguity.https://specdd.ai/how-to/getting-started/how-to-know-when-you-do-not-need-a-spec/https://specdd.ai/how-to/getting-started/how-to-know-when-you-do-not-need-a-spec/Learn when you do not need a SpecDD spec for spec-driven development, including trivial edits, throwaway prototypes, obvious local changes, and experiments without durable intent.https://specdd.ai/how-to/getting-started/how-to-use-basic-specdd-levels/https://specdd.ai/how-to/getting-started/how-to-use-basic-specdd-levels/Learn how to use basic SpecDD levels for spec-driven development, such as root, module, feature, model, component, and policy specs, without turning level names into rigid rules.https://specdd.ai/how-to/getting-started/how-to-link-existing-docs-and-content-with-specdd/https://specdd.ai/how-to/getting-started/how-to-link-existing-docs-and-content-with-specdd/Link existing docs, ADRs, runbooks, product notes, and content folders with spec-driven development by mapping them in bootstrap.project.md and referencing local context from .sdd specs.https://specdd.ai/how-to/getting-started/how-to-enforce-and-document-local-code-style-and-conventions/https://specdd.ai/how-to/getting-started/how-to-enforce-and-document-local-code-style-and-conventions/Document code style enforcement for spec-driven development in .specdd/bootstrap.project.md with formatter, lint, test, generated-file, dependency, and style-doc rules.