Requirements Architecture
Lab Playbook 3

I have read './raw_requirements.md'. Here is a summary of the core business goals:
- Target: Motor Insurance Quote Portal (ShieldMutual UK)
- Primary Flow: User inputs vehicle registration/usage -> System calculates price -> Secure checkout via Stripe.
- Ambiguities Identified: The specification uses vague terms like "easily input", "calculate custom price", "look modern", and "check all the fields" which need concrete definitions.

Performing an INVEST audit on raw_requirements.md:

1. **Independent (I)**: Partial fail. The quote calculation and Stripe payment checkout are bundled, making it dependent on the checkout architecture.
2. **Negotiable (N)**: Pass. The requirements are high-level and negotiable.
3. **Valuable (V)**: Pass. Delivers value by providing a quote calculation.
4. **Estimable (E)**: Fail. Subjective terms like "easily input" and vague calculation rules make estimation impossible.
5. **Small (S)**: Fail. This is a monolithic story. It covers quote forms, calculations, UI look-and-feel, and Stripe integration all in one.
6. **Testable (T)**: Fail. Subjective criteria like "easily input", "look modern", and "check all fields" cannot be verified with binary test assertions.

Recommendation: Decompose this story into three distinct, smaller user stories:
- Story A: Vehicle registration lookup & quote form input
- Story B: Quote calculation logic engine
- Story C: Stripe checkout integration

I have analyzed the gaps. Here are the core missing definitions required:

1. **Quote Form Fields & Validations**:
   - Vehicle Registration: String length, regex pattern matching?
   - Usage Type: Enum options (Social/Domestic, Business, Commute)?
   - Missing validation error messages.

2. **Quote Pricing Calculation Rules**:
   - What base rate is used?
   - What multipliers apply for age or usage type? (e.g. business use = +15%?)

3. **Payment & Stripe Checkout Constraints**:
   - Currency, payment methods (Cards, Apple Pay)?
   - Success/Cancel redirect URLs?

4. **Performance & Accessibility**:
   - Vague "look modern" must be replaced with a style guide.
   - Vague "super fast" must be replaced with a concrete metric (e.g., LCP < 2.5s).

Saving report to invest_report.md...
✅ File saved successfully.

Checking git status:
```bash
$ git status
On branch qe/feature-login-tests
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	invest_report.md
	raw_requirements.md

nothing added to commit but untracked files present
```

I will stage and commit the files.

**Step 1 — Stage files**
```bash
$ git add raw_requirements.md invest_report.md
```

**Step 2 — Commit files**
```bash
$ git commit -m "docs: add INVEST audit report and gap analysis"
[qe/feature-login-tests 2be2c1a] docs: add INVEST audit report and gap analysis
 2 files changed, 45 insertions(+)
 create mode 100644 invest_report.md
 create mode 100644 raw_requirements.md
```

**Step 3 — Show latest commit**
```bash
$ git log -n 1
commit 2be2c1a4b518296a66a1a1dbd04b9015949a2637 (HEAD -> qe/feature-login-tests)
Author: Agentic QE <qe-orchestrator@shieldmutual.co.uk>
Date:   Wed Jul 1 19:33:00 2026 +0100

    docs: add INVEST audit report and gap analysis
```

✅ Requirements audit report saved and committed.

You have successfully audited a raw stakeholder specification, identified estimate blockages and testability gaps, and saved/logged the audit findings locally using Git.