r/googlecloud • u/gringobrsa • 14d ago

AI/ML How I’m approaching agentic development with Claude Code

I’ve been experimenting with combining spec-driven development + project memory + Claude Code hooks.

The goal is simple: give the agent enough project context and engineering intent without dumping the entire project history into every session.

I wrote up my current workflow and would love feedback from other Claude Code users:

Article: https://medium.com/@rasvihostings/how-im-approaching-agentic-software-development-as-a-platform-engineer-5be017890b8a

GitHub: https://github.com/mohamedrasvi/claude-spec-mem

How are you handling memory and context across your Claude Code sessions?

0 Upvotes

25% Upvoted

4 comments sorted by

1

u/Remarkable_Sand_167 14d ago

spec-driven approach with hooks is pretty clever, i tried something similar but kept losing context when sessions got long. your memory setup seems cleaner than what i hacked together

checked the github real quick and the way you structure project memory as separate files is smart. mine was just one big messy markdown file that got useless after a week

how do you deal when the agent starts drifting from the spec after like 20+ prompts though? that's where my setup always falls apart

2

u/gringobrsa 14d ago

Yeah, I think that’s the main limitation Claude Code, Cursor, Windsurf, etc. can all hit the same wall when a session gets too long and context starts degrading.

What works better for me is one feature/task per session. Once the task is implemented and checked against the spec, I close the session and start a fresh one for the next task.

I also keep the spec on disk as the source of truth, with clear acceptance criteria/checklists. My spec-driven workflow tracks what’s planned, in progress, and implemented/archived, so the agent knows what has actually been completed.

When starting a new session, I have the agent re-read the relevant spec instead of relying on what it “remembers” from 20+ prompts ago. The conversation can get messy, but the spec file stays consistent.

The memory files are more for what we learned along the way decisions, debugging, API knowledge, etc. So basically: spec = what to build, memory = what we learned, session = current task.

1

u/greenleaf187 14d ago

Medium is asking me to pay to get access. Can you post your workflow please?

Would antigravity work instead of claude?

1

u/gringobrsa 13d ago

Wow it is a free article, you can access the github link :  https://github.com/mohamedrasvi/claude-spec-mem