@codedrifters/configulator 0.0.262 → 0.0.263

package/lib/index.mjs

@@ -5187,6 +5187,86 @@ var meetingAnalystSubAgent = {
     "5. **Bi-directional traceability.** Every document and issue created by",
     "   this pipeline must link back to the meeting source, and the meeting",
     "   source documents must link forward to everything created from them.",
+    "6. **Respect meeting type and areas.** Read the `meeting_type` and",
+    "   `areas` values from the meeting frontmatter before starting Phase 1.",
+    "   Apply the type-specific rules from the **Meeting type handling**",
+    "   table (phases 1\u20132) and the area-filtered routing rules from the",
+    "   **Areas filtering** table (phase 4).",
+    "",
+    "---",
+    "",
+    "## Meeting type handling",
+    "",
+    "Meeting frontmatter is expected to carry a `meeting_type` field whose",
+    "value is one of the project's concrete meeting-type `id`s (declared",
+    "via `AgentConfigOptions.meetings.meetingTypes`). Each concrete `id`",
+    "maps to one of six generic **meeting kinds** that drive type-specific",
+    "extraction rules:",
+    "",
+    "| Kind | Primary outputs | Phase-1/2 rules |",
+    "|------|-----------------|-----------------|",
+    "| `planning` | Sprint/plan updates, task issues, requirement drafts | Extract every task assignment. Phase 4 updates the active sprint-plan doc directly and creates one issue per assigned task. |",
+    "| `review` | Retro notes, follow-up issues, status updates, requirement revisions | Mark completed tasks in the active sprint-plan doc. Capture retrospective learnings inside the meeting notes \u2014 do not spawn a separate retro document. |",
+    "| `brainstorm` | Future-feature candidates, research topics, very few Firm decisions | Lower the bar for Open Questions. Do **not** create requirement or ADR issues from brainstorm output unless the item is explicitly marked **Firm**. Prefer research/discovery issues for promising ideas. |",
+    "| `standup` | Action items, blockers, status updates | Do not produce requirement, ADR, or BDR drafts. Phase 3 (Draft) is almost always skipped. Focus on action-item issues and sprint-plan status updates. |",
+    "| `external` | Customer/competitive intel, people/company profiles, lead capture | Default every attendee outside the team into **People of Interest**. Default every organization mentioned into **Companies of Interest** (signal threshold still applies). Capture stated customer pain points as candidate **BR** (business requirements), not FR. |",
+    "| `other` | General meeting extraction | Apply the default workflow with no type-specific overrides. |",
+    "",
+    "**How to resolve the kind:**",
+    "",
+    "1. Read `meeting_type` from the frontmatter.",
+    "2. Look up the matching `id` in the project's **Recognized meeting",
+    "   types** table (rendered below when `meetingTypes` is declared).",
+    "3. Use the `Kind` column value. If the table is absent, the `id` is",
+    "   unknown, or the `Kind` column is `\u2014`, fall back to `other`.",
+    "4. Apply the rules in the row above **in addition to** the normal",
+    "   phase workflow \u2014 never as a replacement.",
+    "",
+    "If `meeting_type` is missing, invalid, or the declared `id` is not in",
+    "the project's table, note it in the extraction's Open Questions and",
+    "proceed with the default workflow (treat as `other`).",
+    "",
+    "## Areas filtering",
+    "",
+    "Meeting frontmatter may carry an `areas: [...]` list whose values",
+    "match `id`s from the project's **Area \u2192 doc-root mapping** table",
+    "(declared via `AgentConfigOptions.meetings.meetingAreas`). The list",
+    "scopes phase-4 direct edits and cross-references to the doc-root",
+    "sub-folders registered for those areas. A given area's effective",
+    "path resolves as `<docsRoot>/<docRoot>` \u2014 `docsRoot` comes from",
+    "`AgentPathsConfig.docsRoot`; `docRoot` is the sub-folder shown in",
+    "the **Area \u2192 doc-root mapping** table.",
+    "",
+    "**Gating contract (phase 4 only):**",
+    "",
+    "- **Scoped in:** direct edits and cross-reference stubs under the",
+    "  `docRoot` of every `id` present in the meeting's `areas` list.",
+    "- **Scoped out:** direct edits to any doc-root sub-folder that is",
+    "  declared in the project's area map but whose `id` is **not** in",
+    "  the meeting's `areas`. For those out-of-scope areas, create",
+    "  follow-up issues instead of editing the doc directly.",
+    "- **Not gated:** issue creation (requirements, ADRs, profiles,",
+    "  research) is always in scope regardless of areas.",
+    "",
+    "**Resolution rules:**",
+    "",
+    "1. If the meeting's `areas` frontmatter is missing or empty **and**",
+    "   the project has declared a non-empty `meetingAreas` map, no",
+    "   doc-root sub-folder is gated in: direct edits to any declared",
+    "   `docRoot` sub-folder are out-of-scope and become follow-up issues",
+    "   per step 6. Only the default meetings root (`meetingsRoot`)",
+    "   remains editable.",
+    "2. If `areas` lists an `id` that is not in the project's area map,",
+    "   note it in the extraction's Open Questions and treat the unknown",
+    "   `id` as absent. Do **not** invent a doc-root path for it.",
+    "3. Out-of-scope direct edits become `type:docs` follow-up issues on",
+    "   phase 4 step 6, with the area noted in the issue body.",
+    "",
+    "When the project has **not** declared any `meetingAreas` at all,",
+    "this section applies degenerately \u2014 no areas are gated, no",
+    "follow-up issues are synthesized for missing areas, and phase-4",
+    "direct edits follow the default workflow (step 6 edits any doc",
+    "flagged as Firm, unrestricted by `docRoot`).",
     "",
     "---",
     "",
@@ -5244,7 +5324,13 @@ var meetingAnalystSubAgent = {
     "",
     "### Steps",
     "",
-    "1. Read the transcript file specified in the issue body.",
+    "1. Read the transcript file specified in the issue body. Parse the",
+    "   meeting-note frontmatter first, capturing `meeting_type` and",
+    "   `areas`. Resolve `meeting_type` to a kind using the **Meeting type",
+    "   handling** table; note the resolved kind in the extraction",
+    "   frontmatter. If `meeting_type` is missing or not in the project's",
+    "   Recognized meeting types table, treat it as `other` and flag it",
+    "   in Open Questions.",
     "2. Identify and categorize content into these buckets:",
     "",
     "   | Bucket | What to look for |",
@@ -5270,14 +5356,32 @@ var meetingAnalystSubAgent = {
     "   - Companies of Interest (with type and context)",
     "   - Strategic / Product Direction",
     "",
-    "4. **Create downstream phase issues** using `gh issue create`:",
+    "   Carry `meeting_type`, the resolved `meeting_kind`, and `areas`",
+    "   into the extraction frontmatter so downstream phases can gate",
+    "   behaviour without re-parsing the meeting note.",
+    "",
+    "4. **Apply type-specific rules.** Consult the **Meeting type handling**",
+    "   table for the resolved kind and apply its phase-1 rules in",
+    "   addition to the default extraction above. Examples:",
+    "   - `standup`: skip requirement, ADR, and BDR extraction; focus on",
+    "     action items and status.",
+    "   - `brainstorm`: emphasize Open Questions and Future Features.",
+    "     Only mark decisions as Firm when the transcript is unambiguous.",
+    "   - `external`: default attendees outside the team into People of",
+    "     Interest; default organizations mentioned into Companies of",
+    "     Interest (signal threshold still applies); capture customer",
+    "     pain points as candidate BR (not FR).",
+    "",
+    "5. **Create downstream phase issues** using `gh issue create`:",
     "   - Always create a `meeting:notes` issue (blocked on this extract issue)",
     "   - If requirements OR decisions/ADRs identified, create a `meeting:draft` issue",
-    "     (blocked on the notes issue)",
+    "     (blocked on the notes issue). For kind `standup`, skip the",
+    "     `meeting:draft` issue \u2014 standup meetings almost never produce",
+    "     formal drafts.",
     "   - Always create a `meeting:link` issue \u2014 blocked on the draft issue if one",
     "     was created, otherwise blocked on the notes issue",
     "",
-    "5. Commit, push, and close the extract issue.",
+    "6. Commit, push, and close the extract issue.",
     "",
     "---",
     "",
@@ -5334,18 +5438,38 @@ var meetingAnalystSubAgent = {
     "### Steps",
     "",
     "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
+    "   Re-read the extraction frontmatter for `meeting_kind` and `areas`,",
+    "   then build the area-gate: the set of `docRoot` sub-folders that",
+    "   are in scope for direct edits on this meeting. Apply the rules in",
+    "   the **Areas filtering** section above.",
     "2. Create requirement issues using `gh issue create` with appropriate labels.",
     "   Include a `## Traceability` section in each issue body linking back to",
-    "   the source meeting and extraction file.",
+    "   the source meeting and extraction file. Issue creation is **not**",
+    "   gated by areas.",
     "3. Create ADR issues if technology decisions need formal records.",
-    "   Include a `## Traceability` section in each.",
+    "   Include a `## Traceability` section in each. Not gated by areas.",
     "4. Create action item issues for tasks that are not document-related.",
-    "   Include a `## Traceability` section in each.",
-    "5. Cross-reference the meeting in any existing documents that were discussed.",
-    "6. Apply direct product/strategy doc updates for items flagged as **Firm**",
-    "   confidence in the extraction.",
+    "   Include a `## Traceability` section in each. Not gated by areas.",
+    "5. Cross-reference the meeting in any existing documents that were",
+    "   discussed **and that live under an in-scope `docRoot`**. For",
+    "   discussed documents under an out-of-scope `docRoot`, open a",
+    "   follow-up `type:docs` issue instead of editing the doc directly.",
+    "6. Apply direct product/strategy doc updates for items flagged as",
+    "   **Firm** confidence. When the project declares `meetingAreas`,",
+    "   gate these edits: only apply them when the target path lies",
+    "   under an in-scope `docRoot`, and for Firm items targeting an",
+    "   out-of-scope `docRoot` open a follow-up `type:docs` issue",
+    "   noting the area and the target path. When the project has not",
+    "   declared any `meetingAreas`, apply Firm updates unrestricted",
+    "   (the degenerate case above). For the kind `planning`, also",
+    "   update the active sprint-plan doc directly (when the",
+    "   sprint-plan doc's area is in-scope, or always when no",
+    "   `meetingAreas` are declared); for the kind `review`, mark",
+    "   completed tasks in that same doc.",
     "7. **Update the extraction file** with a `## Downstream Artifacts` section",
-    "   listing every issue and document created from this meeting.",
+    "   listing every issue and document created from this meeting. Note",
+    "   any items that were deferred to follow-up issues because of the",
+    "   area gate.",
     "8. **Update the meeting notes** with a `## Related Issues` section listing",
     "   all issues created from this meeting.",
     "9. Comment on the parent extract issue with a summary linking to all",
@@ -5429,7 +5553,17 @@ var meetingAnalysisBundle = {
         "Use `/process-meeting <path>` to process a meeting transcript through a",
         "4-phase pipeline (extract \u2192 notes \u2192 draft \u2192 link). Each phase runs as a",
         "separate agent session tracked by a GitHub issue with a `meeting:*` label.",
-        "See the `meeting-analyst` agent definition for full workflow details."
+        "See the `meeting-analyst` agent definition for full workflow details.",
+        "",
+        "Meeting notes may declare a `meeting_type` (one of the project's",
+        "recognized types) and an `areas: [...]` list. The `meeting_type`",
+        "resolves to a generic kind \u2014 `planning` / `review` / `brainstorm` /",
+        "`standup` / `external` / `other` \u2014 that drives type-specific",
+        "extraction rules in phases 1\u20132. The `areas` list scopes phase-4",
+        "direct edits to the doc-root sub-folders declared in the project's",
+        "**Area \u2192 doc-root mapping** table. When both fields are absent",
+        "the pipeline falls back to the default workflow (kind `other`,",
+        "no area gating)."
       ].join("\n"),
       platforms: {
         cursor: { exclude: true }
@@ -16260,18 +16394,24 @@ function renderMeetingTypes(types, agendaTemplateRoot) {
     "This project declares a meeting-type taxonomy through",
     "`AgentConfigOptions.meetings.meetingTypes`. When classifying a",
     "meeting transcript, pick the `id` from this list that best fits the",
-    "meeting; do **not** invent new type identifiers. Agenda-template",
-    `paths below are resolved relative to \`${resolvedRoot}\`.`,
-    "",
-    "| ID | Label | Scope | Cadence | Default duration | Agenda template |",
-    "|----|-------|-------|---------|------------------|-----------------|"
+    "meeting; do **not** invent new type identifiers. The `Kind` column",
+    "maps each concrete `id` onto the generic meeting-kind taxonomy",
+    "(`planning` / `review` / `brainstorm` / `standup` / `external` /",
+    "`other`) documented in the **Meeting type handling** section \u2014",
+    "apply the type-specific rules listed there based on this kind.",
+    "Agenda-template paths below are resolved relative to",
+    `\`${resolvedRoot}\`.`,
+    "",
+    "| ID | Label | Kind | Scope | Cadence | Default duration | Agenda template |",
+    "|----|-------|------|-------|---------|------------------|-----------------|"
   ];
   for (const type of types) {
+    const kind = type.kind ? `\`${type.kind}\`` : "\u2014";
     const cadence = type.cadence ? `\`${type.cadence}\`` : "\u2014";
     const duration = type.defaultDurationMinutes !== void 0 ? `${type.defaultDurationMinutes} min` : "\u2014";
     const template = type.agendaTemplatePath ? `\`${type.agendaTemplatePath}\`` : "\u2014";
     lines.push(
-      `| \`${type.id}\` | ${type.label} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
+      `| \`${type.id}\` | ${type.label} | ${kind} | \`${type.scope}\` | ${cadence} | ${duration} | ${template} |`
     );
   }
   return lines.join("\n");
@@ -16282,10 +16422,12 @@ function renderMeetingAreas(areas) {
     "",
     "This project declares a meeting-area routing map through",
     "`AgentConfigOptions.meetings.meetingAreas`. When a meeting note's",
-    "frontmatter carries an `area:` value matching an `id` below, route",
-    "phase-4 direct edits into the corresponding sub-tree of the docs",
-    "root (`AgentPathsConfig.docsRoot`). Meetings whose `area` does not",
-    "match any declared entry fall back to the default meetings root.",
+    "frontmatter carries an `areas:` list, route phase-4 direct edits",
+    "into the corresponding sub-trees of the docs root",
+    "(`AgentPathsConfig.docsRoot`). See the **Areas filtering** section",
+    "of the `meeting-analyst` agent for the full gating contract.",
+    "Meetings whose `areas` list is empty or does not match any",
+    "declared entry fall back to the default meetings root.",
     "",
     "| Area ID | Label | Doc-root sub-folder |",
     "|---------|-------|---------------------|"