@synap-core/workspace-templates 0.6.1 → 0.6.3

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",
@@ -8452,6 +8472,16 @@ const DATA = {
         "groupBy": "post-status",
         "description": "Content posts by status."
       },
+      {
+        "name": "Content Calendar",
+        "slug": "content-calendar",
+        "type": "calendar",
+        "scopeProfileSlug": "post",
+        "description": "Your editorial calendar — every post on the day it publishes.",
+        "config": {
+          "dateField": "properties.publish-date"
+        }
+      },
       {
         "name": "Pillars",
         "slug": "content-pillars",
@@ -8493,6 +8523,12 @@ const DATA = {
           "label": "Posts",
           "icon": "file-edit"
         },
+        {
+          "kind": "view",
+          "viewName": "Content Calendar",
+          "label": "Calendar",
+          "icon": "calendar"
+        },
         {
           "kind": "view",
           "viewName": "Pillars",
@@ -8518,10 +8554,20 @@ const DATA = {
       "blocks": [
         {
           "kind": "view",
-          "viewName": "Pillars",
+          "viewName": "Content Calendar",
           "pos": {
             "x": 0,
             "y": 0,
+            "w": 12,
+            "h": 6
+          }
+        },
+        {
+          "kind": "view",
+          "viewName": "Pillars",
+          "pos": {
+            "x": 0,
+            "y": 6,
             "w": 6,
             "h": 5
           }
@@ -8531,7 +8577,7 @@ const DATA = {
           "viewName": "Newsletters",
           "pos": {
             "x": 6,
-            "y": 0,
+            "y": 6,
             "w": 6,
             "h": 5
           }
@@ -8558,6 +8604,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",
@@ -9678,6 +9755,62 @@ const DATA = {
         "targetProfileSlug": "deal",
         "type": "linked_to_deal"
       }
+    ],
+    "playbooks": [
+      {
+        "name": "Enrich this lead",
+        "description": "Take a thin, freshly-captured lead and fill it out — company, title, LinkedIn, and the relationships around it.",
+        "goalTemplate": "Enrich this lead ({lead}). Starting from whatever is known, fill out the missing detail — company, job title, LinkedIn URL, location, and the people and companies around them — and record it on the lead. Draw on whatever enrichment capability this workspace has connected (e.g. an Apify or Unipile/LinkedIn tool); if none is available, enrich from the public web and what is already in the pod. Link the lead to its company and any related contacts, and note where information is still missing.",
+        "subjectProfile": {
+          "profileSlug": "lead"
+        },
+        "params": [
+          {
+            "name": "lead",
+            "type": "entity",
+            "label": "Lead",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      },
+      {
+        "name": "Qualify this lead",
+        "description": "Assess a lead against the ICP, score the fit, and decide the next step — advance, nurture, or disqualify.",
+        "goalTemplate": "Qualify this lead ({lead}). Assess how well they fit our ideal customer profile — company, role, industry, size, and the signals of intent or need — and set an ICP score. Decide the next step: advance them toward a deal, keep nurturing, or disqualify. Write the reasoning and the decision back onto the lead (its stage, score, and next step) so the call is auditable.",
+        "subjectProfile": {
+          "profileSlug": "lead"
+        },
+        "params": [
+          {
+            "name": "lead",
+            "type": "entity",
+            "label": "Lead",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      },
+      {
+        "name": "Work this deal",
+        "description": "Move a deal toward Won — read the current stage, find the blocker, and propose the next step and owner.",
+        "goalTemplate": "Work this deal ({deal}) toward Won. Assess where it stands — its current stage, value, and close date — and identify the single thing blocking it from advancing. Propose the concrete next step, who owns it, and by when, and update the deal's next step accordingly. If the stage should change, say so and why.",
+        "subjectProfile": {
+          "profileSlug": "deal"
+        },
+        "params": [
+          {
+            "name": "deal",
+            "type": "entity",
+            "label": "Deal",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "status": "active"
+      }
     ]
   },
   "dev-dashboard": {
@@ -11925,6 +12058,79 @@ 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",
+        "schedule": {
+          "cron": "0 9 * * 1",
+          "enabled": false
+        },
+        "grants": [
+          "Web Search",
+          "Entity Creator"
+        ],
+        "status": "active"
+      },
+      {
+        "name": "Discover Competitors",
+        "description": "Scan the market for competitors we don't track yet and add them to the ecosystem — the self-generating half of the radar.",
+        "goalTemplate": "Find companies that compete with us in {ourSpace}. Use neural web search (the exa_search skill with category \"company\") to surface real, named companies — direct competitors, adjacent tools that solve the same job a different way, and emerging players. For each genuinely NEW one (not already a competitor in our ecosystem), propose it as a `competitor` entity and ALWAYS include its `website` (its canonical URL) so it de-duplicates against what we already track — never create a company that already exists. Skip anything already known. Report what you added and why each one matters.",
+        "schedule": {
+          "cron": "0 9 * * 1",
+          "enabled": false
+        },
+        "params": [
+          {
+            "name": "ourSpace",
+            "type": "text",
+            "label": "Our market / category",
+            "required": true
+          }
+        ],
+        "executor": "is-agent",
+        "grants": [
+          "exa_search",
+          "Entity Creator"
+        ],
+        "status": "active"
+      }
+    ],
+    "integrations": [
+      {
+        "templateKey": "exa"
+      }
+    ],
     "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 +12305,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

@@ -176,18 +176,6 @@ export interface TemplateProfileEntityBentoTemplates {
   };
 }
 
-// ============================================================================
-// Automations
-// ============================================================================
-
-export interface TemplateAutomation {
-  name: string;
-  description?: string;
-  trigger: string;
-  action: string;
-  config?: Record<string, unknown>;
-}
-
 // ============================================================================
 // Cross-workspace source pinning
 // ============================================================================
@@ -299,6 +287,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';
 }
 
@@ -508,9 +503,6 @@ export interface WorkspaceYaml {
   /** Per-profile entity bento layouts */
   profileEntityBentoTemplates?: TemplateProfileEntityBentoTemplates;
 
-  /** Automations to install on workspace creation */
-  automations?: TemplateAutomation[];
-
   /** Playbooks (session templates) seeded with the workspace */
   playbooks?: TemplatePlaybook[];
 
@@ -552,7 +544,6 @@ export interface ResolvedWorkspaceTemplate {
     bentoViewName?: string;
     bentoViewBlocks?: TemplateBentoBlock[];
     profileEntityBentoTemplates?: TemplateProfileEntityBentoTemplates;
-    automations: TemplateAutomation[];
     extends?: TemplateExtendsRef[];
   };
 }