Day 2 Task 07 Issue report

Task 07. Project Issue Report

Analyze raw project material together — meeting notes, change history, Action Items, issue lists — and automatically write an issue report focused on urgency/priority.

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 4 files in the automation/ folder.
  2. Hand off the issue report: send the **issue report prompt** below in the Codex Client prompt box and build.
  3. Check the report: review whether the report correctly structures login done, sign-up in progress, payment delay issue (PM/high) and upcoming requirement changes (planning team/high).

Download lab materials

Codex request prompt

Mission 2 Prompt
Summarize the current project's main issues and write a project issue report including urgency and priority.

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.