speckit-brownfield-scanlisted

# Scan Project Analyze an existing codebase to discover its technology stack, architecture patterns, module structure, and coding conventions. This produces a project profile that the bootstrap command uses to generate tailored spec-kit configuration. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). The user may specify a subdirectory to scan (e.g., "backend/"), a focus area (e.g., "only frontend"), or request a specific depth of analysis. ## Prerequisites 1. Verify the current directory is a git repository 2. Verify this is an existing project with source code (not an empty repo) ## Outline 1. **Detect tech stack**: Identify languages, frameworks, and tools by scanning: | Signal | What to Check | |--------|--------------| | **Languages** | File extensions (`.py`, `.ts`, `.go`, `.java`, `.rs`, etc.) and their relative proportions | | **Package managers** | `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, `build.gradle` | | **Frameworks** | Dependencies in package files (React, Django, Spring, Express, Rails, etc.) | | **Build tools** | `Makefile`, `webpack.config.js`, `vite.config.ts`, `Dockerfile`, `docker-compose.yml` | | **CI/CD** | `.github/workflows/`, `.gitlab-ci.yml`, `.circleci/`, `Jenkinsfile` | | **Testing** | Test directories, test frameworks in dependencies (`jest`, `pytest`, `go test`, `JUnit`) | 2. **Analyze architecture**: Identif