@codedrifters/configulator 0.0.182 → 0.0.183

package/lib/index.mjs

@@ -197,6 +197,17 @@ var AGENT_MODEL = {
   BALANCED: "balanced",
   POWERFUL: "powerful"
 };
+function resolveModelAlias(model) {
+  if (!model || model === AGENT_MODEL.INHERIT) {
+    return void 0;
+  }
+  const mapping = {
+    [AGENT_MODEL.POWERFUL]: "opus",
+    [AGENT_MODEL.BALANCED]: "sonnet",
+    [AGENT_MODEL.FAST]: "haiku"
+  };
+  return mapping[model] ?? model;
+}
 var MCP_TRANSPORT = {
   STDIO: "stdio",
   HTTP: "http",
@@ -943,6 +954,297 @@ var jestBundle = {
   }
 };
 
+// src/agent/bundles/meeting-analysis.ts
+var meetingAnalystSubAgent = {
+  name: "meeting-analyst",
+  description: "Processes meeting transcripts through a 4-phase pipeline: extract, notes, draft, and link",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Meeting Analyst Agent",
+    "",
+    "You process meeting transcripts through a structured 4-phase pipeline.",
+    "Each phase runs as a **separate agent session**, triggered by its own",
+    "GitHub issue with a `meeting:*` phase label. You handle exactly **one",
+    "phase per session** \u2014 read the issue to determine which phase to execute.",
+    "",
+    "## Execution Model",
+    "",
+    "1. Each meeting produces up to 4 GitHub issues (one per phase)",
+    "2. Each issue carries a `meeting:*` label identifying the phase",
+    "3. You pick up one issue, execute that phase, commit/push, then close the issue",
+    "4. Phase 1 (Extract) creates the downstream phase issues for phases 2-4",
+    "5. Each downstream issue includes `Depends on: #N` linking to its predecessor",
+    "",
+    "## Design Principles",
+    "",
+    "1. **Extract, don't interpret.** Capture what was said and decided. Flag",
+    "   ambiguity as open items rather than resolving it.",
+    "2. **Route to the right category.** Meeting content maps to requirements,",
+    "   ADRs, product docs, and business strategy. Each output goes to the",
+    "   correct location per the project's taxonomy.",
+    "3. **Preserve provenance.** Every extracted item links back to the meeting",
+    "   source so reviewers can check context.",
+    "4. **Create issues, not documents.** For requirements and ADRs, create",
+    "   GitHub issues that other agents or humans will pick up. Do not write",
+    "   final requirement documents yourself.",
+    "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.",
+    "",
+    "---",
+    "",
+    "## Traceability",
+    "",
+    "All outputs must be bi-directionally linked so any artifact can be traced",
+    "back to the meeting that produced it and forward to everything it spawned.",
+    "",
+    "### Backward links (created artifact \u2192 meeting source)",
+    "",
+    "Every GitHub issue and document created by this pipeline must include a",
+    "`## Traceability` section with:",
+    "",
+    "```markdown",
+    "## Traceability",
+    "",
+    "- **Source meeting:** <path to transcript or meeting notes>",
+    "- **Extraction:** <path to extraction file>",
+    "- **Phase issue:** #<N> (the phase issue that created this artifact)",
+    "```",
+    "",
+    "### Forward links (meeting source \u2192 created artifacts)",
+    "",
+    "After Phase 4 (Link) creates all follow-up issues and documents:",
+    "",
+    "1. **Update the extraction file** with a `## Downstream Artifacts` section",
+    "   listing every issue and document created from this meeting:",
+    "",
+    "   ```markdown",
+    "   ## Downstream Artifacts",
+    "",
+    "   | Artifact | Type | Issue/Path |",
+    "   |----------|------|------------|",
+    "   | <title> | requirement / ADR / action-item / profile | #<N> or <path> |",
+    "   ```",
+    "",
+    "2. **Update the meeting notes** with a similar `## Related Issues` section",
+    "   listing all issues created from this meeting.",
+    "",
+    "3. **Comment on the extract issue** with a summary linking to all created",
+    "   artifacts.",
+    "",
+    "### Within-pipeline links",
+    "",
+    "- Phase issues link to predecessors via `Depends on: #N`",
+    "- Phase issues reference the extraction file path in their body",
+    "- Draft documents reference both the extraction and the meeting notes",
+    "",
+    "---",
+    "",
+    "## Phase 1: Extract (`meeting:extract`)",
+    "",
+    "**Goal:** Read the meeting transcript and categorize all substantive content.",
+    "",
+    "### Steps",
+    "",
+    "1. Read the transcript file specified in the issue body.",
+    "2. Identify and categorize content into these buckets:",
+    "",
+    "   | Bucket | What to look for |",
+    "   |--------|-----------------|",
+    `   | **Decisions** | "We decided...", "Let's go with...", explicit choices |`,
+    '   | **Requirements** | Feature descriptions, acceptance criteria, "it should..." |',
+    "   | **Technology discussions** | Platform comparisons, architecture options, tool evaluations |",
+    '   | **Action items** | "[Person] will...", "Next step is...", assigned tasks |',
+    '   | **Open questions** | "We need to figure out...", unresolved debates |',
+    "   | **People of interest** | Industry contacts, domain experts mentioned |",
+    "   | **Companies of interest** | Competitors, vendors, partners discussed |",
+    "   | **Strategic direction** | Business model changes, market positioning |",
+    "   | **Product direction** | Roadmap changes, feature prioritization |",
+    "",
+    "3. Write the extraction to a markdown file with structured sections:",
+    "   - Attendees",
+    "   - Decisions Made (with category and confidence: Firm / Tentative / Needs confirmation)",
+    "   - Requirements Identified (with category and priority estimate)",
+    "   - Technology Discussions (with status: Decided / Leaning toward / Open)",
+    "   - Action Items (with assignee and due date if stated)",
+    "   - Open Questions",
+    "   - People of Interest (with context and whether a profile exists)",
+    "   - Companies of Interest (with type and context)",
+    "   - Strategic / Product Direction",
+    "",
+    "4. **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)",
+    "   - 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.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Notes (`meeting:notes`)",
+    "",
+    "**Goal:** Transform the extraction into structured meeting notes.",
+    "",
+    "### Steps",
+    "",
+    "1. Read the extraction file referenced in the issue body (output of Phase 1).",
+    "2. Write structured meeting notes with these sections:",
+    "   - Meeting metadata (title, date, attendees)",
+    "   - Agenda / topics covered",
+    "   - Key Discussion Points (organized by topic)",
+    "   - Decisions (numbered, with rationale)",
+    "   - Action Items (table: who, what, when)",
+    "   - Open Questions",
+    "   - Follow-up items",
+    "3. Commit, push, and close the notes issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Draft (`meeting:draft`)",
+    "",
+    "**Goal:** Draft proposals for requirements, ADRs, and product/strategy updates.",
+    "",
+    "This phase only exists if the extraction identified requirements, architectural",
+    "decisions, or strategy changes. If this issue exists, execute it.",
+    "",
+    "### Steps",
+    "",
+    "1. Read the extraction file from Phase 1.",
+    "2. Check existing requirement registries and ADR registries for duplicates.",
+    "3. Draft requirement proposals with:",
+    "   - Category (FR, BR, NFR, etc.)",
+    "   - Summary (2-3 sentences)",
+    "   - Draft acceptance criteria",
+    "   - Related existing requirements",
+    "4. Draft ADR proposals for technology decisions with:",
+    "   - Context and problem statement",
+    "   - Options discussed",
+    "   - Stated preferences or decisions",
+    "   - Status: Proposed or Decided",
+    "5. Summarize product/strategy document updates needed.",
+    "6. Commit, push, and close the draft issue.",
+    "",
+    "---",
+    "",
+    "## Phase 4: Link (`meeting:link`)",
+    "",
+    "**Goal:** Create GitHub issues for follow-up work, cross-reference the",
+    "meeting into existing documentation, and complete bi-directional traceability.",
+    "",
+    "### Steps",
+    "",
+    "1. Read the drafts from Phase 3 (if they exist) and the extraction from Phase 1.",
+    "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.",
+    "3. Create ADR issues if technology decisions need formal records.",
+    "   Include a `## Traceability` section in each.",
+    "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.",
+    "7. **Update the extraction file** with a `## Downstream Artifacts` section",
+    "   listing every issue and document created from this meeting.",
+    "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",
+    "   created artifacts.",
+    "10. Commit and push (if any file changes were made), then close the link issue.",
+    "",
+    "---",
+    "",
+    "## GitHub Integration",
+    "",
+    "- Use `gh` CLI for all GitHub operations",
+    "- Apply the appropriate `meeting:*` phase label to each phase issue",
+    "- Use `type:docs` for documentation-producing issues, `type:chore` for",
+    "  maintenance/organizational tasks",
+    "- Use `status:` labels to track progress (`status:ready`, `status:in-progress`, `status:done`)",
+    "- Reference the source meeting transcript in all created issues",
+    "- Link phase issues with `Depends on: #N` to enforce ordering",
+    "",
+    "## When to Shorten the Pipeline",
+    "",
+    "- **Short meetings** (<30 min, <2000 words): combine extract + notes into one session",
+    "- **No requirements or decisions**: Phase 1 skips creating the `meeting:draft` issue",
+    "- **Only action items**: extract + notes + link (3 phase issues)"
+  ].join("\n")
+};
+var processMeetingSkill = {
+  name: "process-meeting",
+  description: "Process a meeting transcript through the 4-phase meeting analysis pipeline",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "meeting-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Process Meeting Transcript",
+    "",
+    "Kick off meeting transcript processing by executing Phase 1 (Extract)",
+    "and creating downstream phase issues for the remaining phases.",
+    "",
+    "## Usage",
+    "",
+    "/process-meeting <path-to-transcript>",
+    "",
+    "## Steps",
+    "",
+    "1. Read the provided transcript file",
+    "2. Execute Phase 1 (Extract) \u2014 categorize transcript content into",
+    "   decisions, requirements, action items, open questions, and more",
+    "3. Write the extraction to a markdown file",
+    "4. Create downstream phase issues using `gh issue create`:",
+    "   - `meeting:notes` issue (always)",
+    "   - `meeting:draft` issue (if requirements or decisions were found)",
+    "   - `meeting:link` issue (always)",
+    "5. Each downstream issue includes `Depends on:` linking to its predecessor",
+    "6. Commit and push the extraction file",
+    "",
+    "## Input",
+    "",
+    "Provide a path to a meeting transcript file (text or markdown).",
+    "The transcript should contain speaker-attributed dialogue.",
+    "",
+    "## Output",
+    "",
+    "- An extraction markdown file with categorized meeting content",
+    "- Phase issues with `meeting:*` labels for downstream agent sessions",
+    "  to pick up (notes, draft, link)"
+  ].join("\n")
+};
+var meetingAnalysisBundle = {
+  name: "meeting-analysis",
+  description: "Meeting transcript processing workflow with 4-phase pipeline (extract, notes, draft, link)",
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "meeting-processing-workflow",
+      description: "Describes the 4-phase meeting processing pipeline, extraction taxonomy, and labeling conventions",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Meeting Processing Workflow",
+        "",
+        "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."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [processMeetingSkill],
+  subAgents: [meetingAnalystSubAgent]
+};
+
 // src/pnpm/pnpm-workspace.ts
 import { relative } from "path";
 import { Component, YamlFile } from "projen";
@@ -1959,7 +2261,8 @@ var BUILT_IN_BUNDLES = [
   awsCdkBundle,
   projenBundle,
   githubWorkflowBundle,
-  slackBundle
+  slackBundle,
+  meetingAnalysisBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -2291,6 +2594,7 @@ var ClaudeRenderer = class _ClaudeRenderer {
   }
   static renderSkills(component, skills) {
     for (const skill of skills) {
+      if (skill.platforms?.claude?.exclude) continue;
       const lines = [];
       lines.push("---");
       lines.push(`name: "${skill.name}"`);
@@ -2301,8 +2605,9 @@ var ClaudeRenderer = class _ClaudeRenderer {
       if (skill.userInvocable === false) {
         lines.push(`user-invocable: false`);
       }
-      if (skill.model) {
-        lines.push(`model: "${skill.model}"`);
+      const resolvedSkillModel = resolveModelAlias(skill.model);
+      if (resolvedSkillModel) {
+        lines.push(`model: "${resolvedSkillModel}"`);
       }
       if (skill.effort) {
         lines.push(`effort: "${skill.effort}"`);
@@ -2344,8 +2649,9 @@ var ClaudeRenderer = class _ClaudeRenderer {
       lines.push(`name: ${agent.name}`);
       lines.push(`description: >-`);
       lines.push(`  ${agent.description}`);
-      if (agent.model) {
-        lines.push(`model: ${agent.model}`);
+      const resolvedModel = resolveModelAlias(agent.model);
+      if (resolvedModel) {
+        lines.push(`model: ${resolvedModel}`);
       }
       if (agent.tools && agent.tools.length > 0) {
         lines.push(`tools:`);
@@ -2458,6 +2764,7 @@ var CursorRenderer = class _CursorRenderer {
   }
   static renderSkills(component, skills) {
     for (const skill of skills) {
+      if (skill.platforms?.cursor?.exclude) continue;
       const lines = [];
       lines.push("---");
       lines.push(`name: "${skill.name}"`);
@@ -2499,9 +2806,6 @@ var CursorRenderer = class _CursorRenderer {
       lines.push(`name: ${agent.name}`);
       lines.push(`description: >-`);
       lines.push(`  ${agent.description}`);
-      if (agent.model) {
-        lines.push(`model: ${agent.model}`);
-      }
       if (agent.platforms?.cursor?.readonly) {
         lines.push(`readonly: true`);
       }
@@ -4663,8 +4967,10 @@ export {
   getLatestEligibleVersion,
   githubWorkflowBundle,
   jestBundle,
+  meetingAnalysisBundle,
   pnpmBundle,
   projenBundle,
+  resolveModelAlias,
   resolveTemplateVariables,
   slackBundle,
   turborepoBundle,