@codedrifters/configulator 0.0.199 → 0.0.201

package/lib/index.js

@@ -228,7 +228,9 @@ __export(index_exports, {
   meetingAnalysisBundle: () => meetingAnalysisBundle,
   orchestratorBundle: () => orchestratorBundle,
   pnpmBundle: () => pnpmBundle,
+  prReviewBundle: () => prReviewBundle,
   projenBundle: () => projenBundle,
+  requirementsAnalystBundle: () => requirementsAnalystBundle,
   resolveModelAlias: () => resolveModelAlias,
   resolveTemplateVariables: () => resolveTemplateVariables,
   slackBundle: () => slackBundle,
@@ -506,55 +508,11 @@ var createRuleSkill = {
     "- Use `ruleExtensions` to add project-specific content to existing bundle rules instead of replacing them"
   ].join("\n")
 };
-var reviewPrSkill = {
-  name: "review-pr",
-  description: "Review a pull request for code quality, conventions, and correctness",
-  instructions: [
-    "# Review Pull Request",
-    "",
-    "Review the current pull request in **{{repository.owner}}/{{repository.name}}**.",
-    "",
-    "## Review Checklist",
-    "",
-    "1. **Read the PR description** \u2014 understand the intent and linked issue",
-    "2. **Review the diff** \u2014 check all changed files for:",
-    "   - Correctness and logic errors",
-    "   - Adherence to project conventions",
-    "   - Test coverage for new/changed behavior",
-    "   - No unintended side effects",
-    "3. **Check PR conventions:**",
-    "   - Title uses conventional commit prefix (`feat:`, `fix:`, `docs:`, etc.)",
-    "   - Body includes a closing keyword (`Closes #<issue>`)",
-    "   - Summary of changes is present",
-    "4. **Verify build and tests pass**",
-    "",
-    "## Commands",
-    "",
-    "```bash",
-    "# View the PR details",
-    "gh pr view",
-    "",
-    "# View the diff",
-    "gh pr diff",
-    "",
-    "# Check CI status",
-    "gh pr checks",
-    "```",
-    "",
-    "## Output Format",
-    "",
-    "Provide a structured review with:",
-    "- **Summary**: One-line verdict (approve, request changes, or comment)",
-    "- **Findings**: Bulleted list of issues or suggestions, grouped by severity",
-    "- **Positive notes**: What was done well"
-  ].join("\n"),
-  allowedTools: ["Read", "Glob", "Grep", "Bash(gh *)"]
-};
 var baseBundle = {
   name: "base",
   description: "Core rules: project overview, interaction style, and general coding conventions",
   appliesWhen: () => true,
-  skills: [createRuleSkill, reviewPrSkill],
+  skills: [createRuleSkill],
   rules: [
     {
       name: "project-overview",
@@ -1046,21 +1004,7 @@ var githubWorkflowBundle = {
         "6. **Create the PR** using `gh pr create`:",
         "   - **Title**: use a conventional commit style title (e.g., `feat(scope): short description`)",
         "   - **Body**: include `Closes #<issue-number>` (derived from the branch name) and a brief summary of changes",
-        "7. **Enable auto-merge with squash** \u2014 use `gh pr merge --auto --squash` with the merge commit message:",
-        "",
-        "```",
-        "gh pr merge --auto --squash --subject '<conventional-commit-title>' --body '<extended-description>'",
-        "```",
-        "",
-        "The merge commit message should follow this format:",
-        "",
-        "```",
-        "Subject: <conventional-commit-title>",
-        "",
-        "Body:",
-        "- Bullet points summarizing the changes",
-        "- Closes #<issue-number>",
-        "```",
+        "7. **Delegate review and merge to the `pr-reviewer` sub-agent.** After the PR is created, invoke the `/review-pr <pr-number>` skill (or otherwise hand the new PR number to the `pr-reviewer` sub-agent). The reviewer verifies the diff against the linked issue's acceptance criteria and enables squash auto-merge when all checks pass. Do **not** run `gh pr merge --auto` yourself \u2014 review/merge policy lives solely in the `pr-reviewer` agent.",
         "",
         "### PR Body Template",
         "",
@@ -1081,7 +1025,7 @@ var githubWorkflowBundle = {
         "",
         "- Always derive the issue number from the branch name (e.g., `feat/42-add-login` \u2192 `#42`)",
         "- Use conventional commit format for the PR title",
-        "- Always enable auto-merge with squash \u2014 do not merge manually"
+        "- Delegate merge to the `pr-reviewer` sub-agent \u2014 do not merge manually and do not enable auto-merge directly"
       ].join("\n"),
       tags: ["workflow"]
     }
@@ -1863,8 +1807,7 @@ var orchestratorSubAgent = {
     "   - Verify PR conventions: conventional commit title, closing keyword, summary present",
     "   - Check CI status: `gh pr checks N`",
     "3. If the PR passes review:",
-    "   - Approve: `gh pr review N --approve --body '<summary>'`",
-    "   - Enable auto-merge: `gh pr merge N --auto --squash`",
+    "   - Enable squash auto-merge: `gh pr merge N --auto --squash --subject '<conventional-commit-title>' --body '<extended-description>'`",
     "4. If the PR fails review:",
     "   - Request changes: `gh pr review N --request-changes --body '<findings>'`",
     "5. After each PR (whether merged or not):",
@@ -2124,10 +2067,10 @@ var issueWorkerSubAgent = {
     'Closes #<issue-number>"',
     "```",
     "",
-    "Enable auto-merge:",
-    "```bash",
-    "gh pr merge --auto --squash",
-    "```",
+    "Do **not** enable auto-merge yourself. The `pr-reviewer` sub-agent owns",
+    "review and merge for every PR \u2014 it verifies the diff against the issue's",
+    "acceptance criteria and enables squash auto-merge only when all checks",
+    "pass. Record the new PR number so a reviewer can be invoked next.",
     "",
     "## Phase 8: Update Status",
     "",
@@ -2138,9 +2081,9 @@ var issueWorkerSubAgent = {
     "",
     "## Phase 9: Branch Cleanup",
     "",
-    "Auto-merge is enabled, so the PR may not be merged yet. Poll the PR state",
-    "up to 10 times, waiting 30 seconds between polls, until it either merges,",
-    "closes, or the timeout is reached:",
+    "The PR will not auto-merge until the `pr-reviewer` enables it. Poll the PR",
+    "state up to 10 times, waiting 30 seconds between polls, until it either",
+    "merges, closes, or the timeout is reached:",
     "",
     "```bash",
     "gh pr view <pr-number> --json state --jq '.state'",
@@ -2154,8 +2097,8 @@ var issueWorkerSubAgent = {
     "  ```",
     "- **If the state becomes `CLOSED` (not merged):** leave the branch in place",
     "  and report that the PR was closed without merging. Do not delete the branch.",
-    "- **If still `OPEN` after the polling window:** report that auto-merge is",
-    "  still pending and stop. Do not delete the branch.",
+    "- **If still `OPEN` after the polling window:** report that the PR is",
+    "  awaiting review/merge and stop. Do not delete the branch.",
     "",
     "---",
     "",
@@ -2336,6 +2279,392 @@ var pnpmBundle = {
   ]
 };
 
+// src/agent/bundles/pr-review.ts
+var prReviewerSubAgent = {
+  name: "pr-reviewer",
+  description: "Reviews a pull request against its linked issue's acceptance criteria, then enables squash auto-merge or comments with findings",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 40,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# PR Reviewer Agent",
+    "",
+    "You review a single pull request in **{{repository.owner}}/{{repository.name}}**",
+    "against its linked issue's acceptance criteria, verify code quality and",
+    "convention compliance, and then either enable squash auto-merge or leave",
+    "a review comment with findings. You handle exactly **one PR per session**",
+    "unless invoked from the multi-PR loop skill (`/review-prs`), in which case",
+    "you process each eligible PR in turn.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Identify the PR",
+    "",
+    "If a PR number was provided in your instructions, use that. Otherwise stop",
+    "and report that you need a PR number \u2014 do not pick one yourself.",
+    "",
+    "## Phase 1.5: Pre-flight Eligibility Filter",
+    "",
+    "Before spending turns on a full review, run a cheap eligibility check:",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup",
+    "```",
+    "",
+    "The PR is **eligible** only when **all** of the following hold:",
+    "",
+    '1. `mergeable == "MERGEABLE"` (no merge conflicts).',
+    "2. No **failing** required checks in `statusCheckRollup` \u2014 CI must be",
+    "   green or still pending. Any `FAILURE`, `TIMED_OUT`, `CANCELLED`, or",
+    "   `ERROR` conclusion on a required check disqualifies the PR.",
+    "3. The PR body contains a linked issue via one of the closing keywords:",
+    "   `Closes #N`, `Fixes #N`, or `Resolves #N` (case-insensitive).",
+    "",
+    "If **any** check fails, post a short comment explaining the reason and",
+    "stop. Do not proceed to full review.",
+    "",
+    "```bash",
+    "gh pr comment <pr-number> --body '<reason>'",
+    "```",
+    "",
+    "Typical reasons:",
+    "",
+    "- `Not reviewable: merge conflicts \u2014 please rebase onto the default branch.`",
+    "- `Not reviewable: required CI check <name> is failing.`",
+    "- `Not reviewable: PR body is missing a linked issue (Closes #N / Fixes #N / Resolves #N).`",
+    "",
+    "## Phase 2: Gather Context",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json number,title,body,headRefName,baseRefName,isDraft,state,labels,reviews",
+    "gh pr diff <pr-number>",
+    "gh pr checks <pr-number>",
+    "```",
+    "",
+    "Extract the linked issue number from the PR body using the closing keywords",
+    "(`Closes #N`, `Fixes #N`, or `Resolves #N`) identified in Phase 1.5.",
+    "",
+    "Then fetch the linked issue:",
+    "",
+    "```bash",
+    "gh issue view <issue-number>",
+    "```",
+    "",
+    "## Phase 3: Compare Diff to Acceptance Criteria",
+    "",
+    "Read the issue body for an **Acceptance Criteria** (or equivalent) section.",
+    "Build a checklist from it. For each item:",
+    "",
+    "1. Locate the changes in the diff that satisfy it.",
+    "2. Mark it as `met`, `partial`, or `missing`.",
+    "3. Record the specific files / functions / tests that provide evidence.",
+    "",
+    "Also evaluate:",
+    "",
+    "- **Convention compliance** \u2014 PR title uses a conventional commit prefix,",
+    "  body includes a closing keyword, branch name follows project conventions",
+    "- **Test coverage** \u2014 new or changed behavior has tests",
+    "- **CI status** \u2014 `gh pr checks` reports all required checks passing",
+    "- **Scope creep** \u2014 diff stays within the issue's stated scope",
+    "",
+    "## Phase 4: Decide and Act",
+    "",
+    "### If all acceptance criteria are met and CI is green",
+    "",
+    "Enable squash auto-merge with branch deletion. This queues the merge to",
+    "happen once required checks pass; no separate approval review is needed.",
+    "",
+    "```bash",
+    "gh pr merge <pr-number> --auto --squash --delete-branch \\",
+    "  --subject '<conventional-commit-title>' \\",
+    "  --body '<extended-description>'",
+    "```",
+    "",
+    "The squash-merge subject should follow conventional commit format (e.g.",
+    "`feat(scope): description`). The body should bullet the changes and end",
+    "with `Closes #<issue-number>`.",
+    "",
+    "### If any criterion is missing, partial, or CI is failing",
+    "",
+    "Post a plain comment (not a formal review block) with grouped findings:",
+    "",
+    "```bash",
+    "gh pr comment <pr-number> --body '<grouped findings>'",
+    "```",
+    "",
+    "Group findings by severity (**Blocking** / **Suggested** / **Nitpick**).",
+    "For each blocking finding, cite the unmet acceptance criterion and the",
+    "file or function the gap lives in. Do **not** merge, and do **not** push",
+    "any commits to the PR's branch.",
+    "",
+    "Rationale for using a plain comment rather than `gh pr review",
+    "--request-changes`: it is lighter-weight, doesn't require the author to",
+    "dismiss a formal review, and composes cleanly with the multi-PR loop.",
+    "",
+    "## Phase 5: Branch Cleanup and Issue Closure Verification",
+    "",
+    "Auto-merge may not be immediate. Poll the PR state up to 10 times, waiting",
+    "30 seconds between polls:",
+    "",
+    "```bash",
+    "gh pr view <pr-number> --json state --jq '.state'",
+    "```",
+    "",
+    "- **`MERGED`** \u2014 clean up locally **and** verify the linked issue closed:",
+    "  ```bash",
+    "  git checkout {{repository.defaultBranch}}",
+    "  git pull origin {{repository.defaultBranch}}",
+    "  git fetch --prune origin",
+    "  git branch -d <branch-name> 2>/dev/null || git branch -D <branch-name> 2>/dev/null || true",
+    "  ```",
+    "  Then check the linked issue state:",
+    "  ```bash",
+    "  gh issue view <issue-number> --json state --jq '.state'",
+    "  ```",
+    "  If the issue is **not** `CLOSED`, close it explicitly (this covers",
+    "  malformed or missing closing keywords on the merge commit):",
+    "  ```bash",
+    "  gh issue close <issue-number> --reason completed",
+    "  gh issue comment <issue-number> --body 'PR #<pr-number> merged. Closing issue.'",
+    "  ```",
+    "- **`CLOSED` (not merged)** \u2014 leave the branch in place; report the closure.",
+    "- **Still `OPEN`** \u2014 auto-merge is pending; report and stop without deleting.",
+    "",
+    "---",
+    "",
+    "## Output Format",
+    "",
+    "Return a structured report:",
+    "",
+    "```",
+    "PR #<number> \u2014 <title>",
+    "Linked issue: #<issue-number>",
+    "Verdict: AUTO_MERGE_ENABLED | NEEDS_CHANGES | INELIGIBLE | BLOCKED",
+    "",
+    "Acceptance criteria:",
+    "  [x] <criterion> \u2014 <evidence>",
+    "  [~] <criterion> \u2014 partial: <gap>",
+    "  [ ] <criterion> \u2014 missing",
+    "",
+    "Findings:",
+    "  - Blocking: <items>",
+    "  - Suggested: <items>",
+    "  - Nitpick: <items>",
+    "",
+    "Action taken: <enable-auto-merge | commented-on-the-pr | none>",
+    "Branch state: <merged | open | closed>",
+    "Issue state: <closed | open>",
+    "```",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "1. **One PR per session** when invoked directly (`/review-pr`). When",
+    "   invoked from the multi-PR loop (`/review-prs`), process every eligible",
+    "   PR in turn.",
+    "2. **Never merge without a linked issue.** If the PR body has no",
+    "   `Closes #N` / `Fixes #N` / `Resolves #N`, comment and stop.",
+    "3. **Never merge with failing CI.** Even if every criterion is met,",
+    "   block on red checks.",
+    "4. **Never bypass review conventions.** Always use `--squash`, `--auto`,",
+    "   and `--delete-branch` for merges. Do not force-merge.",
+    "5. **Do not implement code.** You review, decide, and orchestrate. If",
+    "   the PR needs changes, comment and stop.",
+    "6. **Never push commits to the PR's branch.** If the PR needs changes,",
+    "   comment and stop \u2014 do not attempt to fix it yourself. The PR author",
+    "   owns the branch; pushing to someone else's branch is out of scope.",
+    "7. **In loop mode (`/review-prs`), never stop early.** If any review",
+    "   fails, comment and move to the next PR. Only abort the loop on a",
+    "   fatal error (e.g. `gh` auth failure, network outage).",
+    "8. **Follow CLAUDE.md conventions** for all `git` and `gh` operations."
+  ].join("\n")
+};
+var reviewPrSkill = {
+  name: "review-pr",
+  description: "Review a single pull request against its linked issue's acceptance criteria, then enable squash auto-merge or comment with findings",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "pr-reviewer",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Review Pull Request",
+    "",
+    "Run a full PR review against the linked issue's acceptance criteria,",
+    "then either enable squash auto-merge or post a findings comment.",
+    "",
+    "## Usage",
+    "",
+    "/review-pr <pr-number>",
+    "",
+    "## What This Skill Does",
+    "",
+    "1. Runs a pre-flight eligibility filter (mergeable, CI not failing, has linked issue)",
+    "2. Fetches the PR, its diff, CI status, and the linked issue",
+    "3. Builds a checklist from the issue's acceptance criteria",
+    "4. Compares the diff against each criterion",
+    "5. Verifies PR conventions (title, closing keyword, branch name)",
+    "6. Verifies CI is green",
+    "7. **If all checks pass:** enables squash auto-merge (with `--delete-branch`)",
+    "8. **If any check fails:** posts a findings comment via `gh pr comment`",
+    "9. After merge, verifies the linked issue is closed and closes it if not",
+    "10. Cleans up the local branch after merge",
+    "",
+    "## Input",
+    "",
+    "Provide the PR number to review. The skill resolves the linked issue from",
+    "the PR body (`Closes #N` / `Fixes #N` / `Resolves #N`).",
+    "",
+    "## Output",
+    "",
+    "A structured report covering verdict, per-criterion status, findings",
+    "grouped by severity, the action taken, and the final branch / issue state.",
+    "",
+    "## Composability",
+    "",
+    "This skill is generic and can be composed with the `github-workflow`",
+    "bundle. The reviewer never implements code and never pushes to the PR",
+    "branch \u2014 it only reviews, decides, and orchestrates merge or comment."
+  ].join("\n")
+};
+var reviewPrsSkill = {
+  name: "review-prs",
+  description: "Loop over every eligible open pull request in the repository and review each one through the full pipeline",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "pr-reviewer",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Review All Eligible Pull Requests",
+    "",
+    "Run the pr-reviewer pipeline over every eligible open PR in",
+    "**{{repository.owner}}/{{repository.name}}**, one after another, until",
+    "the eligible queue is empty.",
+    "",
+    "## Usage",
+    "",
+    "/review-prs",
+    "",
+    "## What This Skill Does",
+    "",
+    "### Step 1: Enumerate open PRs",
+    "",
+    "```bash",
+    "gh pr list --json number,title,body,headRefName,mergeable,mergeStateStatus,statusCheckRollup --limit 50",
+    "```",
+    "",
+    "### Step 2: Filter to eligible PRs",
+    "",
+    "A PR is **eligible** when all of the following hold:",
+    "",
+    '1. `state == "OPEN"` (implicit from `gh pr list`).',
+    '2. `mergeable == "MERGEABLE"` (no conflicts).',
+    "3. No required check in `statusCheckRollup` has a failing conclusion",
+    "   (`FAILURE`, `TIMED_OUT`, `CANCELLED`, `ERROR`). CI green or still",
+    "   pending is fine.",
+    "4. The PR body contains a linked issue (`Closes #N` / `Fixes #N` /",
+    "   `Resolves #N`, case-insensitive).",
+    "",
+    "Drop any PR that fails the filter from the queue. Do not comment on",
+    "them from this skill \u2014 the individual `/review-pr` invocation handles",
+    "the inline rejection comment when run on a specific PR.",
+    "",
+    "### Step 3: Process each eligible PR",
+    "",
+    "For every eligible PR, invoke the full pr-reviewer pipeline",
+    "(Phases 1 through 5) as if `/review-pr <number>` had been called",
+    "directly:",
+    "",
+    "- Gather context (diff, checks, linked issue)",
+    "- Compare diff to acceptance criteria",
+    "- Decide and act (enable auto-merge **or** post findings comment)",
+    "- Verify branch / issue cleanup after merge",
+    "",
+    "Continue to the next PR after each one completes. Never stop the loop",
+    "early because a single PR's review failed \u2014 comment and move on.",
+    "",
+    "### Step 4: Stop when the queue is empty",
+    "",
+    "When no eligible PRs remain, emit a final summary listing every PR",
+    "processed and the verdict for each, then stop.",
+    "",
+    "## Output",
+    "",
+    "Per-PR structured report (same shape as `/review-pr`), followed by a",
+    "one-line-per-PR summary at the end:",
+    "",
+    "```",
+    "Summary:",
+    "  PR #<n>: <verdict>",
+    "  PR #<n>: <verdict>",
+    "  ...",
+    "Total processed: <count>",
+    "```",
+    "",
+    "## Failure Handling",
+    "",
+    "Only abort the loop on a fatal error (e.g. `gh` authentication failure,",
+    "network outage). A failed review for an individual PR is not fatal \u2014",
+    "comment on that PR and continue with the next."
+  ].join("\n")
+};
+var prReviewBundle = {
+  name: "pr-review",
+  description: "Pull request review workflow: verifies PRs against their linked issues' acceptance criteria and orchestrates squash-merge, single or looped over all eligible PRs",
+  // Default-apply: the PR review workflow is safe to include everywhere,
+  // and keeping review/merge policy centralised in the pr-reviewer agent
+  // means consumers get consistent behaviour out of the box. Consumers can
+  // still exclude it explicitly via `excludeBundles` if desired.
+  appliesWhen: () => true,
+  rules: [
+    {
+      name: "pr-review-workflow",
+      description: "Describes the /review-pr and /review-prs skills and their delegation to the pr-reviewer sub-agent",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# PR Review Workflow",
+        "",
+        "Two skills are available, both backed by the same `pr-reviewer`",
+        "sub-agent:",
+        "",
+        "- **`/review-pr <pr-number>`** \u2014 review a single targeted PR.",
+        "- **`/review-prs`** \u2014 loop over every eligible open PR in the",
+        "  repository and review each one in turn.",
+        "",
+        "The `pr-reviewer` sub-agent:",
+        "",
+        "1. Runs a pre-flight eligibility filter (mergeable, CI not failing,",
+        "   has a linked issue). Ineligible PRs get a short comment and are",
+        "   skipped.",
+        "2. Fetches the PR, its diff, CI status, and the linked issue",
+        "3. Builds a checklist from the issue's acceptance criteria",
+        "4. Verifies the diff satisfies each criterion and that CI is green",
+        "5. **Enables squash auto-merge** (with `--delete-branch`) when all",
+        "   checks pass \u2014 no explicit approval review",
+        "6. **Comments with grouped findings** when any check fails (plain",
+        "   `gh pr comment`, not a formal `--request-changes` review)",
+        "7. After a successful merge, verifies the linked issue is closed",
+        "   and closes it explicitly if the merge commit did not",
+        "8. Cleans up the local branch after merge",
+        "",
+        "The reviewer **never** implements code and **never** pushes commits",
+        "to a PR's branch \u2014 it only reviews, decides, and orchestrates merge",
+        "or comment. In loop mode, a failed review for one PR never stops",
+        "the loop; the reviewer comments and moves on. See the `pr-reviewer`",
+        "agent definition for the full phase-by-phase contract."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [reviewPrSkill, reviewPrsSkill],
+  subAgents: [prReviewerSubAgent]
+};
+
 // src/agent/bundles/projen.ts
 var projenBundle = {
   name: "projen",
@@ -2605,6 +2934,474 @@ var projenBundle = {
   ]
 };
 
+// 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.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Requirements Analyst Agent",
+    "",
+    "Dedicated agent loop for discovering requirement gaps from BCM (Business",
+    "Capability Model) documents, product docs, and competitive analysis \u2014 then",
+    "creating well-formed requirement issues for the downstream",
+    "requirements-writer (BCM writer) agent to draft. Designed for scheduled",
+    "execution downstream of the BCM writer and company research agents.",
+    "",
+    "Follow your project's shared agent conventions (`AGENTS.md`,",
+    "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
+    "",
+    "## Design Principles",
+    "",
+    "1. **Discover, don't write.** This agent identifies *what requirements are",
+    "   missing*. The requirements-writer skill writes the actual documents. The",
+    "   boundary keeps this agent fast and the requirements-writer authoritative.",
+    "2. **Trace everything.** Every discovered gap links to the source that",
+    "   revealed it (a BCM model doc, competitive analysis, product doc, or",
+    "   meeting extract).",
+    "3. **Respect the taxonomy.** Route every discovered requirement to the",
+    "   correct BCM category (FR, BR, NFR, SEC, DR, INT, OPS, UX, MT, ADR, TR)",
+    "   using the disambiguation rules in the requirements-writer skill.",
+    "4. **Deduplicate.** Before creating an issue, check whether a requirement",
+    "   already exists or an issue is already open for it.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "Requirements synthesis flows through **3 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",
+    "```",
+    "",
+    "**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 |",
+    "",
+    "All issues also carry `type:requirement` and a `status:*` label.",
+    "",
+    "**Issue count per scan cycle:** 1 scan + 1 draft + 1 trace = **3 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)",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "Projects adopting this bundle must define these paths in their agent",
+    "configuration (`agentConfig.rules` extension or project-level docs):",
+    "",
+    "| Placeholder | Meaning | Typical value |",
+    "|-------------|---------|---------------|",
+    "| `<BCM_DOCS_ROOT>` | Root of BCM model docs (capability models) | `src/content/docs/concepts/` |",
+    "| `<COMPETITIVE_ROOT>` | Competitive analysis docs | `src/content/docs/business-strategy/competitive/` |",
+    "| `<PRODUCT_ROOT>` | Product roadmap / entity taxonomy | `src/content/docs/product/` |",
+    "| `<MEETINGS_ROOT>` | Meeting extracts | `src/content/docs/research/meetings/` |",
+    "| `<RESEARCH_REQUIREMENTS_ROOT>` | Scan reports and proposals | `src/content/docs/research/requirements/` |",
+    "| `<REQUIREMENTS_ROOT>` | Final requirement documents (owned by requirements-writer) | `src/content/docs/requirements/` |",
+    "| `<PREFIX>` | Project-specific requirement ID prefix | e.g. `VRTX`, `ACME` |",
+    "",
+    "If your project stores these in different locations, substitute accordingly",
+    "wherever the phase instructions reference a path.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "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`.",
+    "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.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per your",
+    "   project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Scan (`req:scan`)",
+    "",
+    "**Goal:** Read source documents, identify where requirements are missing,",
+    "incomplete, or contradictory, then check each potential gap against existing",
+    "requirements and open issues to eliminate duplicates. Produces a single",
+    "deduplicated scan report.",
+    "",
+    "**Budget:** Reading source docs + reading requirement registries + searching",
+    "issues. Write one deduplicated scan output file.",
+    "",
+    "### Scan Sources",
+    "",
+    "The issue specifies which source(s) to scan. Common scan scopes:",
+    "",
+    "| Scope | What to read | What to look for |",
+    "|-------|-------------|-----------------|",
+    "| **BCM model doc** | One `{PREFIX}-NNN` doc under `<BCM_DOCS_ROOT>` | `## Vortex Relevance` (or equivalent project-relevance) section \u2014 gaps where capabilities exist but no FR/BR/INT addresses them |",
+    "| **Competitive analysis** | One `comp-*.md` doc under `<COMPETITIVE_ROOT>` | Feature comparison gaps \u2014 competitor features the product lacks requirements for |",
+    "| **Product roadmap** | `<PRODUCT_ROOT>/prioritized-feature-roadmap.md` | Roadmap items without corresponding FRs |",
+    "| **Entity taxonomy** | `<PRODUCT_ROOT>/entity-taxonomy.md` | Entities without CRUD requirements (FR), data requirements (DR), or security requirements (SEC) |",
+    "| **Meeting extract** | `<MEETINGS_ROOT>/meeting-*.extract.md` | Requirements identified but not yet formalized |",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the source documents** specified in the issue.",
+    "",
+    "2. **Identify potential gaps.** For each potential missing requirement:",
+    "   - Classify into the correct BCM category (FR, BR, NFR, SEC, DR, INT,",
+    "     OPS, UX, MT, ADR, TR)",
+    "   - Apply the disambiguation rules from the requirements-writer skill",
+    "   - Note the source that revealed the gap",
+    "   - Estimate priority based on the source context",
+    "",
+    "3. **Read the requirements registry.** Scan `_index.md` files in each",
+    "   `<REQUIREMENTS_ROOT>/<category>/` directory to know what already exists.",
+    "",
+    "4. **Search for existing issues.** For each potential gap, search open issues:",
+    "   ```bash",
+    '   gh issue list --label "type:requirement" --state open \\',
+    "     --json number,title --limit 100",
+    "   ```",
+    "",
+    "5. **Classify each gap:**",
+    "   - **New** \u2014 no existing requirement or open issue covers this",
+    "   - **Duplicate** \u2014 an existing requirement already addresses this",
+    "   - **In progress** \u2014 an open issue already targets this",
+    "   - **Partial** \u2014 existing requirement partially covers this; note the gap",
+    "",
+    "6. **Write the deduplicated scan report** to:",
+    "   ```",
+    "   <RESEARCH_REQUIREMENTS_ROOT>/req-scan-<scope>-<YYYY-MM-DD>.md",
+    "   ```",
+    "",
+    "   Format:",
+    "   ```markdown",
+    "   ---",
+    '   title: "Requirements Scan: <scope>"',
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   status: complete",
+    "   ---",
+    "",
+    "   # Requirements Scan: <scope>",
+    "",
+    "   ## Source Documents Reviewed",
+    "   - <path> \u2014 <brief description>",
+    "",
+    "   ## Existing Requirements Checked",
+    "   - <category>: <count> existing docs, <count> open issues",
+    "",
+    "   ## Identified Gaps (New)",
+    "   ### Gap 1: <Title>",
+    "   - **Category:** FR / BR / NFR / SEC / DR / INT / OPS / UX / MT / ADR / TR",
+    "   - **Source:** <path to doc + section that revealed this gap>",
+    "   - **Priority:** High / Normal / Low",
+    "   - **Rationale:** <why this requirement is needed>",
+    "   - **Duplicate check:** No existing requirement or open issue found",
+    "   - **Proposed scope:** <1-2 sentences on what the requirement should cover>",
+    "",
+    "   ## Already Covered",
+    "   <list of potential gaps that turned out to already have requirements>",
+    "",
+    "   ## In Progress",
+    "   <gaps that already have open issues \u2014 include issue numbers>",
+    "",
+    "   ## Ambiguous / Needs Human Decision",
+    "   <gaps where the correct category or scope is unclear>",
+    "   ```",
+    "",
+    "7. **Create downstream issues based on findings:**",
+    "   - If any new gaps were identified \u2192 create `req:draft` 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",
+    "     to commit and push. The scan issue will be marked done with no",
+    "     downstream work needed.",
+    "",
+    "8. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Phase 2: Draft (`req:draft`)",
+    "",
+    "**Goal:** Expand each identified gap into a requirement proposal with enough",
+    "detail for the requirements-writer to produce a full document.",
+    "",
+    "**Budget:** No web searches. Reading + writing.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scan report** from Phase 1.",
+    "",
+    "2. **For each gap**, write a detailed proposal:",
+    "",
+    "   ```markdown",
+    "   ## Proposed: <PREFIX>-<NNN> \u2014 <Title>",
+    "",
+    "   **Category:** <FR/BR/NFR/SEC/DR/INT/OPS/UX/MT/ADR/TR>",
+    "   **Priority:** <High/Normal/Low>",
+    "   **Source:** <document path and section>",
+    "",
+    "   ### Summary",
+    "   <2-3 sentences describing what the requirement should capture>",
+    "",
+    "   ### Draft Acceptance Criteria",
+    "   - [ ] <testable criterion 1>",
+    "   - [ ] <testable criterion 2>",
+    "   - [ ] <testable criterion 3>",
+    "",
+    "   ### Traceability",
+    "   - **Implements:** <BR or parent requirement if applicable>",
+    "   - **Related:** <existing requirements that interact with this one>",
+    "   - **Source:** <BCM doc, competitive analysis, or meeting that revealed",
+    "     the gap \u2014 use a markdown link. If the source is a meeting note, the",
+    "     downstream requirement doc must include the same meeting as a link in",
+    "     its Traceability `Related:` list.>",
+    "",
+    "   ### Decision Authority",
+    '   <"Direct write" for BR/FR/NFR/SEC/UX, or "Proposed \u2014 needs human',
+    '   decision" for ADR/TR, or "Mixed \u2014 defer technology choices" for',
+    "   DR/MT/INT/OPS>",
+    "",
+    "   ### Notes for Requirements Writer",
+    "   <any context the writer should know \u2014 related ADRs, existing partial",
+    "   coverage, relevant competitive features>",
+    "   ```",
+    "",
+    "3. **Write the proposals** to:",
+    "   ```",
+    "   <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<YYYY-MM-DD>.md",
+    "   ```",
+    "",
+    "4. **Determine next sequence numbers.** Check each target category",
+    "   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.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the proposals** from Phase 2.",
+    "",
+    "2. **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).",
+    "",
+    "   ```bash",
+    "   gh issue create \\",
+    '     --title "docs(<category>): <PREFIX>-<NNN> \u2014 <title>" \\',
+    '     --label "type:requirement" --label "status:ready" --label "priority:medium" \\',
+    '     --body "## Objective',
+    "   Write <PREFIX>-<NNN> \u2014 <title>.",
+    "",
+    "   ## Context",
+    "   - **Gap identified by:** requirements scan of <source>",
+    "   - **Proposals file:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md",
+    "",
+    "   ## Inputs",
+    "   - **Depends on:** (none)",
+    "   - **Read:** <RESEARCH_REQUIREMENTS_ROOT>/req-proposals-<scope>-<date>.md, <source docs>",
+    "",
+    "   ## Acceptance Criteria",
+    "   - [ ] Requirement document follows <category> template",
+    "   - [ ] Traceability links to source BCM/competitive/product doc",
+    "   - [ ] Registry index updated",
+    "   - [ ] Decision authority rules followed (direct write vs. proposed)",
+    "",
+    "   ## Scope Size",
+    "   small",
+    "",
+    "   ## Output Path",
+    '   <REQUIREMENTS_ROOT>/<category>/<PREFIX>-<NNN>-<slug>.md"',
+    "   ```",
+    "",
+    "3. **Update source documents.** In each BCM model doc or competitive",
+    "   analysis that was scanned, add a note in the `## Vortex Relevance` or",
+    "   `## Strategic Implications` section indicating that a requirement issue",
+    "   was created:",
+    "",
+    "   ```markdown",
+    "   - Gap addressed: see [<PREFIX>-<NNN>](<relative path to requirement doc>)",
+    "     (issue #<N>)",
+    "   ```",
+    "",
+    "4. **Comment on the scan issue** with a summary of all issues created and",
+    "   all docs updated.",
+    "",
+    "5. **Commit and push.**",
+    "",
+    "---",
+    "",
+    "## Coordination with Other Agents",
+    "",
+    "| Direction | Agent | What |",
+    "|-----------|-------|------|",
+    "| Upstream | BCM Writer | Scans `## Vortex Relevance` sections for capability gaps |",
+    "| Upstream | Company Research | Scans competitive analysis for feature comparison gaps |",
+    "| Upstream | Meeting Analyst | Scans meeting extracts for requirement proposals |",
+    "| Downstream | Requirements Writer (BCM Writer) | Creates `type:requirement` issues for the skill to draft |",
+    "",
+    "**File boundaries:** Writes to `<RESEARCH_REQUIREMENTS_ROOT>/req-*.md` and",
+    "minor traceability edits to `<BCM_DOCS_ROOT>` and `<COMPETITIVE_ROOT>`.",
+    "Never writes to `<REQUIREMENTS_ROOT>/` \u2014 that is owned by the",
+    "requirements-writer agent.",
+    "",
+    "---",
+    "",
+    "## Blocked Issues",
+    "",
+    "Additional block reasons specific to requirements synthesis:",
+    "- Source document has unresolved contradictions",
+    "- Category classification is ambiguous (needs human disambiguation)",
+    "- Dependent BCM documents are still in draft with placeholder content",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **Discover, don't write requirements.** Create issues for the",
+    "  requirements-writer \u2014 don't write requirement documents directly.",
+    "- **Deduplicate rigorously.** Check both existing docs and open issues",
+    "  before flagging a gap.",
+    "- **Respect decision authority.** Mark ADR/TR proposals as needing human",
+    "  decision. Don't create direct-write issues for technology choices.",
+    "- **Bidirectional traceability.** Every `req-scan-*.md` and",
+    "  `req-proposals-*.md` must include a `## Produced` section listing the",
+    "  downstream requirement issues (and eventual requirement documents) it",
+    "  spawned, as markdown links; each formal requirement document under",
+    "  `<REQUIREMENTS_ROOT>/` must include a forward link back to the scan or",
+    "  proposal that produced it."
+  ].join("\n")
+};
+var scanRequirementsSkill = {
+  name: "scan-requirements",
+  description: "Kick off a requirements-analyst scan across BCM model docs, competitive analysis, product docs, or meeting extracts. Creates a req:scan issue and dispatches Phase 1.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "requirements-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Scan Requirements",
+    "",
+    "Kick off a requirements-analyst scan cycle. Creates a `req:scan` issue",
+    "targeted at the requested scope and dispatches Phase 1 (Scan) in the",
+    "requirements-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/scan-requirements <scope>",
+    "",
+    "Where `<scope>` is one of:",
+    "- `bcm:<PREFIX-NNN>` \u2014 a single BCM model doc",
+    "- `competitive:<slug>` \u2014 a single competitive analysis doc",
+    "- `product-roadmap` \u2014 the prioritized feature roadmap",
+    "- `entity-taxonomy` \u2014 the entity taxonomy doc",
+    "- `meeting:<slug>` \u2014 a meeting extract",
+    "- `all-bcm` / `all-competitive` \u2014 full sweep (long-running)",
+    "",
+    "## Steps",
+    "",
+    "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.",
+    "",
+    "## 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."
+  ].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.",
+  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.",
+      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 (BCM writer) agent. Keep that",
+        "boundary clean: proposals land under the research requirements",
+        "directory, not under the authoritative requirements tree.",
+        "",
+        "See the `requirements-analyst` agent definition for full workflow",
+        "details and phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [scanRequirementsSkill],
+  subAgents: [requirementsAnalystSubAgent],
+  labels: [
+    {
+      name: "type:requirement",
+      color: "1D76DB",
+      description: "Work that produces or discovers a requirement document (FR, BR, NFR, etc.)"
+    },
+    {
+      name: "req:scan",
+      color: "C5DEF5",
+      description: "Phase 1: scan source docs for requirement gaps and deduplicate"
+    },
+    {
+      name: "req:draft",
+      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"
+    }
+  ]
+};
+
 // src/agent/bundles/slack.ts
 var slackBundle = {
   name: "slack",
@@ -3253,7 +4050,9 @@ var BUILT_IN_BUNDLES = [
   githubWorkflowBundle,
   slackBundle,
   meetingAnalysisBundle,
-  orchestratorBundle
+  orchestratorBundle,
+  prReviewBundle,
+  requirementsAnalystBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -6779,7 +7578,9 @@ var TypeScriptConfig = class extends import_projen22.Component {
   meetingAnalysisBundle,
   orchestratorBundle,
   pnpmBundle,
+  prReviewBundle,
   projenBundle,
+  requirementsAnalystBundle,
   resolveModelAlias,
   resolveTemplateVariables,
   slackBundle,