@codedrifters/configulator 0.0.202 → 0.0.204

package/lib/index.js

@@ -231,6 +231,7 @@ __export(index_exports, {
   prReviewBundle: () => prReviewBundle,
   projenBundle: () => projenBundle,
   requirementsAnalystBundle: () => requirementsAnalystBundle,
+  researchPipelineBundle: () => researchPipelineBundle,
   resolveModelAlias: () => resolveModelAlias,
   resolveTemplateVariables: () => resolveTemplateVariables,
   slackBundle: () => slackBundle,
@@ -1093,6 +1094,89 @@ var jestBundle = {
   }
 };
 
+// src/agent/bundles/project-context.ts
+var PROJECT_CONTEXT_PATH = "docs/project-context.md";
+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.",
+  "",
+  "---",
+  ""
+];
+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.",
+  "",
+  "### 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.",
+  "",
+  "## 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.",
+  "",
+  "---",
+  ""
+];
+
 // src/agent/bundles/meeting-analysis.ts
 var meetingAnalystSubAgent = {
   name: "meeting-analyst",
@@ -1134,6 +1218,7 @@ var meetingAnalystSubAgent = {
     "",
     "---",
     "",
+    ...PROJECT_CONTEXT_MAINTAINER_SECTION,
     "## Traceability",
     "",
     "All outputs must be bi-directionally linked so any artifact can be traced",
@@ -1783,6 +1868,7 @@ var orchestratorSubAgent = {
     "",
     "---",
     "",
+    ...PROJECT_CONTEXT_READER_SECTION,
     "## Phase A: Startup",
     "",
     "```bash",
@@ -1949,6 +2035,9 @@ var issueWorkerSubAgent = {
     "doubt, treat the session as interactive \u2014 pausing for approval is always",
     "safe; committing without approval is not.",
     "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_READER_SECTION,
     "## Phase 1: Select an Issue",
     "",
     "If an issue number was provided in your instructions, use that issue.",
@@ -2298,6 +2387,7 @@ var prReviewerSubAgent = {
     "",
     "---",
     "",
+    ...PROJECT_CONTEXT_READER_SECTION,
     "## Phase 1: Identify the PR",
     "",
     "If a PR number was provided in your instructions, use that. Otherwise stop",
@@ -2953,6 +3043,9 @@ var requirementsAnalystSubAgent = {
     "Follow your project's shared agent conventions (`AGENTS.md`,",
     "`CLAUDE.md`, or equivalent) for all commit, branch, and PR rules.",
     "",
+    "---",
+    "",
+    ...PROJECT_CONTEXT_MAINTAINER_SECTION,
     "## Design Principles",
     "",
     "1. **Discover, don't write.** This agent identifies *what requirements are",
@@ -3053,7 +3146,7 @@ var requirementsAnalystSubAgent = {
     "",
     "| 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 |",
+    "| **BCM model doc** | One `{PREFIX}-NNN` doc under `<BCM_DOCS_ROOT>` | The doc's project-relevance section (commonly `## <Project> Relevance` or `## Strategic Implications`) \u2014 gaps where capabilities exist but no FR/BR/INT addresses them. Use `docs/project-context.md` to judge what is relevant. |",
     "| **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) |",
@@ -3246,9 +3339,9 @@ var requirementsAnalystSubAgent = {
     "   ```",
     "",
     "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:",
+    "   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:",
     "",
     "   ```markdown",
     "   - Gap addressed: see [<PREFIX>-<NNN>](<relative path to requirement doc>)",
@@ -3266,7 +3359,7 @@ var requirementsAnalystSubAgent = {
     "",
     "| Direction | Agent | What |",
     "|-----------|-------|------|",
-    "| Upstream | BCM Writer | Scans `## Vortex Relevance` sections for capability gaps |",
+    "| Upstream | BCM Writer | Scans capability-model docs for project-relevance gaps (judged against `docs/project-context.md`) |",
     "| 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 |",
@@ -3402,6 +3495,481 @@ var requirementsAnalystBundle = {
   ]
 };
 
+// src/agent/bundles/research-pipeline.ts
+var researchAnalystSubAgent = {
+  name: "research-analyst",
+  description: "Runs a generic research micro-task pipeline (scope, slice search/synthesize, verify). One phase per session, tracked by research:* GitHub issue labels with filesystem-based durability between phases.",
+  model: AGENT_MODEL.POWERFUL,
+  maxTurns: 80,
+  platforms: { cursor: { exclude: true } },
+  prompt: [
+    "# Research Analyst Agent",
+    "",
+    "Generic research micro-task pipeline. Given a research question, you",
+    "break it into a scope, a fixed number of focused search/synthesize",
+    "slices, and a verification pass that reconciles the slice outputs into",
+    "a single deliverable. Each phase runs as its **own agent session**,",
+    "triggered by a GitHub issue with a `research:*` 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 what",
+    "is being researched (companies, products, people, markets, technical",
+    "topics, academic literature, etc.). All domain-specific vocabulary,",
+    "output locations, and acceptance criteria come from the invoking",
+    "issue body or the consuming project's configuration.",
+    "",
+    "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. **Micro-tasks, not mega-prompts.** Split work into small slices so",
+    "   each session has a bounded context window and a single deliverable.",
+    "2. **Filesystem durability.** Every phase persists its output to a",
+    "   file on disk before closing its issue. Downstream phases read those",
+    "   files \u2014 never rely on session memory.",
+    "3. **Issue graph = state machine.** Phase ordering is encoded with",
+    "   `Depends on: #N` links between phase issues. A phase runs only",
+    "   after its predecessor is closed.",
+    "4. **Generic over specific.** No hardcoded domains, companies, source",
+    "   projects, or proprietary taxonomies. Use placeholders that the",
+    "   skill invocation or consuming project fills in.",
+    "5. **Verifiable synthesis.** The verify phase re-reads every slice",
+    "   output and produces a single deliverable whose claims can each be",
+    "   traced back to a slice.",
+    "",
+    "---",
+    "",
+    "## State Machine Overview",
+    "",
+    "```",
+    "\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\u2500\u2500\u2500\u2510     \u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510",
+    "\u2502  1. SCOPE    \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  2. SLICE (\xD7N)      \u2502\u2500\u2500\u2500\u2500\u25B6\u2502  3. VERIFY   \u2502",
+    "\u2502  Turn the    \u2502     \u2502  For each slice:    \u2502     \u2502  Read every  \u2502",
+    "\u2502  question    \u2502     \u2502  search sources,    \u2502     \u2502  slice       \u2502",
+    "\u2502  into N      \u2502     \u2502  synthesize a       \u2502     \u2502  output,     \u2502",
+    "\u2502  focused     \u2502     \u2502  bounded note file  \u2502     \u2502  reconcile,  \u2502",
+    "\u2502  slices      \u2502     \u2502                     \u2502     \u2502  deliverable \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\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 |",
+    "|-------|-------|-------------|",
+    "| `research:scope` | 1. Scope | Decompose the research question into N focused slices. Write a scope file. Create N `research:slice` issues. |",
+    "| `research:slice` | 2. Slice | Execute one slice: search authorized sources, synthesize, write a single slice note file. |",
+    "| `research:verify` | 3. Verify | Read every slice note, reconcile findings, produce the final deliverable and a verification report. |",
+    "",
+    "All issues also carry `type:research` and a `status:*` label.",
+    "",
+    "**Issue count per research cycle:** 1 scope + N slice + 1 verify =",
+    "**N + 2 sessions**. Typical N is 3\u20136.",
+    "",
+    "**Shortened paths:**",
+    "- Scope phase determines the question is unanswerable or out of scope",
+    "  \u2192 scope issue closes with a justification and no downstream issues",
+    "  are created \u2192 **1 session**.",
+    "- Single-slice research (N = 1) \u2192 **3 sessions**. Never skip verify,",
+    "  even with one slice \u2014 verify is where the deliverable lands.",
+    "",
+    "---",
+    "",
+    "## Configurable Paths",
+    "",
+    "The pipeline uses these placeholders. Consuming projects override the",
+    "defaults by passing paths in the `/research` skill invocation or by",
+    "extending this rule in their own `agentConfig.rules`.",
+    "",
+    "| Placeholder | Meaning | Default |",
+    "|-------------|---------|---------|",
+    "| `<RESEARCH_ROOT>` | Root folder for all research outputs | `docs/research/` |",
+    "| `<SCOPE_DIR>` | Scope files | `<RESEARCH_ROOT>/scopes/` |",
+    "| `<SLICES_DIR>` | Slice note files | `<RESEARCH_ROOT>/slices/` |",
+    "| `<DELIVERABLES_DIR>` | Final verified deliverables | `<RESEARCH_ROOT>/deliverables/` |",
+    "| `<RESEARCH_SLUG>` | Short kebab-case slug identifying one research cycle | derived from the question |",
+    "| `<N>` | Number of slices (default 4, max 8) | `4` |",
+    "",
+    "If `docs/project-context.md` specifies a different research tree,",
+    "prefer that. Otherwise fall back to the defaults above.",
+    "",
+    "---",
+    "",
+    "## Agent Loop",
+    "",
+    "Run this loop exactly once per session. Never start a second issue.",
+    "",
+    "1. Claim one open `type:research` issue using phase priority:",
+    "   `research:scope` > `research:slice` > `research:verify`.",
+    "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 `research:*`",
+    "   label.",
+    "4. Commit, push, open a PR (if applicable), and close the issue per",
+    "   your project's PR workflow.",
+    "",
+    "---",
+    "",
+    "## Phase 1: Scope (`research:scope`)",
+    "",
+    "**Goal:** Turn a natural-language research question into a bounded",
+    "scope file and `N` focused slice issues.",
+    "",
+    "**Budget:** No web searches in this phase. Read the question, the",
+    "project context, and any cited source material already on disk. Write",
+    "one scope file. Create N slice issues.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the research question** from the issue body. The body should",
+    "   include:",
+    "   - The question itself",
+    "   - Authorized source categories (e.g. public web, vendor docs, a",
+    "     cited local file path) \u2014 if absent, default to public web only",
+    "   - Output acceptance criteria for the final deliverable",
+    "   - Optional: `<N>` override, `<RESEARCH_SLUG>` override, custom",
+    "     output paths",
+    "",
+    "2. **Derive `<RESEARCH_SLUG>`** if not supplied \u2014 a 3\u20135 word kebab-case",
+    "   summary of the question. Ensure the slug is not already in use",
+    "   under `<SCOPE_DIR>/`.",
+    "",
+    "3. **Decompose the question into N slices.** Each slice must:",
+    "   - Be answerable independently of the others",
+    "   - Fit inside a single agent session's context budget",
+    "   - Have a clearly scoped set of sources to consult",
+    "   - Produce a bounded note file (target: under 1500 words)",
+    "",
+    "4. **Write the scope file** to",
+    "   `<SCOPE_DIR>/<RESEARCH_SLUG>.scope.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Research Scope: <question>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   slice_count: <N>",
+    "   ---",
+    "",
+    "   # Research Scope: <question>",
+    "",
+    "   ## Question",
+    "   <verbatim question from the issue>",
+    "",
+    "   ## Authorized Sources",
+    "   - <source category or path>",
+    "",
+    "   ## Acceptance Criteria",
+    "   - [ ] <criterion for the final deliverable>",
+    "",
+    "   ## Slices",
+    "   ### Slice 1: <title>",
+    "   - **Focus:** <what this slice answers>",
+    "   - **Sources:** <the subset of authorized sources this slice uses>",
+    "   - **Output:** <SLICES_DIR>/<RESEARCH_SLUG>-01-<slug>.slice.md",
+    "",
+    "   ### Slice 2: <title>",
+    "   ...",
+    "",
+    "   ## Out of Scope",
+    "   <sub-questions deliberately excluded from this cycle>",
+    "",
+    "   ## Deliverable",
+    "   <DELIVERABLES_DIR>/<RESEARCH_SLUG>.md",
+    "   ```",
+    "",
+    "5. **Create N `research:slice` issues**, one per slice, each with",
+    "   `Depends on: #<scope-issue>`. Each slice issue body references the",
+    "   scope file and names the exact slice (by number and title).",
+    "",
+    "6. **Create one `research:verify` issue** that depends on all N slice",
+    "   issues. Its body references the scope file and lists every slice",
+    "   output path that verify must read.",
+    "",
+    "7. **Commit and push** the scope file. Close the scope issue.",
+    "",
+    "---",
+    "",
+    "## Phase 2: Slice (`research:slice`)",
+    "",
+    "**Goal:** Answer one slice by searching the authorized sources and",
+    "writing a single slice note file.",
+    "",
+    "**Budget:** Search budget is one slice \u2014 do not expand scope. Write",
+    "one slice note. Do not create downstream issues.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scope file** referenced in the issue body.",
+    "",
+    "2. **Identify your slice** by number and title. Re-read the slice's",
+    "   focus, sources, and output path.",
+    "",
+    "3. **Search the authorized sources.** Stay within the source list for",
+    "   your slice \u2014 do not broaden to the full scope's source list unless",
+    "   the slice explicitly permits it.",
+    "",
+    "4. **Synthesize a slice note** and write it to the slice's output",
+    "   path (e.g. `<SLICES_DIR>/<RESEARCH_SLUG>-NN-<slug>.slice.md`):",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Slice NN: <title>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   slice: NN",
+    "   date: YYYY-MM-DD",
+    "   parent_scope: <SCOPE_DIR>/<RESEARCH_SLUG>.scope.md",
+    "   parent_issue: <N>",
+    "   ---",
+    "",
+    "   # Slice NN: <title>",
+    "",
+    "   ## Question",
+    "   <the slice-level question>",
+    "",
+    "   ## Key Findings",
+    "   - <finding> \u2014 source: <citation>",
+    "",
+    "   ## Evidence",
+    "   <short quotations, paraphrases, or structured data with citations>",
+    "",
+    "   ## Gaps / Open Questions",
+    "   <anything the slice could not answer inside its budget>",
+    "",
+    "   ## Sources",
+    "   - <source URL or file path> \u2014 <date accessed>",
+    "   ```",
+    "",
+    "5. **Stay within the word budget** (default 1500 words). If the slice",
+    "   cannot fit, add an `## Overflow` section at the end noting what was",
+    "   cut and flag it for the verify phase \u2014 do not expand into other",
+    "   slices' territory.",
+    "",
+    "6. **Commit and push** the slice note. Close the slice issue.",
+    "",
+    "---",
+    "",
+    "## Phase 3: Verify (`research:verify`)",
+    "",
+    "**Goal:** Reconcile every slice into a single verified deliverable.",
+    "",
+    "**Budget:** No new web searches. Read the scope, read every slice",
+    "note, reconcile contradictions, write the deliverable and a short",
+    "verification report.",
+    "",
+    "### Steps",
+    "",
+    "1. **Read the scope file** and every slice note listed in the issue",
+    "   body. If any slice file is missing, stop and re-open the",
+    "   corresponding slice issue with `status:needs-attention`.",
+    "",
+    "2. **Build a claim index.** For every assertion in any slice, note",
+    "   which slice(s) support it and which sources back it.",
+    "",
+    "3. **Reconcile contradictions.** When slices disagree:",
+    "   - Prefer the slice with stronger sources",
+    "   - Flag unresolved contradictions in the verification report",
+    "   - Do not silently pick a side",
+    "",
+    "4. **Write the deliverable** to",
+    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.md`. The structure is dictated",
+    "   by the acceptance criteria in the scope file. Every factual claim",
+    "   in the deliverable must cite at least one slice note.",
+    "",
+    "5. **Write a verification report** to",
+    "   `<DELIVERABLES_DIR>/<RESEARCH_SLUG>.verify.md`:",
+    "",
+    "   ```markdown",
+    "   ---",
+    '   title: "Verification Report: <question>"',
+    "   slug: <RESEARCH_SLUG>",
+    "   date: YYYY-MM-DD",
+    "   parent_issue: <N>",
+    "   slices_read: <count>",
+    "   ---",
+    "",
+    "   # Verification Report: <question>",
+    "",
+    "   ## Acceptance Criteria Coverage",
+    "   - [x] <criterion> \u2014 covered by slice(s) <NN, NN>",
+    "   - [ ] <criterion> \u2014 **not covered**; gap noted in deliverable",
+    "",
+    "   ## Slice Coverage",
+    "   | Slice | Claims | Reused in deliverable | Notes |",
+    "   |-------|--------|-----------------------|-------|",
+    "   | 01 | <count> | <count> | |",
+    "",
+    "   ## Reconciled Contradictions",
+    "   - <short summary of each reconciled contradiction and why>",
+    "",
+    "   ## Unresolved Contradictions",
+    "   - <contradiction the verifier could not resolve>",
+    "",
+    "   ## Gaps",
+    "   - <question the pipeline could not answer>",
+    "   ```",
+    "",
+    "6. **Comment on the scope issue** with a summary linking to the",
+    "   deliverable and verification report.",
+    "",
+    "7. **Commit and push.** Close the verify issue.",
+    "",
+    "---",
+    "",
+    "## Output Boundaries",
+    "",
+    "This agent writes **only** to:",
+    "",
+    "- `<SCOPE_DIR>/` \u2014 scope files (Phase 1)",
+    "- `<SLICES_DIR>/` \u2014 slice notes (Phase 2)",
+    "- `<DELIVERABLES_DIR>/` \u2014 deliverables and verification reports",
+    "  (Phase 3)",
+    "",
+    "The pipeline produces **notes and deliverables only**. It does not",
+    "open downstream `type:requirement`, profile, or comparison issues \u2014",
+    "those are the responsibility of specialized downstream agents (e.g.",
+    "`requirements-analyst`, `meeting-analyst`) that consume the",
+    "deliverables produced here. Keep this boundary clean so the research",
+    "pipeline stays generic.",
+    "",
+    "---",
+    "",
+    "## Rules",
+    "",
+    "- **One phase per session.** Never run two phases back-to-back in a",
+    "  single session.",
+    "- **Persist before closing.** Every phase must write its output file",
+    "  before closing its issue.",
+    "- **Do not expand scope mid-slice.** Overflow goes into the slice's",
+    "  overflow section and is flagged for verify \u2014 not into another",
+    "  slice's territory.",
+    "- **Cite everything.** Claims without a source citation do not belong",
+    "  in a slice note or deliverable.",
+    "- **Produce notes, not downstream work.** Do not create",
+    "  `type:requirement`, profile, or comparison issues from this",
+    "  pipeline. Emit deliverables under `<DELIVERABLES_DIR>/` and let",
+    "  downstream agents decide what to do with them."
+  ].join("\n")
+};
+var researchSkill = {
+  name: "research",
+  description: "Kick off a generic research micro-task pipeline. Creates a research:scope issue and dispatches Phase 1 (Scope) in the research-analyst agent.",
+  disableModelInvocation: true,
+  userInvocable: true,
+  context: "fork",
+  agent: "research-analyst",
+  platforms: { cursor: { exclude: true } },
+  instructions: [
+    "# Research",
+    "",
+    "Kick off a generic research micro-task pipeline. Creates a",
+    "`research:scope` issue carrying the research question and dispatches",
+    "Phase 1 (Scope) in the research-analyst agent.",
+    "",
+    "## Usage",
+    "",
+    "/research <question>",
+    "",
+    "Optional extensions in the question body:",
+    "- `sources: <list>` \u2014 authorized source categories or file paths",
+    "- `slices: <N>` \u2014 override the default slice count (default 4, max 8)",
+    "- `slug: <kebab-case>` \u2014 override the derived research slug",
+    "- `acceptance: <list>` \u2014 explicit acceptance criteria for the",
+    "  deliverable",
+    "",
+    "## Default Paths",
+    "",
+    "If the project has no override in `docs/project-context.md` or",
+    "`agentConfig.rules`, outputs land under:",
+    "",
+    "- `docs/research/scopes/<slug>.scope.md`",
+    "- `docs/research/slices/<slug>-NN-<slice-slug>.slice.md`",
+    "- `docs/research/deliverables/<slug>.md`",
+    "- `docs/research/deliverables/<slug>.verify.md`",
+    "",
+    "## Steps",
+    "",
+    "1. Create a `research:scope` issue with `type:research`,",
+    "   `priority:medium`, and `status:ready`. Body must include the",
+    "   verbatim question, authorized sources, and any overrides.",
+    "2. Execute Phase 1 (Scope) of the research-analyst agent.",
+    "3. Phase 1 creates `research:slice` issues (one per slice) and a",
+    "   single `research:verify` issue. Each downstream issue declares",
+    "   its `Depends on:` predecessor.",
+    "",
+    "## Output",
+    "",
+    "- A scope file under the project's research scope directory",
+    "- One slice note per slice under the slices directory",
+    "- A single deliverable plus verification report under the deliverables",
+    "  directory",
+    "- This pipeline produces **notes and deliverables only** \u2014 it does",
+    "  not open downstream `type:requirement` or profile issues."
+  ].join("\n")
+};
+var researchPipelineBundle = {
+  name: "research-pipeline",
+  description: "Generic research micro-task pipeline: scope, N-way slice search/synthesize, and verify. Opt-in only; domain-neutral; filesystem-durable between phases.",
+  appliesWhen: () => false,
+  rules: [
+    {
+      name: "research-pipeline-workflow",
+      description: "Describes the 3-phase generic research pipeline, the research:* label taxonomy, and the boundary against downstream specialized agents.",
+      scope: AGENT_RULE_SCOPE.ALWAYS,
+      content: [
+        "# Research Pipeline Workflow",
+        "",
+        "Use `/research <question>` to kick off a generic research",
+        "micro-task pipeline. The pipeline runs in 3 phases \u2014 scope, slice,",
+        "verify \u2014 each tracked by its own GitHub issue labeled",
+        "`research:scope`, `research:slice`, or `research:verify`. All",
+        "issues carry `type:research`.",
+        "",
+        "The pipeline produces **notes and deliverables only**. It does",
+        "not open downstream `type:requirement` or profile issues \u2014 those",
+        "belong to specialized downstream agents that consume the",
+        "deliverables.",
+        "",
+        "See the `research-analyst` agent definition for full workflow",
+        "details, default paths, and phase-by-phase instructions."
+      ].join("\n"),
+      platforms: {
+        cursor: { exclude: true }
+      },
+      tags: ["workflow"]
+    }
+  ],
+  skills: [researchSkill],
+  subAgents: [researchAnalystSubAgent],
+  labels: [
+    {
+      name: "type:research",
+      color: "5319E7",
+      description: "Work that produces or consumes a research note, slice, or deliverable"
+    },
+    {
+      name: "research:scope",
+      color: "C5DEF5",
+      description: "Phase 1: decompose a research question into N focused slice issues"
+    },
+    {
+      name: "research:slice",
+      color: "BFDADC",
+      description: "Phase 2: execute one research slice \u2014 search authorized sources and write a slice note"
+    },
+    {
+      name: "research:verify",
+      color: "D4C5F9",
+      description: "Phase 3: reconcile slice notes into a verified deliverable"
+    }
+  ]
+};
+
 // src/agent/bundles/slack.ts
 var slackBundle = {
   name: "slack",
@@ -4052,7 +4620,8 @@ var BUILT_IN_BUNDLES = [
   meetingAnalysisBundle,
   orchestratorBundle,
   prReviewBundle,
-  requirementsAnalystBundle
+  requirementsAnalystBundle,
+  researchPipelineBundle
 ];
 
 // src/agent/bundles/scope.ts
@@ -7581,6 +8150,7 @@ var TypeScriptConfig = class extends import_projen22.Component {
   prReviewBundle,
   projenBundle,
   requirementsAnalystBundle,
+  researchPipelineBundle,
   resolveModelAlias,
   resolveTemplateVariables,
   slackBundle,