brownfield-retrospective

Topics in the source

• Brownfield Retrospective
• When to Activate
• When Not to Use
• The Working Set
• How It Works
• Phase 0 — Pick the Entry Point
• Phase 1 — Present-State Audit
• Phase 2 — Backward Reconstruction

Run ECC's engineering process retroactively against a project that was built without it. Pick any slice of an existing codebase, audit what exists, reconstruct how it got there, extract a four-axis gap register, then execute the fixes forward through the standard ECC pipeline. The workflow is slice-first: no whole-repo onboarding is required before it is useful, and every phase is re-enterable from a durable artifact on disk. Start in the middle, work backwards, then move forward. Adopting ECC in a repository that already exists and is already shaped User asks to "audit my existing project", "retro this codebase", or "what did we miss?" Taking over, inheriting, or returning to a codebase after a long gap User asks "why is it like this?" followed by "should it stay like this?" A module, feature, or service needs a rethink before the next feature lands on top of it Deciding whether a legacy area should be fixed forward, rewritten, or left documented as-is Greenfield work with no existing code — use planner and tdd-workflow directly Onboarding to spec-driven development without the redesign loop — the spec-miner agent does that on its own A launch go/no-go production-readiness pass —

This is an excerpt. Refer to the complete source and its current requirements.