sdd-constitution

You can define project principles by generating a constitution document that establishes foundational standards. This skill scans your project files, asks targeted questions, and writes the finalized principles to a markdown file for consistent adherence throughout the project lifecycle.

A project constitution is a foundational document outlining non-negotiable software development standards like type-checking rules or security response times. You need it when starting a new project to ensure consistency and adherence to standards across the codebase.

To generate a constitution markdown file, the skill scans your existing project files to infer the tech stack and tooling. It then asks targeted questions to fill gaps, confirms details with you, and writes the final principles to the memory directory.

Yes, you can create project documentation without manual tech stack input because the skill is contextually aware. It automatically scans your project files to infer tooling and frameworks, then refines the gathered context through user-guided questions.

The best way to establish coding standards is by creating a project constitution that defines guiding principles early. This ensures all team members understand non-negotiable requirements like type-checking mandates or vulnerability resolution timelines from the beginning.

No dependencies are required to generate a project constitution. The skill operates independently by reading your project structure, interacting with you for clarification, and writing the final markdown document directly into your project directory.