The board your agents work from.

Navegando keeps epics, stories and tickets as markdown files in your repo. Claude Code picks up the next ticket over MCP and can only move it forward when the stage's gate passes.

$ npx navegando

Free, no account. Node 22.13 or later.

127.0.0.1:4700/#/board

NavegandoSCR

Backlog Board Docs Metrics Settings Account Live

EpicsStoriesTickets

Assessment3

T-141

Parse JSON-LD blocks

in S-6 Read schema.org markup

T-15

Dedupe rows by canonical URL

in S-6 Read schema.org markup

T-162

Retry pages that time out

in S-9 Survive slow sites

Development2

T-12

Stream rows to CSV

in S-4 Download as CSV

T-11

Escape quotes in cell values

in S-4 Download as CSV

Testing1

T-10

Gzip exports over 10 MB

in S-4 Download as CSV

Deploy3

T-8

Write a header row

in S-4 Download as CSV

T-7

Export button on results

in S-3 Pick columns to export

T-6

Remember the last column set

in S-3 Pick columns to export

The board at 127.0.0.1:4700. It updates as agents and editors change the files.

Gates

A ticket can't start development without a test plan.

Each stage has a gate. Leaving Assessment needs a technical plan and a test plan with content. Drop a card on Development too early and it bounces back with the list of what's missing.

Moving backwards is always allowed and counts as rework in your metrics. You can force a gate from the CLI with --force, and the override is written to the ticket's history.

127.0.0.1:4700/#/item/T-14

E-2 Structured data › S-6 Read schema.org markup

T-14Parse JSON-LD blocks

Assessment›Development›Testing›Deploy Development

Context

Product pages carry prices and ratings in schema.org markup. S-6 needs them in the export.

Technical plan

Collect every script[type="application/ld+json"], parse each one alone so a broken block doesn't drop the page, and flatten @graph.

Files touched

src/extract/jsonld.ts

Test plan

Gate to leave Assessment Blocked

Technical plan

!Test plan

MCP server

Agents follow the rules you follow.

Add Navegando to .mcp.json and Claude Code gets tools for the whole lifecycle. get_context returns a ticket with its parent chain and what its gate still needs, in one call.

move has no force option, and configure can add a stage or a gate rule but can't remove one. Loosening the lifecycle is for you, from the CLI.

claude · ~/code/scraper

> take the next ticket

navegando.next_up()
  T-12  Stream rows to CSV   assessment · parent S-4

navegando.get_context("T-12")
  # T-12 · Stream rows to CSV
  ticket · stage: Assessment (1 of 4 ticket stages)
  Role prompt for this stage: /assess
  Next stage: Development. Gate passes (section:
  Technical plan; section: Test plan).
  …

The plan is written and the gate passes. Creating
branch T-12-csv-export and starting with the row
writer in src/export/csv.ts.

Git hooks

Branches and merges move tickets.

Run navegando git install once per clone and name branches after tickets. Hooks only move tickets forward and never past a failing gate. If a gate blocks, the hook prints why and git carries on.

What each git command does to ticket T-12
You run	Navegando
`git checkout -b T-12-csv-export`	T-12 moves to Development
`git commit -m "T-12: stream rows"`	The commit is linked to T-12
`navegando git sync`	Finds open PR #44 with `gh`. T-12 moves to Testing
`git merge T-12-csv-export` on main	T-12 moves to Deploy

Metrics

Cycle time from history you already have.

Every stage change is recorded in the ticket file and every commit is linked by id. navegando metrics reads both and shows where tickets wait and how often work goes backwards.

Your agent can call the same report over MCP.

$ navegando metrics --days 70

2.6 d

Median lead time, tickets

Rework rate

Gates forced

Tickets finished per week

3Aug 3

4Aug 10

2Aug 17

5Aug 24

4Aug 31

6Sep 7

5Sep 14

7Sep 21

6Sep 28

8Oct 5

Time spent per stage

Discovery 8%
Refinement 12%
Assessment 16%
Development 41%
Testing 23%

Pricing

Free

Everything that runs on your machine.

Board, backlog, docs and item pages
CLI, MCP server and git hooks
Metrics from your own history
No account, no limit on projects or items

$ npx navegando

Cloud

$—/month

Free, plus your projects on every machine you use.

Link a project with navegando cloud enable and sync it with navegando sync
Auto-sync sends each change up as it's made
Conflicting edits go to .navegando/.conflicts/ and are never overwritten
Team projects, up to 5 members Soon

$ navegando login

Run it in a repo you're working on.

It opens the board and offers to create .navegando/.

$ npx navegando