Junie Workflow Playbook: From a Reviewed Plan to a Verified Merge

Look forWrite build, test, and lint commands plus review rules in .junie/AGENTS.md. When present, that file replaces the combined root AGENTS.md, .junie/playbook.md, and .junie/rules/*.md instructions. Junie CLI also reads ~/.junie/AGENTS.md and offers to import other agents' instructions on first opening a project. Retire legacy .junie/guidelines.md once AGENTS.md exists, since Junie still loads it. A Kotlin developer on Reddit spent a couple of hours writing guidelines for Compose Multiplatform and Ktor and found that closing a gap later meant adding one line. An engineer who built a pull-request dashboard for their team had Junie write the README and project guidelines from an architecture outline before the first task.

Look forUse Plan mode for tasks that touch more than one module. Junie reads code and writes a design before making changes. In the CLI, press Shift+Tab or use /plan. Edit or commit the saved plan under .junie/plans. In AI Chat, approve the plan before Junie implements it. That engineer then built the dashboard one step at a time, from page layout and dummy data to the Azure DevOps and YouTrack calls. They report that almost every step worked on the first try. When Junie grew repetitive, the engineer added a step to consolidate code and configuration.

Look forSet an Action Allowlist. Junie asks before most terminal commands, code execution, and MCP tools. Allow similar commands adds a pattern to that list. Brave mode Auto approves commands its safety check rates safe and asks about the rest. Brave mode On approves everything. Reserve On for disposable environments because release builds of Junie CLI have no OS-level command sandbox.

Look forType follow-up prompts while Junie works to redirect the running CLI task. Use AI Chat rollback for one file or all changed files. Give parallel tasks separate Git worktrees because sessions in the same checkout share files. Engineers who keep Junie on target name the files and the change. One finds it fast and to the point that way, and finds it fails when asked to build a whole feature. Another discarded three Junie runs on one refined prompt and wrote the code by hand.

Look forRun tests through the IDE, then use /review on staged changes or the branch against main. The review agent reads the diff and project guidelines without editing, building, or committing. The Junie GitHub Action runs the same review on pull requests. Require CI and human approval before merge. Check what Junie changed before accepting it. In Brave mode it applies changes before anyone reviews them, and one engineer found it reliable only on small, defined tasks.