63
stars
1
commits
Apr 9, 2026
updated
A Spec Kit extension that bootstraps Specification-Driven Development for existing codebases — auto-discover architecture, generate a tailored constitution, and incrementally migrate features into the SDD workflow.
Spec Kit's specify init creates generic templates that don't fit established projects. Teams with existing codebases face friction adopting SDD:
The Brownfield Bootstrap extension adds four commands for adopting spec-kit in existing projects:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.brownfield.scan | Auto-discover project structure, tech stack, frameworks, and architecture patterns | No — read-only |
/speckit.brownfield.bootstrap | Generate spec-kit configuration tailored to the existing codebase | Yes — creates/updates constitution, templates, AGENTS.md |
/speckit.brownfield.validate | Verify bootstrap output matches actual project structure and conventions | No — read-only |
/speckit.brownfield.migrate | Incrementally adopt SDD for existing features with reverse-engineered specs | Yes — creates spec.md, plan.md, tasks.md for existing features |
specify extension add --from https://github.com/Quratulain-bilal/spec-kit-brownfield/archive/refs/tags/v1.0.0.zip
/speckit.brownfield.scan analyzes your codebase to build a project profile:
Project Profile
├── Tech Stack: TypeScript (68%), Python (32%)
├── Frontend: React 18, Vite, TailwindCSS
├── Backend: FastAPI, SQLAlchemy, PostgreSQL
├── Architecture: Frontend + Backend (separated)
├── Modules: client/, server/, shared/
├── Testing: Jest (frontend), pytest (backend)
├── CI/CD: GitHub Actions
├── Branch Pattern: feat/*, fix/*, chore/*
└── Conventions: kebab-case (frontend), snake_case (backend)
/speckit.brownfield.bootstrap generates spec-kit configuration from the profile:
/speckit.brownfield.validate checks that configuration matches reality:
/speckit.brownfield.migrate brings existing features into SDD:
specify init ← Initialize spec-kit (if not already done)
│
▼
/speckit.brownfield.scan ← Discover tech stack and architecture
│
▼
/speckit.brownfield.bootstrap ← Generate tailored configuration
│
▼
/speckit.brownfield.validate ← Verify configuration accuracy
│
▼
/speckit.brownfield.migrate ← Bring existing features into SDD
│
▼
/speckit.specify ← Start new features with project-aware templates
| Type | Detection |
|---|---|
| Monolith | Single source tree, one entry point |
| Monorepo | Workspace config, packages/ or apps/ directories |
| Microservices | Multiple Dockerfiles, service directories |
| Frontend + Backend | Separate client//server/ directories |
| Library/Package | setup.py, lib/ directory, published package config |
| Category | Detected |
|---|---|
| Languages | TypeScript, JavaScript, Python, Go, Java, Rust, C#, Ruby, PHP |
| Frontend | React, Vue, Angular, Svelte, Next.js, Nuxt |
| Backend | Express, FastAPI, Django, Spring, Rails, Gin, ASP.NET |
| Databases | PostgreSQL, MySQL, MongoDB, SQLite, Redis |
| Package managers | npm, yarn, pnpm, pip, Poetry, Go modules, Cargo, Maven, Gradle |
| CI/CD | GitHub Actions, GitLab CI, CircleCI, Jenkins |
| Testing | Jest, pytest, Go test, JUnit, RSpec, PHPUnit |
The extension registers an optional hook:
specify init to auto-detect conventionsstatus: migrated to distinguish from fresh specsMIT
1 commits
63
stars
1
commits
Apr 9, 2026
updated
A Spec Kit extension that bootstraps Specification-Driven Development for existing codebases — auto-discover architecture, generate a tailored constitution, and incrementally migrate features into the SDD workflow.
Spec Kit's specify init creates generic templates that don't fit established projects. Teams with existing codebases face friction adopting SDD:
The Brownfield Bootstrap extension adds four commands for adopting spec-kit in existing projects:
| Command | Purpose | Modifies Files? |
|---|---|---|
/speckit.brownfield.scan | Auto-discover project structure, tech stack, frameworks, and architecture patterns | No — read-only |
/speckit.brownfield.bootstrap | Generate spec-kit configuration tailored to the existing codebase | Yes — creates/updates constitution, templates, AGENTS.md |
/speckit.brownfield.validate | Verify bootstrap output matches actual project structure and conventions | No — read-only |
/speckit.brownfield.migrate | Incrementally adopt SDD for existing features with reverse-engineered specs | Yes — creates spec.md, plan.md, tasks.md for existing features |
specify extension add --from https://github.com/Quratulain-bilal/spec-kit-brownfield/archive/refs/tags/v1.0.0.zip
/speckit.brownfield.scan analyzes your codebase to build a project profile:
Project Profile
├── Tech Stack: TypeScript (68%), Python (32%)
├── Frontend: React 18, Vite, TailwindCSS
├── Backend: FastAPI, SQLAlchemy, PostgreSQL
├── Architecture: Frontend + Backend (separated)
├── Modules: client/, server/, shared/
├── Testing: Jest (frontend), pytest (backend)
├── CI/CD: GitHub Actions
├── Branch Pattern: feat/*, fix/*, chore/*
└── Conventions: kebab-case (frontend), snake_case (backend)
/speckit.brownfield.bootstrap generates spec-kit configuration from the profile:
/speckit.brownfield.validate checks that configuration matches reality:
/speckit.brownfield.migrate brings existing features into SDD:
specify init ← Initialize spec-kit (if not already done)
│
▼
/speckit.brownfield.scan ← Discover tech stack and architecture
│
▼
/speckit.brownfield.bootstrap ← Generate tailored configuration
│
▼
/speckit.brownfield.validate ← Verify configuration accuracy
│
▼
/speckit.brownfield.migrate ← Bring existing features into SDD
│
▼
/speckit.specify ← Start new features with project-aware templates
| Type | Detection |
|---|---|
| Monolith | Single source tree, one entry point |
| Monorepo | Workspace config, packages/ or apps/ directories |
| Microservices | Multiple Dockerfiles, service directories |
| Frontend + Backend | Separate client//server/ directories |
| Library/Package | setup.py, lib/ directory, published package config |
| Category | Detected |
|---|---|
| Languages | TypeScript, JavaScript, Python, Go, Java, Rust, C#, Ruby, PHP |
| Frontend | React, Vue, Angular, Svelte, Next.js, Nuxt |
| Backend | Express, FastAPI, Django, Spring, Rails, Gin, ASP.NET |
| Databases | PostgreSQL, MySQL, MongoDB, SQLite, Redis |
| Package managers | npm, yarn, pnpm, pip, Poetry, Go modules, Cargo, Maven, Gradle |
| CI/CD | GitHub Actions, GitLab CI, CircleCI, Jenkins |
| Testing | Jest, pytest, Go test, JUnit, RSpec, PHPUnit |
The extension registers an optional hook:
specify init to auto-detect conventionsstatus: migrated to distinguish from fresh specsMIT
1 commits