speckit-brownfield-bootstrap

To bootstrap Spec-Kit for an existing codebase, this tool derives conventions and architecture from a brownfield scan profile or performs an inline scan. It generates constitution rules, customized templates, and task instructions that match your real repository structure.

Setting up Spec-Kit agent boundaries in a monorepo involves generating an AGENTS.md file to define agent ownership and inter-module communication rules. This configuration applies specifically when multiple modules like frontend, backend, and shared paths are detected.

Yes, you can generate constitution rules that match detected repository reality. The process creates a constitution.md file and updates spec, plan, and task templates to reflect detected modules, tooling, and quality gates without inventing unsupported conventions.

No, the brownfield bootstrap process respects existing .specify/ customizations to avoid overwriting without asking. It confirms requirements before writing changes and derives rules strictly from the detected codebase rather than inventing new ones.

The best way to apply spec-kit templates to monorepo module paths is by using a brownfield scan profile. This tailors constitution generation, task instructions, and agent boundaries specifically to the detected frontend, backend, shared, and other module architectures.