The outcome

Produce a tested implementation whose commands and file access remain understandable and reversible.

Step by step

A workflow you can repeat.

  1. 01

    Open a clean Git branch, inspect project-level .junie configuration and guidelines before granting trust, and record baseline tests.

  2. 02

    Start in ask or plan mode and provide the outcome, acceptance criteria, relevant paths, constraints, non-goals, and required validation.

  3. 03

    Review the plan, keep Brave mode off, and allowlist only exact safe diagnostics rather than broad command, MCP, or outside-project categories.

  4. 04

    Supervise implementation, especially build-script edits, dependencies, external paths, MCP calls, credentials, hooks, and requests for wider permissions.

  5. 05

    Run trusted checks, inspect the complete diff, use Junie's local review as additional evidence, and send the result through ordinary peer review.

Working standard

What good use looks like.

  • Review configuration before project trust.
  • Prefer exact allowlist rules.
  • Treat local review as evidence, not approval.

Official references

Check the current product documentation.