speckit-brownfield-scan

Discovers a brownfield repository's technology stack, architecture and coding conventions without modifying files.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-scan-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-brownfield-scan
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-brownfield-scan
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-brownfield-scan-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an unfamiliar repository into a structured project profile so you can understand what it uses, how it is organized, and what standards already exist.

Core Features & Use Cases

  • Tech Stack Detection: Identifies languages, frameworks, package managers, build tools, and testing setup.
  • Architecture Mapping: Recognizes monolith, monorepo, layered, microservice, and frontend-backend structures.
  • Convention Discovery: Surfaces naming patterns, branch and commit styles, and governance files.
  • Use Case: Use it on a brownfield repo before planning a refactor, bootstrap, or spec-kit configuration.

Quick Start

Ask the skill to scan this repository and summarize its stack, architecture, conventions, and existing governance.

Frequently Asked Questions about speckit-brownfield-scan

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

FAQPage Schema
How do I analyze a brownfield repository to understand its tech stack and architecture?

Scanning a brownfield codebase detects its languages, frameworks, package managers, and architecture without modifying source files. It identifies monolith, monorepo, layered, or microservice structures by examining repository contents and governance files.

Can I detect coding conventions and governance files in an unfamiliar codebase?

Yes, convention discovery identifies naming patterns, commit styles, and governance files within a codebase. It surfaces existing standards so you can understand organizational rules before planning refactors or bootstrap configurations.

What is the best way to prepare a spec-kit bootstrap for a mixed-language project?

Scanning the mixed-language repository first identifies its layered architecture, build tools, and module boundaries. This generates a structured project profile that prepares the necessary foundation for spec-kit bootstrap configuration.

Does repository analysis work on subdirectories or layered applications?

Yes, brownfield scanning applies to subdirectories and layered applications. It detects module boundaries and recognizes frontend-backend structures, allowing targeted analysis of specific paths within a mixed-language codebase.

When do I need to map a project's architecture before a refactor?

You need architecture mapping before a refactor when working with an unfamiliar brownfield codebase. Recognizing monolith, monorepo, or microservice structures ensures your changes respect existing module boundaries and coding standards.