Got our whole team on claude about a month and a half ago, engineers and product both. Adoption has been solid, no complaints there still some small bickering about models but the usual shit. Planning though has been a different animal altogether. Velocity is all over the place, with tasks that should take a day done in 45 minutes, others completely fall apart because the context wasn’t crystal clear for AI to interpret. Had a senior get pulled mid-project a few weeks back. He’d been running Opus mostly for two weeks, all those decisions living in chat history nobody else was reading. New person picked it up, agent kept going like nothing changed, caught the drift in QA a week later. Lost it because we never wrote down what the agent knew, and I know everyone will just say generate a spec or “source of truth”, if it was that simple id have done it. Tried throwing together some skill.md files to at least capture the context and decision layer in a consistent way. Helped a little but hasn’t really solved the planning problem, atleast on my end. This has been a pain in our ass and I haven’t cracked it. If anyone’s actually solved this I’m all ears. submitted by /u/eastwindtoday
Originally posted by u/eastwindtoday on r/ClaudeCode