📝 Gremlins MVP spec

2026-10-16 23:12:29 +02:00
parent 5bd945ea60
commit b8affd82e7
3 changed files with 153 additions and 0 deletions
@@ -27,6 +27,16 @@
 - The user wants the whole build bundled into a report that honestly calls it a failure. The approval waits cost time, but they are not the main issue.
 - **Guidance hasn't found its sweet spot yet.** Open question: how big are the skills in text, how much of it is filler, and is each skill truly written for an agent, or does it regurgitate knowledge the model already has?

+## Steering sentences cut both ways (user, 2026-10-16)
+
+- "Keep it small", "happy path first" and "delete what isn't needed" are themselves dangerous: they can fire the other way, into cut corners, missing error handling and deleted tests or needed code.
+- Igor's take on safer framing (options, not decisions):
+  - Tie size to requirements, not adjectives. Each function or module traces to an acceptance box, and anything that doesn't gets a one-line reason in the hand-back.
+  - A size *estimate* in the plan that the builder must explain deviations from. A budget to justify against, not a cap to obey.
+  - "Happy path first" as **sequencing**: the happy path runs end to end before edge cases get built. It's not a value judgement against edge cases.
+  - Reviews report "unrequested surface" as a finding category with the decision left to Igor and the user. Reviewers don't delete on their own.
+  - Pair every push with its counterweight in the same sentence, e.g. "cover the failure paths the boxes name; add no others without a reason".
+
 ## Answer: how much code can Opus 5.5 produce in one go?

 *(Igor, 2026-10-16, from the claude-api skill's model table)*