spec-harness-plan

To turn a product spec into an architecture design document, apply a spec-driven development workflow that transforms finalized specifications into structured design.md files aligned with project standards. This ensures implementation honors existing system architecture without rebuilding components.

Spec-driven development architecture planning is the process of generating structured design artifacts from finalized product specifications. It acts as the second step after spec creation, ensuring new feature designs align with team coding standards and existing codebase patterns.

Generate design docs that align with existing system architecture by using a planning skill that checks project constitution rules and verifier constraints. This prevents redundant component rebuilds and ensures new features match established auth or payment patterns.

Yes, spec-driven development planning works without rebuilding existing components by enforcing standards alignment with the project's constitution.md. It analyzes finalized specifications to produce design artifacts that strictly honor the current system architecture.

AI-generated code breaks existing system patterns due to inconsistent architecture planning that lacks alignment with project coding standards. Without structured design documents generated from finalized specs, implementations fail to follow established codebase conventions.

A limitation of generating architecture design documents from specs is the strict dependency on finalized product specifications and a project constitution.md. Without these prerequisite inputs and ratcheted rules, the design generation cannot accurately honor existing system architecture.