@synap-core/workspace-templates 0.6.1 → 0.6.2

package/dist/index.d.ts

@@ -238,6 +238,16 @@ interface TemplatePlaybook {
     } | 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';
 }
 interface TemplateIntegration {

package/dist/index.js

@@ -6518,6 +6518,26 @@ var DATA = {
         "label": "Depends on"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Evaluate Feature",
+        "description": "Assess a feature \u2014 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 \u2014 continue, cut, or reshape \u2014 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 \u2014 the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight \u2014 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 \u2014 a repo URL beats a wish. Tie the roadmap back to the Foundation's mission and audiences: the surface exists to serve them.\n",
@@ -8571,6 +8591,37 @@ var 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 \u2014 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 \u2014 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 \u2014 the two-to-four recurring themes an audience comes to you for \u2014 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 \u2014 a fuzzy "I'll post more" helps no one.
@@ -11941,6 +11992,47 @@ var DATA = {
         "label": "Involves"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Research Competitor",
+        "description": "Deep-research a competitor and position it against us \u2014 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 \u2014 the key players (companies and people), who partners and competes with whom, and the segments and trends that matter \u2014 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 \u2014 not\n"the incumbents", but the actual companies \u2014 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',
@@ -12116,6 +12208,12 @@ var DATA = {
         "kind": "workspace",
         "relation": "require",
         "reason": "The pipeline \u2014 contacts, leads, clients, and deals."
+      },
+      {
+        "slug": "content-os",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "The editorial engine \u2014 pillars, posts, platforms, and newsletters \u2014 so the company's content operation is part of the operating core."
       }
     ],
     "workspace": {