@synap-core/workspace-templates 0.6.1 → 0.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "type": "module",
   "packageManager": "pnpm@9.15.4",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",

package/src/builder.yaml

@@ -1258,6 +1258,27 @@ entityLinks:
     type: depends_on
     label: Depends on
 
+# Playbooks — session templates seeded with the workspace.
+# `subjectProfile` binds this playbook to the `devplane_feature` kind so the
+# Capture → Session matcher (playbooks.subject_profile->>'profileSlug') can offer
+# it when a feature/idea is captured. The captured feature is passed as the
+# `feature` entity param and substituted into the goalTemplate.
+playbooks:
+  - name: Evaluate Feature
+    description: Assess a feature — its current state, whether it's worth building, and how it fits the rest of the system.
+    goalTemplate: >-
+      Evaluate this feature ({feature}): where it stands today (its status,
+      progress, and any blockers), whether it is actually useful (the problem it
+      solves and for whom), and how it integrates with the existing apps,
+      packages, services, and environments in this workspace. Finish with a clear
+      recommendation — continue, cut, or reshape — and the reasoning behind it.
+    subjectProfile:
+      profileSlug: devplane_feature
+    params:
+      - { name: feature, type: entity, label: Feature, required: true }
+    executor: is-agent
+    status: active
+
 onboarding:
   goal: Capture the real engineering surface — the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight — so the workspace mirrors what the team actually builds and runs, not a generic template.
   framing: >

package/src/content-os.yaml

@@ -473,6 +473,28 @@ entityLinks:
     type: sponsored_by
     label: Sponsor
 
+# Playbooks — session templates seeded with the workspace.
+# `subjectProfile` binds this playbook to the `post` kind so the Capture → Session
+# matcher (playbooks.subject_profile->>'profileSlug') can offer it when a post is
+# captured. The captured post is passed as the `post` entity param and substituted
+# into the goalTemplate; the agent carries it from raw idea to a scheduled draft.
+playbooks:
+  - name: Produce Content
+    description: Take a captured post idea and carry it from spark to a scheduled, platform-ready draft.
+    goalTemplate: >-
+      Produce content for {platform} from this idea ({post}). Take the raw idea,
+      shape it into a {format} draft with a scroll-stopping hook and a clear CTA,
+      keep it aligned to the post's pillar and the operator's brand voice, then
+      move it to Scheduled with a publish date.
+    subjectProfile:
+      profileSlug: post
+    params:
+      - { name: post, type: entity, label: Post, required: true }
+      - { name: platform, type: text, label: Platform, required: true }
+      - { name: format, type: text, label: Format }
+    executor: is-agent
+    status: active
+
 onboarding:
   goal: >
     Stand up the editorial engine — the pillars you're known for, the platforms

package/src/ecosystem.yaml

@@ -368,6 +368,35 @@ entityLinks:
     type: involves
     label: Involves
 
+# Playbooks — session templates seeded with the workspace.
+# Ported from the orphaned `deep-research.playbook.json` (CP templates/packs):
+# same goalTemplate + companyContext param + is-agent executor + Web-Search /
+# Entity-Creator grants + typed outputs (encoded via the {outputTypes} param).
+# `subjectProfile` binds it to the shared `competitor` role so the Capture →
+# Session matcher can offer it when a competitor is captured; the captured
+# competitor is passed as the `competitor` entity param.
+playbooks:
+  - name: Research Competitor
+    description: Deep-research a competitor and position it against us — strengths, weaknesses, pricing, and the gaps we can exploit.
+    goalTemplate: >-
+      Research this competitor ({competitor}) and compare them to us. Investigate
+      their {focus}: positioning, strengths, weaknesses, pricing, and recent
+      moves. Use the provided company context where relevant: {companyContext}.
+      Produce: {outputTypes}. Update the competitor entity with what you find and
+      make clear where we win and where we are exposed.
+    subjectProfile:
+      profileSlug: competitor
+    params:
+      - { name: competitor, type: entity, label: Competitor, required: true }
+      - { name: focus, type: text, label: Focus area, defaultValue: "product, pricing, and positioning" }
+      - { name: companyContext, type: text, label: Our company context }
+      - { name: outputTypes, type: text, label: Outputs, defaultValue: "a head-to-head comparison summary and an updated competitor profile" }
+    executor: is-agent
+    grants:
+      - Web Search
+      - Entity Creator
+    status: active
+
 onboarding:
   goal: >
     Map the real ecosystem — the key players (companies and people), who partners

package/src/enterprise-os.yaml

@@ -10,6 +10,7 @@
 #   • ecosystem  — the market graph (partners, competitors, segments, trends)
 #   • operations — how the company runs (the operational lens)
 #   • crm        — the pipeline (contacts, leads, clients, deals)
+#   • content-os — the editorial engine (pillars, posts, platforms, newsletters)
 #
 # It uses `require` (not `compose`): each constituent is a REAL workspace, not an
 # overlay. Deps-first resolution installs foundation first (the SSOT role
@@ -46,6 +47,10 @@ dependencies:
     kind: workspace
     relation: require
     reason: "The pipeline — contacts, leads, clients, and deals."
+  - slug: content-os
+    kind: workspace
+    relation: require
+    reason: "The editorial engine — pillars, posts, platforms, and newsletters — so the company's content operation is part of the operating core."
 
 workspace:
   name: Enterprise OS

package/src/templates.ts

@@ -6514,6 +6514,26 @@ const DATA = {
         "label": "Depends on"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Evaluate Feature",
+        "description": "Assess a feature — its current state, whether it's worth building, and how it fits the rest of the system.",
+        "goalTemplate": "Evaluate this feature ({feature}): where it stands today (its status, progress, and any blockers), whether it is actually useful (the problem it solves and for whom), and how it integrates with the existing apps, packages, services, and environments in this workspace. Finish with a clear recommendation — continue, cut, or reshape — and the reasoning behind it.",
+        "subjectProfile": {
+          "profileSlug": "devplane_feature"
+        },
+        "params": [
+          {
+            "name": "feature",
+            "type": "entity",
+            "label": "Feature",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
+    ],
     "onboarding": {
       "goal": "Capture the real engineering surface — the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight — so the workspace mirrors what the team actually builds and runs, not a generic template.",
       "framing": "THE STAFF ENGINEER: Act as a pragmatic, precise staff/platform engineer standing up a developer command center. Tease out what's actually shipped vs. planned, where the code lives (repos + local paths), what runs behind each app, where it deploys, and what's on the bench right now. Prefer concrete over aspirational — a repo URL beats a wish. Tie the roadmap back to the Foundation's mission and audiences: the surface exists to serve them.\n",
@@ -8558,6 +8578,37 @@ const DATA = {
         "label": "Sponsor"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Produce Content",
+        "description": "Take a captured post idea and carry it from spark to a scheduled, platform-ready draft.",
+        "goalTemplate": "Produce content for {platform} from this idea ({post}). Take the raw idea, shape it into a {format} draft with a scroll-stopping hook and a clear CTA, keep it aligned to the post's pillar and the operator's brand voice, then move it to Scheduled with a publish date.",
+        "subjectProfile": {
+          "profileSlug": "post"
+        },
+        "params": [
+          {
+            "name": "post",
+            "type": "entity",
+            "label": "Post",
+            "required": true
+          },
+          {
+            "name": "platform",
+            "type": "text",
+            "label": "Platform",
+            "required": true
+          },
+          {
+            "name": "format",
+            "type": "text",
+            "label": "Format"
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
+    ],
     "onboarding": {
       "goal": "Stand up the editorial engine — the pillars you're known for, the platforms you publish on, the cadence you can actually sustain, and a first post placed in the system — so the workspace mirrors how you turn thinking into published content, not a blank calendar.\n",
       "framing": "THE EDITOR-IN-CHIEF: Act as a seasoned content strategist who has grown owned audiences from zero. Anchor everything on PILLARS — the two-to-four recurring themes an audience comes to you for — because pillars are what make a content engine compound instead of drift. Pull voice and identity from Brand and the target audience from Foundation so every piece lands on-strategy. Push for a cadence they can hold for a year, not a heroic month. Be concrete: real platforms, real formats, a real first post — a fuzzy \"I'll post more\" helps no one.\n",
@@ -11925,6 +11976,47 @@ const DATA = {
         "label": "Involves"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Research Competitor",
+        "description": "Deep-research a competitor and position it against us — strengths, weaknesses, pricing, and the gaps we can exploit.",
+        "goalTemplate": "Research this competitor ({competitor}) and compare them to us. Investigate their {focus}: positioning, strengths, weaknesses, pricing, and recent moves. Use the provided company context where relevant: {companyContext}. Produce: {outputTypes}. Update the competitor entity with what you find and make clear where we win and where we are exposed.",
+        "subjectProfile": {
+          "profileSlug": "competitor"
+        },
+        "params": [
+          {
+            "name": "competitor",
+            "type": "entity",
+            "label": "Competitor",
+            "required": true
+          },
+          {
+            "name": "focus",
+            "type": "text",
+            "label": "Focus area",
+            "defaultValue": "product, pricing, and positioning"
+          },
+          {
+            "name": "companyContext",
+            "type": "text",
+            "label": "Our company context"
+          },
+          {
+            "name": "outputTypes",
+            "type": "text",
+            "label": "Outputs",
+            "defaultValue": "a head-to-head comparison summary and an updated competitor profile"
+          }
+        ],
+        "executor": "is-agent",
+        "grants": [
+          "Web Search",
+          "Entity Creator"
+        ],
+        "status": "active"
+      }
+    ],
     "onboarding": {
       "goal": "Map the real ecosystem — the key players (companies and people), who partners and competes with whom, and the segments and trends that matter — so strategy is grounded in the actual market, not a vague \"the market\".\n",
       "framing": "THE ECOSYSTEM LEAD: Act as a sharp ecosystem lead who maps the market\nlandscape AND the relationships inside it. Push for REAL named players — not\n\"the incumbents\", but the actual companies — and for the concrete edges\nbetween them: who partners with whom, who competes, who invested in whom.\nA map with no edges is just a list; the value is in the relationships.\n",
@@ -12099,6 +12191,12 @@ const DATA = {
         "kind": "workspace",
         "relation": "require",
         "reason": "The pipeline — contacts, leads, clients, and deals."
+      },
+      {
+        "slug": "content-os",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "The editorial engine — pillars, posts, platforms, and newsletters — so the company's content operation is part of the operating core."
       }
     ],
     "workspace": {

package/src/types.ts

@@ -299,6 +299,13 @@ export interface TemplatePlaybook {
   schedule?: { cron: string } | null;
   /** tool/skill keys this playbook grants. */
   grants?: string[];
+  /**
+   * The entity kind this playbook operates over, persisted to
+   * `playbooks.subject_profile`. Makes the playbook matchable by
+   * `playbooks.matchForEntity` (filters `subject_profile->>'profileSlug'`), so a
+   * captured entity of this kind can auto-launch the playbook as a session.
+   */
+  subjectProfile?: { profileSlug: string; filter?: Record<string, unknown> };
   status?: 'draft' | 'active' | 'paused';
 }