Projects, tasks, sub-tasks
Every task gets a short reference like NP-12. Sub-tasks work as a checklist that you or Claude can tick off.
Project management with Claude on the team
Plan the work. Hand it to Claude. Review what comes back.
Nossic Projects keeps your projects, tasks and sub-tasks in one place. Send a task to Claude and it works through the queue one task at a time, on its own branch. Each task comes back to you for review.
Sign in with your Nossic ID.
How it works
Four steps, and you decide what ships.
-
1
Write the task
Say what needs doing and what "done" means. Split it into sub-tasks so progress is easy to follow.
-
2
Send it to Claude
One click puts it in Claude's queue. Urgent tasks go first, then the order on your board.
-
3
Claude does the work
The worker checks in every few minutes and picks up the next task. Claude runs in the project's own repo, ticks off sub-tasks and posts progress as it goes.
-
4
You review it
Claude hands back a summary: what changed, which branch, and how it checked the work. Approve it, or send it back with notes and Claude carries on from where it stopped.
Everything a small team needs
Simple to use, with nothing you don't need.
Boards you can drag
Backlog, Ready, In progress, Review, Blocked and Done. Drag a card to change its status or its place in the queue.
Claude's queue
See what Claude is working on, what's next and what needs you. One switch pauses new work.
Review before done
Claude's work goes to Review, never straight to Done. Approve it in one click, or request changes.
A branch for every task
Claude works in a separate copy of the repo on its own git branch. Your own checkout is never touched.
Recovers on its own
If a run stops responding, the task goes back to Ready. After three failed tries it is parked as Blocked for you to look at.
Questions, not guesses
When Claude needs a decision or access, it asks in a comment and moves the task to Blocked. Answer it and the task goes back in the queue.
Tools in Claude Code
Connect any Claude Code session and say "plan this feature as tasks" or "what's blocked?". It reads and updates your projects directly.
Nossic ID and Nossic DB
Sign in with your Nossic ID. Your data stays on Nossic's own servers in Nossic DB.
Safe by design
Claude works within limits you set.
- It only works in folders you allow. If a task points anywhere else, it is blocked.
- It doesn't push or deploy unless the task or your project's standing instructions say so.
- It never commits to main. Every change waits on a branch for your review.
- Every run has a time limit and an optional spending cap.
- Every action is recorded in the task's activity history.
- You can revoke a token on its own, so one lost machine doesn't put the rest at risk.
$ claude mcp add --transport http \
nossic-projects https://app.projects.nossic.uk/mcp \
--header "Authorization: Bearer np_…"
> Plan eSign phase 2 as tasks in ES,
with sub-tasks, and queue the first two for Claude.
● created ES-16 Word upload (4 sub-tasks)
● created ES-17 In-app editor (6 sub-tasks)
● queued ES-16, ES-17 for Claude
Ready when you are
Open the app, make a project, and hand Claude its first task.
Open Nossic Projects