speckit-brownfield-bootstrap

To set up spec-kit for an existing codebase, you can scan the repository to detect its real architecture and module boundaries, then generate tailored constitution, template, and agent configuration files that align with the detected conventions.

A brownfield bootstrap for spec-kit is the process of generating configuration artifacts for an existing repository. You need it when adding spec-kit to an established codebase requires tailored constitutions and templates that reflect actual project conventions before new feature work.

Yes, you can generate spec-kit templates and agent boundaries for a multi-module monorepo. The process detects bounded areas within the project and creates agent coordination rules and customized templates specific to the repository's structure.

You create a project-aware constitution by scanning the repository to identify actual naming, testing, dependency, and quality rules. This scan generates a markdown configuration file tailored to the codebase's specific architectural conventions.

Yes, spec-kit bootstrap works with inherited repositories lacking existing configuration by validating the spec-kit structure and applying architecture-aware generation to produce ready-to-use markdown configuration files for the detected stack.

The limitations of bootstrapping spec-kit for legacy codebases include the dependency on accurate repository scanning; if the existing architecture or conventions are obscured or poorly structured, the generated constitution and templates may require manual adjustment.