Task 01 Specification Inconsistency Detection Practice Guide
📥 Practice Input
- •
meeting-notes.md(meeting minutes) - •
requirements.md(Requirements definition) - •
screen-specification.md(Screen definition)
📤 Practice output (Output)
- • Summary report table of inconsistencies and actions taken
🛠️Practical guide to follow along
- Create file for practice: Click the download buttons below to download 4 files.
automation/Save it within the folder. - Issue report delegation: Build by sending the **issue report prompt** below to the Codex Client prompt input window.
- report check: In the printed report, review whether the classifications for login completion, membership registration progress, payment delay issues (PM responsible/high), and requirements change plans (planning team responsible/high) are structured correctly.
Download practice materials
Codex request prompt
Mission 2 Prompt
Please write a project issue report that summarizes the main issues of the current project and includes urgency and priority.
Expected results report
| Category | Findings and Contradictions | Influence | reference document | Recommended Action |
|---|---|---|---|---|
| Policy/Function | In the meeting minutes, the 10% fee refund policy for cancellation of reservations was confirmed, but the requirements definition (`requirements.md`) was completely missing related information. | high | meeting minutes | Reservation cancellation and 10% penalty refund function requirements must be additionally reflected in the requirements definition document. |
| Policy/Screen | When a member withdraws, the meeting minutes define 'automatic cancellation and full refund' for existing reservations, but the requirements document defines 'retention and maintenance', and the screen definition defines 'hidden processing without pop-up information', so all three documents are different. | high | meeting minutes | After coordination with the planning team, it is necessary to unify the withdrawal logic of the requirements and screen definitions based on the meeting minutes. |
| Function/Screen | In the meeting minutes and screen definitions, it was designed so that 'the user (Customer) evaluates the expert (Expert)', but in the requirements document (FR-004), the subjects were written in the opposite direction so that 'the expert (Expert) evaluates the user (Customer)'. | high | meeting minutes | FR-004 evaluation subject in the requirements definition has been revised and reflected as Customer. |
| screen | In the meeting minutes, it is stated that 'reservation request button is disabled' for non-members, but the screen definition (SCR-001) contradicts it by 'activating non-member reservation button' and entering the schedule without encouraging registration. | middle | meeting minutes | Modified the non-member home screen reservation flow in the screen definition to ‘Induce deactivation or registration pop-up’ |