skills.rest
amoutiers
amoutiersCOMMUNITY
Explore all skills by this author →
GitHub

migrate-from-brownfield

Reverse-engineer brownfield codebases into traceable as-built spec baselines.

1|Updated May 28, 2026
Search Tags:#specifications#verification#provenance#brownfield#code-analysis#reverse-engineering#boundary-discovery
One-click install
npx skills add https://github.com/amoutiers/maxi-superpowers --skill migrate-from-brownfield
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-from-brownfield
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/migrate-from-brownfield
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill migrate-from-brownfield

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield projects often have code but lack formal specs. This skill reverse-engineers an existing codebase into faithful, traceable spec baselines so teams can adopt spec-driven development, surface feature boundaries, and document provenance.

Core Features & Use Cases

  • Boundary discovery: identifies feature boundaries within a brownfield project and drafts as-built specs per boundary.
  • Adversarial verification: checks each drafted spec against the real code before acceptance to ensure fidelity and provenance.
  • Artifact production: writes accepted specs at status done with origin provenance and a recorded commit SHA for traceability.

Quick Start

Reverse-engineer a brownfield codebase into as-built spec baselines and verify each draft before saving.

Frequently Asked Questions about migrate-from-brownfield

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

FAQPage Schema
How do I reverse-engineer specs from an existing codebase that has no documentation?▼

To reverse-engineer specs from a codebase, this skill identifies feature boundaries and drafts as-built specs for each boundary, then verifies them against the actual code to ensure fidelity and provenance.

What is boundary discovery and how does it work for brownfield projects?▼

Boundary discovery is the process of identifying logical feature areas within a brownfield codebase. This skill scans the code to surface these boundaries and drafts a dedicated as-built spec for each one.

How are generated specs verified against the actual source code?▼

Each drafted spec undergoes adversarial verification, checking the specification against the real code before acceptance to ensure the documented behavior matches the implementation.

Can I trace the provenance of specs generated from a legacy codebase?▼

Yes, provenance is recorded in the generated spec frontmatter. The skill records the origin and a commit SHA for each accepted spec, providing full traceability back to the source code.

How do I start adopting spec-driven development on a project that already has code?▼

To adopt spec-driven development on a brownfield project, run the skill to reverse-engineer your codebase into faithful spec baselines, which can then be used for future development.

Does the spec generation workflow handle slug collisions and guard consent?▼

Yes, the skill coordinates with a deterministic workflow that guards consent, handles slug collisions, and records provenance in the generated spec frontmatter.

Related Skills

Explore More Software Engineering Skills→
abdullah1854abdullah1854
1

memory-systems

Design memory architectures with vector stores, knowledge graphs, and temporal knowledge graphs.

Community
Advanced
NoyoucringeNoyoucringe

spec-driven-development

Align implementation with formal specifications in .claude/specs/ and record verification results.

Community
Intermediate
ribeec20ribeec20

vista

Plan features, generate architecture diagrams, and run autonomous development loops in Claude Code.

Community
Advanced
zenobi-uszenobi-us
68

documentation-engineer

Automate API documentation creation and maintenance with OpenAPI integration.

Official
Advanced