brownfield-analyzer

What This Skill Does

The brownfield-analyzer is a powerful OpenClaw agent skill designed to bridge the gap between legacy codebase documentation and the modern SpecWeave architecture. It acts as an automated audit engine that scans existing projects to perform a structural assessment of your technical debt and documentation landscape. By automatically categorizing files into PRDs, HLDs, ADRs, technical specs, and runbooks, it creates a high-fidelity map of your project's current state. Whether you are dealing with massive monoliths or fragmented microservices, the analyzer detects existing documentation patterns and maps them to the standardized SpecWeave structure. Additionally, it identifies external integrations like Jira or Azure DevOps, providing a clear migration roadmap based on your project size, complexity, and specific documentation needs.

Installation

To integrate this skill into your OpenClaw environment, use the CLI installation command: clawhub install openclaw/skills/skills/anton-abyzov/sw-brownfield-analyzer Ensure you are in the root directory of the project you wish to analyze so the skill can perform its initial filesystem scan correctly.

Use Cases

• Project Migration: Transitioning legacy codebases into the SpecWeave ecosystem by mapping scattered docs into a unified structure.
• Technical Audits: Gaining an automated view of total lines of code (LOC), module counts, and existing documentation health before starting a new sprint.
• Onboarding Acceleration: Quickly generating a context map for new developers by identifying the locations of PRDs, architectural diagrams, and operational runbooks.
• System Upgrades: Using the 'Comprehensive Upfront' analysis path to ensure full test coverage and documentation readiness for legacy projects in regulated industries.

Example Prompts

1. "Analyze this project and tell me if I should use the Quick Start or Comprehensive migration path based on our current 120k LOC count."
2. "Scan the docs directory, map my current md files to the SpecWeave structure, and identify any missing runbooks or architecture records."
3. "Look for any references to Jira or Azure DevOps in our repository and report which modules are currently linked to those trackers."

Tips & Limitations

• Recommendation Accuracy: The analyzer provides a recommendation based on project size, but always consider team capacity and external compliance deadlines before choosing a path.
• File Scope: Ensure your project is clean of extraneous build folders or temporary files, as these may skew the initial LOC calculation.
• Incremental Growth: If you choose the Quick Start path, commit to the 'Document -> Modify -> Update' cycle to prevent the documentation from drifting away from the implementation.
• External Integrations: While the tool detects Jira and ADO links, it does not currently perform deep API calls into those platforms; it focuses on local repo discovery.