Legacy feature rebuild

Recover acceptance criteria from an owned feature before implementing a targeted replacement.

Customize the recipe

0/1500 characters

Prompt preview

# Legacy feature rebuild

Recover acceptance criteria from an owned feature before implementing a targeted replacement.

## Deliverable
A source-backed behavior spec and, when selected, a scoped replacement and parity tests.

## Stack and visual direction
- Recommended starting stack: Use the upstream REA project for supported artifact analysis. Deliver findings as a Markdown report with evidence references.
- Swiss grid: Use a visible modular grid, aligned baselines, asymmetric composition and tight typographic hierarchy. Reflow the grid without shrinking essential text. Use this direction for any prototype or visual deliverable without altering what the evidence shows.

- Deliver the evidence-backed report and a small original prototype of the behaviors in scope, using permitted materials.

## Tools and setup · Universal
Use the upstream Reverse Engineer Anything skill as the sole specialized analysis resource. Apply it to supported, authorized builds when the question needs artifact evidence. Scope the work to observable behavior and documented access. When available evidence is sufficient or the REA connection is unavailable, work from the supplied material and record whether REA was applicable and used.

- [Reverse Engineer Anything Skill](https://github.com/morluto/rea/blob/main/.agents/skills/reverse-engineer-anything/SKILL.md) (Skill) — Use the upstream REA workflow when a conclusion needs evidence from a supported, authorized built or shipped app.
  Artifact analysis requires an existing, compatible REA connection.
- [REA Repository](https://github.com/morluto/rea) (Repository) — Consult the upstream documentation for supported artifacts and evidence requirements.

## Workflow
1. Inspect the owned feature and permitted recordings, capture its observable behavior and supported edge cases, and confirm the scope before making a small replacement inside the existing stack.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] The behavior spec names the entry points, inputs and observable outcomes.
- [ ] If implementing, compare old and new paths with the same representative fixtures.
- [ ] Work from supplied material, public references you can inspect, or systems and code the user owns or has permission to analyze. Cite only observed locations or the ranges supplied. Label reconstructions, assumptions and unknowns explicitly, including unseen validation or authentication.
- [ ] For a prototype, use original or licensed materials and verify the relevant responsive, keyboard and accessible interaction behavior.

Recipe resources

Source, setup, and compatibility details.