@codedrifters/configulator 0.0.215 → 0.0.216

package/lib/index.d.mts

@@ -1051,8 +1051,10 @@ declare const bcmWriterBundle: AgentRuleBundle;
  *
  * Consuming projects can disable it with
  * `excludeBundles: ["company-profile"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * `true` per the operating-system directive that bundles assume peers
+ * are present — in Phase 3 this bundle hands work off to
+ * `people-profile` (via `people:research`) and `software-profile` (via
+ * `software:research`).
  *
  * Ships a sub-agent (`company-profile-analyst`), a user-invocable skill
  * (`/profile-company`), and `type:company-profile` plus `company:*`

package/lib/index.d.ts

@@ -1100,8 +1100,10 @@ declare const bcmWriterBundle: AgentRuleBundle;
  *
  * Consuming projects can disable it with
  * `excludeBundles: ["company-profile"]`. `appliesWhen` always returns
- * `true` per this batch's directive that bundles assume peers are
- * present.
+ * `true` per the operating-system directive that bundles assume peers
+ * are present — in Phase 3 this bundle hands work off to
+ * `people-profile` (via `people:research`) and `software-profile` (via
+ * `software:research`).
  *
  * Ships a sub-agent (`company-profile-analyst`), a user-invocable skill
  * (`/profile-company`), and `type:company-profile` plus `company:*`

package/lib/index.js

@@ -1704,7 +1704,7 @@ var bcmWriterBundle = {
 // src/agent/bundles/company-profile.ts
 var companyProfileAnalystSubAgent = {
   name: "company-profile-analyst",
-  description: "Researches an external company (competitor, vendor, partner, customer, etc.) from public sources and produces a structured markdown profile. Optionally enqueues follow-up people and software research tasks. One company per session, tracked by company:* GitHub issue labels.",
+  description: "Researches an external company (competitor, vendor, partner, customer, etc.) from public sources and produces a structured markdown profile, then enqueues downstream `people:research` and `software:research` issues for notable people and software products surfaced during profiling. One company per session, tracked by company:* GitHub issue labels.",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 80,
   platforms: { cursor: { exclude: true } },
@@ -1747,7 +1747,10 @@ var companyProfileAnalystSubAgent = {
     "6. **Follow-up, don't widen scope.** If the session turns up adjacent",
     "   research questions (a key person worth profiling, a product worth",
     "   evaluating), emit a follow-up issue rather than expanding the",
-    "   profile beyond its scope.",
+    "   profile beyond its scope. Notable people are handed off to the",
+    "   `people-profile` bundle via `people:research` issues; software",
+    "   products are handed off to the `software-profile` bundle via",
+    "   `software:research` issues.",
     "",
     "---",
     "",
@@ -1818,6 +1821,8 @@ var companyProfileAnalystSubAgent = {
     "| `<PROFILES_DIR>` | Final company profile files | `<COMPANY_ROOT>/profiles/` |",
     "| `<NOTES_DIR>` | Research-notes files from Phase 1 | `<COMPANY_ROOT>/notes/` |",
     "| `<COMPANY_SLUG>` | Short kebab-case slug identifying the company | derived from the company name |",
+    "| `<PEOPLE_PROFILES_DIR>` | Where existing people profiles live (for duplicate detection during followup) | `docs/people/profiles/` |",
+    "| `<SOFTWARE_PROFILES_DIR>` | Where existing software profiles live (for duplicate detection during followup) | `docs/software/profiles/` |",
     "",
     "If `docs/project-context.md` specifies a different company-research",
     "tree (for example by reusing the research-pipeline deliverables",
@@ -1999,30 +2004,91 @@ var companyProfileAnalystSubAgent = {
     "## Phase 3: Followup (`company:followup`)",
     "",
     "**Goal:** Create downstream research issues for the people and",
-    "products surfaced in the profile.",
+    "software products surfaced in the profile. Hand the candidates off to",
+    "the `people-profile` and `software-profile` bundles so they can be",
+    "researched independently.",
     "",
     "**Budget:** No new research. Read the profile, enqueue issues, close",
-    "the phase.",
+    "the phase. Markdown cross-references in the profile's",
+    "`## Follow-up Candidates` section are preserved \u2014 issue creation is",
+    "**additive** on top of the existing notes-only behavior.",
     "",
     "### Steps",
     "",
     "1. **Read the profile file** referenced in the issue body.",
     "",
-    "2. **Enqueue people-profile issues** for each entry under",
-    "   `Follow-up Candidates > People to profile`. Use the consuming",
-    "   project's people-research pipeline if one exists; otherwise, open",
-    "   a generic `type:research` issue describing what to learn about the",
-    "   person and linking back to the company profile.",
-    "",
-    "3. **Enqueue software-evaluation issues** for each entry under",
-    "   `Follow-up Candidates > Products / software to evaluate`. Again,",
-    "   use a project-specific pipeline if configured, otherwise a generic",
-    "   `type:research` issue.",
-    "",
-    "4. **Cross-link** \u2014 update the profile's `## Follow-up Candidates`",
-    "   section so each entry references its newly-created issue number.",
-    "",
-    "5. **Commit and push** (if the profile was updated). Close the",
+    "2. **Enqueue a `people:research` issue per candidate** under",
+    "   `Follow-up Candidates > People to profile` that is worth",
+    "   downstream research. Each issue must carry:",
+    "",
+    "   - `type:people-profile`",
+    "   - `people:research`",
+    "   - `priority:medium`",
+    "   - `status:ready`",
+    "",
+    "   The issue body must include:",
+    "   - A **discovery source** line naming this company profile",
+    "     (`Discovered while profiling: <company name>`)",
+    "   - A link to the company profile path (`Company profile: <PROFILES_DIR>/<COMPANY_SLUG>.md`)",
+    "   - Enough identifying metadata \u2014 full name, role/title, and",
+    "     employing company \u2014 that the `people-profile-analyst` agent can",
+    "     begin research without revisiting this company profile",
+    "",
+    "3. **Enqueue a `software:research` issue per candidate** under",
+    "   `Follow-up Candidates > Products / software to evaluate` that is",
+    "   worth downstream research. Each issue must carry:",
+    "",
+    "   - `type:software-profile`",
+    "   - `software:research`",
+    "   - `priority:medium`",
+    "   - `status:ready`",
+    "",
+    "   The issue body must include:",
+    "   - A **discovery source** line naming this company profile",
+    "     (`Discovered while profiling: <company name>`)",
+    "   - A link to the company profile path (`Company profile: <PROFILES_DIR>/<COMPANY_SLUG>.md`)",
+    "   - Enough identifying metadata \u2014 product name and vendor (usually",
+    "     this company if it builds the product, otherwise the upstream",
+    "     vendor) \u2014 that the `software-profile-analyst` agent can begin",
+    "     research without revisiting this company profile",
+    "",
+    "4. **Avoid duplicates.** Before opening a `people:research` or",
+    "   `software:research` issue, verify no existing profile covers the",
+    "   candidate:",
+    "",
+    "   - People: check `<PEOPLE_PROFILES_DIR>/` for a matching profile",
+    "     file (by derived slug or by searching the directory for the",
+    "     person's name). If a profile exists, reuse it as a cross-reference",
+    "     only \u2014 **do not** open a new `people:research` issue.",
+    "   - Software: check `<SOFTWARE_PROFILES_DIR>/` the same way. If a",
+    "     profile exists, reuse it as a cross-reference only \u2014 **do not**",
+    "     open a new `software:research` issue.",
+    "   - Also scan open issues carrying the matching `people:research` or",
+    "     `software:research` label so this phase never re-opens research",
+    "     that is already queued.",
+    "",
+    "5. **Exercise restraint.** Only create downstream issues for people",
+    "   and software products that are **genuinely relevant** to the",
+    "   framing of this profile \u2014 executives, founders, and decision-makers",
+    "   for people; products the company builds or materially depends on",
+    "   for software. Do **not** open issues for every name mentioned in",
+    "   passing, every SaaS tool listed in a job ad, or every tangential",
+    "   partner. When in doubt, leave the candidate as a markdown",
+    "   cross-reference in the profile and skip the downstream issue.",
+    "",
+    "6. **Assume the peers are present.** This pipeline assumes the",
+    "   `people-profile` and `software-profile` bundles are enabled in the",
+    "   consuming project. If a consuming project has disabled one of",
+    "   them, flag the followup issue with `status:needs-attention` and",
+    "   list the candidates that could not be routed \u2014 never invent an",
+    "   alternative label taxonomy.",
+    "",
+    "7. **Cross-link** \u2014 update the profile's `## Follow-up Candidates`",
+    "   section so each entry references its newly-created issue number",
+    "   (or the existing profile path, for candidates that were skipped",
+    "   because a profile already exists).",
+    "",
+    "8. **Commit and push** (if the profile was updated). Close the",
     "   followup issue.",
     "",
     "---",
@@ -2034,9 +2100,17 @@ var companyProfileAnalystSubAgent = {
     "- `<NOTES_DIR>/` \u2014 research-notes files (Phase 1)",
     "- `<PROFILES_DIR>/` \u2014 company profiles (Phase 2, updated in Phase 3)",
     "",
-    "The pipeline produces **profiles and notes only**. Deeper research on",
-    "people or products is delegated to downstream research pipelines via",
-    "follow-up issues \u2014 this agent never writes person profiles, product",
+    "In Phase 3, this agent also **creates `people:research` and",
+    "`software:research` issues** for people and software products",
+    "surfaced in the profile. It never writes the downstream profiles",
+    "themselves \u2014 those are the responsibility of the",
+    "`people-profile-analyst` and `software-profile-analyst` agents, which",
+    "pick up the issues this pipeline creates.",
+    "",
+    "The pipeline produces **company profiles and notes only**. Deeper",
+    "research on people or products is delegated to downstream research",
+    "pipelines via `people:research` and `software:research` issues \u2014 this",
+    "agent never writes person profiles, software profiles, product",
     "evaluations, or comparative analyses itself. Keep this boundary clean",
     "so the company-profile pipeline stays generic.",
     "",
@@ -2052,10 +2126,23 @@ var companyProfileAnalystSubAgent = {
     "- **No assumed competition.** Never call a company a competitor unless",
     "  the invoking issue body or the consuming project's configuration",
     "  says so.",
-    "- **Produce profiles, not downstream work.** Do not open",
-    "  `type:requirement` or formal evaluation issues from this pipeline.",
-    "  Follow-up work is scoped through `company:followup` or delegated to",
-    "  downstream research agents."
+    "- **Delegate, don't duplicate.** People and software products",
+    "  surfaced during profiling are handed off to the `people-profile`",
+    "  and `software-profile` bundles via `people:research` and",
+    "  `software:research` issues in Phase 3 \u2014 never inlined as person or",
+    "  software profiles in this pipeline.",
+    "- **Check before enqueueing.** Before opening a `people:research` or",
+    "  `software:research` issue, verify no existing profile or open",
+    "  research issue already covers the candidate. Reuse existing",
+    "  profiles as cross-references rather than re-queuing research.",
+    "- **Restrain the queue.** Only enqueue downstream research for people",
+    "  and products that are genuinely relevant to the framing of this",
+    "  profile. Do not open issues for every name or product mentioned in",
+    "  passing.",
+    "- **Produce profiles, not requirement or evaluation documents.** Do",
+    "  not open `type:requirement` or formal evaluation issues from this",
+    "  pipeline. Follow-up research is scoped through `people:research`",
+    "  and `software:research` only."
   ].join("\n")
 };
 var profileCompanySkill = {
@@ -2107,15 +2194,18 @@ var profileCompanySkill = {
     "",
     "- A research-notes file under the project's notes directory",
     "- A single company profile under the profiles directory",
-    "- Optional follow-up research issues for key people and products",
-    "  surfaced in the profile",
-    "- This pipeline produces **profiles only** \u2014 it does not write person",
-    "  profiles, product evaluations, or comparative analyses itself."
+    "- `people:research` issues for notable people surfaced in the profile",
+    "  (handed off to the `people-profile` bundle)",
+    "- `software:research` issues for software products surfaced in the",
+    "  profile (handed off to the `software-profile` bundle)",
+    "- This pipeline produces **company profiles only** \u2014 it does not",
+    "  write person profiles, software profiles, product evaluations, or",
+    "  comparative analyses itself."
   ].join("\n")
 };
 var companyProfileBundle = {
   name: "company-profile",
-  description: "Company research and profiling pipeline: research, draft profile, followup. Enabled by default; domain-neutral; filesystem-durable between phases.",
+  description: "Company research and profiling pipeline: research, draft profile, followup. Enabled by default; domain-neutral; filesystem-durable between phases. Phase 3 (Followup) hands surfaced people and software products off to the `people-profile` and `software-profile` bundles via `people:research` and `software:research` issues.",
   appliesWhen: () => true,
   rules: [
     {
@@ -2132,8 +2222,10 @@ var companyProfileBundle = {
         "`company:followup`. All issues carry `type:company-profile`.",
         "",
         "The pipeline produces **company profiles only**. Deeper research",
-        "on people or products surfaced in a profile is delegated to",
-        "downstream research pipelines via `company:followup` issues.",
+        "on notable people and software products surfaced while profiling",
+        "is delegated to the `people-profile` and `software-profile`",
+        "bundles via `people:research` and `software:research` issues",
+        "opened during Phase 3 (Followup).",
         "",
         "See the `company-profile-analyst` agent definition for full",
         "workflow details, default paths, the company-type taxonomy, and",