Your first /n45¶

Once you're set up, open your IDE and run /n45 in the chat. It's the hub — it detects the state and offers the right actions.

/n45

/n45 Resume work or show the state

/n45-feat Build a new feature

/n45-fix Investigate and fix a bug

/n45-status See the current state

Invocation prefix per tool

In Claude Code and Cursor the commands use / (e.g. /n45, /n45-feat). In Codex they use $ (e.g. $n45, $n45-feat). The examples below use /; swap for $ if you're on Codex.

The flow differs a little between Project (one repository) and Workspace (several). Pick yours below.

In your project (Project)¶

The first run¶

N45 wakes up and inspects your project:

Reads your package.json, go.mod, Cargo.toml, pyproject.toml, etc.
Detects languages, frameworks and tooling
Generates four foundational docs in .n45/docs/:

Document	What it holds
STACK	Language, runtime, framework, build tooling
PATTERNS	Architectural conventions found in your code
PROJECT	Domain overview, modules, entry points
RUNBOOK	How to run, test and deploy

The first run takes 30–60 seconds. Later runs are instant — N45 just reads the existing docs.

Your first feature¶

With the project open, type something like:

/n45-feat add a health check endpoint

N45 asks questions to clarify, proposes a plan, and then applies the change directly (for small changes) or builds a full discovery, spec and roadmap (for bigger ones). You approve at each step. More in Build a feature.

In your workspace (Workspace)¶

Run /n45 in the workspace folder — it opens the workspace hub (the state is read from each member's disk).

No members yet? The hub helps you add them — existing repositories (workspace add) or new applications that become members.
With members, plan a cross-repo feature:
```
/n45-feat add a chat between the services
```
N45 interviews you, maps the screens and contracts per member, generates the SPEC and the CONTRACT (the seam between the services — you approve), and does the fan-out: each member gets its own roadmap.
Execute and finish: /n45-next advances each member in parallel; when they're all done, the hub offers the unified validation and the coordinated finish.

The full flow is in the Workspace section: Plan a feature → Execute, validate and finish.

Follow along in the dashboard¶

While N45 builds, run in a separate terminal:

npx n45-ai@latest status

This launches the Dashboard in your browser — a kanban where you watch tasks move as the agents execute, plus metrics and the project documents. In a workspace, it aggregates every member in one place. Leave it in a tab and follow the build in real time.

After that¶

Bare /n45 resumes whatever was in progress; if nothing is, it shows what's possible next.

Command	When to use
`/n45-feat`	Build a feature or improvement
`/n45-fix`	Investigate a bug or unexpected behavior
`/n45-status`	See the state — open work, pending validation
`/n45-next`	Advance execution (the next phase)
`/n45-run`	Run the application