Nogra.
Install→

Docs

How to use Nogra.

Nogra is pull-first. Ordinary chat, direct edits, debugging, and implementation stay direct unless you ask for Nogra. Use it when the work needs a plan, approval, evidence, and a local record of what happened.

Install.

claude plugin marketplace add nograai/nogra-claude-marketplace
claude plugin install nogra@nogra-claude

Then open Claude Code inside a project and run /nogra:status to confirm the plugin is visible.

Choose the right flow.

Stay direct for ordinary questions, small edits, routine debug help, and normal implementation where you do not need a durable approval trail.

Pull Nogra in when the work is scoped, risky, cross-lane, or needs a record that another session can inspect. For complex work, shape the orchestration first: lane, topology, role fit, evidence join, GO boundary, and next owner. Then write the brief.

First Nogra run.

  1. 01

    Set up the workspace.

    /nogra:setup

    Creates .nogra/ in your project root. This is local markdown and JSON state: briefs, receipts, evidence, checkpoints, decisions, and current tasks.

  2. 02

    Ask for a brief.

    /nogra:brief Build a small local task tracker in this workspace.

    Nogra turns the request into a scoped contract: what is in, what is out, what evidence is required, and when the run should stop.

  3. 03

    Review before GO.

    Read the brief. If scope, evidence, or risk boundaries are wrong, fix the brief before dispatch. A demo request, preview, or idea selection is not GO.

  4. 04

    Dispatch only after approval.

    GO

    After you approve the brief, dispatch runs a fresh executor role against that approved scope and writes a run receipt.

  5. 05

    Verify the result.

    /nogra:verify

    The verification pass checks output and files against the brief. The executor's own claim is never enough by itself.

  6. 06

    Checkpoint what changed.

    /nogra:status

    Use status to inspect local ledger and checkpoint freshness before continuing in the next session.

Commands.

CommandUse
/nogra:setupInitialize local .nogra/ state in the current workspace.
/nogra:statusShow installed plugin version, workspace id, recent records, and checkpoint freshness.
/nogra:briefShape a scoped work contract before dispatch.
/nogra:dispatchRun an approved brief after you have reviewed it and said GO.
/nogra:verifyCheck returned work against the brief and evidence instead of accepting a self-report.
/nogra:adaptMap an existing project into Nogra's local workspace records.
/nogra:createCreate a project-local Nogra workspace under a hub.
/nogra:settingsInspect or adjust language and runtime preferences.
/nogra:updateRefresh installed Nogra guidance without starting work.
/nogra:watchInspect recent local hook events when you need to see what Nogra observed.
/nogra:helpChoose the right Nogra route when you are unsure.

What gets written.

Nogra writes local workspace records under .nogra/. They are plain markdown and JSON files: briefs, transport records, evidence, checkpoints, decisions, and current tasks. You can read them, delete them, or commit them with your project.

Nogra does not replace Claude Code's native permission model and does not route public plugin work outside Claude Code. It gives the workflow a local contract and evidence trail that can be checked.

Troubleshooting.

  • If a command is missing, run /reload-plugins in Claude Code and check /nogra:status.
  • If the wrong workspace appears, run status from the project root and inspect the local .nogra/ folder.
  • If a run returns partial or blocked, keep the reason. Do not mark the work done until verification has evidence against the brief.

Ready when you are

Install the plugin, then pull Nogra in.

Install Nogra→What Nogra is