A canonical set of agents completes every step from 1.1 to 6.4.

SOURCE PACK · INTERNAL
Product or idea: [product name and one-line idea]
Search words: [3–6 words: project names, code names, team names]
People to check (optional): [person] [person]
Time window: last 12 months
Using only internal work content I can access (my emails, chats and channel posts, meeting recaps and transcripts, shared files and intranet pages), build an Internal Source Pack for a PDLC Product Brief. Do not use the public web.
RULES
1. Use only what you find. End every bullet with its source: [type · title or subject · owner · date · link].
2. Never invent numbers, names, dates, owners or decisions. If not found, write [GAP: what is missing – likely owner].
3. Tag each bullet DECISION, FACT, METRIC, OPINION or QUESTION. A meeting discussion is not a decision.
4. Newest wins. If sources disagree, show both with dates and tag CONFLICT.
5. No customer PII: no customer names, IDs, account or personal details. Aggregate numbers only. Skip HR and personnel matters.
6. Keep labels such as Confidential or Internal Only.
7. Short, plain bullets. At most 8 per section.
OUTPUT
Internal Source Pack – [product] – [today's date]
1 Problem and why now
2 Customers and users affected
3 Current metrics and baselines, with dates
4 Goals, OKRs and success measures already stated
5 Decisions so far, with decider and date
6 People and roles (Product Leader, Tech Lead, BI, Compliance, others)
7 Constraints, risks, compliance and AI notes
8 Dependencies, systems and related work
9 Open questions and GAPs
10 Numbered source list with links
End with: INTERNAL SOURCE PACK DONE · items: [n] · GAPs: [n]

SOURCE PACK · EXTERNAL
Topic: [the product idea in general public terms, with no confidential details]
Search words: [3–6 public words, for example: renewal reminders subscription billing]
Time window: last 24 months
Search the public web only and build an External Source Pack for a PDLC Product Brief.
RULES
1. Use reputable public sources: regulators and government, published research, analyst and industry reports, company press releases and official sites, and established news. Use a blog only if it names an expert author or company, and tag it BLOG.
2. End every bullet with [publisher · title · date · URL]. No URL, no bullet.
3. Never invent statistics. Quote numbers exactly as published, with year and population.
4. Tag each bullet FACT, STAT, REGULATION, COMPETITOR, TREND or OPINION.
5. These are outside views, not company positions. Do not guess internal data.
6. Tag anything older than 24 months DATED.
7. Short, plain bullets. At most 8 per section.
OUTPUT
External Source Pack – [topic] – [today's date]
1 Market and customer trends
2 Industry benchmarks and statistics
3 Regulation and policy
4 Competitor and peer moves
5 Evidence on what works
6 Risks and watch-outs
7 Numbered source list with URLs
End with: EXTERNAL SOURCE PACK DONE · sources: [n]

PDLC BRIEF · DRAFT A · PROMPT 1 of 3 · 1.1-3.5
SOURCES: [source 1] [source 2] [source 3] [source 4]
Edit only this document. Act as the PDLC Brief Author (Author rules on the Harness page). Never edit Project Identity (read it as context) or Appendix C.
For 1.1 to 3.5 in order: fill the section's [bracketed] fields and empty input cells from SOURCES, following each field's description. ONE EDIT PER SECTION: write all of a section's fields in one edit and fill each input table (all rows) in one edit; no line-by-line edits.
Rules: Never change headings, RAPID tables, gate tables, checklists, TO-DO boxes, definitions or instruction text. Never tick, sign or set OUTCOME. Fill existing input tables; no duplicates. Unknown = [GAP: what · who], highlighted. Cite every field. No guesses. AI ROLE or AI Risk Tier from a requester's idea stays [ASSUMPTION · low] until the Tech Lead confirms. No review or findings here; Prompt 3 does that.
Fixes: 1.1: no solution language. 1.3: ROI and Year-1 arithmetic one line each; unsourced inputs = [GAP · BI Lead]. 1.4: KPI = metric · baseline (or "not instrumented") · target · source. 1.5: fill only "Name for This Project"; exception approver = Product Leader. 2.1: Body = problem, solution, one role-attributed internal quote. 2.2: quote is "(composite)". 2.3: 5-7 real customer questions. 2.4: AI Risk Tier = Project Identity value; one option per required field. 2.5: archetypes, never a real person. 2.6: the table's row names, incl. KPIs to Measure, are the fields. 3.1: format "As [customer archetype], I learned that … because …" + Implication + Evidence tier. 3.2: Opportunity = users, ROI range, fit; trade-off and riskiest-assumption test in Why It Works. 3.3: business capabilities, not features; A2 Reuse is the reuse field. 3.5: Project Identity tier governs; all four blocks if Assistive or higher, one line if None.
FRAME CHECK after 1.6, before 2.1; reply with five lines, PASS or FAIL plus one reason: (a) 1.1 names a problem, not a solution; (b) every 1.4 KPI measures it; (c) each 1.3 ROI input is sourced or [GAP · BI Lead]; (d) 1.2 names the customer outcome; (e) 1.6 DVQE has evidence or GAP on every dimension. Two or more FAIL: write "FRAME CHECK FAILED" and stop; I will fix FRAME and re-run Prompt 1. Otherwise continue.
If space runs low, stop after a whole section, write "NEXT: x.x"; I reply CONTINUE. Finish with "DRAFT A DONE", FRAME check lines, sections filled, GAPs by owner.
END PROMPT 1

PDLC BRIEF · DRAFT B · PROMPT 2 of 3 · 4.1-6.4
SOURCES: [source 1] [source 2] [source 3] [source 4]
Edit only this document. Act as the PDLC Brief Author (Author rules on the Harness page). Never write in Appendix C. If sources hold no build, launch or post-launch evidence, write [GAP: stage not reached · owner] in those fields. Never write Cleared or Met without a source.
For 4.1 to 6.4 in order: fill the section's [bracketed] fields and empty input cells from SOURCES, sections 1-3 and Appendix A, following each field's description. ONE EDIT PER SECTION: write all of a section's fields in one edit and fill each input table (all rows) in one edit; no line-by-line edits.
Rules: Never change headings, RAPID tables, gate tables, checklists, TO-DO boxes, definitions or instruction text. Never tick, sign or set OUTCOME. Fill existing input tables; no duplicates. Unknown = [GAP: what · who], highlighted. Cite every field. No guesses. AI ROLE or AI Risk Tier from a requester's idea stays [ASSUMPTION · low] until the Tech Lead confirms. No review or findings here; Prompt 3 does that.
Fixes: 4.1: classify each CAP into Now, Next, Later or Parking lot in the input table, with reason and target increment. 4.3: treat A1-A6 as the tables to fill, one edit per table. 4.4: record each failing Appendix A item in the 4.4 input table: ID · standard failed · fix · owner. 4.5: leave the Ready to transfer verdict to Prompt 3. 5.4: rollback triggers are numbers tied to 1.4 KPIs or error budgets. 6.1: treat Current as holding 30/60/90-day actuals, variance and counter-metric. 6.2: treat Your Input and the harness signal table as the fields. 6.4: treat the answer as "Recommendation: …" only; owner and date = [GAP · Product Leader decides].
If space runs low, stop after a whole section, write "NEXT: x.x"; I reply CONTINUE. Finish with "DRAFT B DONE", sections filled, GAPs by owner.
END PROMPT 2

PDLC BRIEF · REVIEW · PROMPT 3 of 3 · 1.1-6.4, G1-G6
SOURCES: [source 1] [source 2] [source 3] [source 4]
Edit only this document. Act as the PDLC Adversarial Reviewer (Reviewer rules, Gate review rules and killer questions on the Harness page). Appendix C (Adversarial Review Log) is right after Start here: C1 is the findings table, C2 holds one row per gate readout.
1 REVIEW: attack every section 1.1 to 6.4 against SOURCES and against each other; check each metric measures the stated problem, not a neighbouring one, and name the alternative cause; flag contradictions between sections (a 1.4 KPI that 6.1 never measures, a 3.2 solution that drifts from 1.1, a 4.1 roadmap item with no CAP). Include the 4.5 Ready to transfer / Not ready verdict as a finding.
2 LOG: write the findings into the C1 table, Status Open, newest rows first after the header. ONE EDIT PER BLOCK: fill up to 20 rows per edit (add rows if the table is full); never one edit per finding.
3 GATES: for G1 to G6 apply the Gate review rules and that gate's killer questions; write all six readouts into their C2 rows in a single edit.
4 CLOSE: revise a section only to close a FIXABLE finding the sources resolve, one edit per section; set those rows Closed. Leave FATAL and STRUCTURAL rows Open for the owners.
Rules: The Reviewer writes in Appendix C and, for step 4 only, in the sections it closes. Never change headings, RAPID tables, gate tables, checklists, TO-DO boxes, definitions or instruction text. Never tick, sign or set OUTCOME. Never edit Project Identity. Unknown stays [GAP: what · who]. No praise, no cruelty; name the mechanism. G6 readout includes a kill memo and the steelman of the rejected option.
If space runs low, stop after a whole section, write "NEXT: x.x"; I reply CONTINUE. Finish with "REVIEW DONE", findings by severity, FIXABLE closed count, G1 to G6 verdicts, orphan count.
END PROMPT 3

In the Adversarial Review Log right after Start here, move every finding written as a paragraph into its own row of the C1 findings table, and every gate readout written outside the C2 table into its gate's C2 row. Do not change anything else.

TRANSFER · FEATURES (after G3)
From table A3 produce a table with exactly these columns in this order: Title, Description, Primary Program, State, Parent (Capability title), Estimate, Target Increment. One row per Feature, text only, no blank Descriptions.

TRANSFER · STORIES AND TASKS (after G4)
From tables A4–A6 produce a CSV-ready table with exactly these columns: Work Item Type, Title, Description, Acceptance Criteria, Tags, Story Points, Area Path, Iteration Path. Epics first, then each Epic's User Stories, then each Story's Tasks. Acceptance Criteria in Given/When/Then lines. No ID, State or Assigned To columns.

TRANSFER · DEFINITION OF READY CHECK (after IDs are pasted back)
Compare tables A3 and A5 with the IDs now recorded. List any Feature without a backlog ID, any Story without a delivery-tool ID, any Story whose acceptance criteria are not Given/When/Then, and any Story over 8 points. Return a to-do list by owner.