speckit-brownfield-bootstrap

Name: speckit-brownfield-bootstrap
Availability: InStock
Author: Numu

Generate spec-kit bootstrap artifacts for existing brownfield repositories.

2|Updated Jan 6, 2026

Search Tags:#templates #agents #constitution #brownfield #spec-kit #bootstrap

Ready to run

npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-bootstrap-numu-io

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-brownfield-bootstrap
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-brownfield-bootstrap
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-bootstrap-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you bootstrap spec-kit configuration for an existing repository by detecting the real architecture, conventions, and module boundaries instead of relying on generic templates.

Core Features & Use Cases

Project-Aware Constitution: Creates a tailored constitution that reflects the codebase’s actual naming, testing, dependency, and quality rules.
Template Customization: Adapts spec, plan, and task templates to the repository’s stack, structure, and workflows.
Multi-Module Support: Generates agent boundaries and coordination rules when the project has multiple modules or bounded areas.
Use Case: A team inheriting a brownfield FastAPI monorepo can use this Skill to turn the repo into a spec-kit-ready environment before writing new specs or features.

Quick Start

Use the speckit-brownfield-bootstrap skill to scan this repository and generate a spec-kit constitution, customized templates, and agent boundaries for the existing codebase.

Frequently Asked Questions about speckit-brownfield-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up spec-kit for an existing codebase instead of starting from scratch?▼

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.

What is a brownfield bootstrap for spec-kit and when do I need it?▼

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.

Can I generate spec-kit templates and agent boundaries for a multi-module monorepo?▼

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.

How do I create a project-aware constitution that matches my repository's coding conventions?▼

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.

Does spec-kit bootstrap work with inherited repositories that have no existing configuration?▼

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.

What are the limitations of bootstrapping spec-kit configuration for legacy codebases?▼

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.