Common issues I've noticed thus far

[mdeforge]

I've been using this to vibe code a story tracking web app using Claude. Spec-driven development seems powerful. Thank you for this project! My feedback thus far, however, is that Claude is having a hard time keeping track of its role in the agent-os process.

1. Often forgets to update the database structure
2. Often forgets to create a feature branch when starting a new feature
3. Often forgets to commit and merge at the end of a feature
4. Often forgets to create a spec for new features and instead starts implementing them
5. If it does create a new spec for a new feature, it often forgets to develop off the spec and/or update the todos/tasks
6. Despite instructions in ~/.agent-os, forgets not to run npm run dev since that will never return

Claude seems especially sensitive to when I start a new session after restarting VS Code. It could be that I messed up the installation, but my CLAUDE.md does have a section that points to each of the ~/.agent-os files. Is there a specific prompt I should start each session with (e.g., "Please reread the Agent OS files at ~/.agent-os")?

Are others encountering the same problems? If so, how have you helped Claude out?

[sangjaepark0000]

There is instructions in core files about context analysis

in execute-tasks.md step 2, use context-fetcher agent. read task.md and *-lite.md

[mdeforge]

What's a good prompt to double-check that those instructions are being found and loaded at the beginning of a session?

[sangjaepark0000]

In my case

There is difference between.
--dangerosuly-skip-permissons
Is given or not.

I guess when session doesn't have authority to home directory.
Try to read working directory.

[CasJam]

I noticed that Claude Code doesn't naturally choose to follow the instructions based on natural language. So now I'm making sure to explicitely call the /create-spec, /execute-tasks commands to kick off those processes ("instead of saying 'create a spec' or 'proceed with tasks' etc.). Using the commands directly seems to work reliably in my recent experience.

[mdeforge]

Same. Question: If I have a new session in an existing project and want to work outside of spec-driven development for a moment (maybe for a bug fix), but want claude to honor best practices, etc., that I've defined in agent os, what's the best way to do that? Is there something I can add to the prompt that would steer it towards using agent os information, or do I need to add a task for the bug fix and that have it execute said task?

[foertel]

Just tell it to: still adhere to @spec-file...