Software Development
An AI delivery team with human gates. The Software Development package installs two governed, spec-driven delivery workflows where agents do the engineering work — define, design, implement, validate, document, and review — and your team approves at every gate before anything merges.
What you get
| Component | Contents |
|---|---|
| Workflows | Feature Request (Define → Design → Implement → Validate → Document → Review → Approval) and Bug Fix (Reproduce → Fix → Validate → Approval), each with rework loops and a final human approval gate |
| Service | A Product Backlog intake with Feature Request and Bug Report forms — anyone in your company can submit; no seat required |
| Delivery agent | One agent seated on every working phase with a phase-specific job (specify, plan, implement, verify, review, document) via the included responsibility-matrix template |
| Roles | Author, Reviewer, Approver, Triage Lead — assigning one authorizes the member's seat |
| Starter documents | A constitution.md (the delivery rules agents must obey — you ratify it, only you change it) and a product.md (your product record, which grounds every specification) |
How the loop works
- Someone submits a Feature Request or Bug Report to the Product Backlog.
- On acceptance, the workflow starts. At each phase, the delivery agent works in your repository on a dedicated branch: it writes the spec, plans the approach, implements with tests, validates against the acceptance criteria, updates docs, and reviews the diff.
- Every phase ends at a gate. You read the phase's report in Nembl (spec, plan, diff, verdicts — no tab-switching) and approve, reject for a re-run, or send it back to an earlier phase with your comments. Agents receive your comments on re-entry and act on them.
- When the Review phase's gate is approved, the reviewer identity posts an approving pull-request review on your behalf; the final Approval gate merges — satisfying your branch protection rather than bypassing it.
- Cancel is available at any phase; a cancelled workflow returns the request to a state you can re-accept later.
Prerequisites
- A paid Nembl plan.
- A GitHub organization where you can install two GitHub Apps: the delivery agent (authors branches and pull requests) and the reviewer (posts the approving review). You choose exactly which repository they may access.
- An AI provider API key — the package runs on your own Anthropic key (bring-your-own-key), stored in your Nembl vault. You pay your provider directly for model usage; Nembl never marks it up.
Setup
Install the package, then open Set up on the add-on card. The checklist walks you through the four steps and verifies each one:
- Install the GitHub Apps on your organization, granting access to your chosen repository.
- Add your API key to the vault.
- Bind the repository — Nembl verifies the Apps can actually reach it.
- Add the starter documents — one click commits
constitution.mdandproduct.mdtemplates to your repository; edit them to match your team's rules, then ratify. The constitution is yours: agents obey it and never edit it.
A connection preflight on the same page shows the live health of both App connections so a misconfiguration explains itself before your first run.
Usage allowances
Your subscription includes a monthly allowance of workflow runs that scales with seats (a base allowance plus an increment per seat) and a limit on concurrently running workflows. When a limit is reached, starting another run is blocked with a clear message — add seats, wait for the month to reset, or finish a running workflow. Limits protect you from surprise usage; there are no overage charges.
Data handling
- Your code stays in your repository. Agents clone it into an isolated, single-use execution environment for the duration of a job, work on a branch, and push back to your repository — nothing is retained between jobs.
- Model calls use your own key. Prompt content (including relevant repository context) is sent to your AI provider — Anthropic, under your own agreement with them — to perform the work. Nembl does not use your code or prompts to train anything.
- Credentials. Your API key lives in your Nembl vault; repository access uses short-lived, repository-scoped tokens minted from the GitHub App installations you control — uninstalling the Apps revokes access immediately.
- Isolation. Each job runs with only its own tenant's credentials and workspace; platform credentials are never exposed to agent sessions.
Frequently asked
Does everyone on my team need a seat? No. Submitting requests and reading their progress is open to all members. Seats are for operators — the people holding package roles who work the backlog and approve gates. The minimum viable team is one Approver.
What happens if we cancel? Execution pauses; everything you built — requests, history, workflows, documents — remains visible. Resubscribe and it all works again, exactly as configured.
Can agents change our delivery rules? No. constitution.md is human-ratified and read-only to agents. Proposed refinements to your product record surface at approval gates and merge only when you accept them.
Which repositories can agents touch? Only the one you bound, and only through the App installations you control. A repository removed from the installation's access is denied at the next run.