@higrowth/cli 0.3.2 → 0.3.4

package/dist/index.js

@@ -703,7 +703,7 @@ just say which one \u2014 you don't have to redo the whole interview."*
 // src/skills/marketing-strategy.ts
 var MARKETING_STRATEGY = `---
 name: higrowth-marketing-strategy
-description: Helps the user interpret a Higrowth diagnostic, choose a bounded scoped-plan area, and shape the next 2-4 week sprint. Use when the user wants to talk through their report, decide what to ship, ask what can be fixed in an area, or plan.
+description: Helps the user interpret a Higrowth diagnostic, choose a bounded scoped-plan or topic-roadmap area, review imagination hypotheses, and shape the next 2-4 week sprint. Use when the user wants to talk through their report, decide what to ship, ask what can be fixed in an area, create/update content from roadmap gaps, or plan.
 allowed-tools: mcp__higrowth__execute_typescript
 ---
 
@@ -717,7 +717,8 @@ measurable scoped plan that can move the needle.
 
 Trigger on: "what should I focus on", "walk me through my report",
 "prioritize this", "what's the move", "plan my sprint", "what can we
-fix in [area/topic/page]".
+fix in [area/topic/page]", "what are the gaps in this topic", "plan this
+roadmap", "what new pages or updates should we create".
 
 ## Mental model
 
@@ -725,7 +726,27 @@ Plans are not giant backlogs. A good plan is a scoped intervention:
 one topic area, page cluster, gap type, or conversion slice with enough
 evidence to act and narrow enough boundaries to avoid conflicting work.
 
-Rank by **leverage and executability**, not raw opportunity count.
+The planning stack has five layers:
+
+1. **Answer map** \u2014 what questions the site answers for which persona
+   and decision stage.
+2. **Decision candidates** \u2014 executable moves grounded in answer cells,
+   gaps, GSC, GA, strategy, and conflict checks.
+3. **Topic roadmap** \u2014 the topic-area execution ledger: new pages to
+   create, pages to refresh, consolidation/removal, internal links, and
+   measurement/setup rows. When the user asks about a topic's gaps or
+   roadmap, these rows are a first-class planning source.
+4. **Imagination candidates** \u2014 adjacent hypotheses HG can infer from
+   weak or missing answers. They are ideas only.
+5. **Scoped plans** \u2014 a small selected scope that generates execution
+   items from roadmap rows, scoped gaps, pages, answer cells, or decision
+   candidates.
+
+Rank by **leverage, evidence, and executability**, not raw opportunity count.
+Never create work orders directly from imagination candidates. Promote
+good imagination candidates into decision candidates first, then plan.
+Roadmap rows do not need promotion: use them directly when the user's
+intent is to execute a topic roadmap.
 
 ## The conversation
 
@@ -745,41 +766,259 @@ Anything missing or recently changed?"*
 Use the answer to steer scope selection. Recent launches, product
 changes, seasonality, and sales priorities should shape what you plan.
 
-### Step 2 \u2014 Choose a bounded area
+### Step 2 \u2014 Resolve the topic or area
 
 If the user named an area, use it as the scope query. If not, help them
 pick one from the diagnostic: a pillar, subtopic, page cluster, gap type,
 or conversion issue.
 
+Find the most likely topic/pillar id before generating plans. Use the
+current API surface available in the MCP harness; if the harness exposes
+topic search, use it. If not, use scoped candidates with the user's query
+and read the returned \`topicId\`.
+
 \`\`\`ts
 const q = userIntent || 'highest leverage scoped fixes';
+const firstPass = await api.get(
+  \`/api/entities/\${entityId}/plan-scopes/candidates?q=\${encodeURIComponent(q)}&limit=8&maxItems=8\`
+);
+const topicId = firstPass.candidates.find(c => c.topicId)?.topicId;
+\`\`\`
+
+### Step 3 \u2014 Check source signal before planning
+
+Do not jump straight to a plan if the answer map and decision registry
+are empty. HG should reason from the rich signal it already gathered.
+
+\`\`\`ts
+const answerSummary = topicId
+  ? await api.get(\`/api/entities/\${entityId}/answer-map/summary?topicId=\${topicId}\`)
+  : null;
+console.log(answerSummary?.summary);
+\`\`\`
+
+If the summary has no cells, compute it:
+
+\`\`\`ts
+if (topicId && (!answerSummary || answerSummary.summary.totalCells === 0)) {
+  await api.post(\`/api/entities/\${entityId}/answer-map/compute\`, {
+    topicId,
+    limit: 500,
+  });
+}
+\`\`\`
+
+Then refresh decision candidates for the topic or page slice:
+
+\`\`\`ts
+await api.post(\`/api/entities/\${entityId}/decision-candidates/refresh\`, {
+  topicId,
+  limit: 500,
+});
+
+const decisions = await api.get(
+  \`/api/entities/\${entityId}/decision-candidates?topicId=\${topicId}&status=candidate&limit=50\`
+);
+console.log(decisions.candidates.slice(0, 10));
+\`\`\`
+
+If answer-map compute still returns little or no signal, say so. The
+right prerequisite may be a scan, GSC/GA connection, KB population, or
+pillar analysis. Do not fabricate a strategic plan from thin data.
+
+Also check the topic roadmap when the user asks about a topic, gaps,
+new content, content updates, or comprehensiveness:
+
+\`\`\`ts
+const roadmap = topicId
+  ? await api.get(\`/api/topics/\${topicId}/roadmap\`)
+  : null;
+const openRoadmapItems =
+  roadmap?.items?.filter(item => item.status === 'open') ?? [];
+
+console.log(openRoadmapItems.map(item => ({
+  id: item.id,
+  actionType: item.actionType,
+  title: item.title,
+  targetPageUrl: item.targetPageUrl,
+  queries: item.queries?.slice(0, 5) ?? [],
+  existingCoverage: item.coverage?.length ?? 0,
+})));
+\`\`\`
+
+Roadmap rows answer: what new pages to create, which pages to update,
+what to consolidate or remove, where internal links are missing, and
+what measurement/setup work blocks confidence. Treat open roadmap rows
+as source evidence, not as loose suggestions.
+
+### Step 4 \u2014 Use imagination only when useful
+
+When the user asks "what else could we do here?", "what are we missing?",
+or the decision registry feels too narrow, generate imagination
+candidates. This is HG's ideation layer: adjacent questions and content
+angles extrapolated from answer-map gaps.
+
+\`\`\`ts
+const imagination = await api.post(
+  \`/api/entities/\${entityId}/imagination-candidates/generate\`,
+  { topicId, limit: 20 }
+);
+console.log(imagination.candidates);
+\`\`\`
+
+Review these critically with the user. Reject weak, duplicate, or noisy
+hypotheses:
+
+\`\`\`ts
+await api.post(\`/api/entities/\${entityId}/imagination-candidates/\${id}/reject\`, {
+  reason: 'Duplicate of an existing page angle',
+});
+\`\`\`
+
+Promote only the best 1-3 ideas. Promotion creates decision candidates;
+it still does not create work orders or plan items.
+
+\`\`\`ts
+const promoted = await api.post(
+  \`/api/entities/\${entityId}/imagination-candidates/\${id}/promote\`
+);
+console.log(promoted.candidate);
+\`\`\`
+
+After promotion, re-run scoped candidates so promoted ideas can compete
+with observed-gap candidates.
+
+### Step 5 \u2014 Choose a bounded scope
+
+If the user explicitly asked to execute a topic roadmap, prefer a
+roadmap-derived scope over a generic candidate. The open roadmap rows
+are the scope thesis.
+
+\`\`\`ts
+function compactRoadmapSourceId(topicId, items) {
+  const key = (items ?? [])
+    .map(item => item.id)
+    .sort()
+    .join('_')
+    .replace(/[^a-zA-Z0-9_-]/g, '')
+    .slice(0, 96) || 'open';
+  return \`roadmap_topic_v6_\${topicId}_\${key}\`;
+}
+
+function analysisTypesFromRoadmap(items) {
+  const types = new Set(['supply_tactical']);
+  for (const item of items ?? []) {
+    if (item.actionType === 'new_content') types.add('demand_pull');
+    if (item.actionType === 'internal_linking') types.add('structural');
+    if (item.actionType === 'page_refresh') types.add('positioning');
+    if (item.actionType === 'measurement') types.add('conversion');
+  }
+  return [...types];
+}
+
+function roadmapScope(topicId, topicName, entityId, openItems) {
+  const analysisTypes = analysisTypesFromRoadmap(openItems);
+  return {
+    version: 1,
+    selectedAt: new Date().toISOString(),
+    selectedBy: 'agent',
+    sourceCandidateId: compactRoadmapSourceId(topicId, openItems),
+    entityId,
+    label: \`\${topicName ?? 'Topic'} roadmap execution scope\`,
+    scopeType: 'subtopic',
+    topicId,
+    subtopicIds: [],
+    pageIds: [],
+    gapIds: [],
+    answerCellIds: [],
+    decisionCandidateIds: [],
+    primaryPersonaIds: [],
+    decisionStages: [],
+    scopeThesis: [
+      \`Use the \${topicName ?? 'selected topic'} roadmap as the execution source of truth.\`,
+      ...openItems.slice(0, 8).map((item, index) =>
+        [
+          \`\${index + 1}. \${item.title}\`,
+          \`Action: \${item.actionType} (\${item.priority} priority).\`,
+          item.recommendedAction ? \`Recommended move: \${item.recommendedAction}\` : null,
+          item.targetPageUrl ? \`Target page: \${item.targetPageUrl}\` : null,
+          item.queries?.length ? \`Queries/questions: \${item.queries.join('; ')}\` : null,
+          item.why ? \`Why: \${item.why}\` : null,
+        ].filter(Boolean).join(' ')
+      ),
+    ].join('\\n'),
+    analysisTypes,
+    includedSignals: [
+      'topic_roadmap',
+      'gap_inventory',
+      'question_pool',
+      'page_summaries',
+      'serp_opportunities',
+      ...analysisTypes,
+    ],
+    excludedAdjacentScopes: [],
+    reasonForScope:
+      'The user requested a plan that executes the currently open roadmap gaps for this topic.',
+    expectedOutcome:
+      'Generate concrete plan items to create, refresh, consolidate, remove, link, or measure the pages called out by the open roadmap rows without cannibalizing existing topic coverage.',
+  };
+}
+
+const useRoadmapScope = topicId && openRoadmapItems.length > 0 &&
+  /roadmap|gaps|gap|new pages|new content|updates|refresh|comprehensive/i.test(userIntent ?? '');
+
+let selected = null;
+let preview = null;
+if (useRoadmapScope) {
+  const scope = roadmapScope(topicId, topicName, entityId, openRoadmapItems);
+  preview = await api.post(\`/api/entities/\${entityId}/plan-scopes/preview\`, {
+    selectedBy: 'agent',
+    userIntent: q,
+    scope,
+  });
+}
+\`\`\`
+
+If you are not in roadmap mode, use ranked scoped candidates:
+
+\`\`\`ts
 const candidates = await api.get(
-  \`/api/entities/\${entityId}/plan-scopes/candidates?q=\${encodeURIComponent(q)}&limit=6&maxItems=8\`
+  \`/api/entities/\${entityId}/plan-scopes/candidates?q=\${encodeURIComponent(q)}&limit=8&maxItems=8\`
 );
 \`\`\`
 
 Show the top 3 candidates with:
 - label
 - scope type
-- pages and gaps included
+- pages, gaps, answer cells, roadmap rows, and decision candidates included
+- personas and decision stages if present
 - expected outcome
 - conflict state and warnings
 - why you prefer one
 
+Prefer scopes that are:
+- roadmap-backed or decision-backed
+- page-bounded or small topic-bounded
+- clear about persona x decision stage x question
+- conflict-clear
+- commercially or strategically meaningful
+
 If every candidate is weak, broaden the query once. If candidates are
 still thin, say the source data is missing and suggest the prerequisite
-connection or scan.
+connection, scan, KB work, or roadmap generation.
 
-### Step 3 \u2014 Inspect conflicts before committing
+### Step 6 \u2014 Inspect conflicts before committing
 
 Never stage a scope blindly. Use preview when the user is leaning toward
 a candidate or asks why it is safe.
 
+For non-roadmap scopes, convert the candidate to a full scope without
+dropping the evidence bindings:
+
 \`\`\`ts
-const selected = candidates.candidates[0];
-const preview = await api.post(\`/api/entities/\${entityId}/plan-scopes/preview\`, {
-  selectedBy: 'agent',
-  scope: {
+selected = candidates.candidates[0];
+function toScope(selected) {
+  return {
     version: 1,
     selectedAt: new Date().toISOString(),
     selectedBy: 'agent',
@@ -791,13 +1030,31 @@ const preview = await api.post(\`/api/entities/\${entityId}/plan-scopes/preview\
     subtopicIds: selected.subtopicIds,
     pageIds: selected.pageIds,
     gapIds: selected.gapIds,
+    answerCellIds: selected.answerCellIds ?? [],
+    decisionCandidateIds: selected.decisionCandidateIds ?? [],
+    primaryPersonaIds: selected.primaryPersonaIds ?? [],
+    decisionStages: selected.decisionStages ?? [],
+    scopeThesis: selected.scopeThesis ?? null,
     analysisTypes: selected.analysisTypes,
-    includedSignals: ['gap_inventory', ...selected.analysisTypes],
+    includedSignals: [
+      'gap_inventory',
+      'answer_map',
+      'decision_candidates',
+      ...selected.analysisTypes,
+    ],
     excludedAdjacentScopes: [],
     reasonForScope: selected.whyThisScope,
     expectedOutcome: selected.expectedOutcome,
-  },
-});
+  };
+}
+
+if (!preview) {
+  preview = await api.post(\`/api/entities/\${entityId}/plan-scopes/preview\`, {
+    selectedBy: 'agent',
+    userIntent: q,
+    scope: toScope(selected),
+  });
+}
 \`\`\`
 
 If preview returns blocked conflicts, do not create the plan. Explain
@@ -806,15 +1063,30 @@ the overlap and pick another scope.
 If preview returns warnings, ask for explicit user acceptance before
 creating. Warnings are allowed only when the user understands the overlap.
 
-### Step 4 \u2014 Create the scoped plan
+### Step 7 \u2014 Clean old plans only with approval
+
+If the user says old plans are conflicting, list them first and ask
+before deleting. Do not silently remove plans.
+
+\`\`\`ts
+const existing = await api.get(\`/api/plans?entityId=\${entityId}\`);
+console.log(existing.plans.map(p => ({ id: p.id, name: p.name, status: p.status })));
+
+// After explicit user approval:
+await Promise.all(existing.plans.map(p => api.delete(\`/api/plans/\${p.id}\`)));
+\`\`\`
+
+### Step 8 \u2014 Create the scoped plan
 
 Create from the selected scope. Do not use legacy topic-plan or
 opportunity-basket endpoints.
 
 \`\`\`ts
+const planLabel = selected?.label ?? preview.scope.label;
+const planDescription = selected?.expectedOutcome ?? preview.scope.expectedOutcome;
 const plan = await api.post(\`/api/entities/\${entityId}/plans/from-scope\`, {
-  name: selected.label,
-  description: selected.expectedOutcome,
+  name: planLabel,
+  description: planDescription,
   scope: preview.scope,
   conflictOverride:
     preview.conflicts.some(c => c.severity === 'warn')
@@ -823,7 +1095,7 @@ const plan = await api.post(\`/api/entities/\${entityId}/plans/from-scope\`, {
 });
 \`\`\`
 
-### Step 5 \u2014 Generate scoped items
+### Step 9 \u2014 Generate scoped items
 
 \`\`\`ts
 const generation = await api.post(\`/api/plans/\${plan.plan.id}/generate-scoped\`);
@@ -831,14 +1103,55 @@ console.log(generation);
 \`\`\`
 
 Generation must stay inside the selected scope. It should claim only
-the gaps and pages in the scope, carry conflict warnings into the audit,
-and return deferred or not-recommended items instead of stretching the
-scope to look productive.
+the gaps and pages in the scope, cite the selected evidence spine
+(\`topic_roadmap\` rows, scoped gaps, pages, answer cells, or
+\`decisionCandidateIds\`), carry conflict warnings into the audit, and
+return deferred or not-recommended items instead of stretching the scope
+to look productive.
+
+After generation, read the plan and verify it stayed grounded:
+
+\`\`\`ts
+const detail = await api.get(\`/api/plans/\${plan.plan.id}\`);
+console.log(detail.items.map(i => ({
+  title: i.title,
+  bundle: i.bundleJson,
+})));
+\`\`\`
+
+Explain what to review and which first 1-3 items are safest to move into
+execution.
+
+### Step 10 \u2014 Generate content briefs when the plan item is ready
+
+For roadmap new-page rows or plan items that need a writer-ready brief,
+use the brief generator only when you can resolve a source question id
+from the roadmap row or its covered opportunity keys. Let the user add a
+thesis, proof point, competitor angle, product workflow, related product,
+use case, benefit, or unique take as \`guidance\`.
+
+\`\`\`ts
+const brief = await api.post(
+  \`/api/diagnostics/\${diagnosticId}/questions/\${questionId}/generate-brief\`,
+  {
+    targetPlanItemId: planItemId ?? null,
+    guidance: userBriefGuidance ?? null,
+    previousFailure: previousBriefFailure ?? null,
+  }
+);
+console.log(brief);
+\`\`\`
+
+A useful brief should cover focus keyword, secondary keywords, target
+questions, competitor/SERP and AEO shape, related products, use cases,
+benefits to include, the company's unique angle or thesis, outline, and
+key facts/proof the writer can cite.
 
-After generation, send the user to the plan detail. Explain what to
-review and which first 1-3 items are safest to move into execution.
+If the generator asks for missing inputs, do not invent them. Surface the
+open questions to the user and use the brief chat/context flow to fill
+only those blanks. Then regenerate with the user's guidance.
 
-### Step 6 \u2014 Set expectations
+### Step 11 \u2014 Set expectations
 
 End with reality:
 
@@ -849,20 +1162,37 @@ End with reality:
 ## Strong opinions to bring
 
 - **One bounded scope per plan.** Always.
+- **Decision candidates are the execution menu.** If a plan ignores them,
+  stop and investigate, unless this is a roadmap-derived scope whose
+  execution menu is the open roadmap rows.
+- **Topic roadmap rows are execution evidence.** Use them directly for
+  topic-gap, new-page, page-refresh, consolidation, internal-link, and
+  measurement planning.
+- **Imagination is hypothesis generation.** Promote it before planning;
+  never execute it directly.
 - **Prefer conflict-clear scopes.** Warning scopes require explicit user acceptance.
-- **Use the signal, not the URL.** Match on topic, page summaries, gap evidence,
-  GSC, GA, AEO, conversion, and strategy context.
+- **Use the signal, not the URL.** Match on topic, page summaries, answer
+  cells, gap evidence, GSC, GA, AEO, conversion, and strategy context.
 - **Small is fine.** A plan with 3 high-confidence page items can beat a giant backlog.
 - **Don't promise CTR lift in week 1.** The data takes 14 days.
 - **Inconclusive is not failed.** Many outcomes need another window.
-- **Archive old/conflicting plans.** Open-ended plans become graveyards.
+- **Archive old/conflicting plans only with approval.** Open-ended plans
+  become graveyards, but deleting them is still destructive.
 
 ## What success looks like
 
+- Source signal checked
+- Topic roadmap checked when the user asks about topic gaps, new pages,
+  updates, or comprehensiveness
+- Decision candidates refreshed
+- Imagination candidates reviewed when useful
 - One bounded scope picked
 - Conflicts reviewed
 - One scoped plan created
 - Scoped generation run
+- Generated items cite the selected evidence spine
+- Content briefs generated only from resolvable roadmap/plan-item source
+  questions, with user guidance captured when needed
 - First execution items are obvious
 - User knows when to come back: 14 days for outcomes, sooner for approvals
 
@@ -874,7 +1204,19 @@ End with reality:
   or \`POST /api/plans/:id/generate-topic\`.
 - Don't sort opportunities by score and list the top 10. That's not strategy.
 - Don't let URLs alone classify scope. Use the evidence Higrowth gathered.
+- Don't ignore open topic roadmap rows when the user asks for topic gaps,
+  comprehensiveness, new pages, or content updates.
+- Don't drop \`answerCellIds\`, \`decisionCandidateIds\`, \`primaryPersonaIds\`,
+  \`decisionStages\`, or \`scopeThesis\` when previewing or creating a scope.
+  For roadmap scopes, preserve the roadmap rows in \`scopeThesis\` and
+  include \`topic_roadmap\` in \`includedSignals\`.
 - Don't create a plan that overlaps blocked active work.
+- Don't create work orders from imagination candidates.
+- Don't hand-write content briefs when the brief generator has a source
+  question. Generate, inspect open questions, collect guidance, then
+  regenerate.
+- Don't run a new scan by default. Check answer map, decision candidates,
+  GSC, GA, and KB first; scan only when source signal is missing or stale.
 - Don't gloss over the KB. If the KB is empty, stop and run the
   populate-kb playbook first. Strategy without KB context is generic.
 `;
@@ -1060,7 +1402,7 @@ var SKILLS = [
   {
     slug: "higrowth-marketing-strategy",
     title: "Marketing strategy chat",
-    description: "Walk a diagnostic, pick a pillar, build the sprint plan.",
+    description: "Walk a diagnostic, pick a scoped topic or roadmap, build the sprint plan.",
     body: MARKETING_STRATEGY
   },
   {
@@ -1305,7 +1647,7 @@ function beginUpdateCheck(currentVersion) {
 // package.json
 var package_default = {
   name: "@higrowth/cli",
-  version: "0.3.2",
+  version: "0.3.4",
   description: "Higrowth CLI \u2014 log in via browser, install Claude Code / Codex skills, manage the MCP connection.",
   type: "module",
   license: "Apache-2.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@higrowth/cli",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Higrowth CLI — log in via browser, install Claude Code / Codex skills, manage the MCP connection.",
   "type": "module",
   "license": "Apache-2.0",