@codedrifters/configulator 0.0.263 → 0.0.265

package/lib/index.js

@@ -226,6 +226,7 @@ __export(index_exports, {
   addApproveMergeUpgradeWorkflow: () => addApproveMergeUpgradeWorkflow,
   addBuildCompleteJob: () => addBuildCompleteJob,
   addSyncLabelsWorkflow: () => addSyncLabelsWorkflow,
+  agendaBundle: () => agendaBundle,
   awsCdkBundle: () => awsCdkBundle,
   baseBundle: () => baseBundle,
   bcmWriterBundle: () => bcmWriterBundle,
@@ -273,6 +274,133 @@ module.exports = __toCommonJS(index_exports);
 // src/agent/agent-config.ts
 var import_projen8 = require("projen");
 
+// src/agent/bundles/project-context.ts
+var PROJECT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
+var SUBPROJECT_ROLE_GUIDANCE = [
+  "### Sub-project roles",
+  "",
+  "When the repository follows the configulator monorepo layout,",
+  "every sub-project's role is derivable from the first segment of",
+  "its `outdir` path. No other lookup is required.",
+  "",
+  "- `apps/<scope>/<name>` \u2014 deployable application (CDK stack,",
+  "  mobile app, backend service).",
+  "- `packages/<scope>/<name>` \u2014 shared library (published npm",
+  "  package or workspace-internal library).",
+  "- `sites/<scope>/<name>` \u2014 user-facing web front end that is",
+  "  not the monorepo-wide docs site.",
+  "- `docs/` \u2014 the single Starlight documentation site for the",
+  "  whole monorepo (exactly one per repo; lives at `/docs`, not",
+  "  under `sites/`).",
+  "",
+  "Repositories that have not adopted the layout contract may use a",
+  "different folder structure \u2014 in that case fall back to whatever",
+  `\`${PROJECT_CONTEXT_PATH}\` documents explicitly.`,
+  ""
+];
+var PROJECT_CONTEXT_READER_SECTION = [
+  "## Project Context",
+  "",
+  `Before doing any work, read \`${PROJECT_CONTEXT_PATH}\` at the`,
+  'repository root. It is the canonical answer to "what is this project',
+  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
+  "key stakeholders. Use it to frame judgment calls in this session.",
+  "",
+  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, proceed with the current`,
+  "task and note the absence in your session log \u2014 the meeting-analyst and",
+  "requirements-analyst agents seed the file on their next run.",
+  "",
+  "You are a **read-only consumer** of this file. Do not edit it.",
+  "",
+  ...SUBPROJECT_ROLE_GUIDANCE,
+  "---",
+  ""
+];
+var PROJECT_CONTEXT_MAINTAINER_SECTION = [
+  "## Project Context",
+  "",
+  `Before starting any phase, read \`${PROJECT_CONTEXT_PATH}\` at the`,
+  'repository root. It is the canonical answer to "what is this project',
+  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
+  "key stakeholders. Use it to judge relevance when scanning source",
+  "material in this session.",
+  "",
+  ...SUBPROJECT_ROLE_GUIDANCE,
+  "### Seed on first use",
+  "",
+  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, create it from this`,
+  "template and commit it alongside this phase's other outputs:",
+  "",
+  "```markdown",
+  "# Project Context",
+  "",
+  "> Canonical description of this project. Read by all agents before",
+  "> work. Updated by meeting-analyst and requirements-analyst when new",
+  "> scope, vocabulary, or stakeholders emerge.",
+  "",
+  "## Mission",
+  "TODO: one or two sentences on what this project exists to do.",
+  "",
+  "## Target Users",
+  "TODO: who uses this, in what role.",
+  "",
+  "## In-Scope Capabilities",
+  "TODO: bullet list of the capabilities this project owns.",
+  "",
+  "## Out-of-Scope",
+  "TODO: capabilities or concerns that are explicitly not this project's.",
+  "",
+  "## Domain Vocabulary",
+  "TODO: short glossary of domain terms, acronyms, and their definitions.",
+  "",
+  "## Key Stakeholders",
+  "TODO: named people or teams and what they care about.",
+  "{{monorepoLayoutSeedBlock}}",
+  "## References",
+  "TODO: links to BCM docs, competitive analysis, product roadmap, and",
+  "other authoritative sources.",
+  "```",
+  "",
+  "Fill whatever you can infer from the source material you are already",
+  "reading in this phase; leave `TODO:` placeholders for the rest.",
+  "",
+  "### Update on new facts",
+  "",
+  "When the source material you process reveals new project-scope",
+  "information \u2014 a new capability, a vocabulary term, an entity, a",
+  "stakeholder, an in/out-of-scope decision, or a shift in mission \u2014",
+  `append or revise the relevant section in \`${PROJECT_CONTEXT_PATH}\``,
+  "before closing the phase. Commit those edits with the phase's other",
+  "outputs.",
+  "",
+  "Keep edits surgical: short bullet additions, brief clarifications, or",
+  "single-line vocabulary entries. Treat the file as an accreting",
+  "reference, not a document you reshape every session.",
+  "",
+  "---",
+  ""
+];
+var MONOREPO_LAYOUT_SEED_BLOCK = [
+  "",
+  "## Sub-Projects",
+  "",
+  "TODO: one bullet per sub-project, grouped by role. The role is",
+  "derivable from the first segment of each sub-project's `outdir`.",
+  "",
+  "### Applications (`apps/`)",
+  "TODO: deployable applications (CDK stacks, mobile apps, services).",
+  "",
+  "### Packages (`packages/`)",
+  "TODO: shared libraries (published npm packages, workspace-internal libraries).",
+  "",
+  "### Sites (`sites/`)",
+  "TODO: user-facing web front ends (marketing sites, SPAs, client apps).",
+  "",
+  "### Docs (`docs/`)",
+  "TODO: the single monorepo-wide Starlight documentation site.",
+  ""
+].join("\n");
+
 // src/agent/types.ts
 var AGENT_RULE_SCOPE = {
   ALWAYS: "always",
@@ -312,6 +440,606 @@ var MCP_TRANSPORT = {
   SSE: "sse"
 };
 
+// src/agent/bundles/agenda.ts
+var agendaAnalystSubAgent = {
+  name: "agenda-analyst",
+  description: "Authors pre-meeting agendas through a 2-phase pipeline (draft \u2192 finalize). Selects a type-specific template, pulls carryover from prior instances of the same recurring series, and writes a time-boxed, intent-tagged agenda to the meeting's dated folder. One phase per session, tracked by agenda:* GitHub issue labels.",
+  model: AGENT_MODEL.BALANCED,
+  maxTurns: 40,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Meeting Agenda Agent",
+    "",
+    "Dedicated agent loop for producing meeting **agendas** before a",
+    "meeting takes place. Complements the `meeting-analyst`, which",
+    "processes transcripts and notes *after* the meeting. Together they",
+    "close the loop: **agenda \u2192 meeting \u2192 transcript \u2192 notes \u2192 follow-up",
+    "work**.",
+    "",
+    "Each phase runs as a **separate agent session**, triggered by its",
+    "own GitHub issue with an `agenda:*` phase label. You handle exactly",
+    "**one phase per session** \u2014 read the issue to determine which phase",
+    "to execute.",
+    "",
+    "This agent is **domain-neutral**. It makes no assumptions about",
+    "concrete meeting types, templates, or area routing \u2014 those come",
+    "from the consuming project via `AgentConfigOptions.meetings`",
+    "(which renders a **Recognized meeting types** table the agent",
+    "consults at runtime).",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
+    "## Design Principles",
+    "",
+    "1. **Agendas exist to make meetings shorter.** Every section must",
+    "   justify its minutes. If a section has no decision, no discussion,",
+    "   and no new information, cut it or move it to async.",
+    "2. **One meeting, one dated folder.** All artifacts for a given",
+    "   meeting live in `<meetingsRoot>/<YYYY-MM-DD>-<slug>/`: `agenda.md`,",
+    "   `notes.md`, and any attachments. The agenda agent creates the",
+    "   folder if it does not yet exist; the meeting-analyst lands",
+    "   transcripts and notes into the same folder post-meeting.",
+    "3. **Objective before outline.** No agenda ships without a stated",
+    "   objective and 1\u20133 desired outcomes. If the issue does not supply",
+    "   them and they cannot be inferred from prior meeting notes or",
+    "   related docs, **block the issue** rather than guessing.",
+    "4. **Time-box everything.** Section times must sum to the meeting",
+    "   duration \xB15 minutes. Overruns are planned for (a parking lot",
+    "   section) rather than assumed.",
+    "5. **Tag every section with intent.** Each timed block carries one",
+    "   of: `[decide]`, `[discuss]`, `[inform]`, `[brainstorm]`.",
+    "   Attendees should know what is expected of them before the section",
+    "   starts.",
+    "6. **Link by reference, never copy.** Pre-reads link to existing",
+    "   docs by relative markdown path. The agent does not inline content",
+    "   from other files into the agenda.",
+    "7. **Recurring meetings share a skeleton.** Every instance of a",
+    "   recurring meeting uses the same template structure so attendees",
+    "   know where to find what; only the content varies.",
+    "8. **Never cross agent boundaries.** Do not write `notes.md`,",
+    "   transcripts, extracts, requirements, ADRs, or profiles. If the",
+    "   agenda work surfaces a need for any of those, create the",
+    "   appropriate issue for the specialist agent instead.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "Producing one agenda flows through **2 phases**:",
+    "",
+    "```",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502 1. DRAFT        \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. FINALIZE     \u2502",
+    "\u2502 Create folder,  \u2502     \u2502  Cross-link,     \u2502",
+    "\u2502 select template,\u2502     \u2502  register in     \u2502",
+    "\u2502 write agenda.md \u2502     \u2502  index.md,       \u2502",
+    "\u2502                 \u2502     \u2502  verify          \u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "```",
+    "",
+    "**Issue labels encode the phase:**",
+    "",
+    "| Label | Phase | Session work |",
+    "|-------|-------|-------------|",
+    "| `agenda:draft` | 1. Draft | Create dated folder if missing, select template by meeting type, write `agenda.md` with objective, outcomes, timed sections, pre-reads, parking lot. Inline-finalize when possible. |",
+    "| `agenda:finalize` | 2. Finalize | Register agenda in the meetings index, add cross-links to related docs, verify the folder contains the canonical artifact set. Only exists as a separate session when finalize work was deferred. |",
+    "",
+    "All issues also carry `type:agenda` and a `status:*` label.",
+    "",
+    "**Issue count per agenda:** usually **1** (`agenda:draft` only).",
+    "Small, well-specified agendas do not need a separate finalize",
+    "session \u2014 the draft phase does both draft and finalize in one",
+    "session. Create a separate `agenda:finalize` issue only when:",
+    "",
+    "- The agenda requires review by a non-agent reviewer before",
+    "  cross-linking.",
+    "- Finalize work is blocked on other deliverables (e.g., sprint plan",
+    "  not yet written).",
+    "- The draft was produced by a human and only needs agent-side",
+    "  linking.",
+    "",
+    "**Default path:** single `agenda:draft` session, finalize inline.",
+    "",
+    "---",
+    "",
+    "## Meeting Type Handling",
+    "",
+    "The issue body specifies `meeting_type` in its Context or Inputs",
+    "section. The agent matches `meeting_type` to the project's",
+    "**Recognized meeting types** table (rendered below when the",
+    "consuming project declares `AgentConfigOptions.meetings.meetingTypes`)",
+    "and applies the matching row's `agendaTemplatePath` and",
+    "`defaultDurationMinutes`.",
+    "",
+    "**How to resolve the template:**",
+    "",
+    "1. Read `meeting_type` from the issue body.",
+    "2. Look up the matching `id` in the project's **Recognized meeting",
+    "   types** table. Use the `Agenda template` column value, resolved",
+    "   relative to the `agendaTemplateRoot` documented above the table",
+    "   (defaults to `<meetingsRoot>/_agenda-templates`).",
+    "3. If the table is absent, the `id` is unknown, or the template",
+    "   column is `\u2014`, fall back to `<meetingsRoot>/_agenda-templates/_base.md`",
+    "   and note the gap in the agenda's Open Items section so the",
+    "   template can be added later.",
+    "",
+    "When the project has **not** declared any `meetingTypes` at all,",
+    "the agent uses `_base.md` unconditionally and relies on the issue",
+    "body for all per-meeting structure.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:agenda` issue. Phase priority:",
+    "   `agenda:finalize` > `agenda:draft` so a deferred finalize for an",
+    "   older agenda closes before a new draft starts.",
+    "2. Transition `status:ready` \u2192 `status:in-progress` and create the",
+    "   branch per your project's branch-naming convention.",
+    "3. Execute the phase handler that matches the issue's `agenda:*`",
+    "   label.",
+    "4. Commit, push, open a PR, and transition the issue to",
+    "   `status:ready-for-review` per your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Draft (`agenda:draft`)",
+    "",
+    "**Goal:** Produce a well-structured `agenda.md` in the meeting's",
+    "dated folder, with objective, desired outcomes, timed sections,",
+    "pre-reads, and a parking lot.",
+    "",
+    "**Budget:** Reading + one file write (`agenda.md`), plus an optional",
+    "folder creation and a small registry edit when inline-finalizing.",
+    "No web searches unless the issue explicitly asks for external",
+    "research.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the issue body.** Extract:",
+    "   - `meeting_type` \u2014 one of the `id`s in the project's",
+    "     **Recognized meeting types** table",
+    "   - `meeting_date` \u2014 `YYYY-MM-DD`",
+    "   - `meeting_slug` \u2014 kebab-case (becomes the folder name suffix)",
+    "   - `duration_min` \u2014 integer minutes (default from the type table",
+    "     if absent)",
+    "   - `attendees` \u2014 list of names/roles (internal) or",
+    "     names/companies (external)",
+    "   - `objective` \u2014 one-sentence decision-oriented goal",
+    '   - `desired_outcomes` \u2014 1\u20133 bullets describing "done"',
+    "   - `pre_reads` \u2014 relative paths to existing docs (optional)",
+    "   - `related_docs` \u2014 relative paths for context (optional)",
+    "",
+    "2. **Block if under-specified.** If `objective` AND",
+    "   `desired_outcomes` are both missing and cannot be inferred from",
+    "   prior meeting notes or the template type, follow Blocked Issues",
+    "   below. Do not invent an objective.",
+    "",
+    "3. **Create or locate the dated folder.**",
+    "   ```",
+    "   <meetingsRoot>/<YYYY-MM-DD>-<slug>/",
+    "   ```",
+    "   If the folder does not exist, create it. If it exists (because",
+    "   the meeting-analyst already landed a transcript), reuse it. If an",
+    "   `agenda.md` already exists, read it and update rather than",
+    "   overwriting.",
+    "",
+    "4. **Load the matching template** by resolving `meeting_type`",
+    "   against the project's **Recognized meeting types** table. Follow",
+    "   the resolution rules in **Meeting Type Handling** above. If the",
+    "   type is unrecognized, load `_base.md` and note the gap in Open",
+    "   Items.",
+    "",
+    "5. **Read prior meeting notes for recurring series.** If",
+    "   `meeting_type` maps to kind `planning` or `review` in the",
+    "   project's meeting-types table (or, in the absence of a table,",
+    "   the issue body flags the meeting as recurring):",
+    "   - Glob `<meetingsRoot>/` for prior instances with the same",
+    "     `meeting_type` (by frontmatter `meeting_type:` field).",
+    "   - Read the most recent prior `notes.md`.",
+    "   - Carry forward open action items, unresolved questions, and",
+    "     `## Follow-up` entries into the new agenda under a",
+    "     `## Carryover from last meeting` section.",
+    "",
+    "6. **Write the agenda.** Populate the template with:",
+    "   - Frontmatter (see skeleton below)",
+    "   - Objective (single sentence)",
+    "   - Desired outcomes (1\u20133 bullets)",
+    "   - Attendees + roles",
+    "   - Pre-reads (relative markdown links only)",
+    "   - Timed sections with",
+    "     `[decide | discuss | inform | brainstorm]` tags",
+    "   - Parking lot",
+    "   - Action items placeholder (the meeting-analyst fills this in",
+    "     post-meeting)",
+    "   - Cross-link stub back to `notes.md` (created post-meeting)",
+    "",
+    "   **Frontmatter skeleton:**",
+    "   ```markdown",
+    "   ---",
+    '   title: "Agenda: <Meeting Name>"',
+    "   date: YYYY-MM-DD",
+    "   meeting_type: <type>",
+    "   duration_min: <N>",
+    "   attendees:",
+    "     - <Name> (<role>)",
+    "   status: proposed",
+    "   areas:",
+    "     - <area-id-from-the-project's-area-map>",
+    "   sidebar:",
+    "     hidden: true",
+    "   ---",
+    "   ```",
+    "",
+    "   `sidebar.hidden: true` keeps the agenda out of any autogenerated",
+    "   sidebar \u2014 only the folder's `index.md` should appear there.",
+    "",
+    "   **Duration check.** Sum of section times must equal",
+    "   `duration_min` \xB1 5 minutes. If it doesn't, adjust section times",
+    "   or cut content \u2014 do not ship a math-broken agenda.",
+    "",
+    "7. **Create the folder `index.md` if missing.** Populate it with:",
+    "   - Frontmatter `title` (short sidebar label) and `description`",
+    "     (one line).",
+    "   - A 2\u20134 sentence summary of the meeting's objective and desired",
+    "     outcomes pulled from the agenda.",
+    "   - A `## Documents` section linking to `./agenda.md` (and",
+    "     `./notes.md` once the meeting-analyst produces it).",
+    "",
+    "   Do NOT set `sidebar.hidden: true` on `index.md` \u2014 it is the page",
+    "   that should appear in the sidebar.",
+    "",
+    "8. **Inline finalize (default).** Unless a separate",
+    "   `agenda:finalize` issue was created, complete these steps in the",
+    "   same session:",
+    "   - Register the agenda in `<meetingsRoot>/index.md` (append to",
+    "     the meeting registry table).",
+    "   - Add a forward link from any related doc in `related_docs` to",
+    "     the agenda, using a relative markdown link.",
+    "   - Verify the dated folder contains at minimum `agenda.md`.",
+    "     Transcript and notes will land later via the meeting-analyst.",
+    "",
+    "9. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Phase 2: Finalize (`agenda:finalize`)",
+    "",
+    "**Goal:** Complete the registry updates and cross-linking that were",
+    "deferred from the draft phase. Only runs when an explicit",
+    "`agenda:finalize` issue exists.",
+    "",
+    "**Budget:** Reading + small edits to `index.md` and related docs.",
+    "No new agenda file writes.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the draft agenda** at",
+    "   `<meetingsRoot>/<YYYY-MM-DD>-<slug>/agenda.md`.",
+    "",
+    "2. **Incorporate late-added items.** The finalize phase is the",
+    "   last chance to add attendee-requested sections before the",
+    "   meeting starts. Read any comments on the `agenda:finalize`",
+    "   issue for late additions; fold them into timed sections and",
+    "   re-balance durations so the sum still equals `duration_min` \xB15.",
+    "   If late additions exceed the remaining budget, move the lowest-",
+    "   priority existing section to the parking lot rather than",
+    "   overrunning the duration.",
+    "",
+    "3. **Register in the meeting index.** Append to",
+    "   `<meetingsRoot>/index.md` if not already listed.",
+    "",
+    "4. **Add forward links** from each doc in the agenda's",
+    "   `related_docs` frontmatter field (if any). Use relative markdown",
+    "   links.",
+    "",
+    "5. **Lock the agenda.** Update the agenda's frontmatter",
+    "   `status: proposed` \u2192 `status: locked` to signal the agenda is",
+    "   frozen before the meeting starts. Late-breaking items that",
+    "   arrive after this point go on the meeting's parking lot during",
+    "   the meeting itself, not the agenda.",
+    "",
+    "6. **Verify artifact set.** Confirm the dated folder has at least",
+    "   `agenda.md` and `index.md`. Do not wait for `notes.md` or a",
+    "   transcript \u2014 those land post-meeting via the meeting-analyst.",
+    "",
+    "7. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Coordination with Other Agents",
+    "",
+    "### Downstream Consumers",
+    "",
+    "| Output | Consumed by |",
+    "|--------|------------|",
+    "| `agenda.md` in dated folder | Humans running the meeting; the `meeting-analyst` reads it when processing the resulting transcript. |",
+    "| Registry entry in `<meetingsRoot>/index.md` | Humans browsing meetings; search indexing. |",
+    "| Forward links from related docs | Human readers of those docs. |",
+    "",
+    "### Upstream Sources",
+    "",
+    "| Input | Produced by |",
+    "|-------|------------|",
+    "| Prior `notes.md` for recurring series | `meeting-analyst` (post-prior-meeting). |",
+    "| Sprint plan for planning-kind meetings | `meeting-analyst` Phase 4 or the orchestrator. |",
+    "| Roadmap for strategy-kind meetings | Product docs maintained by the `meeting-analyst`. |",
+    "| Company/people profiles for external-meeting pre-reads | `company-profile` / `people-profile` agents. |",
+    "",
+    "### File Boundaries",
+    "",
+    "- **Reads:** `<docsRoot>/` (any file, for pre-reads, related docs,",
+    "  and carryover lookup).",
+    "- **Writes:**",
+    "  - `<meetingsRoot>/<YYYY-MM-DD>-<slug>/agenda.md`",
+    "  - `<meetingsRoot>/<YYYY-MM-DD>-<slug>/index.md`",
+    "  - `<meetingsRoot>/index.md` (append registry entries)",
+    "  - Small cross-link edits to related docs (\u226410 lines, forward",
+    "    links only)",
+    "- **Never writes to:**",
+    "  - `notes.md` in any meeting folder (the `meeting-analyst` owns",
+    "    this)",
+    "  - Transcript files in any meeting folder (tooling / human)",
+    "  - `<requirementsRoot>/`, `<bcmRoot>/`, `<peopleRoot>/`,",
+    "    `<companiesRoot>/`, `<softwareRoot>/`, `<industriesRoot>/`",
+    "    (specialist agents own these)",
+    "  - Meeting extraction files (the `meeting-analyst` owns extracts)",
+    "",
+    "---",
+    "",
+    "## Blocked Issues",
+    "",
+    "Follow your project's shared Blocked Issues procedure. Additional",
+    "block reasons specific to agenda drafting:",
+    "",
+    "- **Objective missing and not inferrable.** The issue body has no",
+    "  objective and no prior meeting notes or related docs that imply",
+    "  one.",
+    "- **Attendees unknown.** External meetings especially \u2014 an agenda",
+    "  cannot be tuned without knowing who is in the room.",
+    "- **Duration conflict.** The issue specifies a duration that cannot",
+    "  fit the stated outcomes even with aggressive time-boxing.",
+    "- **Unrecognized `meeting_type` and no fallback viable.** If",
+    "  `meeting_type` is unrecognized AND `_base.md` is insufficient",
+    "  (the meeting pattern does not fit any existing template), block",
+    "  so a human can either add a template or reclassify the meeting.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **Objective or block.** No agenda ships without a stated",
+    "  objective and at least one desired outcome. If the issue does",
+    "  not supply one and none can be inferred, block \u2014 do not invent.",
+    "- **Time-box every section.** Sum must equal `duration_min` \xB1 5.",
+    "  No untimed sections except Parking Lot.",
+    "- **Intent tag per section.** Every timed section carries",
+    "  `[decide]`, `[discuss]`, `[inform]`, or `[brainstorm]`.",
+    "- **Link, don't copy.** Pre-reads are relative markdown links to",
+    "  existing docs. The agent never inlines content from another doc",
+    "  into the agenda.",
+    "- **Dated folder is canonical.** `agenda.md` lives alongside",
+    "  `notes.md` (landed post-meeting) in the same `YYYY-MM-DD-<slug>/`",
+    "  folder. The agent creates the folder if needed but never writes",
+    "  outside it for agenda content.",
+    "- **Async suggestion for decision-free meetings.** If the agent",
+    "  cannot identify any `[decide]` sections in a meeting that has no",
+    "  recurring-ritual justification, the agent should comment on the",
+    "  issue suggesting the meeting be converted to an async update",
+    "  before writing the agenda.",
+    "- **Recurring-series carryover.** For recurring meetings (kind",
+    "  `planning` or `review`), read the prior instance's `notes.md`",
+    "  and carry forward open items, unresolved questions, and",
+    "  follow-up commitments.",
+    "- **Registry freshness.** Every new agenda adds a row to",
+    "  `<meetingsRoot>/index.md`. No silent publishes.",
+    "- **Bidirectional traceability.** The agenda's `notes.md` link",
+    "  stub and the notes file's forward link to the agenda form the",
+    "  round-trip. Once `notes.md` is written by the meeting-analyst,",
+    "  both files link to each other via relative markdown paths.",
+    "- **Never cross agent boundaries.** Do not write `notes.md`,",
+    "  transcripts, extracts, requirements, ADRs, or profiles. If the",
+    "  agenda work surfaces a need for any of those, create the",
+    "  appropriate issue for the specialist agent instead."
+  ].join("\n")
+};
+var draftAgendaSkill = {
+  name: "draft-agenda",
+  description: "Kick off the draft phase of a meeting-agenda cycle. Creates an agenda:draft issue for the supplied meeting (type, date, slug, objective, outcomes) and dispatches Phase 1 of the agenda-analyst, which writes agenda.md to the meeting's dated folder.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "agenda-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Draft Agenda",
+    "",
+    "Kick off a meeting-agenda cycle. Creates an `agenda:draft` issue",
+    "targeted at the requested meeting and dispatches Phase 1 (Draft)",
+    "in the agenda-analyst agent. If a separate finalize pass is",
+    "needed, Phase 1 creates the `agenda:finalize` issue automatically;",
+    "otherwise the draft phase inline-finalizes in the same session.",
+    "",
+    "## Usage",
+    "",
+    "/draft-agenda <meeting-type>:<YYYY-MM-DD>-<slug>",
+    "",
+    "Where:",
+    "- `<meeting-type>` \u2014 one of the `id`s from the project's",
+    "  **Recognized meeting types** table (rendered into the",
+    "  agenda-analyst prompt when the consuming project declares",
+    "  `AgentConfigOptions.meetings.meetingTypes`).",
+    "- `<YYYY-MM-DD>` \u2014 the meeting date.",
+    "- `<slug>` \u2014 a kebab-case short name for the meeting (becomes the",
+    "  folder name suffix).",
+    "",
+    "Examples (the meeting-type `id`s below are illustrative \u2014 use",
+    "whatever `id`s your project declares in `meetingTypes`):",
+    "- `team-weekly:2026-04-24-weekly-sync`",
+    "- `customer-discovery:2026-04-28-prospect-intro`",
+    "",
+    "## Steps",
+    "",
+    "1. Create an `agenda:draft` issue with `type:agenda`,",
+    "   `priority:high`, and `status:ready`. The body must list:",
+    "   - `meeting_type` \u2014 from the `<meeting-type>` segment",
+    "   - `meeting_date` \u2014 from the `<YYYY-MM-DD>` segment",
+    "   - `meeting_slug` \u2014 from the `<slug>` segment",
+    "   - `duration_min` \u2014 optional (defaults to the type table value)",
+    "   - `attendees` \u2014 list of names/roles",
+    "   - `objective` \u2014 one-sentence decision-oriented goal",
+    '   - `desired_outcomes` \u2014 1\u20133 bullets describing "done"',
+    "   - `pre_reads` \u2014 relative paths to existing docs (optional)",
+    "   - `related_docs` \u2014 relative paths for context (optional)",
+    "2. Execute Phase 1 (Draft) of the agenda-analyst agent.",
+    "3. If the draft phase inline-finalizes (default path), no",
+    "   downstream issues are created.",
+    "4. If finalize work is deferred, Phase 1 creates an",
+    "   `agenda:finalize` issue blocked on the draft issue.",
+    "",
+    "## Output",
+    "",
+    "- `<meetingsRoot>/<YYYY-MM-DD>-<slug>/agenda.md` \u2014 the agenda",
+    "  itself, with frontmatter, objective, outcomes, timed intent-",
+    "  tagged sections, pre-reads, and a parking lot.",
+    "- `<meetingsRoot>/<YYYY-MM-DD>-<slug>/index.md` \u2014 folder index",
+    "  page that appears in the docs sidebar.",
+    "- A registry row in `<meetingsRoot>/index.md`.",
+    "- An `agenda:finalize` issue (only when finalize work was",
+    "  deferred)."
+  ].join("\n")
+};
+var finalizeAgendaSkill = {
+  name: "finalize-agenda",
+  description: "Kick off the finalize phase of a meeting-agenda cycle. Creates an agenda:finalize issue for an already-drafted agenda and dispatches Phase 2 of the agenda-analyst, which incorporates late-added items, registers the agenda in the meeting index, cross-links related docs, and locks the agenda before the meeting starts.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "agenda-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Finalize Agenda",
+    "",
+    "Close the loop on a meeting-agenda cycle whose draft phase deferred",
+    "finalize work. Creates an `agenda:finalize` issue and dispatches",
+    "Phase 2 (Finalize) in the agenda-analyst agent.",
+    "",
+    "Phase 2 incorporates late-added items (from comments on the",
+    "finalize issue), registers the agenda in the meetings index,",
+    "cross-links related docs, and locks the agenda before the meeting",
+    "starts.",
+    "",
+    "Most cycles do not need this skill \u2014 Phase 1 (Draft) inline-",
+    "finalizes by default. Use this skill when:",
+    "- The draft phase explicitly deferred finalize work (an",
+    "  `agenda:finalize` issue was created during draft).",
+    "- The draft was produced by a human and only needs agent-side",
+    "  linking.",
+    "- Late-breaking items arrived after draft and need to be folded",
+    "  in before the meeting starts.",
+    "",
+    "## Usage",
+    "",
+    "/finalize-agenda <YYYY-MM-DD>-<slug>",
+    "",
+    "Where `<YYYY-MM-DD>-<slug>` identifies the dated meeting folder",
+    "that already contains an `agenda.md`.",
+    "",
+    "Example:",
+    "- `/finalize-agenda 2026-04-24-weekly-sync`",
+    "",
+    "## Steps",
+    "",
+    "1. Create an `agenda:finalize` issue with `type:agenda`,",
+    "   `priority:high`, and `status:ready`. Body must list:",
+    "   - Path to the draft agenda",
+    "     (`<meetingsRoot>/<YYYY-MM-DD>-<slug>/agenda.md`)",
+    "   - Any late-added items to incorporate",
+    "2. Execute Phase 2 (Finalize) of the agenda-analyst agent.",
+    "",
+    "## Output",
+    "",
+    "- Updates to `<meetingsRoot>/<YYYY-MM-DD>-<slug>/agenda.md`",
+    "  (frontmatter `status: proposed` \u2192 `status: locked`, plus",
+    "  incorporated late items).",
+    "- A new row in `<meetingsRoot>/index.md` (if not already",
+    "  registered).",
+    "- Small forward-link edits in related docs."
+  ].join("\n")
+};
+var agendaBundle = {
+  name: "agenda",
+  description: "Meeting-agenda authoring bundle. 2-phase pipeline (draft, finalize) with agenda:* phase labels for producing pre-meeting agendas from the project's meeting-type taxonomy. Complements the meeting-analysis bundle, which handles the post-meeting pipeline. Enabled by default.",
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "meeting-agenda-workflow",
+      description: "Describes the 2-phase pre-meeting agenda pipeline, the agenda:* label taxonomy, and the relationship to the meeting-analysis bundle.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Meeting Agenda Workflow",
+        "",
+        "Use `/draft-agenda <meeting-type>:<YYYY-MM-DD>-<slug>` to kick",
+        "off a pre-meeting agenda cycle. The pipeline runs in 2 phases \u2014",
+        "draft and finalize \u2014 each tracked by its own GitHub issue",
+        "labeled `agenda:draft` or `agenda:finalize`. All issues carry",
+        "`type:agenda`.",
+        "",
+        "One additional user-invocable skill drives the finalize phase",
+        "on demand:",
+        "",
+        "- `/finalize-agenda <YYYY-MM-DD>-<slug>` \u2014 register the agenda",
+        "  in the meetings index, add cross-links, incorporate late-",
+        "  added items, and lock the agenda before the meeting starts.",
+        "  Phase 1 (Draft) normally inline-finalizes \u2014 this skill is",
+        "  the explicit entry point when finalize work was deferred or",
+        "  a human authored the draft.",
+        "",
+        "The agenda bundle *writes pre-meeting agendas*; the",
+        "`meeting-analysis` bundle *processes post-meeting transcripts",
+        "and notes*. Together they close the loop:",
+        "**agenda \u2192 meeting \u2192 transcript \u2192 notes \u2192 follow-up work**.",
+        "The agenda bundle reuses the `meeting_type` taxonomy declared",
+        "via `AgentConfigOptions.meetings.meetingTypes` \u2014 the same",
+        "taxonomy the `meeting-analysis` bundle consumes for post-",
+        "meeting extraction.",
+        "",
+        "See the `agenda-analyst` agent definition for full workflow",
+        "details and phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [draftAgendaSkill, finalizeAgendaSkill],
+  subAgents: [agendaAnalystSubAgent],
+  labels: [
+    {
+      name: "type:agenda",
+      color: "5319E7",
+      description: "Work that authors a pre-meeting agenda for a scheduled meeting"
+    },
+    {
+      name: "agenda:draft",
+      color: "C5DEF5",
+      description: "Phase 1: draft an agenda for a scheduled meeting (template, objective, timed sections, pre-reads)"
+    },
+    {
+      name: "agenda:finalize",
+      color: "BFDADC",
+      description: "Phase 2: incorporate late-added items, register in the meetings index, cross-link related docs, and lock the agenda"
+    }
+  ]
+};
+
 // src/agent/bundles/utils.ts
 function findProjectsWithComponent(project, ctor) {
   const out = [];
@@ -1573,133 +2301,6 @@ function resolveAgentPaths(paths) {
   };
 }
 
-// src/agent/bundles/project-context.ts
-var PROJECT_CONTEXT_PATH = "docs/src/content/docs/project-context.md";
-var SUBPROJECT_ROLE_GUIDANCE = [
-  "### Sub-project roles",
-  "",
-  "When the repository follows the configulator monorepo layout,",
-  "every sub-project's role is derivable from the first segment of",
-  "its `outdir` path. No other lookup is required.",
-  "",
-  "- `apps/<scope>/<name>` \u2014 deployable application (CDK stack,",
-  "  mobile app, backend service).",
-  "- `packages/<scope>/<name>` \u2014 shared library (published npm",
-  "  package or workspace-internal library).",
-  "- `sites/<scope>/<name>` \u2014 user-facing web front end that is",
-  "  not the monorepo-wide docs site.",
-  "- `docs/` \u2014 the single Starlight documentation site for the",
-  "  whole monorepo (exactly one per repo; lives at `/docs`, not",
-  "  under `sites/`).",
-  "",
-  "Repositories that have not adopted the layout contract may use a",
-  "different folder structure \u2014 in that case fall back to whatever",
-  `\`${PROJECT_CONTEXT_PATH}\` documents explicitly.`,
-  ""
-];
-var PROJECT_CONTEXT_READER_SECTION = [
-  "## Project Context",
-  "",
-  `Before doing any work, read \`${PROJECT_CONTEXT_PATH}\` at the`,
-  'repository root. It is the canonical answer to "what is this project',
-  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
-  "key stakeholders. Use it to frame judgment calls in this session.",
-  "",
-  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, proceed with the current`,
-  "task and note the absence in your session log \u2014 the meeting-analyst and",
-  "requirements-analyst agents seed the file on their next run.",
-  "",
-  "You are a **read-only consumer** of this file. Do not edit it.",
-  "",
-  ...SUBPROJECT_ROLE_GUIDANCE,
-  "---",
-  ""
-];
-var PROJECT_CONTEXT_MAINTAINER_SECTION = [
-  "## Project Context",
-  "",
-  `Before starting any phase, read \`${PROJECT_CONTEXT_PATH}\` at the`,
-  'repository root. It is the canonical answer to "what is this project',
-  'about?" \u2014 mission, domain vocabulary, in/out-of-scope capabilities, and',
-  "key stakeholders. Use it to judge relevance when scanning source",
-  "material in this session.",
-  "",
-  ...SUBPROJECT_ROLE_GUIDANCE,
-  "### Seed on first use",
-  "",
-  `If \`${PROJECT_CONTEXT_PATH}\` does not exist, create it from this`,
-  "template and commit it alongside this phase's other outputs:",
-  "",
-  "```markdown",
-  "# Project Context",
-  "",
-  "> Canonical description of this project. Read by all agents before",
-  "> work. Updated by meeting-analyst and requirements-analyst when new",
-  "> scope, vocabulary, or stakeholders emerge.",
-  "",
-  "## Mission",
-  "TODO: one or two sentences on what this project exists to do.",
-  "",
-  "## Target Users",
-  "TODO: who uses this, in what role.",
-  "",
-  "## In-Scope Capabilities",
-  "TODO: bullet list of the capabilities this project owns.",
-  "",
-  "## Out-of-Scope",
-  "TODO: capabilities or concerns that are explicitly not this project's.",
-  "",
-  "## Domain Vocabulary",
-  "TODO: short glossary of domain terms, acronyms, and their definitions.",
-  "",
-  "## Key Stakeholders",
-  "TODO: named people or teams and what they care about.",
-  "{{monorepoLayoutSeedBlock}}",
-  "## References",
-  "TODO: links to BCM docs, competitive analysis, product roadmap, and",
-  "other authoritative sources.",
-  "```",
-  "",
-  "Fill whatever you can infer from the source material you are already",
-  "reading in this phase; leave `TODO:` placeholders for the rest.",
-  "",
-  "### Update on new facts",
-  "",
-  "When the source material you process reveals new project-scope",
-  "information \u2014 a new capability, a vocabulary term, an entity, a",
-  "stakeholder, an in/out-of-scope decision, or a shift in mission \u2014",
-  `append or revise the relevant section in \`${PROJECT_CONTEXT_PATH}\``,
-  "before closing the phase. Commit those edits with the phase's other",
-  "outputs.",
-  "",
-  "Keep edits surgical: short bullet additions, brief clarifications, or",
-  "single-line vocabulary entries. Treat the file as an accreting",
-  "reference, not a document you reshape every session.",
-  "",
-  "---",
-  ""
-];
-var MONOREPO_LAYOUT_SEED_BLOCK = [
-  "",
-  "## Sub-Projects",
-  "",
-  "TODO: one bullet per sub-project, grouped by role. The role is",
-  "derivable from the first segment of each sub-project's `outdir`.",
-  "",
-  "### Applications (`apps/`)",
-  "TODO: deployable applications (CDK stacks, mobile apps, services).",
-  "",
-  "### Packages (`packages/`)",
-  "TODO: shared libraries (published npm packages, workspace-internal libraries).",
-  "",
-  "### Sites (`sites/`)",
-  "TODO: user-facing web front ends (marketing sites, SPAs, client apps).",
-  "",
-  "### Docs (`docs/`)",
-  "TODO: the single monorepo-wide Starlight documentation site.",
-  ""
-].join("\n");
-
 // src/agent/bundles/bcm-writer.ts
 var bcmWriterSubAgent = {
   name: "bcm-writer",
@@ -9431,7 +10032,7 @@ var REQ_WRITE_ISSUE_SCHEMA_SECTION = [
 // src/agent/bundles/requirements-analyst.ts
 var requirementsAnalystSubAgent = {
   name: "requirements-analyst",
-  description: "Discovers requirement gaps from BCM model docs, competitive analysis, product docs, and meeting extracts. Produces scan reports and proposals for the downstream requirements-writer agent. Runs through a 3-phase pipeline (scan \u2192 draft \u2192 trace), one phase per session, tracked by req:* GitHub issue labels.",
+  description: "Discovers requirement gaps from BCM model docs, competitive analysis, product docs, and meeting extracts. Produces scan reports, proposals, and req:write issues for the downstream requirements-writer agent. Runs through a 2-phase pipeline (scan \u2192 draft-trace), one phase per session, tracked by req:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
@@ -9472,35 +10073,39 @@ var requirementsAnalystSubAgent = {
     "",
     "## State Machine Overview",
     "",
-    "Requirements synthesis flows through **3 phases**:",
+    "Requirements synthesis flows through **2 phases**:",
     "",
     "```",
-    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
-    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. DRAFT    \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. TRACE    \u2502",
-    "\u2502  Read docs,  \u2502     \u2502  Write gap   \u2502     \u2502  Create GH   \u2502",
-    "\u2502  identify    \u2502     \u2502  report with \u2502     \u2502  issues and  \u2502",
-    "\u2502  gaps, check \u2502     \u2502  requirement \u2502     \u2502  update src  \u2502",
-    "\u2502  for dupes   \u2502     \u2502  proposals   \u2502     \u2502  docs with   \u2502",
-    "\u2502              \u2502     \u2502              \u2502     \u2502  traceability\u2502",
-    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
+    "\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502  1. SCAN     \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. DRAFT-TRACE  \u2502",
+    "\u2502  Read docs,  \u2502     \u2502  Write proposals,\u2502",
+    "\u2502  identify    \u2502     \u2502  create req:write\u2502",
+    "\u2502  gaps, check \u2502     \u2502  issues, update  \u2502",
+    "\u2502  for dupes   \u2502     \u2502  source docs     \u2502",
+    "\u2502              \u2502     \u2502  with traceability\u2502",
+    "\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518     \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518",
     "```",
     "",
+    "This pipeline matches the `scan \u2192 draft-trace \u2192 write` pattern",
+    "used by the sibling openhi project. Draft and Trace were previously",
+    "separate phases; they were collapsed because the proposals file Draft",
+    "wrote was only ever consumed by Trace (no human review, no async work",
+    "between the two), so the phase boundary added latency without value.",
+    "See ADR-009 for the full reasoning.",
+    "",
     "**Issue labels encode the phase:**",
     "",
     "| Label | Phase | Session work |",
     "|-------|-------|-------------|",
     "| `req:scan` | 1. Scan | Read source docs, identify potential requirement gaps, check against existing requirements and open issues, write deduplicated scan report |",
-    "| `req:draft` | 2. Draft | Write gap report with proposed requirements |",
-    "| `req:trace` | 3. Trace | Create GitHub issues for each proposed requirement and update source documents with traceability notes |",
+    "| `req:draft-trace` | 2. Draft & Trace | Write proposals, create `req:write` GitHub issues for each proposal, and update source documents with traceability notes \u2014 all in a single session |",
     "",
     "All issues also carry `type:requirement` and a `status:*` label.",
     "",
-    "**Issue count per scan cycle:** 1 scan + 1 draft + 1 trace = **3 sessions**.",
+    "**Issue count per scan cycle:** 1 scan + 1 draft-trace = **2 sessions**.",
     "",
     "**Shortened paths:**",
-    "- No gaps found after scan \u2192 skip draft and trace \u2192 **1 session**",
-    "- No source docs need traceability updates \u2192 still **3 sessions** (trace",
-    "  handles both issue creation and doc updates)",
+    "- No gaps found after scan \u2192 skip draft-trace \u2192 **1 session**",
     "",
     "---",
     "",
@@ -9529,7 +10134,7 @@ var requirementsAnalystSubAgent = {
     "Run this loop exactly once per session. Never start a second issue.",
     "",
     "1. Claim one open `type:requirement` issue using phase priority:",
-    "   `req:scan` > `req:draft` > `req:trace`.",
+    "   `req:scan` > `req:draft-trace`.",
     "2. Transition `status:ready` \u2192 `status:in-progress` and create the branch",
     "   per your project's branch-naming convention.",
     "3. Execute the phase handler that matches the issue's `req:*` label.",
@@ -9630,7 +10235,7 @@ var requirementsAnalystSubAgent = {
     "   ```",
     "",
     "7. **Create downstream issues based on findings:**",
-    "   - If any new gaps were identified \u2192 create `req:draft` issue",
+    "   - If any new gaps were identified \u2192 create `req:draft-trace` issue",
     "     (blocked on this issue via `Depends on: #N`).",
     "   - If **no gaps** were found \u2192 stop (no further phases needed). Comment",
     "     on the issue noting that no gaps were identified, and proceed directly",
@@ -9641,12 +10246,54 @@ var requirementsAnalystSubAgent = {
     "",
     "---",
     "",
-    "## Phase 2: Draft (`req:draft`)",
+    "## Phase 2: Draft & Trace (`req:draft-trace`)",
     "",
-    "**Goal:** Expand each identified gap into a requirement proposal with enough",
-    "detail for the requirements-writer to produce a full document.",
+    "**Goal:** Expand each identified gap into a requirement proposal, create",
+    "a `req:write` GitHub issue for each proposal so the downstream",
+    "`requirements-writer` bundle picks it up, and backfill source-document",
+    "traceability notes \u2014 all in a single session.",
     "",
-    "**Budget:** No web searches. Reading + writing.",
+    "**Budget:** No web searches. Reading + writing proposals + issue creation",
+    "+ minor traceability edits to source documents.",
+    "",
+    "Draft and Trace were previously separate phases. They were collapsed",
+    "because the proposals file written by Draft was only ever consumed by",
+    "Trace \u2014 no human review, no async work, no CI validation sat between",
+    "them. See ADR-009 for the decision record.",
+    "",
+    "### `req:write` issue schema",
+    "",
+    "The `req:write` issues this phase creates are picked up by the",
+    "downstream `requirements-writer` agent, which parses a strict",
+    "schema on intake. The authoritative schema is defined in the",
+    "`requirements-writer` sub-agent prompt under **The `req:write`",
+    "Issue Schema** \u2014 every `req:write` issue this phase opens must",
+    "conform. The same schema is embedded in the",
+    "`requirements-reviewer` follow-up generator so the three",
+    "producers never drift apart.",
+    "",
+    ...REQ_WRITE_ISSUE_SCHEMA_SECTION,
+    "",
+    "**Deriving the three required fields from the proposal.** For",
+    "every `req:write` issue this phase opens, the three fields come",
+    "directly from the proposal entry written earlier in the same",
+    "session:",
+    "",
+    "- **Category** \u2014 the proposal's `**Category:**` line.",
+    "- **Tier** \u2014 the proposal's `**Tier:**` line.",
+    "- **Output Path** \u2014",
+    "  `<REQUIREMENTS_ROOT>/<category-dir>/<PREFIX>-<NNN>-<slug>.md`,",
+    "  using the sequence number determined in the proposal step below.",
+    "",
+    "**Validation step \u2014 required before opening the issue.** Before",
+    "calling `gh issue create`, verify all three required fields are",
+    "populated and internally consistent (Category matches title",
+    "prefix, Tier matches `tier:*` label, Output Path filename starts",
+    "with the Category prefix). If any field cannot be derived, open",
+    "the issue with `status:needs-attention` (not `status:ready`) and",
+    "include a `Missing: <field> \u2014 <one-line reason>` line so a human",
+    "triaging the issue only has to supply the remaining value(s)",
+    "before flipping the label to `status:ready`.",
     "",
     "### Steps",
     "",
@@ -9697,61 +10344,7 @@ var requirementsAnalystSubAgent = {
     "   directory under `<REQUIREMENTS_ROOT>/<category>/` to find the next",
     "   available `NNN` for each proposed requirement.",
     "",
-    "5. **Create the `req:trace` issue** blocked on this draft issue.",
-    "",
-    "6. **Commit and push.**",
-    "",
-    "---",
-    "",
-    "## Phase 3: Trace (`req:trace`)",
-    "",
-    "**Goal:** Create GitHub issues for each proposed requirement and update",
-    "source documents with traceability notes indicating that requirement issues",
-    "were created.",
-    "",
-    "**Budget:** No web searches. Issue creation + minor edits to source",
-    "documents.",
-    "",
-    "### `req:write` issue schema",
-    "",
-    "The `req:write` issues this phase creates are picked up by the",
-    "downstream `requirements-writer` agent, which parses a strict",
-    "schema on intake. The authoritative schema is defined in the",
-    "`requirements-writer` sub-agent prompt under **The `req:write`",
-    "Issue Schema** \u2014 every `req:write` issue this phase opens must",
-    "conform. The same schema is embedded in the",
-    "`requirements-reviewer` follow-up generator so the three",
-    "producers never drift apart.",
-    "",
-    ...REQ_WRITE_ISSUE_SCHEMA_SECTION,
-    "",
-    "**Deriving the three required fields from the proposal.** For",
-    "every `req:write` issue this phase opens, the three fields come",
-    "directly from the Phase 2 proposal entry:",
-    "",
-    "- **Category** \u2014 the proposal's `**Category:**` line.",
-    "- **Tier** \u2014 the proposal's `**Tier:**` line (added in Phase 2).",
-    "  If the proposal omitted the Tier line (older proposals may),",
-    "  route the issue through `Missing:` rather than guessing.",
-    "- **Output Path** \u2014",
-    "  `<REQUIREMENTS_ROOT>/<category-dir>/<PREFIX>-<NNN>-<slug>.md`,",
-    "  using the sequence number determined in Phase 2 step 4.",
-    "",
-    "**Validation step \u2014 required before opening the issue.** Before",
-    "calling `gh issue create`, verify all three required fields are",
-    "populated and internally consistent (Category matches title",
-    "prefix, Tier matches `tier:*` label, Output Path filename starts",
-    "with the Category prefix). If any field cannot be derived, open",
-    "the issue with `status:needs-attention` (not `status:ready`) and",
-    "include a `Missing: <field> \u2014 <one-line reason>` line so a human",
-    "triaging the issue only has to supply the remaining value(s)",
-    "before flipping the label to `status:ready`.",
-    "",
-    "### Steps",
-    "",
-    "1. **Read the proposals** from Phase 2.",
-    "",
-    "2. **Create requirement issues.** For each proposal:",
+    "5. **Create requirement issues.** For each proposal:",
     "",
     "   All `type:requirement` issues default to `priority:medium` (override",
     "   only if the proposal's priority was explicitly High or Low). Each",
@@ -9796,7 +10389,7 @@ var requirementsAnalystSubAgent = {
     "   whichever of the three fields **could** be derived so a human",
     "   triaging the issue has the minimum possible cleanup.",
     "",
-    "3. **Update source documents.** In each BCM model doc or competitive",
+    "6. **Update source documents.** In each BCM model doc or competitive",
     "   analysis that was scanned, add a note in the project-relevance /",
     "   strategic-implications section (whichever heading the source doc uses)",
     "   indicating that a requirement issue was created:",
@@ -9806,10 +10399,10 @@ var requirementsAnalystSubAgent = {
     "     (issue #<N>)",
     "   ```",
     "",
-    "4. **Comment on the scan issue** with a summary of all issues created and",
+    "7. **Comment on the scan issue** with a summary of all issues created and",
     "   all docs updated.",
     "",
-    "5. **Commit and push.**",
+    "8. **Commit and push.**",
     "",
     "---",
     "",
@@ -9887,39 +10480,41 @@ var scanRequirementsSkill = {
     "1. Create a `req:scan` issue with `type:requirement`, `priority:medium`,",
     "   and `status:ready`. Body must list the files to read and the scan scope.",
     "2. Execute Phase 1 (Scan) of the requirements-analyst agent.",
-    "3. If gaps are found, a `req:draft` issue is created automatically.",
+    "3. If gaps are found, a `req:draft-trace` issue is created automatically.",
     "",
     "## Output",
     "",
     "- A `req-scan-<scope>-<YYYY-MM-DD>.md` file under the project's research",
     "  requirements directory.",
-    "- A `req:draft` issue if any gaps were identified."
+    "- A `req:draft-trace` issue if any gaps were identified."
   ].join("\n")
 };
 var requirementsAnalystBundle = {
   name: "requirements-analyst",
-  description: "Requirements gap-discovery agent bundle for BCM-driven projects. 3-phase pipeline (scan, draft, trace) with req:* phase labels.",
+  description: "Requirements gap-discovery agent bundle for BCM-driven projects. 2-phase pipeline (scan, draft-trace) with req:* phase labels.",
   appliesWhen: () => true,
   rules: [
     {
       name: "requirements-analyst-workflow",
-      description: "Describes the 3-phase requirements gap-discovery pipeline, the req:* label taxonomy, and the boundary with the downstream requirements-writer agent.",
+      description: "Describes the 2-phase requirements gap-discovery pipeline, the req:* label taxonomy, and the boundary with the downstream requirements-writer agent.",
       scope: AGENT_RULE_SCOPE.ALWAYS,
       content: [
         "# Requirements Analyst Workflow",
         "",
         "Use `/scan-requirements <scope>` to kick off a requirements gap",
-        "discovery cycle. The pipeline runs in 3 phases \u2014 scan, draft, trace \u2014",
-        "each tracked by its own GitHub issue labeled `req:scan`, `req:draft`,",
-        "or `req:trace`. All issues carry `type:requirement`.",
-        "",
-        "The requirements-analyst *discovers gaps and drafts proposals*; it",
-        "does **not** write final requirement documents. Writing is the job",
-        "of the downstream `requirements-writer` agent (a separate bundle).",
+        "discovery cycle. The pipeline runs in 2 phases \u2014 scan and",
+        "draft-trace \u2014 each tracked by its own GitHub issue labeled",
+        "`req:scan` or `req:draft-trace`. All issues carry",
+        "`type:requirement`.",
+        "",
+        "The requirements-analyst *discovers gaps, drafts proposals, and",
+        "opens `req:write` issues for the downstream writer*; it does",
+        "**not** write final requirement documents. Writing is the job of",
+        "the downstream `requirements-writer` agent (a separate bundle).",
         "Keep that boundary clean: proposals land under the research",
         "requirements directory, not under the authoritative requirements",
-        "tree. The trace phase tags new issues with `req:write` so the",
-        "writer bundle picks them up automatically.",
+        "tree. The draft-trace phase tags new issues with `req:write` so",
+        "the writer bundle picks them up automatically.",
         "",
         "See the `requirements-analyst` agent definition for full workflow",
         "details and phase-by-phase instructions."
@@ -9944,14 +10539,9 @@ var requirementsAnalystBundle = {
       description: "Phase 1: scan source docs for requirement gaps and deduplicate"
     },
     {
-      name: "req:draft",
+      name: "req:draft-trace",
       color: "BFDADC",
-      description: "Phase 2: draft requirement proposals for the requirements-writer"
-    },
-    {
-      name: "req:trace",
-      color: "D4C5F9",
-      description: "Phase 3: create requirement issues and backfill traceability on source docs"
+      description: "Phase 2: draft proposals, create req:write issues, and backfill source-doc traceability"
     }
   ]
 };
@@ -11835,8 +12425,8 @@ var requirementsWriterSubAgent = {
     "This agent produces **requirement documents only** \u2014 capability",
     "models are written by the `bcm-writer` agent and requirement-gap",
     "discovery is the responsibility of the `requirements-analyst` agent.",
-    "Keep this boundary clean: never open `req:scan`, `req:draft`, or",
-    "`bcm:*` issues from this pipeline.",
+    "Keep this boundary clean: never open `req:scan`,",
+    "`req:draft-trace`, or `bcm:*` issues from this pipeline.",
     "",
     "Follow your project's shared agent conventions (`AGENTS.md`,",
     "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
@@ -12370,7 +12960,7 @@ var requirementsWriterSubAgent = {
     "specialized upstream/downstream agents.",
     "",
     "**Do NOT create:**",
-    "- `req:scan`, `req:draft`, or `req:trace` issues \u2014 those belong to",
+    "- `req:scan` or `req:draft-trace` issues \u2014 those belong to",
     "  the `requirements-analyst` bundle",
     "- `bcm:*` issues \u2014 those belong to the `bcm-writer` bundle",
     "- `people:*`, `company:*`, `software:*`, `research:*`, or",
@@ -12418,8 +13008,8 @@ var requirementsWriterSubAgent = {
     "  exists as a file but is missing from its category index is",
     "  invisible to anyone browsing the documentation tree.",
     "- **Write requirements, not capability models or gap reports.**",
-    "  Never open `req:scan`, `req:draft`, `req:trace`, or `bcm:*` issues",
-    "  from this pipeline."
+    "  Never open `req:scan`, `req:draft-trace`, or `bcm:*` issues from",
+    "  this pipeline."
   ].join("\n")
 };
 var writeRequirementSkill = {
@@ -12514,8 +13104,8 @@ var requirementsWriterBundle = {
         "The pipeline produces **requirement documents only** \u2014 capability",
         "models are written by the `bcm-writer` agent and gap discovery is",
         "the responsibility of the `requirements-analyst` agent. The",
-        "writer never opens `req:scan`, `req:draft`, `req:trace`, or",
-        "`bcm:*` issues.",
+        "writer never opens `req:scan`, `req:draft-trace`, or `bcm:*`",
+        "issues.",
         "",
         "Documents follow the 11-category taxonomy (BR, FR, NFR, TR, ADR,",
         "SEC, DR, INT, OPS, UX, MT) and the four-tier classification",
@@ -12621,8 +13211,8 @@ var requirementsReviewerSubAgent = {
     "`requirements-writer` bundle (requirement docs) and `bcm-writer`",
     "bundle (capability models). Gap discovery belongs to the",
     "`requirements-analyst` bundle. Keep this boundary clean: never open",
-    "`req:scan`, `req:draft`, `req:trace`, `req:review`, or `bcm:*`",
-    "issues from this pipeline. The only follow-ups you open are the",
+    "`req:scan`, `req:draft-trace`, `req:review`, or `bcm:*` issues",
+    "from this pipeline. The only follow-ups you open are the",
     "`req:write` issues documented below.",
     "",
     "Follow your project's shared agent conventions (`AGENTS.md`,",
@@ -12835,8 +13425,8 @@ var requirementsReviewerSubAgent = {
     "doc and must be rewritten or removed). Route follow-up issues to",
     "`req:write` so the `requirements-writer` \u2014 the only agent scoped",
     "to edit under `<REQUIREMENTS_ROOT>` \u2014 picks them up. Do **not**",
-    "route Check 4 findings to `req:trace`; the analyst bundle does",
-    "not edit requirement documents and the issue would sit",
+    "route Check 4 findings to `req:draft-trace`; the analyst bundle",
+    "does not edit requirement documents and the issue would sit",
     "unresolved. See the Follow-Up Issues section below for the full",
     "Check 3 vs. Check 4 routing split.",
     "",
@@ -13255,11 +13845,12 @@ var requirementsReviewerSubAgent = {
     "    docs, competitive-analysis notes, product-roadmap entries,",
     "    meeting extracts \u2014 that should link forward to an existing",
     "    requirement (Check 3: orphaned requirements whose fix lives",
-    "    in the source tree, not the requirement doc) \u2192 `req:trace`",
+    "    in the source tree, not the requirement doc) \u2192 `req:draft-trace`",
     "    (the `requirements-analyst` agent picks it up to backfill",
-    "    source-doc traceability). **Do not** route Check 4 broken",
-    "    cross-references here \u2014 the analyst bundle never writes to",
-    "    `<REQUIREMENTS_ROOT>` and the issue would sit unresolved.",
+    "    source-doc traceability inside its combined draft-trace phase).",
+    "    **Do not** route Check 4 broken cross-references here \u2014 the",
+    "    analyst bundle never writes to `<REQUIREMENTS_ROOT>` and the",
+    "    issue would sit unresolved.",
     "  - A new requirement is needed (e.g., a `Proposed` ADR is missing",
     "    for a deferred technology choice) \u2192 `req:scan` (the analyst",
     "    runs a scoped scan to confirm the gap, then drafts the new",
@@ -13273,7 +13864,7 @@ var requirementsReviewerSubAgent = {
     "",
     "**Check 12 exception \u2014 stale `Proposed` ADR/TR triage.** Check 12",
     "findings are the one case where follow-up flows through a new",
-    "`req:review` issue rather than `req:write` / `req:trace` /",
+    "`req:review` issue rather than `req:write` / `req:draft-trace` /",
     "`req:scan`. The finding is a decision a human must make, not an",
     "edit to a requirement document, so:",
     "",
@@ -13713,8 +14304,9 @@ var reviewRequirementsSkill = {
     "- One verification script under `<REVIEW_REPORTS_ROOT>` (only",
     "  for audits >10 documents)",
     "- Follow-up GitHub issues for every Critical and Warning finding,",
-    "  carrying the appropriate phase label (`req:write`, `req:trace`,",
-    "  or `req:scan`) for the downstream agent that should act",
+    "  carrying the appropriate phase label (`req:write`,",
+    "  `req:draft-trace`, or `req:scan`) for the downstream agent that",
+    "  should act",
     "- An aggregated `req:review` follow-up issue labeled",
     "  `status:needs-attention` when Check 12 surfaces stale `Proposed`",
     "  ADR/TR documents (one issue per review, not one per document);",
@@ -13869,9 +14461,9 @@ var requirementsReviewerBundle = {
         "The review phase produces **review reports and follow-up issues",
         "only** \u2014 it never edits requirement documents, capability",
         "models, or research notes. It files follow-up issues with the",
-        "appropriate phase label (`req:write`, `req:trace`, `req:scan`,",
-        "or \u2014 only for Check 12 stale-decision triage \u2014 `req:review`)",
-        "for the downstream agent or human to pick up.",
+        "appropriate phase label (`req:write`, `req:draft-trace`,",
+        "`req:scan`, or \u2014 only for Check 12 stale-decision triage \u2014",
+        "`req:review`) for the downstream agent or human to pick up.",
         "",
         "For audits covering more than 10 documents, the reviewer writes",
         "a read-only Python verification script alongside the report and",
@@ -13914,9 +14506,9 @@ var requirementsReviewerBundle = {
         "Authoring remains the responsibility of the `requirements-writer`",
         "(requirement docs) and `bcm-writer` (capability models) bundles.",
         "Gap discovery is the responsibility of the `requirements-analyst`",
-        "bundle. The reviewer never opens `req:scan`, `req:draft`,",
-        "`req:trace`, `req:review`, or `bcm:*` issues \u2014 only `req:write`",
-        "follow-ups from either phase.",
+        "bundle. The reviewer never opens `req:scan`, `req:draft-trace`,",
+        "`req:review`, or `bcm:*` issues \u2014 only `req:write` follow-ups",
+        "from either phase.",
         "",
         "**Soft dependency on the `requirements-writer` bundle.** The",
         "reviewer reads category templates from",
@@ -16588,6 +17180,7 @@ var BUILT_IN_BUNDLES = [
   githubWorkflowBundle,
   slackBundle,
   meetingAnalysisBundle,
+  agendaBundle,
   orchestratorBundle,
   prReviewBundle,
   requirementsAnalystBundle,
@@ -20371,6 +20964,7 @@ var TypeScriptConfig = class extends import_projen22.Component {
   addApproveMergeUpgradeWorkflow,
   addBuildCompleteJob,
   addSyncLabelsWorkflow,
+  agendaBundle,
   awsCdkBundle,
   baseBundle,
   bcmWriterBundle,