Day 2 Task 03 Decision tracking

Task 03. Decision Tracking

Learn to preserve project history by pulling the owner, approval reason and open items of decisions from unstructured spoken meeting notes or messenger chats into a structured archive.

Task 03 Decision History Extraction Lab Guide

📥 Lab input

  • • messenger-chat.md (planning-dev meeting transcript)

📤 Lab output

  • • Decision Log table
  • • Pending Items table

🛠️ Follow-along lab guide

  1. Get the transcript: click the download button below to get messenger-chat.md, the raw planning meeting chat file.
  2. Ask for decision extraction: send the Codex request prompt below in Codex Client and build.
  3. Check business context: check whether the decision table accurately sums up the reason for dropping Apple login (review delay risk) and why card payment alone was used.

Download lab materials

Codex request prompt

Task 03 PromptRead the 'messenger-chat.md' transcript in the project folder and write a Decision Log and Pending Items for project management and tracking.

Analyze it under these conditions.
1. For settled matters, write a 'Decision Log' table. Columns must include 'Decision item', 'Decision', 'Reason/background', 'Decision date', 'Owner' and 'Status'.
2. Put matters not yet decided, needing follow-up or on hold into a 'Pending Items' table. Columns: 'Pending item', 'Follow-up action', 'Owner' and 'Due date'.
3. Don't make up dates or decision owners not based on the transcript text.

Expected result report

1. Decision Log

Decision item Decision Reason/background Decision date Owner States
Login method Use Google login (Apple login on hold) Apple login dropped from the first spec because of a tight dev schedule and delays in Apple developer account review 2026-07-15 PM Completed
Payment method Credit card payment first Real-time bank transfer on hold for the first launch because of PG contract and review timing 2026-07-16 Dev team (Dev_Lead) Ongoing
Admin permissions 2-level tiered permissions (Super/Sub Admin) PM gave final approval to meet security audit requirements 2026-07-17 PM Completed

2. Pending Items

Pending item Follow-up action Owner Due
Whether to use Apple login On hold for the first launch; review bringing it back at the next meeting PM Next meeting
Whether to support overseas payment Do a technical review of PayPal integration and report results Dev team (Dev_Lead) To PM after technical review

💡 AI use and learning points

In projects, recording the 'background/reason (Why)' of a decision is over 10 times more important for risk management than the result itself. Learn to use AI to systematically keep the specific context and approval history inside messenger/chat flows.

Flow How the three Tasks connect, and wrap-up

Synergy in Requirements Lifecycle Management

In real projects, we learn these three Tasks as a linked sequence to keep planning, design and dev outputs in sync and control decision history.

  1. Step 1. Find mismatches (Task 01)

    Compare meeting notes, requirements doc and screen spec to find contradictions and gaps between docs early. (What is different?)

  2. Step 2. Track decisions (Task 03)

    Parse the meeting transcripts and messenger records behind the contradictions, structure 'why that decision was made' and pending item history, and resolve the issues. (Why is it different?)

  3. Step 3. Manage changes (Task 02)

    Map how requirement changes (v1.0 ➔ v2.0) affect downstream screen plans and API designs, and write specific action history. (What must we fix?)

🎓 The final value of the Day 2 lab

Through today's lab, students went beyond using AI as a simple code generator and built the base to become an 'AI Business Analyst' who corrects complex business design and controls mismatches.