Re:Scaling LLMs to Larger Codebases
by AlexB138 on Monday December 22, 2025 @11:54AM
(#46355863)
This is essentially my exact workflow. I also keep the plan markdown files around in the repo to refer agents back to when adding new features. I have found it to be a really effective loop, and a great way to reprime context when returning to features.
[ Parent
| on HN ]
Exactly this. I clear the old plans every few weeks.
For really big features or plans I’ll ask the agent to create linear issue tickets to track progress for each phase over multiple sessions. Only MCP I have loaded is usually linear but looking for a good way to transition it to a skill.
Ah, that's a great idea. I've just been having the agent add a Progress section to the plan files and checking things off as we work.
Re:Scaling LLMs to Larger Codebases
by doublerebel on Monday December 22, 2025 @01:22PM
(#46356972)
I like Linearis as a CLI/skill interface to Linear, its help and json output are built well for use with Agents.
Re:Scaling LLMs to Larger Codebases
by JamesSwift on Monday December 22, 2025 @01:23PM
(#46357002)
In general anything with an API is simply saying "find the auth token at ~/.config/foo.json". It mostly knows the rest endpoints and can figure out the rest
I use an Obsidian MCP to essentially keep a database of plans, or versions sometimes that I can just fire off.
Why eat up the context with an MCP when a ./docs/plans folder does the same?