Final result to be created today

Input / Output data pipeline

This is the overall workflow map in which input files pass through the Codex Client during the exercise process and are refined into a result table.

STEP 1. Task 01 - Inconsistency detection

After creating a practice file in the project folder, proceed with contradiction auditing by sending the instructions below to the Codex Client prompt window.

Compare and analyze the three documents ‘meeting-notes.md’, ‘requirements.md’, and ‘screen-specification.md’ in the project folder.

Find and organize items that are contradictory or inconsistent between each document, or items that exist in one document but are missing from the other.
Print the results according to the requirements below.

1. Organize the results in the form of a Markdown table with columns ‘Classification’, ‘Findings and contradictions’, ‘Impact’, ‘Highest authority standard document’, and ‘Recommended action’.
2. When entering development and testing, indicate the impact as ‘high’ for matters that may cause fatal rework.
3. Do not create arbitrary answers, but derive comparative analysis results based on facts only based on the document text.

• The 10% penalty fee policy for meeting minutes is checked to see if any omissions in the requirements definition are caught.
• When processing membership withdrawal, check whether policy inconsistencies (automatic cancellation vs. retention vs. hiding without pop-up) in the three documents are identified.
• In the FR-004 requirements, check whether the logical error in which the evaluation subject was written as Expert rather than Customer was caught.

STEP 2. Task 02 - Change Management

After preparing two types of requirements change files (v1.0 vs v2.0) and existing design/API specifications, we send a change impact mapping directive.

First, analyze which policy has been changed by comparing the 'requirements-before.md' and 'requirements-after.md' files in the project folder.

After that, analyze which part of the ‘screen-specification-v2.md’ and ‘api-specification.md’ documents, which remain at the v1.0 level, where the changed policy content should be reflected.

The results are output in a Markdown table format according to the format below:
1. ‘Change items’, ‘Before change’, ‘After change’, ‘Scope of influence (screen/API)’, ‘Importance’, ‘Actions (guide for specific modifications required)’
2. Additionally, based on the v2.0 requirements, classify the importance of parts that require modification in the order of ‘high/medium/low’ and mark them in the column.

• Check whether a guide for changing the login screen UI and API parameters (oauth_token) has been established in accordance with Google Social Login.
• Check whether the subscription UI is replaced according to the introduction of SMS authentication and whether the required API Payload parameters (phone, verification_code) are reflected.
• Check whether the new dashboard screen is designed according to Admin authority classification and the API role field mapping is checked.

STEP 3. Task 03 - Decision tracking

After preparing an unstructured development chat log (messenger-chat.md), decision logs and follow-up tasks are automatically separated and extracted.

Read the 'messenger-chat.md' conversation log in the project folder and create Decision Log and Pending Items for project management and tracking.

Please perform the analysis according to the conditions below.
1. For matters that have been decided, please fill out the ‘Decision Log’ table. The column must include ‘decision item’, ‘decision content’, ‘decision background/basis’, ‘decision date’, ‘person in charge/subject’, and ‘status’.
2. Organize matters that have not yet been decided and require follow-up review or are on hold in the ‘Pending Items’ table. In the column, please include ‘Pending items’, ‘Follow-up details’, ‘Person in charge’, and ‘Planned due date’.
3. Please do not write fictitious dates or decision-making entities that are not based on the conversation log text.

• In the first launch, check whether the basis (delay in review, etc.) and the subject for deciding to only use Google login and exclude Apple login have been extracted.
• Check whether the reason for holding real-time account transfer, the person in charge (development team) for reviewing overseas Paypal linkage, and follow-up actions have been identified.
• Ensures that Super/Sub Admin level 2 hierarchical authority component decision basis is included to meet security room audit requirements.

Mission 1. Analysis of the impact of changes in membership registration (Task 06)

We use Codex to analyze the impact of the entire system (screen, API, DB, documents) and create a report in response to the customer's change request to "add mobile phone authentication when signing up."

If the mobile phone authentication function is added to membership registration, please find all affected screens, APIs, DBs, and documents and prepare an impact analysis report.

• With the addition of mobile phone authentication, check whether the impact of the sign-up screen (UI) has been detected with the 'High' and 'Modify Screen' actions.
• Verify that the Login/Signup API impact has been detected as 'Medium' and 'API Modification'.
• Check whether the influence of the User DB has been mapped to ‘High’ and ‘Add Column’ actions.
• Make sure you've mapped the impact of your admin screens to 'Low' and 'Add Hit' actions.

Mission 2. Write a project issue report (Task 07)

By analyzing original project data such as meeting minutes, change history, action items, and issue lists, reports on current progress and major issues are automatically created.

Please write a project issue report that summarizes the main issues of the current project and includes urgency and priority.

• Make sure completion (login function) and progress (membership registration function) status are classified correctly.
• Check whether the payment API schedule delay issue is prioritized as ‘high’ and PM responsible.
• Ensure requirements change upcoming risks are mapped to 'High' and Planning Team Responsibility.
• Confirm the administrator authority policy and confirm that the priority of outstanding matters has been accurately determined as 'medium' and the planning team.

Semantic Diff

It's not just comparing lines of text or detecting changes. Be aware of how the core logic of your business requirements (e.g. email verification ➔ SMS mobile number verification) has been revised; This is the principle of mapping the modification guide by dependently interpreting the variable mapping table of the physical files (front-end UI wireframe design and back-end API REST specifications) that have a dependency relationship with it.

Context encapsulation within unstructured conversations

In the flow of informal group chat rooms, such as “Apple will talk again at the next meeting,” and “Bank transfers are on hold for now due to PG review.” AI semantically refines the background factors that led to the final agreement (Apple developer annual account review schedule, delay in PG company contract approval, etc.). This allows the conference room decision-making background (why) to be fully remembered even if project members change.

Synergy of connection flow of three tasks

The planning/design review process is not a one-time task. It serves as an organic design control device that bridges the planning and development gap in the IT project life cycle.

Instructional Design Specifications

Planning and design stage final training task

Learner questions and discussion topics