“"9,10两章没有内容" — yaduns”
You know that feeling when your coding agent starts strong, then forgets the goal, edits the wrong file, or says it is done too early. You keep patching that with a longer prompt, but the prompt turns into a wall of text that your agent only half follows. You also lose context between sessions because the plan, progress, and checks live in chat instead of in your repo. This project tackles that by moving the working memory and rules into files your team can review.
Think of it like giving your coding agent a shared binder instead of one long speech. You put the rules in `AGENTS.md` or `CLAUDE.md`, the scope in `feature_list.json`, the current status in a progress note, and setup steps in `init.sh`. The agent reads the right file for the right job, updates state as it works, and uses explicit verification steps before it declares the task done. The course teaches that file set through 12 lectures, 6 projects, and a bundled skill that can create or assess the same repo artifacts.
If you already use Claude Code, Codex, or another coding agent and you want your repo to hold the rules instead of chat memory, this is for you. It also fits if you lead a small team and you want a shared file pattern for agent work. It is not a good fit yet if you need a finished production standard, a tagged release, or a fully complete course.
Yes, if you want a practical way to think about agent workflow control inside a repo. Right now it looks beta: the core model is clear, activity is current, and the template set is useful, but the repo has no tagged release and open issues call out missing chapters and fuzzy scope. You should use it to shape your internal playbook, not as your only source of truth.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.