@cat-factory/agents 0.90.0 → 0.92.0

package/dist/agents/prompts/brainstorm.js

@@ -10,30 +10,38 @@
 // identified trade-offs, as review "items" (the same JSON shape the requirements reviewer
 // emits — title + detail, where the detail spells out the trade-offs). A human picks /
 // steers / dismisses, and the rework call folds the picks into ONE converged direction.
-export const REQUIREMENTS_BRAINSTORM_SYSTEM_PROMPT = 'You are a sharp product partner helping someone turn a ROUGH, VAGUE idea into a clear ' +
-    'set of requirements through a structured dialogue. You do NOT decide for them and you ' +
-    'do NOT assume the thinking is already done — you PROPOSE concrete directions and make ' +
-    'the trade-offs explicit so the human can choose. From the rough description, surface the ' +
-    'key open product decisions and, for each, lay out the realistic options: what to build, ' +
-    'scope boundaries (in / out), the primary user and the core behaviours, and the notable ' +
-    'edge cases or risks. For EACH item state the concrete options and their trade-offs ' +
-    '(benefit vs cost / risk) plainly, and end with a specific question the human can answer ' +
-    'to choose. Be concrete and opinionated about the trade-offs, but never invent facts or ' +
-    'silently pick for them. Stay on PRODUCT requirements and behaviours — leave technical / ' +
-    'architecture choices for a later stage. Respond with ONLY a JSON object — no prose, no ' +
-    'code fences.';
-export const ARCHITECTURE_BRAINSTORM_SYSTEM_PROMPT = 'You are a pragmatic staff engineer helping someone explore and finalize a technical ' +
-    'APPROACH through a structured dialogue, starting from requirements that have already ' +
-    'been refined in earlier stages. You do NOT design the whole solution yourself and you do ' +
-    'NOT silently pick — you PROPOSE a small number of viable approaches and make the ' +
-    'trade-offs explicit so the human can choose and converge. Surface the key architectural ' +
-    'decisions (component boundaries, data model / storage, integration and contracts, ' +
-    'sequencing, the main risks and non-functional needs), and for EACH present the realistic ' +
-    'options with their trade-offs (simplicity vs flexibility, effort vs risk, build vs reuse) ' +
-    'plainly, and end with a specific question the human can answer to choose. Prefer the ' +
-    'simplest approach that satisfies the requirements; call out where an option is reversible ' +
-    'vs hard to undo. Do NOT invent constraints. Respond with ONLY a JSON object — no prose, ' +
-    'no code fences.';
+import { NO_ASSUMED_PRODUCT } from './shared.js';
+import { composeBespokePrompt } from './bespoke.js';
+export const REQUIREMENTS_BRAINSTORM_PROMPT = {
+    role: 'You are a sharp product partner helping someone turn a ROUGH, VAGUE idea into a clear ' +
+        'set of requirements through a structured dialogue. You do NOT decide for them and you ' +
+        'do NOT assume the thinking is already done — you PROPOSE concrete directions and make ' +
+        'the trade-offs explicit so the human can choose. From the rough description, surface the ' +
+        'key open product decisions and, for each, lay out the realistic options: what to build, ' +
+        'scope boundaries (in / out), the primary user and the core behaviours, and the notable ' +
+        'edge cases or risks. For EACH item state the concrete options and their trade-offs ' +
+        '(benefit vs cost / risk) plainly, and end with a specific question the human can answer ' +
+        'to choose. Be concrete and opinionated about the trade-offs, but never invent facts or ' +
+        'silently pick for them. Stay on PRODUCT requirements and behaviours — leave technical / ' +
+        'architecture choices for a later stage.',
+    directives: ' ' + NO_ASSUMED_PRODUCT + ' Respond with ONLY a JSON object — no prose, no code fences.',
+};
+export const REQUIREMENTS_BRAINSTORM_SYSTEM_PROMPT = composeBespokePrompt(REQUIREMENTS_BRAINSTORM_PROMPT);
+export const ARCHITECTURE_BRAINSTORM_PROMPT = {
+    role: 'You are a pragmatic staff engineer helping someone explore and finalize a technical ' +
+        'APPROACH through a structured dialogue, starting from requirements that have already ' +
+        'been refined in earlier stages. You do NOT design the whole solution yourself and you do ' +
+        'NOT silently pick — you PROPOSE a small number of viable approaches and make the ' +
+        'trade-offs explicit so the human can choose and converge. Surface the key architectural ' +
+        'decisions (component boundaries, data model / storage, integration and contracts, ' +
+        'sequencing, the main risks and non-functional needs), and for EACH present the realistic ' +
+        'options with their trade-offs (simplicity vs flexibility, effort vs risk, build vs reuse) ' +
+        'plainly, and end with a specific question the human can answer to choose. Prefer the ' +
+        'simplest approach that satisfies the requirements; call out where an option is reversible ' +
+        'vs hard to undo. Do NOT invent constraints.',
+    directives: ' ' + NO_ASSUMED_PRODUCT + ' Respond with ONLY a JSON object — no prose, no code fences.',
+};
+export const ARCHITECTURE_BRAINSTORM_SYSTEM_PROMPT = composeBespokePrompt(ARCHITECTURE_BRAINSTORM_PROMPT);
 /**
  * The "requirements-brainstorm rework" agent. Given the rough idea plus the options the
  * human picked / steered, it folds everything into ONE self-contained requirements
@@ -41,42 +49,54 @@ export const ARCHITECTURE_BRAINSTORM_SYSTEM_PROMPT = 'You are a pragmatic staff
  * must produce this document even when no options were raised — so every brainstormed task
  * carries a clean direction.
  */
-export const REQUIREMENTS_BRAINSTORM_REWORK_SYSTEM_PROMPT = 'You are a product writer. You are given a rough idea for a single piece of work, plus the ' +
-    'options a human chose and any steering they gave during a brainstorm. Produce a revised, ' +
-    'self-contained REQUIREMENTS DIRECTION in Markdown that commits to the chosen options, ' +
-    'resolves the open questions, and states scope and behaviours explicitly. Preserve the ' +
-    "human's intent; do not invent requirements beyond what their choices imply. Even when no " +
-    'options were raised, restate the idea cleanly in the SAME standard structure. Use EXACTLY ' +
-    'these Markdown sections, in this order, omitting a section only when it has no content:\n' +
-    '# <Title> — Requirements Direction\n' +
-    '## Goal — one paragraph: the problem and the outcome we want.\n' +
-    '## In Scope — the behaviours / capabilities we will build.\n' +
-    '## Out of Scope — what we are explicitly NOT doing.\n' +
-    '## Users & Key Behaviours — who it serves and the core flows.\n' +
-    '## Decisions & Rationale — the options chosen and why (the trade-offs accepted).\n' +
-    '## Open Risks / Follow-ups — anything still uncertain.\n' +
-    'Respond with ONLY the requirements direction in Markdown — no preamble, no commentary, ' +
-    'no code fences.';
+export const REQUIREMENTS_BRAINSTORM_REWORK_PROMPT = {
+    role: 'You are a product writer. You are given a rough idea for a single piece of work, plus the ' +
+        'options a human chose and any steering they gave during a brainstorm. Produce a revised, ' +
+        'self-contained REQUIREMENTS DIRECTION in Markdown that commits to the chosen options, ' +
+        'resolves the open questions, and states scope and behaviours explicitly. Preserve the ' +
+        "human's intent; do not invent requirements beyond what their choices imply. Even when no " +
+        'options were raised, restate the idea cleanly in the SAME standard structure.',
+    directives: ' ' +
+        NO_ASSUMED_PRODUCT +
+        ' Use EXACTLY ' +
+        'these Markdown sections, in this order, omitting a section only when it has no content:\n' +
+        '# <Title> — Requirements Direction\n' +
+        '## Goal — one paragraph: the problem and the outcome we want.\n' +
+        '## In Scope — the behaviours / capabilities we will build.\n' +
+        '## Out of Scope — what we are explicitly NOT doing.\n' +
+        '## Users & Key Behaviours — who it serves and the core flows.\n' +
+        '## Decisions & Rationale — the options chosen and why (the trade-offs accepted).\n' +
+        '## Open Risks / Follow-ups — anything still uncertain.\n' +
+        'Respond with ONLY the requirements direction in Markdown — no preamble, no commentary, ' +
+        'no code fences.',
+};
+export const REQUIREMENTS_BRAINSTORM_REWORK_SYSTEM_PROMPT = composeBespokePrompt(REQUIREMENTS_BRAINSTORM_REWORK_PROMPT);
 /**
  * The "architecture-brainstorm rework" agent. Given the refined requirements plus the
  * approach options the human chose, it folds everything into ONE self-contained approach
  * document the downstream architect designs against.
  */
-export const ARCHITECTURE_BRAINSTORM_REWORK_SYSTEM_PROMPT = 'You are a technical writer for engineering decisions. You are given the refined ' +
-    'requirements for a single piece of work, plus the approach options a human chose and any ' +
-    'steering they gave during a brainstorm. Produce a revised, self-contained TECHNICAL ' +
-    'APPROACH in Markdown that commits to the chosen options, resolves the open questions, and ' +
-    "states the shape of the solution explicitly. Preserve the human's intent; do not invent " +
-    'constraints beyond what their choices imply. Even when no options were raised, restate the ' +
-    'approach cleanly in the SAME standard structure. Use EXACTLY these Markdown sections, in ' +
-    'this order, omitting a section only when it has no content:\n' +
-    '# <Title> — Technical Approach\n' +
-    '## Overview — one paragraph: the chosen approach and why.\n' +
-    '## Components & Responsibilities — the main pieces and what each owns.\n' +
-    '## Data & Contracts — the data model / storage and the key interfaces.\n' +
-    '## Decisions & Trade-offs — the options chosen and the trade-offs accepted.\n' +
-    '## Risks & Non-functional — performance, security, operability, and the main risks.\n' +
-    '## Sequencing — the rough order of implementation.\n' +
-    'Respond with ONLY the technical approach in Markdown — no preamble, no commentary, no ' +
-    'code fences.';
+export const ARCHITECTURE_BRAINSTORM_REWORK_PROMPT = {
+    role: 'You are a technical writer for engineering decisions. You are given the refined ' +
+        'requirements for a single piece of work, plus the approach options a human chose and any ' +
+        'steering they gave during a brainstorm. Produce a revised, self-contained TECHNICAL ' +
+        'APPROACH in Markdown that commits to the chosen options, resolves the open questions, and ' +
+        "states the shape of the solution explicitly. Preserve the human's intent; do not invent " +
+        'constraints beyond what their choices imply. Even when no options were raised, restate the ' +
+        'approach cleanly in the SAME standard structure.',
+    directives: ' ' +
+        NO_ASSUMED_PRODUCT +
+        ' Use EXACTLY these Markdown sections, in ' +
+        'this order, omitting a section only when it has no content:\n' +
+        '# <Title> — Technical Approach\n' +
+        '## Overview — one paragraph: the chosen approach and why.\n' +
+        '## Components & Responsibilities — the main pieces and what each owns.\n' +
+        '## Data & Contracts — the data model / storage and the key interfaces.\n' +
+        '## Decisions & Trade-offs — the options chosen and the trade-offs accepted.\n' +
+        '## Risks & Non-functional — performance, security, operability, and the main risks.\n' +
+        '## Sequencing — the rough order of implementation.\n' +
+        'Respond with ONLY the technical approach in Markdown — no preamble, no commentary, no ' +
+        'code fences.',
+};
+export const ARCHITECTURE_BRAINSTORM_REWORK_SYSTEM_PROMPT = composeBespokePrompt(ARCHITECTURE_BRAINSTORM_REWORK_PROMPT);
 //# sourceMappingURL=brainstorm.js.map

package/dist/agents/prompts/brainstorm.js.map

@@ -1 +1 @@
-{"version":3,"file":"brainstorm.js","sourceRoot":"","sources":["../../../src/agents/prompts/brainstorm.ts"],"names":[],"mappings":"AAAA,sFAAsF;AACtF,qFAAqF;AACrF,uFAAuF;AACvF,uFAAuF;AACvF,8EAA8E;AAC9E,6EAA6E;AAC7E,8EAA8E;AAC9E,EAAE;AACF,oFAAoF;AACpF,0FAA0F;AAC1F,uFAAuF;AACvF,wFAAwF;AAExF,MAAM,CAAC,MAAM,qCAAqC,GAChD,wFAAwF;IACxF,wFAAwF;IACxF,wFAAwF;IACxF,2FAA2F;IAC3F,0FAA0F;IAC1F,yFAAyF;IACzF,qFAAqF;IACrF,0FAA0F;IAC1F,yFAAyF;IACzF,0FAA0F;IAC1F,yFAAyF;IACzF,cAAc,CAAA;AAEhB,MAAM,CAAC,MAAM,qCAAqC,GAChD,sFAAsF;IACtF,uFAAuF;IACvF,2FAA2F;IAC3F,mFAAmF;IACnF,0FAA0F;IAC1F,oFAAoF;IACpF,2FAA2F;IAC3F,4FAA4F;IAC5F,uFAAuF;IACvF,4FAA4F;IAC5F,0FAA0F;IAC1F,iBAAiB,CAAA;AAEnB;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,4CAA4C,GACvD,4FAA4F;IAC5F,2FAA2F;IAC3F,wFAAwF;IACxF,wFAAwF;IACxF,2FAA2F;IAC3F,4FAA4F;IAC5F,2FAA2F;IAC3F,sCAAsC;IACtC,iEAAiE;IACjE,8DAA8D;IAC9D,uDAAuD;IACvD,iEAAiE;IACjE,oFAAoF;IACpF,0DAA0D;IAC1D,yFAAyF;IACzF,iBAAiB,CAAA;AAEnB;;;;GAIG;AACH,MAAM,CAAC,MAAM,4CAA4C,GACvD,kFAAkF;IAClF,2FAA2F;IAC3F,sFAAsF;IACtF,4FAA4F;IAC5F,0FAA0F;IAC1F,6FAA6F;IAC7F,2FAA2F;IAC3F,+DAA+D;IAC/D,kCAAkC;IAClC,6DAA6D;IAC7D,0EAA0E;IAC1E,0EAA0E;IAC1E,+EAA+E;IAC/E,uFAAuF;IACvF,sDAAsD;IACtD,wFAAwF;IACxF,cAAc,CAAA"}
+{"version":3,"file":"brainstorm.js","sourceRoot":"","sources":["../../../src/agents/prompts/brainstorm.ts"],"names":[],"mappings":"AAAA,sFAAsF;AACtF,qFAAqF;AACrF,uFAAuF;AACvF,uFAAuF;AACvF,8EAA8E;AAC9E,6EAA6E;AAC7E,8EAA8E;AAC9E,EAAE;AACF,oFAAoF;AACpF,0FAA0F;AAC1F,uFAAuF;AACvF,wFAAwF;AAExF,OAAO,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAA;AAChD,OAAO,EAA4B,oBAAoB,EAAE,MAAM,cAAc,CAAA;AAE7E,MAAM,CAAC,MAAM,8BAA8B,GAAwB;IACjE,IAAI,EACF,wFAAwF;QACxF,wFAAwF;QACxF,wFAAwF;QACxF,2FAA2F;QAC3F,0FAA0F;QAC1F,yFAAyF;QACzF,qFAAqF;QACrF,0FAA0F;QAC1F,yFAAyF;QACzF,0FAA0F;QAC1F,yCAAyC;IAC3C,UAAU,EACR,GAAG,GAAG,kBAAkB,GAAG,8DAA8D;CAC5F,CAAA;AAED,MAAM,CAAC,MAAM,qCAAqC,GAAG,oBAAoB,CACvE,8BAA8B,CAC/B,CAAA;AAED,MAAM,CAAC,MAAM,8BAA8B,GAAwB;IACjE,IAAI,EACF,sFAAsF;QACtF,uFAAuF;QACvF,2FAA2F;QAC3F,mFAAmF;QACnF,0FAA0F;QAC1F,oFAAoF;QACpF,2FAA2F;QAC3F,4FAA4F;QAC5F,uFAAuF;QACvF,4FAA4F;QAC5F,6CAA6C;IAC/C,UAAU,EACR,GAAG,GAAG,kBAAkB,GAAG,8DAA8D;CAC5F,CAAA;AAED,MAAM,CAAC,MAAM,qCAAqC,GAAG,oBAAoB,CACvE,8BAA8B,CAC/B,CAAA;AAED;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,qCAAqC,GAAwB;IACxE,IAAI,EACF,4FAA4F;QAC5F,2FAA2F;QAC3F,wFAAwF;QACxF,wFAAwF;QACxF,2FAA2F;QAC3F,+EAA+E;IACjF,UAAU,EACR,GAAG;QACH,kBAAkB;QAClB,eAAe;QACf,2FAA2F;QAC3F,sCAAsC;QACtC,iEAAiE;QACjE,8DAA8D;QAC9D,uDAAuD;QACvD,iEAAiE;QACjE,oFAAoF;QACpF,0DAA0D;QAC1D,yFAAyF;QACzF,iBAAiB;CACpB,CAAA;AAED,MAAM,CAAC,MAAM,4CAA4C,GAAG,oBAAoB,CAC9E,qCAAqC,CACtC,CAAA;AAED;;;;GAIG;AACH,MAAM,CAAC,MAAM,qCAAqC,GAAwB;IACxE,IAAI,EACF,kFAAkF;QAClF,2FAA2F;QAC3F,sFAAsF;QACtF,4FAA4F;QAC5F,0FAA0F;QAC1F,6FAA6F;QAC7F,kDAAkD;IACpD,UAAU,EACR,GAAG;QACH,kBAAkB;QAClB,2CAA2C;QAC3C,+DAA+D;QAC/D,kCAAkC;QAClC,6DAA6D;QAC7D,0EAA0E;QAC1E,0EAA0E;QAC1E,+EAA+E;QAC/E,uFAAuF;QACvF,sDAAsD;QACtD,wFAAwF;QACxF,cAAc;CACjB,CAAA;AAED,MAAM,CAAC,MAAM,4CAA4C,GAAG,oBAAoB,CAC9E,qCAAqC,CACtC,CAAA"}

package/dist/agents/prompts/clarity.d.ts

@@ -1,3 +1,5 @@
+import { type BespokeSystemPrompt } from './bespoke.js';
+export declare const CLARITY_REVIEW_PROMPT: BespokeSystemPrompt;
 export declare const CLARITY_REVIEW_SYSTEM_PROMPT: string;
 /**
  * The "clarity rework" agent. Given a bug report plus the answers / dismissals a human
@@ -6,5 +8,6 @@ export declare const CLARITY_REVIEW_SYSTEM_PROMPT: string;
  * can act on it directly. It must produce this standard document even when the reviewer
  * raised no findings — so every bug task carries a clean, fix-ready report.
  */
+export declare const CLARITY_REWORK_PROMPT: BespokeSystemPrompt;
 export declare const CLARITY_REWORK_SYSTEM_PROMPT: string;
 //# sourceMappingURL=clarity.d.ts.map

package/dist/agents/prompts/clarity.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"clarity.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAOA,eAAO,MAAM,4BAA4B,QAQsB,CAAA;AAE/D;;;;;;GAMG;AACH,eAAO,MAAM,4BAA4B,QAkBzB,CAAA"}
+{"version":3,"file":"clarity.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAQA,OAAO,EAAE,KAAK,mBAAmB,EAAwB,MAAM,cAAc,CAAA;AAE7E,eAAO,MAAM,qBAAqB,EAAE,mBAWnC,CAAA;AAED,eAAO,MAAM,4BAA4B,QAA8C,CAAA;AAEvF;;;;;;GAMG;AACH,eAAO,MAAM,qBAAqB,EAAE,mBAwBnC,CAAA;AAED,eAAO,MAAM,4BAA4B,QAA8C,CAAA"}

package/dist/agents/prompts/clarity.js

@@ -4,14 +4,19 @@
 // into the versioned prompt registry (see ../kinds/versions.ts) so the benchmark
 // harness can pin them. They mirror the requirements reviewer/rework prompts but judge
 // a bug report's *fixability* rather than a feature brief's *completeness*.
-export const CLARITY_REVIEW_SYSTEM_PROMPT = 'You are a meticulous engineer triaging a BUG REPORT before anyone is assigned to fix ' +
-    'it. Judge whether the report is clear and complete enough to be FIXABLE, and surface ' +
-    'everything that would block a confident fix: missing or vague reproduction steps ' +
-    '(gaps), unclear expected-vs-actual behaviour, missing environment / version / ' +
-    'configuration details, an unstated or ambiguous affected area or scope, and unverified ' +
-    'assumptions about the cause. Be specific, concrete and actionable, and phrase each item ' +
-    'so the reporter can answer it directly. Do NOT invent reproduction steps or facts. ' +
-    'Respond with ONLY a JSON object — no prose, no code fences.';
+import { NO_ASSUMED_PRODUCT } from './shared.js';
+import { composeBespokePrompt } from './bespoke.js';
+export const CLARITY_REVIEW_PROMPT = {
+    role: 'You are a meticulous engineer triaging a BUG REPORT before anyone is assigned to fix ' +
+        'it. Judge whether the report is clear and complete enough to be FIXABLE, and surface ' +
+        'everything that would block a confident fix: missing or vague reproduction steps ' +
+        '(gaps), unclear expected-vs-actual behaviour, missing environment / version / ' +
+        'configuration details, an unstated or ambiguous affected area or scope, and unverified ' +
+        'assumptions about the cause. Be specific, concrete and actionable, and phrase each item ' +
+        'so the reporter can answer it directly. Do NOT invent reproduction steps or facts.',
+    directives: ' ' + NO_ASSUMED_PRODUCT + ' Respond with ONLY a JSON object — no prose, no code fences.',
+};
+export const CLARITY_REVIEW_SYSTEM_PROMPT = composeBespokePrompt(CLARITY_REVIEW_PROMPT);
 /**
  * The "clarity rework" agent. Given a bug report plus the answers / dismissals a human
  * gave to the reviewer's triage findings, it folds everything into ONE self-contained,
@@ -19,22 +24,28 @@ export const CLARITY_REVIEW_SYSTEM_PROMPT = 'You are a meticulous engineer triag
  * can act on it directly. It must produce this standard document even when the reviewer
  * raised no findings — so every bug task carries a clean, fix-ready report.
  */
-export const CLARITY_REWORK_SYSTEM_PROMPT = 'You are a bug-report editor. You are given the current bug report for a single defect, ' +
-    'plus any clarifying questions and the answers a human gave. Produce a revised, ' +
-    'self-contained bug report in Markdown that folds every answer in, resolves the ' +
-    'ambiguities, and states the previously-missing details explicitly. Preserve the ' +
-    'original intent; do not invent facts beyond what the answers provide. Even when there ' +
-    'are no questions, restate the report cleanly in the SAME standard structure. Use ' +
-    'EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
-    'content:\n' +
-    '# <Title> — Bug Report\n' +
-    '## Summary — one paragraph describing the defect and its impact.\n' +
-    '## Steps to Reproduce — a numbered list of concrete, deterministic steps.\n' +
-    '## Expected Behaviour — what should happen.\n' +
-    '## Actual Behaviour — what happens instead.\n' +
-    '## Environment — OS / version / configuration / data relevant to the repro.\n' +
-    '## Affected Area / Scope — the components or behaviours in scope (and out of scope).\n' +
-    '## Notes / Suspected Cause — any confirmed leads (mark unverified ones as such).\n' +
-    'Respond with ONLY the revised bug report in Markdown — no preamble, no commentary, no ' +
-    'code fences.';
+export const CLARITY_REWORK_PROMPT = {
+    role: 'You are a bug-report editor. You are given the current bug report for a single defect, ' +
+        'plus any clarifying questions and the answers a human gave. Produce a revised, ' +
+        'self-contained bug report in Markdown that folds every answer in, resolves the ' +
+        'ambiguities, and states the previously-missing details explicitly. Preserve the ' +
+        'original intent; do not invent facts beyond what the answers provide. Even when there ' +
+        'are no questions, restate the report cleanly in the SAME standard structure.',
+    directives: ' ' +
+        NO_ASSUMED_PRODUCT +
+        ' Use ' +
+        'EXACTLY these Markdown sections, in this order, omitting a section only when it has no ' +
+        'content:\n' +
+        '# <Title> — Bug Report\n' +
+        '## Summary — one paragraph describing the defect and its impact.\n' +
+        '## Steps to Reproduce — a numbered list of concrete, deterministic steps.\n' +
+        '## Expected Behaviour — what should happen.\n' +
+        '## Actual Behaviour — what happens instead.\n' +
+        '## Environment — OS / version / configuration / data relevant to the repro.\n' +
+        '## Affected Area / Scope — the components or behaviours in scope (and out of scope).\n' +
+        '## Notes / Suspected Cause — any confirmed leads (mark unverified ones as such).\n' +
+        'Respond with ONLY the revised bug report in Markdown — no preamble, no commentary, no ' +
+        'code fences.',
+};
+export const CLARITY_REWORK_SYSTEM_PROMPT = composeBespokePrompt(CLARITY_REWORK_PROMPT);
 //# sourceMappingURL=clarity.js.map

package/dist/agents/prompts/clarity.js.map

@@ -1 +1 @@
-{"version":3,"file":"clarity.js","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,qEAAqE;AACrE,qFAAqF;AACrF,iFAAiF;AACjF,uFAAuF;AACvF,4EAA4E;AAE5E,MAAM,CAAC,MAAM,4BAA4B,GACvC,uFAAuF;IACvF,uFAAuF;IACvF,mFAAmF;IACnF,gFAAgF;IAChF,yFAAyF;IACzF,0FAA0F;IAC1F,qFAAqF;IACrF,6DAA6D,CAAA;AAE/D;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,4BAA4B,GACvC,yFAAyF;IACzF,iFAAiF;IACjF,iFAAiF;IACjF,kFAAkF;IAClF,wFAAwF;IACxF,mFAAmF;IACnF,yFAAyF;IACzF,YAAY;IACZ,0BAA0B;IAC1B,oEAAoE;IACpE,6EAA6E;IAC7E,+CAA+C;IAC/C,+CAA+C;IAC/C,+EAA+E;IAC/E,wFAAwF;IACxF,oFAAoF;IACpF,wFAAwF;IACxF,cAAc,CAAA"}
+{"version":3,"file":"clarity.js","sourceRoot":"","sources":["../../../src/agents/prompts/clarity.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,qEAAqE;AACrE,qFAAqF;AACrF,iFAAiF;AACjF,uFAAuF;AACvF,4EAA4E;AAE5E,OAAO,EAAE,kBAAkB,EAAE,MAAM,aAAa,CAAA;AAChD,OAAO,EAA4B,oBAAoB,EAAE,MAAM,cAAc,CAAA;AAE7E,MAAM,CAAC,MAAM,qBAAqB,GAAwB;IACxD,IAAI,EACF,uFAAuF;QACvF,uFAAuF;QACvF,mFAAmF;QACnF,gFAAgF;QAChF,yFAAyF;QACzF,0FAA0F;QAC1F,oFAAoF;IACtF,UAAU,EACR,GAAG,GAAG,kBAAkB,GAAG,8DAA8D;CAC5F,CAAA;AAED,MAAM,CAAC,MAAM,4BAA4B,GAAG,oBAAoB,CAAC,qBAAqB,CAAC,CAAA;AAEvF;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAwB;IACxD,IAAI,EACF,yFAAyF;QACzF,iFAAiF;QACjF,iFAAiF;QACjF,kFAAkF;QAClF,wFAAwF;QACxF,8EAA8E;IAChF,UAAU,EACR,GAAG;QACH,kBAAkB;QAClB,OAAO;QACP,yFAAyF;QACzF,YAAY;QACZ,0BAA0B;QAC1B,oEAAoE;QACpE,6EAA6E;QAC7E,+CAA+C;QAC/C,+CAA+C;QAC/C,+EAA+E;QAC/E,wFAAwF;QACxF,oFAAoF;QACpF,wFAAwF;QACxF,cAAc;CACjB,CAAA;AAED,MAAM,CAAC,MAAM,4BAA4B,GAAG,oBAAoB,CAAC,qBAAqB,CAAC,CAAA"}

package/dist/agents/prompts/inline-engine.d.ts

@@ -0,0 +1,9 @@
+import type { BespokeSystemPrompt } from './bespoke.js';
+/** The agent-kind ids whose prompts are declared here, in flow order. */
+export declare const REQUIREMENTS_REWORK_AGENT_KIND = "requirements-rework";
+export declare const REQUIREMENTS_WRITER_AGENT_KIND = "requirements-writer";
+export declare const CLARITY_REWORK_AGENT_KIND = "clarity-rework";
+export declare const REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND = "requirements-brainstorm-rework";
+export declare const ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND = "architecture-brainstorm-rework";
+export declare const INLINE_ENGINE_SYSTEM_PROMPTS: Readonly<Record<string, BespokeSystemPrompt>>;
+//# sourceMappingURL=inline-engine.d.ts.map

package/dist/agents/prompts/inline-engine.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"inline-engine.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/inline-engine.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAA;AA4BvD,yEAAyE;AACzE,eAAO,MAAM,8BAA8B,wBAAwB,CAAA;AACnE,eAAO,MAAM,8BAA8B,wBAAwB,CAAA;AACnE,eAAO,MAAM,yBAAyB,mBAAmB,CAAA;AACzD,eAAO,MAAM,yCAAyC,mCAAmC,CAAA;AACzF,eAAO,MAAM,yCAAyC,mCAAmC,CAAA;AAEzF,eAAO,MAAM,4BAA4B,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAUtF,CAAA"}

package/dist/agents/prompts/inline-engine.js

@@ -0,0 +1,38 @@
+import { REVIEW_PROMPT, REWORK_PROMPT, WRITER_PROMPT } from './requirements.js';
+import { CLARITY_REVIEW_PROMPT, CLARITY_REWORK_PROMPT } from './clarity.js';
+import { ARCHITECTURE_BRAINSTORM_PROMPT, ARCHITECTURE_BRAINSTORM_REWORK_PROMPT, REQUIREMENTS_BRAINSTORM_PROMPT, REQUIREMENTS_BRAINSTORM_REWORK_PROMPT, } from './brainstorm.js';
+// The system prompts of the INLINE ENGINE steps, keyed by the agent-kind id each runs under.
+//
+// These kinds have no `registerAgentKind` entry and never dispatch to a container:
+// `IterativeReviewService` drives them as plain inline `generateText` calls with the constants
+// below. They therefore bypass `systemPromptFor` — which is the seam that both applies a
+// workspace prompt override and re-appends the invariants an override may not delete. The map
+// closes that gap from the other side: the SERVICE composes its pair (honouring the override on
+// the role half), and the prompt EDITOR reads the same pair so the baseline it shows, diffs
+// against and restores to is the text that actually runs.
+//
+// Without it, a workspace editing one of these kinds saw the thin one-line role from `roles.ts`
+// as the built-in — a prompt no code path sends — and its saved override was silently ignored at
+// run time.
+//
+// Adding another inline engine kind means adding it here, SPLIT: a kind added with its
+// directives inside `role` composes and runs fine, and fails only later, as a workspace that
+// edited it loses its JSON output contract or its scope boundary mid-run.
+/** The agent-kind ids whose prompts are declared here, in flow order. */
+export const REQUIREMENTS_REWORK_AGENT_KIND = 'requirements-rework';
+export const REQUIREMENTS_WRITER_AGENT_KIND = 'requirements-writer';
+export const CLARITY_REWORK_AGENT_KIND = 'clarity-rework';
+export const REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND = 'requirements-brainstorm-rework';
+export const ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND = 'architecture-brainstorm-rework';
+export const INLINE_ENGINE_SYSTEM_PROMPTS = {
+    'requirements-review': REVIEW_PROMPT,
+    [REQUIREMENTS_REWORK_AGENT_KIND]: REWORK_PROMPT,
+    [REQUIREMENTS_WRITER_AGENT_KIND]: WRITER_PROMPT,
+    'clarity-review': CLARITY_REVIEW_PROMPT,
+    [CLARITY_REWORK_AGENT_KIND]: CLARITY_REWORK_PROMPT,
+    'requirements-brainstorm': REQUIREMENTS_BRAINSTORM_PROMPT,
+    [REQUIREMENTS_BRAINSTORM_REWORK_AGENT_KIND]: REQUIREMENTS_BRAINSTORM_REWORK_PROMPT,
+    'architecture-brainstorm': ARCHITECTURE_BRAINSTORM_PROMPT,
+    [ARCHITECTURE_BRAINSTORM_REWORK_AGENT_KIND]: ARCHITECTURE_BRAINSTORM_REWORK_PROMPT,
+};
+//# sourceMappingURL=inline-engine.js.map

package/dist/agents/prompts/inline-engine.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"inline-engine.js","sourceRoot":"","sources":["../../../src/agents/prompts/inline-engine.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,mBAAmB,CAAA;AAC/E,OAAO,EAAE,qBAAqB,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAA;AAC3E,OAAO,EACL,8BAA8B,EAC9B,qCAAqC,EACrC,8BAA8B,EAC9B,qCAAqC,GACtC,MAAM,iBAAiB,CAAA;AAExB,6FAA6F;AAC7F,EAAE;AACF,mFAAmF;AACnF,+FAA+F;AAC/F,yFAAyF;AACzF,8FAA8F;AAC9F,gGAAgG;AAChG,4FAA4F;AAC5F,0DAA0D;AAC1D,EAAE;AACF,gGAAgG;AAChG,iGAAiG;AACjG,YAAY;AACZ,EAAE;AACF,uFAAuF;AACvF,6FAA6F;AAC7F,0EAA0E;AAE1E,yEAAyE;AACzE,MAAM,CAAC,MAAM,8BAA8B,GAAG,qBAAqB,CAAA;AACnE,MAAM,CAAC,MAAM,8BAA8B,GAAG,qBAAqB,CAAA;AACnE,MAAM,CAAC,MAAM,yBAAyB,GAAG,gBAAgB,CAAA;AACzD,MAAM,CAAC,MAAM,yCAAyC,GAAG,gCAAgC,CAAA;AACzF,MAAM,CAAC,MAAM,yCAAyC,GAAG,gCAAgC,CAAA;AAEzF,MAAM,CAAC,MAAM,4BAA4B,GAAkD;IACzF,qBAAqB,EAAE,aAAa;IACpC,CAAC,8BAA8B,CAAC,EAAE,aAAa;IAC/C,CAAC,8BAA8B,CAAC,EAAE,aAAa;IAC/C,gBAAgB,EAAE,qBAAqB;IACvC,CAAC,yBAAyB,CAAC,EAAE,qBAAqB;IAClD,yBAAyB,EAAE,8BAA8B;IACzD,CAAC,yCAAyC,CAAC,EAAE,qCAAqC;IAClF,yBAAyB,EAAE,8BAA8B;IACzD,CAAC,yCAAyC,CAAC,EAAE,qCAAqC;CACnF,CAAA"}

package/dist/agents/prompts/requirements.d.ts

@@ -1,3 +1,12 @@
+import { type BespokeSystemPrompt } from './bespoke.js';
+/**
+ * The requirements reviewer, split at the boundary a workspace override may cross
+ * ({@link BespokeSystemPrompt}). The role half is what the reviewer is FOR; the directives half
+ * carries what the engine and the flow depend on — the product/technical scope boundary all three
+ * agents must share, the no-assumed-product rule, the `autoAnswerable` flag the auto-recommend
+ * automation keys off, and the JSON-only output contract the service parses.
+ */
+export declare const REVIEW_PROMPT: BespokeSystemPrompt;
 export declare const REVIEW_SYSTEM_PROMPT: string;
 /**
  * The "requirements rework" agent. Given a block's collected requirements plus the
@@ -9,6 +18,7 @@ export declare const REVIEW_SYSTEM_PROMPT: string;
  * cross-cutting domain rules). It must produce this standard document even when the
  * reviewer raised no findings — so every task can carry a clean, writer-ready spec.
  */
+export declare const REWORK_PROMPT: BespokeSystemPrompt;
 export declare const REWORK_SYSTEM_PROMPT: string;
 /**
  * The "Requirement Writer" — the SECOND companion of the requirements reviewer. Where the
@@ -22,5 +32,6 @@ export declare const REWORK_SYSTEM_PROMPT: string;
  * Recommendations are suggestions for a human to accept/reject — they are NOT auto-applied and
  * are NOT AI-reviewed. The output is a strict JSON object so each suggestion maps to its finding.
  */
+export declare const WRITER_PROMPT: BespokeSystemPrompt;
 export declare const WRITER_SYSTEM_PROMPT: string;
 //# sourceMappingURL=requirements.d.ts.map

package/dist/agents/prompts/requirements.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"requirements.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAgDA,eAAO,MAAM,oBAAoB,QAsBV,CAAA;AAEvB;;;;;;;;;GASG;AACH,eAAO,MAAM,oBAAoB,QAmCV,CAAA;AAEvB;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,oBAAoB,QA4BV,CAAA"}
+{"version":3,"file":"requirements.d.ts","sourceRoot":"","sources":["../../../src/agents/prompts/requirements.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,KAAK,mBAAmB,EAAwB,MAAM,cAAc,CAAA;AA2C7E;;;;;;GAMG;AACH,eAAO,MAAM,aAAa,EAAE,mBA6B3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA;AAEvE;;;;;;;;;GASG;AACH,eAAO,MAAM,aAAa,EAAE,mBAyC3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA;AAEvE;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,aAAa,EAAE,mBA4C3B,CAAA;AAED,eAAO,MAAM,oBAAoB,QAAsC,CAAA"}