Lesson 5.2 · Weeks 3–4 · Reading: Chapter 5

Task Decomposition and Prompt Sequences


Breaking a complex AI-supported request into bounded, logically ordered stages—each with its own prompt, inputs, outputs, and verification points—so that human authority is preserved throughout.

Estimated study time: 3–4 hours Prerequisite: Lesson 5.1 Module 2 · Weeks 3–4

Table of Contents

1. Lesson Overview

In Lesson 5.1, you learned to build a controlled context package—selecting sources, establishing hierarchies, and minimising information. But even with a perfect context package, a single prompt may not be sufficient for complex tasks. This lesson introduces task decomposition and prompt sequences: the practice of breaking a complex request into bounded, logically ordered stages, each with its own prompt, inputs, outputs, and verification points.

You will learn to identify when a task is too complex for a single prompt, how to divide it into stages with clear dependencies, and how to construct prompt sequences that preserve purpose and constraints across multiple interactions. You will also learn to recognise error propagation—how an error in one stage can cascade into later stages—and when to restart a conversation rather than continuing a drifting interaction.

This lesson builds directly on the context-engineering skills from Lesson 5.1 and prepares you for structured inputs, outputs, and workflows in Lesson 5.3.

Why this matters: Real-world AI-supported tasks—policy analysis, research synthesis, decision support, content creation—are rarely solved in one prompt. Attempting to cram everything into a single interaction leads to overloaded context, overlooked details, and outputs that are difficult to verify. Decomposition gives you control: you can inspect each stage, catch errors early, and maintain human authority throughout the process.

2. Learning Outcomes

By the end of this lesson, you should be able to:

  1. Define task decomposition, prompt sequence, and error propagation.
  2. Identify when a task is too complex for a single prompt.
  3. Decompose a complex request into bounded, logically ordered stages.
  4. Identify dependencies among stages.
  5. Assign inputs and expected outputs to each stage.
  6. Construct prompt sequences using PCAFE-V for each stage.
  7. Preserve purpose and constraints across multiple interactions.
  8. Diagnose error propagation and identify where review should occur.
  9. Decide when a clean restart is preferable to continuing a conversation.
  10. Apply the Organize element of SCOPE to a workflow.

3. Before You Begin

4. Retrieval Practice: Concepts from Lesson 5.1 and Unit 4

Before we begin, let's activate your knowledge from Lesson 5.1 and Unit 4.

Question 1: What is a context package, and what are its main sections?

Show answer

A context package is a structured collection of information and instructions for a bounded AI-supported task. Its main sections include: Purpose, Authorised Instructions, Definitions, Authoritative Sources, Supporting Sources, Constraints, Known Gaps, Conflicts, Prohibited Uses, and Required Output.

Question 2: What is a source hierarchy, and what rules must it include?

Show answer

A source hierarchy is an ordered priority list that specifies which sources take precedence when sources conflict. It must include: priority order, rationale, conflict rule, missing-information rule, and exclusion rule.

Question 3: What are the six elements of PCAFE-V? Briefly describe each.

Show answer

P — Purpose: the legitimate human goal.
C — Context: relevant background, constraints, and sources.
A — Audience: who will read or use the output.
F — Format: structure and presentation of the output.
E — Evaluation: criteria for judging the output.
V — Verification: steps to confirm accuracy and completeness.

Question 4: Why is context minimisation important in AI-supported work?

Show answer

Context minimisation is important because it reduces cognitive load on the AI, reduces the risk of including outdated or untrusted content, improves traceability, limits prompt-injection surface, and respects context-window limits. It does not mean removing all context—it means selecting the right context.

5. Opening Scenario: "The Folder of Twenty Documents"

📌 Scenario — Research Support: Literature Synthesis

You are a research assistant in a public-policy institute. A senior researcher has asked you to prepare a briefing note on the effectiveness of carbon-pricing mechanisms in reducing emissions. The researcher has provided you with a folder of 15 peer-reviewed articles, 3 government reports, and 2 policy briefs from reputable think tanks.

The researcher's request is: "Read all these sources and write a comprehensive briefing note that summarises the evidence, identifies gaps, and makes recommendations for our next project."

You realise that this is far too much for a single prompt. You need to break the task into stages, but you are not sure where to start. You also notice that some sources conflict with others, and some are more recent than others.

Questions to consider:

  1. Why is this task too complex for a single prompt?
  2. What stages might you use to break this task down?
  3. What dependencies exist between the stages?
  4. Where should you place human review points?
Show guided analysis

1. Why is this task too complex? The task involves multiple subtasks: source selection, reading and summarising 20 documents, synthesising findings, identifying gaps, and making recommendations. Each subtask requires different cognitive operations. A single prompt would overload the context window, mix instructions, and produce an output that is difficult to verify.

2. Possible stages:

  1. Stage 1 – Source classification: Classify sources by authority, date, and relevance.
  2. Stage 2 – Source summarisation: Summarise each source individually (or in batches).
  3. Stage 3 – Synthesis: Synthesise findings into themes.
  4. Stage 4 – Gap analysis: Identify gaps and conflicting evidence.
  5. Stage 5 – Recommendations: Draft recommendations based on the synthesis.
  6. Stage 6 – Review and revision: Human review and final revision.

3. Dependencies: Stage 2 depends on Stage 1 (you need to know which sources to summarise). Stage 3 depends on Stage 2 (you need the summaries to synthesise). Stage 4 depends on Stage 3. Stage 5 depends on Stages 3 and 4. Stage 6 depends on all previous stages.

4. Review points: After Stage 2 (review the summaries for accuracy), after Stage 3 (review the synthesis for completeness), and after Stage 5 (review the recommendations before finalising).

6. Task Decomposition

Definition — Task Decomposition

Task decomposition is the process of breaking a complex AI-supported task into smaller, bounded, logically ordered stages, each with its own purpose, inputs, outputs, and verification points.

Task decomposition is a core practice in context engineering. It transforms an overwhelming request into a manageable sequence of steps that you can control, review, and verify.

When to decompose

You should consider decomposition when the task involves multiple distinct operations, such as:

Common misconception: "Decomposition means splitting the task into as many small pieces as possible." False. Over-decomposition can create unnecessary complexity, increase hand-off risks, and make the workflow harder to manage. The goal is to find a balanced decomposition that improves control without adding unnecessary overhead.

How to decompose a task

  1. Define the overall purpose. What is the ultimate goal?
  2. Identify the major operations. What are the distinct kinds of work required?
  3. Order the operations logically. What must happen before what?
  4. Define inputs and outputs for each stage. What does each stage need, and what does it produce?
  5. Add verification and review points. Where must a human check the work?
  6. Identify exceptions and stop conditions. When should the workflow stop?
Example: decomposition of a policy-analysis task
Overall purpose: Prepare a briefing note on carbon-pricing
effectiveness.

Stage 1: Source classification
  – Input: 20 documents
  – Output: List of authoritative, supporting, and excluded sources
  – Review: Human checks the classification

Stage 2: Source summarisation
  – Input: Authoritative and supporting sources
  – Output: 100-word summary of each source
  – Review: Human checks each summary

Stage 3: Thematic synthesis
  – Input: Source summaries
  – Output: Thematic synthesis (3–5 themes)
  – Review: Human checks themes against sources

Stage 4: Gap analysis
  – Input: Thematic synthesis
  – Output: Identification of gaps and conflicts
  – Review: Human reviews gaps

Stage 5: Recommendations
  – Input: Synthesis and gaps
  – Output: Draft recommendations
  – Review: Human reviews and revises

Stage 6: Final review and approval
  – Input: Draft recommendations
  – Output: Final briefing note
  – Approval: Senior researcher approves
Section summary
  • Task decomposition breaks complex tasks into bounded, ordered stages.
  • It improves control, reviewability, and traceability.
  • Decomposition should be balanced—not too coarse, not too fine.

7. Prompt Sequences

Definition — Prompt Sequence

A prompt sequence is a series of stage-specific prompts that together accomplish a complex task. Each prompt in the sequence builds on the outputs of previous stages and preserves the overall purpose, scope, and constraints.

A prompt sequence is more than a collection of prompts. It is a designed sequence in which each stage is carefully specified, and the hand-off between stages is managed.

Elements of a prompt sequence

For each stage in a prompt sequence, you should specify:

Using PCAFE-V in a prompt sequence

Each stage should have its own PCAFE-V specification. The Context element may include the outputs of previous stages. The Purpose and Audience should remain consistent across stages.

Example: Stage 1 prompt in a sequence
Sequence objective: Prepare a briefing note on carbon-pricing
effectiveness.

Stage 1: Source classification

Purpose: To classify a set of documents by authority, date, and
  relevance.
Context: A folder of 20 documents related to carbon pricing.
Audience: The researcher (who will use the classification).
Format: A table with columns: File name, Classification,
  Justification.
Evaluation: Each document is correctly classified.
Verification: Human checks a random sample of classifications.

Prompt:
"You are a research assistant. Your task is to classify the
attached documents. Use these categories: authoritative,
supporting, contextual, outdated, conflicting, irrelevant.
For each document, provide a one-sentence justification.
Output: A table with the columns: File name, Classification,
Justification. Do not include any document that is labelled
'irrelevant' in the final output."
Critical principle: Do not pass errors from one stage to the next. Each stage should be verified before its output becomes an input to the next stage. If an error is detected, the workflow should stop, escalate, or go back to correct the error.
Section summary
  • A prompt sequence is a designed series of stage-specific prompts.
  • Each stage has its own purpose, prompt, output, and verification.
  • PCAFE-V should be applied to each stage.
  • Errors must be caught before they propagate to later stages.

8. Dependencies and Hand‑Offs

In a multi-stage workflow, stages depend on each other. Understanding these dependencies is essential for designing a robust prompt sequence.

Types of dependencies

Table 1. Common dependency types in prompt sequences
Dependency type Description Example
Sequential Stage B cannot start until Stage A is complete. You cannot synthesise until you have summaries.
Data dependency Stage B requires the output of Stage A as input. The synthesis stage requires the source summaries.
Conditional Stage B depends on a decision made in Stage A. If a source is classified as "irrelevant," it is excluded from Stage 2.
Verification dependency Stage B depends on the verification of Stage A. You cannot proceed to synthesis until the summaries are verified.

Hand-off risks

When passing information from one stage to the next, several risks arise:

Mitigation strategies
  • Specify output formats clearly. Use structured outputs (tables, lists, JSON) to reduce ambiguity.
  • Add verification points. Do not pass outputs blindly—review them first.
  • Document the hand-off. Record what was passed, from which stage, and on what date.
  • Use explicit stage boundaries. Each stage should have a clear start and end.
Section summary
  • Dependencies between stages must be identified and managed.
  • Hand-off risks include loss of context, error propagation, ambiguity, and format mismatch.
  • Structured outputs and verification points reduce hand-off risks.

9. Error Propagation

Definition — Error Propagation

Error propagation is the process by which an error, omission, or distortion introduced in one stage of a workflow is carried forward into subsequent stages, potentially compounding or creating new errors.

Error propagation is one of the most significant risks in multi-stage AI-supported workflows. A small error in an early stage can become a major problem by the final output.

Figure 1 (placeholder): [INSERT ERROR-PROPAGATION DIAGRAM] — Error propagation in a three-stage workflow.

How errors propagate

  1. Introduction: An error is introduced in Stage 1 (e.g., a source is mis-summarised).
  2. Propagation: The error is passed to Stage 2 as part of the input.
  3. Amplification: Stage 2 uses the erroneous input to generate a new output, which may amplify or distort the error.
  4. Propagation: The amplified error is passed to Stage 3.
  5. Output: The final output contains the error, which may be harder to detect because it has been "laundered" through multiple stages.
Example: error propagation in a policy-analysis workflow

Stage 1: The AI summarises Source A as stating that "carbon pricing reduces emissions by 20%." In reality, the source states "up to 20% under optimal conditions."

Stage 2: The synthesis stage uses the summary and states: "All sources agree that carbon pricing reduces emissions by 20%."

Stage 3: The recommendations stage proposes policies based on this "fact."

Final output: The briefing note includes a recommendation that assumes a 20% reduction, which is not supported by the source.

Where it could have been caught: At Stage 1, if the summary had been verified against the source. Or at Stage 2, if the synthesis had been checked against the original sources.

Preventing error propagation

Section summary
  • Error propagation occurs when errors from one stage carry into subsequent stages.
  • Errors can be amplified through multiple stages.
  • Verification, structured outputs, traceability, and human review are key prevention strategies.

10. Restart vs. Continue

One of the most important decisions in a prompt sequence is whether to continue an existing interaction or start a new one. Continuing can preserve context and momentum, but it can also accumulate drift and errors.

When to continue

  • The conversation is still on track.
  • The purpose and scope are unchanged.
  • The AI is responding appropriately.
  • No significant errors or misunderstandings have occurred.

When to restart

  • The conversation has drifted off topic.
  • The AI has forgotten key instructions.
  • The context has become too long or cluttered.
  • An error has been detected and you want to start fresh.
  • The task has changed significantly.
  • The AI is repeating itself or providing inconsistent outputs.
When to stop

Sometimes the best decision is to stop—not restart, not continue, but stop the workflow entirely. Stop when:

  • You have identified a critical error that cannot be corrected.
  • The task is no longer appropriate for AI support.
  • You lack the authority or information to proceed.
  • The risks outweigh the benefits.
Example: restart decision

Scenario: You are in Stage 3 of a 5-stage workflow. The AI has started to ignore the source hierarchy and is citing outdated documents. The conversation is now long (12 exchanges), and the AI is becoming less responsive to your instructions.

Decision: Restart. Start a new conversation with a fresh context package that explicitly states the source hierarchy. Do not try to correct the AI in the current conversation—it is too far gone.

Section summary
  • Deciding to continue, restart, or stop is a critical human decision.
  • Continue when the conversation is on track.
  • Restart when drift, errors, or context overload occur.
  • Stop when the risks outweigh the benefits or the task is no longer appropriate.

11. SCOPE: Organize Human and AI Operations

The SCOPE framework provides a comprehensive approach to context and workflow design. In this lesson, we focus on the third element: O (Organize Human and AI Operations).

Figure 2 (placeholder): [INSERT VERIFIED SCOPE WORKFLOW DIAGRAM] — The SCOPE framework, with stage 3 emphasised in this lesson.

O: Organize Human and AI Operations

In this stage, you design the sequence of operations—human and AI—that will accomplish the task. You decide who does what, in what order, and with what dependencies.

Guiding questions:

🧩 Practice: organizing a workflow

Using the Opening Scenario (research support – literature synthesis), organise the workflow into stages. For each stage, specify:

  • The stage name and purpose
  • Whether it is AI-supported, human-led, or both
  • The input and output
  • The verification or review point
Show a possible organisation
Table 2. Workflow organisation for literature synthesis
Stage Responsibility Input Output Review
1. Source classification AI + human (verification) 20 documents Classified list Human checks classification
2. Source summarisation AI Authoritative sources Source summaries Human verifies each summary
3. Thematic synthesis AI Summaries Thematic synthesis Human reviews themes
4. Gap analysis AI + human Synthesis Gap identification Human reviews gaps
5. Recommendations AI Synthesis + gaps Draft recommendations Human reviews and revises
6. Final approval Human Draft recommendations Final briefing note Senior researcher approves
Section summary
  • O (Organize) is about designing the sequence of human and AI operations.
  • It includes specifying stages, inputs, outputs, dependencies, and review points.
  • Human intervention points must be explicitly designed into the workflow.
  • Full human-AI role allocation will be covered in Unit 6.

12. Process Walkthrough: From Complex Task to Prompt Sequence

This walkthrough shows a complete process from receiving a complex request to designing a prompt sequence with verification points.

Step 1: Receive the request

Request: "Prepare a summary of the provincial government's new housing affordability policy, including an analysis of its potential impacts on first-time homebuyers, and recommend whether our organisation should support it."

Step 2: Identify why it is too complex for a single prompt

Step 3: Decompose into stages

  1. Stage 1 – Policy summarisation: Summarise the key provisions of the policy.
  2. Stage 2 – Impact analysis: Analyse the impacts on first-time homebuyers.
  3. Stage 3 – Stakeholder perspectives: Summarise stakeholder submissions.
  4. Stage 4 – Synthesis: Synthesise the analysis into a balanced assessment.
  5. Stage 5 – Recommendation: Draft a recommendation based on the synthesis.
  6. Stage 6 – Final review and approval: Human review and approval.

Step 4: Identify dependencies

Step 5: Design the prompt sequence

Stage 1 prompt (Policy summarisation):
Purpose: Summarise the key provisions of the housing
  affordability policy.
Context: The policy document (attached) is the authoritative
  source.
Audience: Internal policy analysts.
Format: 200-word summary with bullet points.
Evaluation: All key provisions are included.
Verification: Compare the summary to the policy document.

Stage 2 prompt (Impact analysis):
Purpose: Analyse the impacts of the policy on first-time
  homebuyers.
Context: The policy summary (output of Stage 1) and supporting
  research.
Audience: Internal policy analysts.
Format: Table with impact areas and assessments.
Evaluation: Impacts are plausible and supported by evidence.
Verification: Check each impact against sources.

Stage 3 prompt (Stakeholder perspectives):
Purpose: Summarise stakeholder submissions on the policy.
Context: Stakeholder submissions (attached).
Audience: Internal policy analysts.
Format: 150-word summary of key themes.
Evaluation: All major stakeholder groups are represented.
Verification: Compare to original submissions.

Stage 4 prompt (Synthesis):
Purpose: Synthesise the analysis into a balanced assessment.
Context: Stage 1, 2, and 3 outputs.
Audience: Senior leadership.
Format: 300-word synthesis with pros/cons.
Evaluation: Balanced and comprehensive.
Verification: Check against earlier stage outputs.

Stage 5 prompt (Recommendation):
Purpose: Draft a recommendation on whether to support the policy.
Context: Stage 4 synthesis.
Audience: Senior leadership.
Format: 150-word recommendation with rationale.
Evaluation: Recommendation is supported by the analysis.
Verification: Review the logic chain.

Step 6: Add verification and human review points

Step 7: Identify exception and stop conditions

Walkthrough summary
  • Start by recognising when a task is too complex for a single prompt.
  • Decompose the task into bounded, ordered stages.
  • Identify dependencies between stages.
  • Design a prompt sequence with stage-specific prompts using PCAFE-V.
  • Add verification and human review points at key stages.
  • Define exception and stop conditions.

13. Worked Example: Complete Prompt Sequence for a Public‑Health Communication

Context: A public-health communicator needs to prepare a community-friendly summary of a new provincial guideline on indoor air quality, along with a set of FAQs for the public. The guideline is 25 pages long, with technical language.

Step 1: Overall purpose

To produce a community-friendly summary and FAQ set on the indoor air quality guideline.

Step 2: Decomposition

  1. Stage 1 – Extract key provisions: Identify the 10 most important recommendations from the guideline.
  2. Stage 2 – Translate to plain language: Rewrite the key provisions in plain language (grade-8 reading level).
  3. Stage 3 – Generate FAQs: Create a set of 10 FAQs based on the key provisions.
  4. Stage 4 – Review and revise: Human review and revision of the summary and FAQs.
  5. Stage 5 – Final approval: Public-health director approves the materials.

Step 3: Prompt sequence

Stage 1: Extract key provisions
Purpose: Identify the 10 most important recommendations from the
  guideline.
Context: The official guideline (attached) is the authoritative
  source.
Audience: The communicator (who will translate the provisions).
Format: Numbered list of 10 provisions, each with a brief title.
Evaluation: Provisions are the most important for public health.
Verification: Compare to the guideline's executive summary.

Prompt:
"You are a public-health analyst. Review the attached indoor air
quality guideline. Identify the 10 most important recommendations
for the public. For each recommendation, provide a brief title
(5-10 words) and a reference to the section of the guideline.
Output: a numbered list."

Stage 2: Translate to plain language
Purpose: Rewrite the key provisions in plain language.
Context: The list of 10 provisions (output of Stage 1).
Audience: The general public (grade-8 reading level).
Format: Bullet points with plain-language explanations.
Evaluation: Each provision is clear and accessible.
Verification: Use a readability checker.

Prompt:
"Using the attached list of 10 key provisions, rewrite each one
in plain language suitable for the general public. Use short
sentences, avoid jargon, and aim for a grade-8 reading level.
Output: bullet points."

Stage 3: Generate FAQs
Purpose: Create a set of 10 FAQs based on the key provisions.
Context: The plain-language provisions (output of Stage 2).
Audience: The general public.
Format: Question-answer pairs.
Evaluation: FAQs address common questions.
Verification: Check that FAQs are consistent with the provisions.

Prompt:
"Based on the attached plain-language provisions, generate 10
FAQs that the public might ask about the indoor air quality
guideline. For each FAQ, provide a clear, concise answer.
Output: question-answer pairs."

Stage 4: Human review and revision
– Human reviews the summary and FAQs.
– Revises for clarity, accuracy, and tone.

Stage 5: Final approval
– Public-health director reviews and approves the materials.

Step 4: Verification points

Step 5: Exception and stop conditions

Worked example summary
  • A complex communication task was decomposed into five stages.
  • Each stage has a specific prompt using PCAFE-V.
  • Verification points are placed after each stage.
  • Exception and stop conditions are defined.

14. Guided Learning Activities

🧩 Activity 5.2.A: Single Prompt or Sequence?
  • Purpose: To identify when a task is too complex for a single prompt.
  • Learning outcome: Identify when a task requires decomposition.
  • Estimated time: 10–15 minutes.

Instructions: For each task below, decide whether it is suitable for a single bounded prompt, better suited to a prompt sequence, requiring a non-AI process, or requiring specialist review. Justify your decision.

  1. Asking an AI to translate a 500-word document from French to English.
  2. Asking an AI to prepare a 5-page policy analysis using 12 sources, including a recommendation.
  3. Asking an AI to summarise a 2-page meeting agenda.
  4. Asking an AI to draft a legal contract.
Show model analysis
  1. Single prompt. Translation is a bounded, well-defined task that can be done in one interaction.
  2. Prompt sequence. Policy analysis with multiple sources and a recommendation requires decomposition into source selection, summarisation, synthesis, and recommendation stages.
  3. Single prompt. A 2-page meeting agenda is short and bounded.
  4. Specialist review / non-AI process. Drafting a legal contract should be done by a qualified legal professional. AI may assist with drafting, but a lawyer must review and approve.
🧩 Activity 5.2.B: Task-Decomposition Map
  • Purpose: To decompose a complex task into stages with dependencies.
  • Learning outcome: Divide a complex task into bounded and logically ordered stages.
  • Estimated time: 20–25 minutes.

Instructions: Using the Opening Scenario (research support – literature synthesis), create a decomposition map with:

  • Overall purpose
  • Stages (with names and purposes)
  • Dependencies (which stages depend on which)
  • Inputs and outputs for each stage
  • Verification points
  • Human decisions
  • Escalation conditions
Show a possible solution design

Overall purpose: Prepare a briefing note on the effectiveness of carbon-pricing mechanisms.

Table 3. Decomposition map for the literature-synthesis task
Stage Purpose Depends on Input Output Verification
1. Source classification Classify sources by authority, date, relevance None 20 documents Classified list Human checks
2. Source summarisation Summarise each source Stage 1 Authoritative sources Source summaries Human verifies
3. Thematic synthesis Synthesise findings into themes Stage 2 Summaries Thematic synthesis Human reviews
4. Gap analysis Identify gaps and conflicts Stage 3 Synthesis Gap list Human reviews
5. Recommendations Draft recommendations Stages 3, 4 Synthesis, gaps Draft recommendations Human reviews
6. Final approval Finalise and approve Stage 5 Draft Final briefing note Senior researcher

Escalation conditions: If a source conflict cannot be resolved, escalate to the senior researcher. If the synthesis reveals significant gaps, escalate for further research.

🧩 Activity 5.2.C: Prompt Sequence Builder
  • Purpose: To write stage-specific prompts using PCAFE-V.
  • Learning outcome: Construct a prompt sequence that preserves purpose, scope, criteria, and verification requirements.
  • Estimated time: 25–30 minutes.

Instructions: Using the decomposition from Activity 5.2.B, write a prompt for Stage 2 (Source summarisation) and Stage 3 (Thematic synthesis). Each prompt must include all six PCAFE-V elements.

Show a possible solution design

Stage 2 prompt (Source summarisation):

Purpose: To produce a 100-word summary of each authoritative
  source on carbon pricing.
Context: The sources have been classified as "authoritative" in
  Stage 1.
Audience: The policy analyst who will synthesise the sources.
Format: A numbered list with: Source title, Summary (100 words),
  Key claim, Source date.
Evaluation: Each summary accurately reflects the source's main
  argument.
Verification: Compare each summary to the original source.

Prompt:
"You are a research assistant. Your task is to summarise each of
the attached authoritative sources on carbon pricing. For each
source, provide:
1. The source title
2. A 100-word summary of the main argument
3. The key claim or finding
4. The source date
Use only the information in the source. Do not add your own
interpretation. Output: A numbered list."

Stage 3 prompt (Thematic synthesis):

Purpose: To synthesise the source summaries into 3-5 themes on
  carbon pricing effectiveness.
Context: The source summaries from Stage 2.
Audience: The policy analyst who will identify gaps and draft
  recommendations.
Format: Themes with supporting evidence from sources.
Evaluation: Each theme is supported by at least two sources.
Verification: Check that each theme is grounded in the source
  summaries.

Prompt:
"Using the attached source summaries, identify 3-5 themes that
capture the key findings on the effectiveness of carbon pricing.
For each theme, provide:
1. The theme name
2. A 50-word description
3. The sources that support this theme (list by title)
Do not include themes that are not supported by the sources."
🧩 Activity 5.2.D: Error Propagation Analysis
  • Purpose: To diagnose how errors propagate through a workflow.
  • Learning outcome: Diagnose error propagation and identify where review should occur.
  • Estimated time: 15–20 minutes.

Scenario: A three-stage workflow for preparing a policy summary:

  • Stage 1: AI summarises three policy documents.
  • Stage 2: AI synthesises the summaries into a comparative analysis.
  • Stage 3: AI drafts a recommendation based on the synthesis.

Problem: In Stage 1, the AI mis-summarises Document A, stating that it supports Policy Option X when it actually supports Option Y. This error is not detected until Stage 3, when the recommendation is inconsistent with the source.

Task: Identify where the error entered, why it was not detected, the downstream consequences, where review should have occurred, and whether later stages must be repeated.

Show analysis

Where the error entered: Stage 1 (source summarisation). The AI misinterpreted Document A.

Why it was not detected: There was no verification point after Stage 1. The output of Stage 1 was passed directly to Stage 2 without human review.

Downstream consequences: Stage 2 used the incorrect summary to synthesise the comparison, leading to a biased analysis. Stage 3 used the biased analysis to draft a recommendation that was not supported by the source.

Where review should have occurred: After Stage 1, before the summary was passed to Stage 2. A human should have verified that the summary accurately reflected the source.

Whether later stages must be repeated: Yes. Stage 2 and Stage 3 must be repeated after correcting the Stage 1 error. The entire downstream work is invalid because it was based on incorrect input.

Lesson: Verification must occur early. Do not assume that later stages will catch errors introduced earlier.

15. Exercises

📝 Exercise 5.2.1: Determine Whether a Task Requires Decomposition
  • Difficulty: Introductory
  • Estimated time: ~10 min
  • Learning outcome: Identify when a task is too complex for a single prompt.

Scenario: A manager asks you to prepare a report that includes: (a) a summary of a 10-page policy document, (b) an analysis of the policy's financial implications, and (c) a set of recommendations for the next quarter.

Task: Explain why this task requires decomposition, and propose a high-level decomposition (stages and their purposes).

Show answer

Why decomposition is required: The task involves three distinct operations: summarisation, analysis, and recommendation. Each requires different cognitive work. A single prompt would be too long, would mix instructions, and would produce an output that is difficult to verify.

Proposed decomposition:

  1. Stage 1 – Policy summarisation: Summarise the policy document.
  2. Stage 2 – Financial analysis: Analyse the financial implications.
  3. Stage 3 – Recommendations: Draft recommendations based on the summary and analysis.
  4. Stage 4 – Review and finalise: Human review and finalisation.
📝 Exercise 5.2.2: Identify Logical Stages and Dependencies
  • Difficulty: Intermediate
  • Estimated time: ~15 min
  • Learning outcome: Identify logical stages and dependencies.

Scenario: A task: "Review 15 job applications, shortlist the top 5, and prepare interview questions for each shortlisted candidate."

Task: Identify the stages, the dependencies between them, and the inputs and outputs of each stage.

Show solution design

Stages:

  1. Stage 1 – Application screening: Review all 15 applications against criteria. Output: Scored list.
  2. Stage 2 – Shortlisting: Select top 5 candidates based on scores. Output: Shortlist of 5.
  3. Stage 3 – Question generation: Generate interview questions for each candidate. Output: Set of questions.
  4. Stage 4 – Review: Human reviews shortlist and questions. Output: Final shortlist and questions.

Dependencies:

  • Stage 2 depends on Stage 1 (you need the scored list).
  • Stage 3 depends on Stage 2 (you need the shortlist to generate questions).
  • Stage 4 depends on all previous stages.

Inputs/Outputs:

  • Stage 1: Input = 15 applications; Output = Scored list.
  • Stage 2: Input = Scored list; Output = Shortlist of 5.
  • Stage 3: Input = Shortlist; Output = Interview questions.
  • Stage 4: Input = Shortlist + Questions; Output = Final materials.
📝 Exercise 5.2.3: Write One Prompt for Each Stage
  • Difficulty: Intermediate
  • Estimated time: ~20 min
  • Learning outcome: Write stage-specific prompts using PCAFE-V.

Scenario: Using the decomposition from Exercise 5.2.2, write a prompt for Stage 1 (Application screening) and Stage 3 (Question generation). Each prompt must include all six PCAFE-V elements.

Show solution design

Stage 1 prompt (Application screening):

Purpose: To screen 15 job applications against a set of
  criteria.
Context: The job description and the application materials are
  attached.
Audience: The hiring manager who will review the shortlist.
Format: A table with columns: Candidate, Score (out of 10),
  Strengths, Weaknesses.
Evaluation: Each candidate is scored consistently against the
  criteria.
Verification: Check a random sample of applications against the
  scores.

Prompt:
"You are an HR assistant. Your task is to screen the attached 15
job applications against the attached job description criteria.
For each candidate, provide:
- A score out of 10
- Top 2 strengths
- Top 2 weaknesses
Output: A table with the specified columns."

Stage 3 prompt (Question generation):

Purpose: To generate interview questions for each shortlisted
  candidate.
Context: The shortlisted candidates' applications and the job
  description.
Audience: The hiring manager who will conduct the interviews.
Format: For each candidate, 5 interview questions.
Evaluation: Questions are relevant to the job and the candidate's
  background.
Verification: Check that questions are not duplicated across
  candidates.

Prompt:
"Using the attached shortlisted applications and job description,
generate 5 interview questions for each candidate. The questions
should be tailored to each candidate's experience and the job
requirements. Output: For each candidate, a list of 5 questions."
📝 Exercise 5.2.4: Identify Review and Verification Points
  • Difficulty: Intermediate
  • Estimated time: ~10 min
  • Learning outcome: Identify review and verification points.

Scenario: A 4-stage workflow for preparing a briefing note:

  • Stage 1: Source classification
  • Stage 2: Source summarisation
  • Stage 3: Thematic synthesis
  • Stage 4: Recommendation drafting

Task: Identify where verification points should be placed and what each verification should check.

Show answer
  • After Stage 1: Verify that sources are correctly classified (authoritative, supporting, etc.). Check a random sample.
  • After Stage 2: Verify that each summary accurately reflects the source. Check all summaries against original sources.
  • After Stage 3: Verify that themes are grounded in the source summaries and that no themes are missing.
  • After Stage 4: Verify that the recommendation is supported by the synthesis and that it is logically coherent.

Additional checks: Verify that the briefing note as a whole is consistent, well-structured, and meets the audience's needs.

📝 Exercise 5.2.5: Diagnose Error Propagation
  • Difficulty: Advanced
  • Estimated time: ~15 min
  • Learning outcome: Diagnose error propagation.

Scenario: A 3-stage workflow:

  • Stage 1: AI summarises a 50-page policy document.
  • Stage 2: AI identifies key stakeholders based on the summary.
  • Stage 3: AI drafts a communication plan for the stakeholders.

Problem: The Stage 1 summary omits a key section on environmental impacts. As a result, Stage 2 misses a major stakeholder group (environmental NGOs), and Stage 3's communication plan does not include outreach to them.

Task: Identify where the error entered, why it was not detected, the downstream consequences, and what should be done.

Show analysis

Where the error entered: Stage 1. The summary omitted the environmental impacts section.

Why it was not detected: No verification point after Stage 1. The summary was assumed to be complete.

Downstream consequences: Stage 2 missed environmental NGOs. Stage 3 did not include them in the communication plan.

What should be done: Stop the workflow. Return to Stage 1 and correct the summary to include the environmental impacts section. Then re-run Stage 2 and Stage 3. Do not proceed without the correction.

Prevention: Add a verification point after Stage 1 to check the summary against the policy document. Use a checklist to ensure all key sections are covered.

16. Homework Problems

Estimated time: 1.5–2 hours · Formative · Recommended for portfolio preparation.

🧠 Problem 5.2.1: Single Prompt vs. Sequence (I)
  • Difficulty: Introductory
  • Estimated time: ~5 min

Task: For each task below, state whether it is suitable for a single prompt or requires a sequence. Justify your answer.

  1. Translating a 300-word email from French to English.
  2. Preparing a 3-page research summary using 8 academic articles.
  3. Checking a document for spelling and grammar errors.
Show answers
  1. Single prompt. Translation is bounded and well-defined.
  2. Sequence. Requires source selection, reading, summarising, and synthesising.
  3. Single prompt. Spelling and grammar checking is a single operation.
🧠 Problem 5.2.2: Single Prompt vs. Sequence (II)
  • Difficulty: Introductory
  • Estimated time: ~5 min

Task: For each task, decide whether it is suitable for a single prompt, a sequence, or requires a non-AI process. Justify.

  1. Writing a 500-word blog post on a familiar topic.
  2. Preparing a financial forecast for a company using 5 years of data.
  3. Making a hiring decision.
Show answers
  1. Single prompt (if the topic is familiar and the writer has clear ideas).
  2. Sequence. Data analysis, forecasting, and presentation require multiple stages.
  3. Non-AI process / human decision. Hiring decisions involve human judgment, values, and in-person assessment. AI may support, but the final decision must be human.
🧠 Problem 5.2.3: Decomposition Problem
  • Difficulty: Intermediate
  • Estimated time: ~15 min

Task: A task: "Prepare a training manual for new employees on our company's cybersecurity policy. The manual should cover the policy, common threats, best practices, and a quiz." Decompose this task into stages. For each stage, specify the purpose, input, output, and verification point.

Show solution design
  1. Stage 1 – Policy extraction: Extract the key provisions of the cybersecurity policy. Input: policy document. Output: key provisions list. Verification: check against policy.
  2. Stage 2 – Threat identification: Identify common cybersecurity threats. Input: policy and external sources. Output: threat list. Verification: check against authoritative sources.
  3. Stage 3 – Best practices: Identify best practices for each threat. Input: threat list. Output: best practices. Verification: check against industry standards.
  4. Stage 4 – Quiz generation: Generate a quiz based on the manual content. Input: all previous outputs. Output: quiz questions. Verification: check answers.
  5. Stage 5 – Manual assembly: Assemble the manual. Input: all previous outputs. Output: draft manual. Verification: human review.
  6. Stage 6 – Approval: Human approval. Input: draft manual. Output: final manual.
🧠 Problem 5.2.4: Dependency Problem
  • Difficulty: Intermediate
  • Estimated time: ~10 min

Task: Using the decomposition from Problem 5.2.3, identify the dependencies between stages. Which stages depend on which?

Show answer
  • Stage 2 depends on Stage 1 (you need the policy to identify threats).
  • Stage 3 depends on Stage 2 (you need the threats to identify best practices).
  • Stage 4 depends on Stages 1, 2, and 3 (you need all content to generate a quiz).
  • Stage 5 depends on Stages 1–4 (you need all pieces to assemble the manual).
  • Stage 6 depends on Stage 5 (you need the draft to approve).
🧠 Problem 5.2.5: Stage-Prompt Problem (I)
  • Difficulty: Intermediate
  • Estimated time: ~15 min

Task: Write a prompt for Stage 2 (Threat identification) from Problem 5.2.3. Use PCAFE-V.

Show solution design
Purpose: To identify common cybersecurity threats relevant to
  our organisation.
Context: The attached cybersecurity policy and industry threat
  reports.
Audience: New employees who will read the training manual.
Format: A numbered list of threats with a brief description of
  each.
Evaluation: Threats are relevant and up-to-date.
Verification: Check against authoritative cybersecurity sources.

Prompt:
"Using the attached cybersecurity policy and industry threat
reports, identify the 5 most common cybersecurity threats relevant
to our organisation. For each threat, provide a brief description
(2-3 sentences) and a real-world example. Output: A numbered
list."
🧠 Problem 5.2.6: Stage-Prompt Problem (II)
  • Difficulty: Intermediate
  • Estimated time: ~15 min

Task: Write a prompt for Stage 4 (Quiz generation) from Problem 5.2.3. Use PCAFE-V.

Show solution design
Purpose: To generate a 10-question quiz on cybersecurity for new
  employees.
Context: The policy provisions, threat list, and best practices.
Audience: New employees.
Format: Multiple-choice questions with answers.
Evaluation: Questions cover all key topics.
Verification: Check answers against the source materials.

Prompt:
"Using the attached policy provisions, threat list, and best
practices, generate 10 multiple-choice questions for a
cybersecurity awareness quiz. Each question should have 4 options
and a correct answer. Output: A numbered list of questions with
options and answers."
🧠 Problem 5.2.7: Hand-Off Problem
  • Difficulty: Advanced
  • Estimated time: ~15 min

Task: In a workflow, Stage 1 produces a list of key findings, and Stage 2 uses that list to generate recommendations. What could go wrong in the hand-off? What would you do to mitigate the risks?

Show solution design

Potential hand-off risks:

  • Incomplete information: Stage 1 may omit key findings, leading to incomplete recommendations.
  • Format mismatch: Stage 1's output may not be in a format that Stage 2 can easily use.
  • Error propagation: If Stage 1 contains an error, Stage 2 will build on it.
  • Ambiguity: The findings may be vague or unclear, leading to vague recommendations.

Mitigation strategies:

  • Specify output format: Require Stage 1 to output a structured list (e.g., numbered with clear headings).
  • Add verification: Verify Stage 1's output before passing it to Stage 2.
  • Document the hand-off: Record what was passed and when.
  • Include traceability: Ensure that each finding can be traced back to its source.
🧠 Problem 5.2.8: Error-Propagation Problem
  • Difficulty: Advanced
  • Estimated time: ~15 min

Task: A 4-stage workflow has the following error: Stage 1 misidentifies the date of a key policy document as 2022 instead of 2025. This error is not detected until Stage 4, when the recommendation references the outdated policy.

Identify where the error entered, the downstream consequences, and what should be done. How could this have been prevented?

Show solution design

Where the error entered: Stage 1 (data extraction). The AI incorrectly read or interpreted the document date.

Downstream consequences: Stage 2 used the incorrect date to assess policy relevance. Stage 3 used the incorrect date in the synthesis. Stage 4 used the incorrect date to recommend action on an outdated policy.

What should be done: Stop the workflow. Correct the date in Stage 1. Re-run Stages 2–4. Do not use the current output.

Prevention:

  • Verification point after Stage 1: Check all dates against original sources.
  • Structured output: Require Stage 1 to output dates with source references.
  • Human review: A human should review key data points like dates, names, and numbers.
🧠 Problem 5.2.9: Restart vs. Continue Problem
  • Difficulty: Intermediate
  • Estimated time: ~10 min

Task: You are in Stage 3 of a 5-stage workflow. The AI has started to ignore the source hierarchy and is citing outdated documents. The conversation is now 8 exchanges long. Should you continue, restart, or stop? Justify your decision.

Show answer

Decision: Restart. The AI is showing clear signs of drift (ignoring the source hierarchy). The conversation is already 8 exchanges long, and correcting the AI in the current conversation is unlikely to be effective. Starting a new conversation with a refreshed context package will reset the AI's focus.

Rationale: Continuing would risk propagating the error to later stages. Stopping would be appropriate if the task were no longer suitable, but since the task is still valid and the AI can be reset, restarting is the best option.

🧠 Problem 5.2.10: Sequence-Documentation Problem
  • Difficulty: Advanced
  • Estimated time: ~15 min

Task: Document a complete prompt sequence for a task of your choice. Include: overall purpose, stages, dependencies, prompts (using PCAFE-V), verification points, and exception conditions.

Show solution architecture
  1. Choose a task: Select a bounded, low-risk task from your own learning, work, or everyday life.
  2. Define overall purpose: What is the ultimate goal?
  3. Decompose into stages: Identify 3–5 stages with clear purposes.
  4. Identify dependencies: Which stages depend on which?
  5. Write prompts: For each stage, write a prompt using PCAFE-V.
  6. Add verification points: Where will you verify the output?
  7. Define exceptions: What will you do if something goes wrong?

Example (different context): A student preparing a study guide from a course syllabus.

Overall purpose: To prepare a study guide for the final exam
in COMP 3270.

Stage 1: Syllabus extraction
  – Purpose: Extract key topics from the syllabus.
  – Prompt: "Extract the key topics from the attached syllabus."

Stage 2: Topic expansion
  – Purpose: Expand each topic into a set of subtopics.
  – Prompt: "For each topic, generate 3-5 subtopics."

Stage 3: Question generation
  – Purpose: Generate practice questions for each subtopic.
  – Prompt: "For each subtopic, generate 2 practice questions."

Stage 4: Review and revision
  – Human reviews and revises the study guide.
🧠 Problem 5.2.11: Transfer Problem
  • Difficulty: Advanced
  • Estimated time: ~20 min

Task: A researcher asks you to prepare a literature review on "the impact of remote work on employee productivity." They have provided 12 articles, 3 reports, and 2 datasets. Design a prompt sequence for this task, including stages, dependencies, prompts (using PCAFE-V), verification points, and exception conditions.

Show solution design

Overall purpose: To prepare a literature review on remote work and productivity.

Stages:

  1. Stage 1 – Source classification: Classify sources by authority, date, and relevance. Input: 17 items. Output: classified list. Verification: human check.
  2. Stage 2 – Source summarisation: Summarise each authoritative source. Input: authoritative sources. Output: summaries. Verification: human check.
  3. Stage 3 – Thematic synthesis: Identify themes across sources. Input: summaries. Output: themes. Verification: human review.
  4. Stage 4 – Data integration: Integrate dataset findings with the literature. Input: datasets and themes. Output: integrated analysis. Verification: human review.
  5. Stage 5 – Draft review: Assemble the literature review. Input: all previous outputs. Output: draft. Verification: human review.
  6. Stage 6 – Approval: Researcher approval. Input: draft. Output: final literature review.

Dependencies: Stage 2 depends on Stage 1; Stage 3 depends on Stage 2; Stage 4 depends on Stages 2 and 3; Stage 5 depends on Stages 1–4; Stage 6 depends on Stage 5.

Exception conditions: If sources conflict, escalate to the researcher. If data is inconsistent, stop and seek clarification.

17. Mini‑Project: Prompt Sequence Design

📁 Project: Prompt Sequence Design
  • Purpose: To design a complete prompt sequence for a complex, bounded task.
  • Learning outcomes: Identify when a task requires decomposition; decompose a complex task into bounded and logically ordered stages; construct a prompt sequence that preserves purpose, scope, criteria, and verification requirements.
  • Estimated effort: 90–120 minutes.

Available contexts

Choose one of the following contexts, or propose your own (must be approved by your instructor):

  • Educational: Creating a study guide or exam review from a course syllabus and materials.
  • Professional: Preparing a policy analysis or briefing note from multiple sources.
  • Research: Conducting a literature review on a specific topic.
  • Everyday life: Planning a complex event or project.

Required deliverable

Using the task you choose, develop a complete prompt sequence that includes all sixteen elements listed below.

  1. Overall purpose
  2. Scope
  3. Source package (from Lesson 5.1)
  4. Stage list (names and purposes)
  5. Dependencies (which stages depend on which)
  6. Stage inputs (what each stage requires)
  7. Stage-specific prompts (using PCAFE-V)
  8. Stage outputs (what each stage produces)
  9. Evaluation criteria for each stage
  10. Verification points (where and what to verify)
  11. Human review points (where a human must review)
  12. Exception conditions (what to do when something goes wrong)
  13. Restart condition (when to restart the interaction)
  14. Stop condition (when to stop the workflow entirely)
  15. Sequence diagram (visual representation of the workflow)
  16. Prompt-version record (version, date, author, changes)

Privacy and integrity requirements

  • Do not use real personal, confidential, proprietary, or security-sensitive information.
  • Use synthetic, public, or generalised information.
  • If you use real sources, ensure they are publicly available and properly cited.
  • Do not use this project for high-stakes decisions.

Self-review checklist

  • ☐ Have I clearly stated the overall purpose?
  • ☐ Have I decomposed the task into logical stages?
  • ☐ Have I identified dependencies between stages?
  • ☐ Have I written a prompt for each stage using PCAFE-V?
  • ☐ Have I added verification points?
  • ☐ Have I added human review points?
  • ☐ Have I defined exception, restart, and stop conditions?
  • ☐ Have I recorded a sequence version?
Show Hint 1: Start with purpose and scope

Begin by defining your overall purpose as clearly as possible. What is the specific, bounded goal? Then define the scope: what is included, what is excluded, and what system will you use?

Show Hint 2: Decompose into stages

Identify the major operations required. What must happen first? What must happen next? Aim for 3–6 stages—too few and you lose control, too many and you add overhead.

Show Hint 3: Identify dependencies

Draw a dependency diagram. Which stages depend on which? What information must flow from one stage to the next?

Show Hint 4: Write prompts

For each stage, write a prompt using PCAFE-V. Be specific about the input, output, and verification requirements.

Show solution architecture
  1. Choose a task that is bounded and low-risk.
  2. Define purpose — be specific about the overall goal.
  3. Decompose — identify 3–6 stages with clear purposes.
  4. Identify dependencies — which stages depend on which?
  5. Write prompts — for each stage, use PCAFE-V.
  6. Add verification — where and what to check.
  7. Add human review — where a human must intervene.
  8. Define exceptions — what to do when things go wrong.
  9. Define restart and stop — when to restart or stop.
  10. Record the version — date, author, changes.
Show illustrative partial example (different context)

Context: A student is preparing a study guide for a history exam. The task is to create a 10-page study guide from the course syllabus, lecture notes, and textbook.

Overall purpose: To prepare a 10-page study guide for the history
exam.

Stages:
1. Topic extraction – Extract key topics from the syllabus.
2. Content gathering – Gather relevant content from lecture notes
   and textbook.
3. Content organisation – Organise content by topic.
4. Study guide drafting – Draft the study guide.
5. Review and revision – Human review and revision.

Stage 1 prompt:
Purpose: To extract key topics from the history syllabus.
Context: The syllabus is attached.
Audience: The student who will study from the guide.
Format: Numbered list of topics.
Evaluation: Topics are complete and accurately extracted.
Verification: Compare to the syllabus.
Prompt: "Extract the key topics from the attached history
syllabus. Output: a numbered list."

Dependencies:
– Stage 2 depends on Stage 1 (you need topics to gather content).
– Stage 3 depends on Stage 2 (you need content to organise).
– Stage 4 depends on Stage 3 (you need organised content to draft).
– Stage 5 depends on Stage 4 (you need a draft to review).

Verification points:
– After Stage 1: Verify topics against the syllabus.
– After Stage 2: Verify content against sources.
– After Stage 4: Verify the draft against the syllabus and notes.

Exception conditions:
– If a topic is missing, escalate to the instructor.
– If content is contradictory, note the conflict and seek
  clarification.

Note: This is a partial example. Your complete project must include all sixteen elements.

18. Self‑Check Quiz

~20 minutes · Formative · Ungraded. Explanatory feedback is provided for every item.

Question 1: What is task decomposition?

Select one:
Show answer and explanation

Answer: b

Explanation: Task decomposition is the process of breaking a complex task into smaller, bounded stages. Option (a) is the opposite—cramming everything into one prompt. Option (c) describes a multi-task prompt, which is not decomposition. Option (d) is context minimisation, not decomposition.

Question 2: When should you consider decomposing a task?

Select one:
Show answer and explanation

Answer: b

Explanation: Decomposition is appropriate when a task involves multiple distinct operations that require different cognitive work. Options (a) and (c) describe simple tasks that do not require decomposition. Option (d) is unrelated.

Question 3: What is a prompt sequence?

Select one:
Show answer and explanation

Answer: b

Explanation: A prompt sequence is a designed series of stage-specific prompts that work together to accomplish a complex task. Option (a) describes unrelated prompts. Option (c) describes a multi-instruction prompt, not a sequence. Option (d) describes repetition.

Question 4: What is error propagation?

Select one:
Show answer and explanation

Answer: b

Explanation: Error propagation is the process by which an error from one stage is carried forward into subsequent stages, potentially compounding. Options (a) and (d) describe error correction, not propagation. Option (c) describes multiple errors in one stage.

Question 5: True or False: You should always continue a conversation rather than restarting it, because continuing preserves context.

Select one:
Show answer and explanation

Answer: False

Explanation: While continuing can preserve context, it can also accumulate drift and errors. Restarting is often preferable when the conversation has drifted, the AI has forgotten key instructions, or the context has become too cluttered. The decision to continue or restart depends on the situation.

Question 6: What is the main purpose of a verification point in a prompt sequence?

Select one:
Show answer and explanation

Answer: b

Explanation: The main purpose of a verification point is to catch errors before they propagate to later stages. It is a quality-control step. Options (a), (c), and (d) are not purposes of verification.

Question 7: In the SCOPE framework, what does the O stand for, and what is its focus?

Select one:
Show answer and explanation

Answer: a

Explanation: In SCOPE, O stands for Organize Human and AI Operations. It is about designing the sequence of stages, inputs, outputs, and responsibilities. Options (b), (c), and (d) are not the meaning of O in SCOPE.

Question 8: What should you do if you detect an error in Stage 2 of a 5-stage workflow?

Select one:
Show answer and explanation

Answer: b

Explanation: If you detect an error in Stage 2, you should stop the workflow, correct the error, and re-run the affected stages (2–5). Options (a), (c), and (d) risk propagating the error and producing an invalid final output.

19. Assignment Connections

Assignment 2: Prompt Engineering Portfolio

Unit 5 provides advanced support for Assignment 2. As you work through this lesson, retain the following materials for your portfolio:

  • Task-decomposition map — the stages, dependencies, and inputs/outputs.
  • Prompt sequence — the stage-specific prompts you designed.
  • Verification points — where and how you verified the outputs.
  • Human decisions — where humans intervened and what they decided.

At the end of Unit 5, you will extend at least one portfolio entry into a context-engineered design. For now, focus on building a strong foundation.

📝 Assignment 1: Reflective Journal

Unit 5 journal prompts will address your decomposition and sequencing decisions. For this lesson, consider:

  • How did you decide how many stages to use?
  • What dependencies did you identify, and how did you manage them?
  • Where did you place verification points, and why?
  • What would cause you to restart a conversation instead of continuing?

Do not provide model journal answers. These are for your personal reflection.

Show reflection-planning checklist
  • ☐ I can identify when a task requires decomposition.
  • ☐ I can decompose a complex task into logical stages.
  • ☐ I can identify dependencies between stages.
  • ☐ I can write stage-specific prompts using PCAFE-V.
  • ☐ I can diagnose error propagation and place verification points.
  • ☐ I can decide when to continue, restart, or stop.

20. Key Takeaways

Remember these points
  • Task decomposition breaks complex requests into bounded, logically ordered stages.
  • A prompt sequence is a series of stage-specific prompts that together accomplish a complex task.
  • Each stage should have a clear purpose, input, output, prompt (using PCAFE-V), and verification point.
  • Dependencies between stages must be identified and managed.
  • Error propagation occurs when errors from one stage are carried forward into later stages.
  • Verification points are essential for catching errors early.
  • You must decide when to continue (on track), restart (drift or errors), or stop (risks outweigh benefits).
  • The Organize element of SCOPE is about designing the sequence of human and AI operations.
  • Documentation of stages, prompts, and decisions is essential for traceability.

21. Key Terms

Task decomposition
Breaking a complex task into smaller, bounded, logically ordered stages.
Prompt sequence
A series of stage-specific prompts that together accomplish a complex task.
Dependency
A relationship in which one stage relies on the output of another.
Hand-off
The transfer of information from one stage to the next.
Error propagation
The process by which an error from one stage is carried forward into subsequent stages.
Verification point
A point in the workflow where output is checked for accuracy and completeness.
Human review point
A point where a human must intervene and make a decision.
Restart
Starting a new interaction with a refreshed context package.
Stop condition
A condition that triggers the termination of the workflow.
Exception condition
A condition that triggers an escalation or special handling.
Traceability
The ability to link outputs back to specific stages, prompts, and sources.
Organize (SCOPE)
The element of SCOPE that focuses on designing the sequence of human and AI operations.

22. Looking Ahead: Lesson 5.3

In this lesson, you learned to decompose complex tasks into prompt sequences with verification points. In Lesson 5.3, you will learn to design structured inputs and outputs, connect stages into multi-stage workflows, and establish permission boundaries. You will also learn to preserve traceability from source to output.

After Lesson 5.3, you will move on to drift detection, prompt injection, and the complete SCOPE framework in Lesson 5.4.

23. Sources & Further Reading

Note: All page numbers, specific definitions, and direct quotations from the textbook are to be confirmed from the supplied course materials. [PAGE NUMBER TO BE CONFIRMED]

⚠️ Note

Some textbook content, definitions, examples, and figures are marked with placeholders. These will be supplied by the course coordinator or subject-matter expert.


👤