okay this is going kinda viral and tbh my original text was kind of messy, so here's a second pass with the help of Claude:
--
Implement <SPEC>. As you work maintain a running implementation-notes.html file that captures anything I should know about how the implementation diverges from or interprets the spec, including:
- Design decisions: choices you made where the spec was ambiguous
- Deviations: places where you intentionally departed from the spec, and why
- Tradeoffs: alternatives you considered and why you picked what you did
- Open questions: anything you'd want me to confirm or revise
@bcherny@bcherny
Or do we need to give the agents the context in the PR comments? I’m asking because I want to know how these can be used to validate features against business model/logic.
@bcherny What’s the basis of the review? Do you still need to feed those code reviewer agents the overall specs of the application you are building? Or they can read all my specs-*.md in my repository?
@claude_code@brendankblong Like a follow up instructions while it was in progress and it will automatically incorporate it with it’s the current tasks it was working on?
@claude_code@brendankblong Hi @claude_code , is there a way to input additional context or prompt while model is in-progress doing what you previously asks w/o the need to esc and interrupt the currently running tasks?
@GigaKp Wow, that's an impressive score! I've never even come close to that. Have you been playing Temple Run for a long time or was this just a one-time accomplishment?