brownfield-analyzer
Analyzes existing brownfield projects to map documentation structure to SpecWeave's PRD/HLD/Spec/Runbook pattern. Scans folders, classifies documents, detects external tools (Jira, ADO, GitHub), and creates project context map for just-in-time migration. Activates for brownfield, existing project, migrate, analyze structure, legacy documentation.
npx skills add majiayu000/claude-skill-registry --skill brownfield-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Brownfield Analyzer **Self-contained brownfield project analysis for ANY existing codebase.** --- ## Purpose Analyze existing projects and create migration plan to SpecWeave structure. Two paths supported: Quick Start (incremental) or Comprehensive (upfront). --- ## Two Migration Paths ### Path 1: Quick Start (Recommended for Large Projects) **Best for**: 50k+ LOC, fast iteration, small teams **Process**: 1. Initial scan: Document core architecture (1-3 hours) 2. Start working immediately 3. Per increment: Document → Modify → Update docs 4. Documentation grows with changes **Benefits**: - Start in days, not weeks - Focus where it matters - No analysis paralysis ### Path 2: Comprehensive Upfront **Best for**: <50k LOC, teams, regulated industries **Process**: 1. Full analysis (1-4 weeks) 2. Document all modules, business rules 3. Create baseline tests 4. Then start increments **Benefits**: - Complete context upfront - Full regression coverage - Team coordination - Compliance ready ### Automatic Recommendation | Project Size | LOC | Upfront Effort | Recommended | |--------------|-----|----------------|-------------| | Small | <10k | 4-8 hours | Comprehensive | | Medium | 10k-50k |
- Purpose
- Two Migration Paths
- Path 1: Quick Start (Recommended for Large Projects)
- Path 2: Comprehensive Upfront
- Automatic Recommendation
- Analysis Workflow
- Step 1: Project Assessment
- Step 2: Document Classification
- Step 3: External Tool Detection
- Step 4: Coding Standards Discovery
- Step 5: Generate Migration Plan
- Migration Checklist
- Before SpecWeave Init
- During Migration
Scan project
find . -type f -name "*.ts" -o -name "*.js" -o -name "*.py" | wc -l
find . -type f \( -name "*.ts" -o -name "*.js" \) -exec wc -l {} + | awk '{sum+=$1} END {print sum}'
Search for Jira references
grep -r "JIRA" . --include="*.md" --include="*.txt"
grep -r "jira.atlassian" . --include="*.md"
grep -r "dev.azure.com" . --include="*.md"
grep -r "visualstudio.com" . --include="*.md"
grep -r "github.com/.*/issues" . --include="*.md"
Naming conventionsWhat does the brownfield-analyzer skill do?
Analyzes existing brownfield projects to map documentation structure to SpecWeave's PRD/HLD/Spec/Runbook pattern. Scans folders, classifies documents, detects external tools (Jira, ADO, GitHub), and creates project context map for just-in-time migration. Activates for brownfield, existing project, migrate, analyze structure, legacy documentation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill brownfield-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.