The problem everyone has
You use Claude, Cursor, Copilot. Works great for one-off questions. But when you ask for something more ambitious...
Without methodology
- Invents imports that don't exist in your project
- Ignores your patterns and writes code in its own style
- Doesn't validate if what it generated actually works
- Hallucinates files, functions and APIs that never existed
- One day it generates well, the next it generates garbage. No way to predict which.
With NexusAgile
- Reads your real codebase before generating a single line
- Uses your existing files as explicit exemplars
- QA Agent verifies each Acceptance Criteria with evidence
- Adversary Agent attacks the solution before it reaches review
- Reproducible pipeline: same results every sprint
What is NexusAgile
A development methodology where specialized AI agents execute a complete engineering pipeline (analysis, design, implementation, adversarial attack, validation) and humans make decisions at gates.
Sprints, roles and ceremonies
Planning, standups, retrospectives. PO, TL, Dev, QA, SM. Velocity and carry-over as team metrics.
Spec first, code second
Nothing is implemented without an approved SDD. Explicit contracts with Story File. Traceability with file:line evidence.
9 specialized AI agents
Who specifies does NOT implement. Who implements does NOT validate. Segregation of duties applied to AI.
Adversarial Review
One AI agent attacks another's solution before it reaches review. 8 categories: security, drift, regression, edge cases.
The human decides WHAT. The agents decide HOW. The gates ensure nobody skips the process. Not humans. Not AI.
The pipeline
Between gates, the pipeline runs on its own. It only stops where it needs your decision.
Context
AI reads your real codebase, detects stack, patterns, structure
Discovery
AI generates Work Item with precise Acceptance Criteria
Spec / SDD
AI designs solution referencing YOUR code as exemplar
Story File
AI generates the implementation contract: waves, files, constraints
Implementation
AI implements following the Story File, wave by wave
Adversarial Review
A different AI agent attacks the solution looking for flaws across 8 categories
QA Validation
Verification of each AC with file:line evidence
3 modes. Not everything needs the full pipeline.
FAST is not 'no process'. It's adapted process. AI auto-triages and escalates to QUALITY if it detects complexity.
Trivial change
1–2 files, <30 lines, no DB, no new logic
- Fix a typo
- Change a color
- Update static text
MVP from scratch
First version of an app, investor demo, new prototype
- Greenfield app
- Hackathon demo
- New feature MVP
Production feature
Payment flows, authentication, dashboards with DB, anything reaching real users
- Payment flow
- Auth system
- Metrics dashboard
When in doubt, use QUALITY. The extra steps exist to prevent the bugs that cost you hours to debug in production.
9 agents. Specialization, not generalism.
Who specifies doesn't implement. Who implements doesn't validate. The same segregation of duties principle from security, applied to AI.
Analyst
Extracts requirements, normalizes the HU
Understands the WHAT
Architect
Reads codebase, designs SDD, generates Story File
Decides the HOW
UX
Microcopy, flows, accessibility
Protects the user
Dev
Implements ONLY from Story File
Executes without inventing
Adversary
Attacks the solution looking for flaws
Breaks what Dev built
QA
Validates each AC with evidence
Verifies with tests
SM
Facilitates ceremonies
Coordinates the team
Triage
Abbreviated pipeline for trivial changes
Avoids over-engineering
Docs
Documents everything
Leaves traceability
Anti-hallucination. The differentiator.
3 mechanisms that guarantee the AI generates code that follows YOUR actual project, not an imagined one.
Codebase Grounding
Before generating anything, the agent reads real files from your project, extracts naming patterns, imports and structure, and documents what it read in a Context Map.
// Context Map generated by Architect Stack: Next.js 14 App Router Auth pattern: src/lib/auth.ts:15 API pattern: src/app/api/recipes/route.ts:5 DB client: src/lib/supabase.ts:8
Exemplar Pattern
Every SDD decision references a real file from your codebase. If the exemplar doesn't exist, the agent looks for it. If it can't find it, it escalates.
| Pattern | File:Line | | API handler | src/app/api/auth/route.ts:5 | | Component props | src/components/Card.tsx:8 | | Auth check | src/lib/auth.ts:15 |
Constraint Directives
The Story File includes explicit rules about what's allowed and what's forbidden. Eliminates the most common AI error class: inventing solutions when one already exists.
REQUIRED: Use getCurrentUser() from src/lib/auth.ts REQUIRED: Follow pattern from src/app/api/recipes/route.ts FORBIDDEN: No localStorage for sensitive data FORBIDDEN: No manual join table — use ORM relation
The difference in numbers
Real scenario: a favorites feature. DB + API + UI + Auth.
For teams of any size
NexusAgile scales from 1 person to teams of 12+. The process stays the same; only who does what changes.
You are PO + TL + Dev. Auto-approved gates. AI with maximum delegation.
PO (scope) + TL/Dev (technical). Separate gates: the person who approves scope doesn't implement.
PO + TL + 1–2 Devs. Real human peer review. Rotating SM.
Dedicated roles: PO, TL, 2+ Devs, QA Lead, SM. HU parallelism.
Split into teams. Scrum of Scrums. Cross-team protocol.
Gates belong to people, not bots
Only the exact text activates a gate. Saying 'yes' or 'ok' activates nothing. This isn't bureaucracy. It's traceability.
Case Types. Not all HUs are equal.
NexusAgile automatically detects when an HU needs additional checks. The Case Type doesn't change the pipeline. It enriches it with specific checks.
Any database schema change: ALTER TABLE, new tables, type changes.
Adds to pipeline:
Rollback plan, down migration, staging verification
Changes to public endpoints, response types, or any interface others consume.
Adds to pipeline:
Backward compatibility, consumer notification, contract tests
New environment variables, infrastructure changes, secrets or deployment configuration.
Adds to pipeline:
Env vars in all environments, secrets check
Reported or detected vulnerability. Full AR is mandatory. No FAST mode for this.
Adds to pipeline:
Mandatory full AR, find variants, vulnerability test
Migration or transformation of existing production data. Never easily undoable.
Adds to pipeline:
Idempotent script, mandatory dry-run, human supervision
In 15 minutes
Your first HU will be slower while you learn the flow. From the second one on, you'll know exactly what to expect at each step.
Install the skill
Clone the repository inside your project. One command.
mkdir -p .claude/skills git clone https://github.com/ferrosasfp/nexus-agile-enterprise \ .claude/skills/nexus-agile
Generate context
Open Claude Code and say one line. The AI scans your stack, dependencies, structure and patterns.
# In Claude Code: "NexusAgile, this is a new project. Read the codebase and generate project-context.md"
Your first HU
Say what you want. The pipeline starts automatically.
# In Claude Code: "NexusAgile, process this HU: As a user, I want [your feature]"
For teams
Each role reads only what they need. No need to read everything.