project-init

Project initialization for a new workspace involves auto-detecting the repository structure and applying standard configurations. The process generates a .specs-fire directory containing state.yaml and constitution files to establish baseline rules and reduce configuration drift.

Yes, you can set up FIRE standards in a brownfield repository. The initialization process auto-detects existing workspace structures and infers the tech stack to generate appropriate universal and module-specific standards safely alongside your current codebase.

Workspace detection for monorepos works by scanning the repository to identify multiple modules and inferring their individual tech stacks. It then generates per-module standards alongside a universal constitution within the .specs-fire directory to manage structure-specific rules.

Initializing a FIRE project generates a .specs-fire directory containing a state.yaml file and a universal constitution. For monorepo structures, it also produces per-module standards files to define specific configurations for each detected workspace segment.

A universal constitution in project setup is a generated standards document that defines baseline rules across an entire repository. It is produced within the .specs-fire directory to maintain configuration consistency and kickstart intent-driven planning flows.

No dependencies are required to apply FIRE standards to your repository. The initialization process runs directly on your workspace, auto-detecting the tech stack and structure to produce the .specs-fire configuration files without needing external packages or tools.