Day 2 Task 06 Impact analysis

Task 06. Impact Analysis

Use Codex Workspace to reason about the screens, APIs, DB and doc schemas affected in a chain by a request to add phone verification at sign-up.

Task 01 Spec Mismatch Lab Guide

📥 Lab input

  • • meeting-notes.md (meeting notes)
  • • requirements.md (requirements doc)
  • • screen-specification.md (screen spec)

📤 Lab output

  • • Summary report table of contradictions and actions

🛠️ Follow-along lab guide

  1. Understand the request: identify the customer's change request "add phone verification at sign-up".
  2. Codex impact analysis: send the impact analysis prompt in the Codex Client prompt box and build.
  3. Check the report: review whether the report correctly maps actions for the sign-up screen (high), login API (medium), User DB (high) and admin screen (low).

How this lab works

This mission is a lab in reasoning about the ripple effects of a new change request based on the whole Codex Workspace project context (UI plans, API specs, DB schema, etc.). No lab file download needed — just copy the prompt below into Codex Client.

Codex request prompt

Mission 1 Prompt
If phone verification is added to sign-up, find every screen, API, DB and doc affected and write an impact analysis report.

Expected result report

Type Finding and contradiction Impact Source doc Recommended action
Policy/feature The meeting notes confirmed a 10% fee refund policy for booking cancellations, but the requirements doc (`requirements.md`) leaves it out completely. High Meeting notes Add a requirement for booking cancellation and 10% penalty refunds to the requirements doc
Policy/screen For existing bookings when a member deletes their account, the meeting notes say 'auto-cancel and full refund', the requirements doc says 'keep stored', and the screen spec says 'hide with no notice pop-up' — all three docs differ. High Meeting notes After the planning team agrees, align the deletion logic in the requirements and screen spec to the meeting notes
Feature/screen The meeting notes and screen spec design 'the user (Customer) rates the expert (Expert)', but the requirements doc (FR-004) reverses it: 'the expert (Expert) rates the user (Customer)'. High Meeting notes Change the rater in FR-004 of the requirements doc to Customer
Screen The meeting notes say 'booking button disabled' for non-members, but the screen spec (SCR-001) contradicts it with 'Book button enabled for non-members' and entering the schedule without a sign-up prompt. Medium Meeting notes Change the non-member home booking flow in the screen spec to 'disabled or sign-up pop-up'

💡 AI use and learning points

Checking productivity is highest when you train AI as a 'careful Reviewer', not an 'answer writer'. It's a practical method that checks mismatches between the 3 docs early, saving rework costs from design gaps by about 100 times.