Generate Constitution

Derive technical principles by mapping user pain points, differentiators, and metrics from product.md to concrete architecture decisions, tech stack choices, and development constraints. This ensures every technical choice traces back to specific user value, eliminating arbitrary decisions and guaranteeing alignment between product goals and engineering choices.

A development constitution should organize principles into articles covering architecture, data, performance, security, UX, and testing. Each article includes evidence linking back to user needs, rationale explaining the principle, and verification methods. This structure ensures traceability and makes every technical constraint defensible by its source user need.

Create a derivation map that links every technical principle back to its originating user need from product.md. This traceability mechanism prevents orphaned principles, maintains alignment across the development lifecycle, and provides auditability—allowing teams to justify any architecture or tech choice by its user value.

Yes. Development principles derived from user needs generate concrete, justifiable targets—such as performance requirements (e.g., <2s dashboard load) and security standards—each tied to user pain points or differentiators. This approach replaces arbitrary benchmarks with user-driven specifications that engineering teams can implement and validate.

User needs in product.md describe what users want and why; a constitution transforms those needs into how—specific technical principles, constraints, and architecture decisions. The constitution operationalizes product strategy by creating enforceable development guidelines that every engineering choice must satisfy and trace back to.

Yes. The constitution derives entirely from product.md, which must document user needs, pain points, differentiators, and North Star metrics. Without this input, principles cannot be grounded in user value, and traceability to justify technical choices is lost.