Garden

Agents copy whatever the codebase already does, good or bad, so drift compounds. Gardening runs alongside feature work to keep the codebase a place where the right change is the easy one.

Scan first and fix later: a queue of findings shows the causes that fixing them one by one would hide. Run to the end on your own; anything for the human goes in the report, written in the user's active language.

Lenses

Pick the lens the user names, or the one with the strongest signal:

• Architecture: concepts owned in several places, shallow modules that only pass calls through, files that always change together, boundaries the code crosses against its design. Use the deletion test from strategic-programming.
• Consistency: deviations from the project's agent instructions and coding standards, the same mechanism implemented several ways, the same defect fixed in more than one feature, dead code and leftovers.
• Performance: product budgets and the work behind them, such as round trips, queries, bundle size, and renders, measured before and after.
• Tests: run prune.
• Verification: run setup-verification.

Process