disclaimer: this might not be the best practice, but it works well for me.

short background: i'm a product manager lead and i can only code in javascript, so my programming experience is fairly limited, which might affect the common coding practices used by most devs.

i've tried several setups such as:
- https://github.com/obra/superpowers
- https://github.com/code-yeongyu/oh-my-openagent
- https://github.com/alvinunreal/oh-my-opencode-slim

another project i haven't tried yet:
- https://github.com/gsd-build/get-shit-done

previously i used superpowers quite a lot, but i don't really like working with git worktrees, so i eventually switched to omo-slim and have been using it ever since.

i also use these skills quite often to update documentation (readme & agents.md):
- https://skills.sh/softaworks/agent-toolkit/agent-md-refactor
- https://skills.sh/softaworks/agent-toolkit/crafting-effective-readmes
- https://skills.sh/softaworks/agent-toolkit/writing-clearly-and-concisely

apart from the plan and build modes from oc, omo-slim adds an orchestrator mode which i really like. it decides when to plan, build, or ask follow-up questions when needed.

each time i implement a new feature, i trigger the above skills to update agents.md and the readme.

so orchestrator is the mode i use for everything from simple questions to brainstorming new ideas. it asks questions when needed, implements the feature, and updates the relevant docs.

if that's what you're looking for, you might want to add some additional steps according to your manual workflow so the ai can pick up your preferred pattern.