SDLC Automation
Loan application status tracker · synthetic data
Live · Mesh API
Input · version 1

Business brief

Start from a short brief, the kickoff notes and the policies that apply. The Brief to BRD skill turns them into the bank's BRD template. Use synthetic or masked inputs only.

What is wrong today, what the bank wants, and how it will measure success.

Decisions and open items from kickoff or workshops.

The parts of bank policy the feature must respect, with the policy name.

Before anything leaves

Mesh will receive placeholders for 1 email, 1 mobile number.

Every prompt passes through a masker on the server before it reaches Mesh, whichever skill sends it. Names are not detected, so pilot briefs must be synthetic.

What happens next

  1. 1Brief to BRD writes the BRD; the business analyst approves the requirements baseline.
  2. 2BRD to user stories; the product manager signs off scope.
  3. 3Stories to test cases, one Mesh call per story; the QA lead approves the test plan.
  4. 4Test cases to UAT pack; the traceability check runs, then the UAT coordinator signs off.