Day 2 Task 01 Find mismatches

Task 01. Consistency Check

Learn a practical way to automatically find hidden contradictions between different planning docs with Codex Client and build an action report.

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. Create lab files: press the download buttons below and save the 3 files in the automation/ folder.
  2. Hand the review to Codex: send the Codex request prompt below in the Codex Client prompt box and build.
  3. Check the report: confirm the report correctly finds the planted contradictions, like the account deletion auto-cancel conflict and the reversed reviewer/reviewee error.

Download lab materials

Codex request prompt

Task 01 PromptCompare and analyze the three docs 'meeting-notes.md', 'requirements.md' and 'screen-specification.md' in the project folder.

Find and list items that contradict or don't match between the docs, or items that exist in one doc but are missing from another.
Output the result to meet these requirements.

1. Organize the result as a Markdown table with the columns 'Type (feature/screen/policy/term, etc.)', 'Finding and contradiction', 'Impact (high/medium/low)', 'Highest-authority source doc' and 'Recommended action'.
2. Mark items that could cause serious rework when entering development or testing as 'high' impact.
3. Don't invent answers; base the comparison only on facts from the doc text.

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.