New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nav Brief

by qf-studio in qf-studio/navigator

Render a one-screen intent brief (Goal/Scope/Approach/Limits/Verify/Won't-do/Contradiction) before implementing ambiguous task-shaped prompts, triggered by the promptbrief op (UserPromptSubmit via…

MITAuto-check passed

Install Nav Brief

skills CLI
$ npx skills add qf-studio/navigator --skill nav-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install qf-studio/navigator nav-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nav-brief .claude/skills/nav-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nav-brief
GitHub stars
355
Token cost
~1.5k tokens
SKILL.md length
627 words
Files
2
Skills in repo
32
Repo updated
First seen
Licence
MIT

At a glance

Render a one-screen intent brief (Goal/Scope/Approach/Limits/Verify/Won't-do/Contradiction) before implementing ambiguous task-shaped prompts, triggered by the promptbrief op (UserPromptSubmit via…

  • SKILL.md covers Why This Exists, When This Fires, Rendering the Brief and When a Contradiction Is…, plus 5 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Nav Brief is an agent skill from qf-studio/navigator. Render a one-screen intent brief (Goal/Scope/Approach/Limits/Verify/Won't-do/Contradiction) before implementing ambiguous task-shaped prompts, triggered by the promptbrief op (UserPromptSubmit via hooks/navdispatch.py). Confirms scope with max 2 open questions before touching files; detects brief drift mid-task.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `functions/test_ambiguity_scorer.py`).

The repository describes itself as: Finish What You Start — Context engineering for Claude Code. Sessions last 20+ exchanges instead of crashing at 7. The licence is MIT.

Example prompts

  • “/nav-brief”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 3bb9eac. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nav Brief loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 627 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qf-studio/navigator at commit 3bb9eac, republished under its MIT licence (© qf-studio). 627 words, ~1,514 tokens.

Download SKILL.mdSave it as .claude/skills/nav-brief/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
nav-brief
description
Render a one-screen intent brief (Goal/Scope/Approach/Limits/Verify/Won't-do/Contradiction) before implementing ambiguous task-shaped prompts, triggered by the prompt_brief op (UserPromptSubmit via hooks/nav_dispatch.py). Confirms scope with max 2 open questions before touching files; detects brief drift mid-task.
version
1.0.0

Navigator Intent Brief Skill

Front-load the scope negotiation. When a prompt is task-shaped but ambiguous, render a one-screen INTENT BRIEF and get confirmation before writing code — turning 2-4 correction exchanges into 1 confirmation exchange.

Why This Exists

Ambiguity is not complexity. A small task can be highly ambiguous ("fix the bug" — which bug?) while a large one can be fully specified. The expensive failure mode is implementing on guessed scope: rework burns tokens on undo/redo, pollutes context with dead ends, and forces mid-feature compacts.

When This Fires

Hook contract: render a brief ONLY when this turn's injected context contains a NAV-BRIEF reminder block (emitted by the prompt_brief op — hooks/ops/prompt_brief.py, dispatched by nav_dispatch.py — on UserPromptSubmit when ambiguity score >= threshold). Never self-trigger from your own judgment alone — the hook is the single trigger source, so behavior stays predictable and tunable via config.

Config (.agent/.nav-config.json):

json
"brief_hook": {
  "enabled": true,
  "ambiguity_threshold": 0.5,
  "memory_budget_chars": 1200
}

Rendering the Brief

Use the template below. Pre-fill every field you can from the injected ## Relevant Memories section and current session context; mark assumptions explicitly.

┌─ BRIEF: <short title> ──────────────────────────────┐
│ Goal      <outcome, one line>                       │
│ Scope     <files/dirs/endpoints — concrete>         │
│           NOT <adjacent things left untouched>      │
│ Approach  <how — cite memory if pre-filled>         │
│ Limits    <numbers, constraints — mark ASSUMED>     │
│ Verify    <how completion will be proven>           │
│ Won't do  <explicit non-goals>                      │
│ Contradict <improving X worsens Y — or "none">      │
└─────────────────────────────────────────────────────┘
Confirm / edit? (open questions: <0-2>)

Rules:

  • Max 2 open questions. Ask only what you cannot infer or safely assume; everything else is a pre-filled default the user can veto.
  • Stop and wait for user confirmation before any Edit/Write/Bash that modifies the project.
  • After confirmation, capture corrections: changed defaults are candidate knowledge-graph memories ("Remember we decided..." flow via nav-graph), so future briefs pre-fill better.

When a Contradiction Is Declared (TRIZ, TASK-72)

Contradict is the TRIZ row: the task is inventive only when improving one thing worsens another ("faster session start vs enough context"). Most tasks are routine — none is the expected common case. Never invent a tension to fill the row.

When the row is not none, query prior resolutions BEFORE filling Approach:

bash
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
python3 "$PLUGIN_DIR/skills/nav-graph/functions/graph_manager.py" \
  --action contradictions --filter "<2-3 key terms>"

Cite matching mem-NNN ids in Approach ("resolved by separation in time before: mem-063"). If nothing matches, say so in one line. On a substantial task (Task Mode complexity ≥ 0.5 or more than one subsystem), hand off to nav-triz before filling Approach: it produces three candidates from different separation modes and recommends one. After the task, if the resolution was non-obvious, capture it as a decision with --contradiction / --separation / --principle (see nav-graph Step 3B) so the next brief can find it. Drift detection does not cover this row.

Show full SKILL.md (256 more words)Show less

Passthrough Rules (do NOT render a brief)

  • No NAV-BRIEF reminder in this turn's context.
  • The prompt is plainly an answer to a pending brief's open questions (model-side judgment — the hook is stateless in v1 and may re-fire on answers that contain task verbs; known limitation).
  • User signals urgency/override: "just do it", "quick fix", "skip the brief". Respect it silently.

Brief Drift Detection

Mid-implementation, if the work is about to exceed the confirmed brief's Scope or Limits (touching files outside scope, changing an untouched-by- agreement area), STOP and surface:

⚠ BRIEF DRIFT: <what exceeds the brief, one line>
Options: extend brief / skip this change

One question, then continue per the answer.

Interaction with workflow_enforcer / Task Mode

Both UserPromptSubmit hooks may fire on the same prompt. Show both blocks — they are complementary: WORKFLOW CHECK decides how to execute (mode), the brief decides what is in scope. In Task Mode, the confirmed brief replaces ad-hoc scope derivation in the PLAN phase.

Examples

Brief rendered — "add rate limiting to the API" (score 0.7): brief with Scope pre-filled to public routes (graph memory), Limits marked ASSUMED, 1 open question about limit numbers. User answers; implementation starts.

Passthrough — "fix the typo in README.md" (score 0.1): file reference gives full scope; no brief, direct execution.

Drift — brief confirmed scope /api/public/*; implementation later needs a shared middleware file used by internal routes → BRIEF DRIFT raised, user extends the brief.

Future Work (explicitly deferred from v1)

  • Statefulness: persist pending-brief state across turns (removes the answer-re-fire limitation).
  • strict_block: hard-gate implementation until a brief is confirmed.
  • Measurement: briefs-shown/passthrough counters + corrections-per-task metrics (pairs with nav-stats; deferred until there is a consumer).
  • Prompt rewriting.

© qf-studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/nav-brief of qf-studio/navigator.

  • SKILL.md
  • functions/test_ambiguity_scorer.py

Open the folder on GitHubat commit 3bb9eac

Compare with similar skills

Nav Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nav Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nav Brief this skillqf-studio/navigator355—~1.5kAutomated safety check: PassMIT
Briefalirezarezvani/claude-skills28k—~967Automated safety check: PassMIT
Goalscodewhale-hq/Codewhale41k—~273Automated safety check: PassMIT
Morning Brief Rendererasgeirtj/system_prompts_leaks69k—~4.5kAutomated safety check: PassCC0-1.0
Render Blockingthedaviddias/Front-End-Checklist74k—~430Automated safety check: PassMIT
Intent Requirements IntakeYeachan-Heo/oh-my-claudecode40k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Brief

    alirezarezvani/claude-skills

    /cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.

    28k GitHub stars~967 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Goals

    codewhale-hq/Codewhale

    Set, review, and update the user's goals. An agent skill from codewhale-hq/Codewhale.

    41k GitHub stars~273 tokensUpdated today
    Auto-check passed

  • Morning Brief Renderer

    asgeirtj/system_prompts_leaks

    Renders a calm, single-page HTML morning brief from your connected calendar, email and chat, or sets it up to run automatically on weekdays.

    69k GitHub stars~4.5k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Render Blocking

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources.

    74k GitHub stars~430 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

  • Intent Requirements Intake

    Yeachan-Heo/oh-my-claudecode

    Turns a pasted chat log or spoken problem report from support or ops staff into a reviewed five-section intent.md through numbered batches of questions.

    40k GitHub stars~1.5k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Brief

    davepoon/buildwithclaude

    Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.

    3.6k GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check: notes

More from qf-studio/navigator

All 32 skills in this repo

  • Nav Start

    qf-studio/navigator

    Load Navigator documentation navigator when starting development session, resuming work, or beginning new feature.

    355 GitHub stars~4.7k tokensUpdated 2 days ago
    Auto-check: notes

  • Backend Endpoint

    qf-studio/navigator

    Create REST/GraphQL API endpoint with validation, error handling, and tests.

    355 GitHub stars~4.5k tokensUpdated 2 days ago
    Auto-check: notes

  • Backend Test

    qf-studio/navigator

    Generate backend tests (unit, integration, mocks) for existing code.

    355 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check: notes

  • Database Migration

    qf-studio/navigator

    Create database migration with schema changes and rollback. An agent skill from qf-studio/navigator.

    355 GitHub stars~3.7k tokensUpdated 2 days ago
    Auto-check: notes

  • Frontend Component

    qf-studio/navigator

    Create React/Vue component with TypeScript, tests, and styles.

    355 GitHub stars~4.5k tokensUpdated 2 days ago
    Auto-check: notes

  • Frontend Test

    qf-studio/navigator

    Generate frontend component tests (React Testing Library, Vue Test Utils, snapshot) for existing components.

    355 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check: notes

Questions about Nav Brief

What does Nav Brief do?

Render a one-screen intent brief (Goal/Scope/Approach/Limits/Verify/Won't-do/Contradiction) before implementing ambiguous task-shaped prompts, triggered by the promptbrief op (UserPromptSubmit via…. Nav Brief is an agent skill from qf-studio/navigator.py).

How do I install Nav Brief in Claude Code?

Run `npx skills add qf-studio/navigator --skill nav-brief -a claude-code`. Or copy the skill folder (skills/nav-brief in qf-studio/navigator) into .claude/skills/nav-brief in your project. Claude Code loads it when a task matches its description.

How do I install Nav Brief in Codex?

Run `npx skills add qf-studio/navigator --skill nav-brief -a codex`. Or copy the skill folder (skills/nav-brief in qf-studio/navigator) into .agents/skills/nav-brief in your project. Codex loads it when a task matches its description.

Can I use Nav Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qf-studio/navigator --skill nav-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nav-brief, .gemini/skills/nav-brief, .github/skills/nav-brief and .opencode/skills/nav-brief in your project.

What does Nav Brief need to run?

Going by SKILL.md and its folder, Nav Brief needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Nav Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nav Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nav Brief use?

Nav Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nav Brief use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nav Brief?

Skills that share tags, products or a category with Nav Brief: Brief (alirezarezvani/claude-skills, 28k stars), Goals (codewhale-hq/Codewhale, 41k stars), Morning Brief Renderer (asgeirtj/system_prompts_leaks, 69k stars) and Render Blocking (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nav Brief?

qf-studio (a GitHub organization) maintains it in qf-studio/navigator, which has 355 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

Source: qf-studio/navigator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.