Nandu

Nandu Development FrameworkAgentic development for real teams.

Spec-driven and test-driven development with agents, packaged as a versioned framework your team installs and updates on its own schedule. Built for complex projects where several people and many agents share one codebase.

Why it exists

Agentic coding works in a demo and breaks in a team

One developer with an agent on a small repository is easy. The same setup on a large codebase with five contributors falls apart, because agent output optimizes for looking locally right while the system slowly loses its shape. Context windows reset, people hand over, and nothing carries the state across.

NDF is built for exactly that scale. Collaboration sits in its foundations: plans and specs carry the project's state instead of anyone's session, tests define what correct means before code exists, and independent reviewer agents check work whose reasoning they never saw. That is what lets a team run agentic development on software that actually matters.

The core

Team collaboration is built in from the ground up

Plans, specs, and conventions carry the project state, so the codebase never depends on what one person remembers. A new session, or a new team member, reads the plan and continues where the last one stopped. Several people and many agents work in parallel, and the framework keeps them coherent.

The method

Plan before code. Spec-driven, with no ad-hoc path around it
Tests before implementation
Independent reviewer agents that did not write the code
Evidence before completion claims. An agent's own report is not evidence
Effort scales with risk, not with size
The plan outlives the session, so handovers cost nothing

What a licence includes

The versioned framework: agents, commands, conventions, and methodology docs
The CLI that installs and updates it, with a migration system between versions
Read-only access to the framework repository, refreshed through the CLI
A field-notes repository so your team's observations feed the framework's own improvement loop
Onboarding, methodology coaching, and accompaniment through the first project
A 12-month credential cycle

How adoption works

We do not hand over artifacts and leave. A licence includes onboarding and accompaniment through the first real project, because the switch to spec-driven and test-driven work with agents is a change of habits before anything else. The framework files without the habit change deliver very little, so the habit change is part of the delivery.

Install it with us

We will look at your codebase and your current workflow, and scope what adoption would actually take.