Implement closed-loop workspace follow-ups

2026-07-15 23:48:12 +04:00
parent 3a48ecd24f
commit ed7efb6072
51 changed files with 702 additions and 54 deletions
@@ -81,6 +81,10 @@ Emit a JSON object that validates against the `execution_plan` schema:
    decompose tasks here — task creation is out of scope for the plan.
 - Keep stages small and single-responsibility. Prefer more stages over large monolithic
  prompts.
+- Write stage prompts as constraints and verification goals, not a pre-scripted list of exact
+  resulting files or their full contents. State the responsibility, boundaries, existing APIs or
+  references to honor, acceptance checks, and what must not change; let the implementer inspect the
+  actual workspace and choose the smallest fitting file edits.
 - **Declare `touches` to fence a stage to its area.** When a stage's job belongs to one part of
  the tree (a frontend/client stage → `["frontend/**"]`; a stage that edits only the API layer →
  `["apps/server/**"]`), list those globs in `touches`. Every concrete path the stage `writes`