Agent skill · affaan-m
brownfield-retrospective
Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.
What it needs
About 7k tokens when loaded.
What this skill does
Brownfield Retrospective 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. When to Activate 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 When Not to Use 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 — use production-audit Security-only sweeps — use security-review Team process retrospectives (sprint ceremonies) — this audits a codebase, not people The Working Set All artifacts are written inside the audited project, under docs/retro/<slice>/: File Phase Purpose ------ ------- --------- gap-register.md 0-6 The state machine — perimeter, Current phase: marker, and rows. The only file required to resume mid-stream. baseline-audit.md 1 Reviewer findings, test/CI snapshot, TODO inventory. reconstructed-spec.md 2 What the code actually does today (Requirements + Invariants). target-design.md 4 Target shape for the slice and the fix sequence. Backfilled decisions go to docs/adr/ per the architecture-decision-records skill. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/brownfield-retrospective--9ff817