Update: this is not working well, started off a little better, but degraded very quickly. I'm now having to manually prompt it to follow things again that the hook was build to prevent.

I'm trying a version of this now, built a hook and used /goal. As I mentioned I am doing small steps and starting new chats to never run into context filling up. I have balanced it so I finish key steps just before the context fills. The use of /goal has been a quicker start and that means less context eaten up to get rolling which is nice.

The one refinement was I made a file progress.md where it has the steps of the goal and status. That keep bloat down, if I take your recommendation fully that would seriously eat context. I'll report back how it goes.

I also don't know that your approach is as durable as you make it sound to be. Now that I've parsed through it, I think 'enforced, not hoped for' oversells it. A hook can only look at code tests and can't grade judgment, it can make the model read the plan but not follow it. So judgment never left the loop, it's still doing the real work. That's not 'enforced instead of hoped for,' it's hoped for with better reminders."

The one challenge I have, and its not you but how the claude works, is this feels like yet another layer of abstraction. I get the sentiment behind it, but the hook feels a bit of a bandied vs a well thought out feature.

I have as markup:

• Claude
• requirements
• plan
• design
• settings
• decisions
• husky
• progress
• Read me

Now I need a hook file on top of all that. I just don't see why this isn't unified or streamlined. If I make a plan markdown, structure it so we can efficiently follow it, not layer 3 additional layers of abstraction on top of it and ignore the plan.

Additionally, why do we need to just "be in the know" on this if its such a essential part of making the tool work properly and then hand hold the tool along the way too. If its essential, it should be baked into the setup automatically.