sw-brownfield-analyzer_skill

Overview

This skill analyzes existing brownfield projects and produces a migration plan that maps legacy documentation into SpecWeave’s structure (PRD, HLD, Spec, Runbook). It detects external tools like Jira, Azure DevOps, and GitHub and recommends either an incremental Quick Start or a Comprehensive upfront path. The output is a practical, runnable migration checklist and mapping that preserves existing docs and integrates tool sync options.

How this skill works

The analyzer scans the repository to measure LOC, file counts, modules, and test coverage, then classifies documentation into PRD, HLD, ADR, Spec, and Runbook candidates. It detects coding standards, config files, diagrams, and references to external tools and generates a recommended migration path and step‑by‑step plan. Final output includes a migration checklist, document-to-SpecWeave mapping, and sync strategies for Jira/ADO/GitHub.

When to use it

• Migrating an existing project into SpecWeave
• Scanning legacy docs to create project context maps
• Choosing a migration path for small, medium, or large codebases
• Preparing a compliance-ready documentation baseline
• Setting up tool sync between SpecWeave and Jira/ADO/GitHub

Best practices

• Pick Quick Start for very large codebases to avoid analysis paralysis
• Document module architecture before modifying code
• Preserve all original docs and back them up before migrating
• Use incremental increments to let documentation grow with changes
• Detect and map external tool structures early (epics → features, issues → user stories)

Example use cases

• Large Node.js backend (80k+ LOC) — Quick Start: init, core architecture docs, first increment, iterate
• Small Python app (8k LOC) — Comprehensive: full docs baseline, ADRs, tests, then migrate
• Legacy repo with Jira — detect Jira references, map epics/stories to SpecWeave, choose import vs. sync
• Repo with mixed docs in docs/, README, and wiki exports — classify and map files into .specweave/ structure