Skip to content

Cohort Session 2 Frame and Spec

github-actions[bot] edited this page Oct 2, 2026 · 2 revisions

Session 2 · Frame and spec

What is the candidate worth, how often must it be right, and what does a spec an agent can be built from look like?

Part of the Cohort Kit. Ninety minutes. The arithmetic session: by the end the room has a value line, a bar derived from damage and saving, an autonomy decision, and has seen the one hard gate: the sign-off that decides whether anything gets built.

Pre-reading (about 35 minutes)

  • P0 · Frame — is an AI agent worth building: the pain register, the AI-fit verdict, the value line, the autonomy decision
  • P1 · Design and spec — a spec an agent can build from, and the decisions it deliberately leaves to the builder
  • The one hard gate — why the spec, the bar and the guardrails are settled before P2 opens, and nothing else is

Bring. The pain register from session 1's homework, with numbers. Last quarter's figures for cases per day and cost per wrong case, if the team has them.

You will leave with. A value line for the candidate, a bar with the damage and saving it came from, an autonomy decision record, and the list of what the hard gate needs before the build starts.

Run-sheet

Minutes Block Do this Material
0–10 Recap What are the four P0 artefacts? What are the three things the hard gate needs? What is a decision left to the builder? —
10–35 The idea Walk the P0 map from the lesson, then the hard-gate picture. In the workbench, run the value line calculator on SkyWays' numbers live, then the acceptance bar calculator, so the room sees the bar move when the damage figure moves P0 · Frame · The hard gate · Value line · Acceptance bar
35–65 Exercise Pairs do A3 · the value line and B1 · deriving a bar on the team's candidate, using the pain register. Then every pair puts its bar on the board. The spread is the exercise: find the assumption that differs A3, B1 · Formulas
65–80 Decision The room settles one damage figure and one saving figure, derives the bar from them, and records the autonomy level for the riskiest action with the kind of door it is. Then lists what the hard gate still needs Autonomy decision record · Hard or soft gate classifier · Templates · Frame and Specify
80–90 Close Homework named. One sentence each: what does the bar make you want to change about the candidate? —

Facilitator notes

  • The bar will come out high. A refund with $600 of damage needs about 98% to break even. The lesson the room needs is the lever: a person on the charge drops the damage, and the same step needs 71%. Do not let the room conclude "we cannot build this"; let it conclude "not at that autonomy level".
  • Spread on the board is good. If every pair has the same bar, somebody copied. Ask which assumption differs before checking against the worked answer; the assumption is the session.
  • "Decisions left to the builder" is the part of P1 people skip. Have the room name three for the candidate. If it cannot, the spec is a wish list.
  • Ten-minute version: the hard gate in one sentence, the bar formula on the whiteboard with the SkyWays numbers, then straight to B1 on the candidate.

Homework

The spec, in the product manager's Specify template, with the decisions left to the builder marked as such, and the bar with its damage and saving beside it. The engineer or architect in the room reviews it before session 3 and marks one thing the builder could not build from as written.

Next

Session 3 · Build, run and the loops — how it is built in proven slices, run in production, and kept honest by the eight loops. Back to Session 1.

🗺️ Navigate

🏠 Wiki Home

▶ Start

▶ Start here · 55 lessons, on the site ↗

  1. Getting started · 2
  2. Agentic PDLC fundamentals · 9
  3. Methods decoded · 7
  4. Running delivery · 13
  5. By role · 9
  6. Teams and organisation · 4
  7. Practice · 4
  8. Interviews and careers · 7

📗 Method and reference

The method
The Agentic PDLC
The Eight Loops
Gates & Governance
The Evidence Pack

The journey · end to end
Product manager
Solution architect
Engineering lead
QA lead
DevOps & platform

The method · by role
Product manager
Solution architect
Engineering lead
QA lead
DevOps and platform
Sponsor

How to
Run an NFR workshop
Design an agent on paper
Build, buy or borrow
Cut sprints into bolts
Review by risk band
Prove the bar
Control the token bill
Hold the security boundary
Run a missing-control postmortem

Reference
Mental Models
Glossary
Formulas & Calculators
Decision Trees
Scenario Library
Exercises & Answers
Anti-Patterns
Sources & Confidence
Where do I find…?


📚 Course and labs

The course companion · Labs

The 16 modules
  1. Agentic Foundations
  2. LLM Intuition and the AWS Bridge
  3. Amazon Bedrock Essentials
  4. Amazon Bedrock Agents
  5. Agent Builder, Knowledge Bases and Guardrails
  6. The Agent Loop: No Framework to Strands
  7. Strands Foundations: Tools, Memory and MCP
  8. Multi-Agent Patterns with Strands
  9. LangChain and LangGraph
  10. LLM Memory Mechanics
  11. RAG, OpenSearch and LiteLLM
  12. Amazon Bedrock AgentCore
  13. A2A and A2UI: Agent Interoperability
  14. Agentic QA and Evaluation
  15. End-to-End Production Pipeline
  16. Agentic Product Lifecycle

Learning paths · Field guide
Study Plans


🎓 Cohort kit

Cohort Kit · Session template

Eight sessions
  1. Kick-off
  2. Frame and spec
  3. Build, run and the loops
  4. Methods decoded
  5. Plan and review
  6. Prove and ship
  7. Govern and scale
  8. Practice and roles

💬 Community and maintenance

Living notes
Error Index
Community Answers
Field Notes
Model & Region Notes
Cost Log
Scoreboard 🧪

The project
Roadmap
Editing this wiki
Maintainer Runbook


📦 Elsewhere

📘 The manual · live
🛫 Ninety Days, the simulator
🧰 The workbench
👔 For leadership
🧠 Mental models
Templates · Prompts
Frameworks & acronyms
The repository · Setup

Pinned discussions
Discussion map — where to post what
Exercise & lab index
Simulator Arena — get a lab graded
Pitch an idea
All discussions →

Clone this wiki locally