<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spec-driven workflows | SpecDD</title><link>https://specdd.ai/how-to/spec-driven-workflows/</link><description>Spec-driven development workflow guides for running the spec-first loop, drafting specs with AI, syncing specs with code, resolving conflicts, and evolving behavior safely.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://specdd.ai/how-to/spec-driven-workflows/index.xml" rel="self" type="application/rss+xml"/><item><title>How to run the spec-first loop</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-run-the-spec-first-loop/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-run-the-spec-first-loop/</guid><description>Run the SpecDD spec-first loop for spec-driven development by writing or updating the local spec, reviewing it, implementing a bounded task, checking the result, and keeping code and specs aligned.</description></item><item><title>How to draft specs automatically with AI, then review</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-draft-specs-automatically-with-ai-then-review/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-draft-specs-automatically-with-ai-then-review/</guid><description>Draft SpecDD specs with AI for spec-driven development by generating a first pass from code or a feature idea, marking assumptions, reviewing boundaries, and approving before implementation.</description></item><item><title>How to implement one spec at a time</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-implement-one-spec-at-a-time/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-implement-one-spec-at-a-time/</guid><description>Implement one SpecDD spec at a time in a spec-driven development workflow by choosing a local contract, confirming writable scope, completing one task or behavior, verifying it, and avoiding multi-area drift.</description></item><item><title>How to keep specs in sync with code changes</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-keep-specs-in-sync-with-code-changes/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-keep-specs-in-sync-with-code-changes/</guid><description>Keep SpecDD specs in sync with code in a spec-driven development workflow by updating behavior, tasks, scenarios, and completion criteria in the same changeset as implementation changes.</description></item><item><title>How to recover from spec-code drift</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-recover-from-spec-code-drift/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-recover-from-spec-code-drift/</guid><description>Recover from SpecDD spec-code drift in a spec-driven development workflow by pausing new edits, comparing specs to implementation, choosing the intended contract, and updating code, tests, and specs.</description></item><item><title>How to configure team rules in bootstrap.project.md</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-configure-team-rules-in-bootstrap-project-md/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-configure-team-rules-in-bootstrap-project-md/</guid><description>Configure shared spec-driven development team rules in .specdd/bootstrap.project.md for commands, code style, naming, syntax choices, documentation locations, and project workflow conventions.</description></item><item><title>How to configure personal preferences in bootstrap.local.md</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-configure-personal-preferences-in-bootstrap-local-md/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-configure-personal-preferences-in-bootstrap-local-md/</guid><description>Configure personal spec-driven development preferences in .specdd/bootstrap.local.md without weakening shared project rules, committing local settings, or changing spec authority.</description></item><item><title>How to resolve conflicts between specs</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-resolve-conflicts-between-specs/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-resolve-conflicts-between-specs/</guid><description>Resolve SpecDD spec conflicts in a spec-driven development workflow by reading the effective chain, applying stricter constraints, preserving Must not and Forbids, and requesting decisions.</description></item><item><title>How to reference another area's spec safely</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-reference-another-areas-spec-safely/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-reference-another-areas-spec-safely/</guid><description>Reference another spec-driven development area's spec safely by using explicit References or Can read entries for context while preserving local write authority and sibling boundaries.</description></item><item><title>How to change a spec safely after code already exists</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-change-a-spec-safely-after-code-already-exists/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-change-a-spec-safely-after-code-already-exists/</guid><description>Change an existing SpecDD spec safely in a spec-driven development workflow by comparing current code, deciding intended behavior, updating the owning spec, and aligning implementation, checks, and task status.</description></item><item><title>How to deprecate behavior with SpecDD</title><link>https://specdd.ai/how-to/spec-driven-workflows/how-to-deprecate-behavior-with-specdd/</link><guid>https://specdd.ai/how-to/spec-driven-workflows/how-to-deprecate-behavior-with-specdd/</guid><description>Deprecate behavior with spec-driven development by documenting the transition in existing sections, preserving required compatibility, blocking new usage, and tracking removal tasks.</description></item></channel></rss>