Example engagement · Northwind OMS

From four client sources to one committed delivery plan.

A retailer needs warehouse scanners to continue working offline while NetSuite remains the system of record. Here is how TalkToBuild turns that ambiguity into an executable pack.

Intake

Whatever the client already had.

E-001BriefWarehouse inventory replacement brief
E-002TranscriptDiscovery call · Operations + IT
E-003FigmaScanner and replenishment flows
E-004Architectureexisting_architecture.md

Scope

A cited baseline the client can approve.

PRODUCT BASELINE · V03 · APPROVED

Warehouse staff can receive, count, and move inventory when connectivity is unavailable.

Local operations reconcile through the sync boundary after connectivity returns. NetSuite remains authoritative for financial inventory.^{[E-002, E-004]}

Architecture

Boundaries and decisions, visible before code.

MODULE

Scanner client

Queues inventory writes offline

MODULE

Sync boundary

Reconciles idempotent operations

MODULE

Inventory service

Owns available-to-promise state

MODULE

NetSuite adapter

Maps committed changes into ERP

Export

A deterministic ZIP for the delivery tool.

AGENTS.md
architecture_map.json
openapi.yaml
schema.sql
backlog/001-tracer-bullet.md
.claude/commands/build-loop.md

Cursor pack

The engineer opens the repository, loads the pack, and starts ticket 001 without another architecture clarification.

Start with what the client sent.

TalkToBuild will sort it, cite it, and turn it into the delivery spine.

Create workspace