@productbrain/cli 0.1.0-beta.99 → 0.1.0-beta.9904

package/dist/lib/onboarding-phases.js

@@ -1,120 +0,0 @@
-/**
- * Onboarding conversation phases — the 5-phase arc for first-time setup.
- * WP-304: Each phase has a directive (what the LLM should do) and exit criteria (what the CLI checks).
- */
-export const ONBOARDING_PHASES = [
-    {
-        id: 'greet',
-        directive: `Your job: Say hello and ask what they're building. One sentence. No fluff.
-Example: "Hey! What are you building?"
-Do NOT ask multiple questions. Do NOT explain Product Brain yet.`,
-        exitCriteria: [
-            {
-                name: 'greeting_sent',
-                check: (s) => s.phaseExchanges['greet'] !== undefined && (s.phaseExchanges['greet'] ?? 0) >= 0,
-                required: true,
-            },
-        ],
-        maxExchanges: 1,
-    },
-    {
-        id: 'explore',
-        directive: `Your job: Learn what they're building. Get specific.
-If they gave a vague answer ("something big", "a tool", "an app"), pick one concrete detail and dig in.
-Ask who uses it, what it actually does, or how it works today.
-Good questions: "Who's using it?" / "What does it replace?" / "How does that work today?"
-Bad questions: "What domain are you operating in?" / "Can you elaborate on that?"
-Do NOT ask why they're trying Product Brain yet.
-One question only.`,
-        exitCriteria: [
-            {
-                name: 'user_mentioned_product',
-                check: (s) => s.signals.mentionedProduct,
-                required: true,
-            },
-            {
-                name: 'has_substantive_answer',
-                check: (s) => s.signals.hasSubstantiveAnswer,
-                required: true,
-            },
-        ],
-        maxExchanges: 3,
-    },
-    {
-        id: 'deepen',
-        directive: `Your job: Understand what's hard about what they're building.
-Pick ONE specific thing they mentioned and ask what breaks or why it's hard. Be direct and short.
-Good: "What breaks when the agent doesn't have that context?" / "Where does the rework hit hardest?"
-Bad: "What makes it hard to ensure X?" / "Can you tell me more about the challenges?"
-Do NOT ask why they're trying Product Brain yet.
-One question only.`,
-        exitCriteria: [
-            {
-                name: 'user_mentioned_challenge',
-                check: (s) => s.signals.mentionedChallenge,
-                required: false,
-            },
-            {
-                name: 'min_2_substantive_messages',
-                check: (s) => s.signals.substantiveMessageCount >= 2,
-                required: true,
-            },
-        ],
-        maxExchanges: 2,
-    },
-    {
-        id: 'why_pb',
-        directive: `Your job: Ask what made them try Product Brain. Be direct.
-Examples: "What made you try Product Brain?" or "What problem are you hoping Product Brain solves?"
-Do NOT summarize or synthesize yet.
-One question only.`,
-        exitCriteria: [
-            {
-                name: 'user_answered_why_pb',
-                check: (s) => s.signals.mentionedWhyPB,
-                required: false,
-            },
-            {
-                name: 'min_total_words_25',
-                check: (s) => s.totalUserWords >= 25,
-                required: true,
-            },
-            {
-                name: 'min_3_substantive_messages',
-                check: (s) => s.signals.substantiveMessageCount >= 3,
-                required: true,
-            },
-        ],
-        maxExchanges: 2,
-    },
-    {
-        id: 'bridge',
-        directive: `Your job: Bridge the conversation to Product Brain's value. Speak as Product Brain (first person "I").
-Keep it SHORT — 2-3 sentences max. Do NOT list bullet items. The CLI will handle showing examples.
-
-Structure:
-1. One sentence connecting their problem to what you (PB) do. Use first person.
-2. One sentence showing you understood something specific they said.
-
-Good example: "I can remember all of that across your AI sessions — so next time you open your AI tools, they already know about the decision rot problem and your cashflow automation. No more re-explaining."
-Bad example: "Product Brain can help — it remembers context. Here's what I'd save: * item 1 * item 2 * item 3"
-
-Do NOT list items. Do NOT use bullet points or asterisks. The CLI shows examples separately.
-This is a STATEMENT. Do NOT ask a question. Do NOT end with a question mark.`,
-        exitCriteria: [
-            {
-                name: 'bridge_delivered',
-                check: (s) => (s.phaseExchanges['bridge'] ?? 0) >= 1,
-                required: true,
-            },
-        ],
-        maxExchanges: 1,
-    },
-];
-/** User wants to skip — detected by regex on user input. */
-const SKIP_PATTERNS = [/\b(?:skip|done|that'?s it|wrap up|let'?s go|finish|end)\b/i];
-/** Check if user wants to skip the conversation. */
-export function userWantsToSkip(text) {
-    return SKIP_PATTERNS.some((p) => p.test(text));
-}
-//# sourceMappingURL=onboarding-phases.js.map

package/dist/lib/onboarding-phases.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"onboarding-phases.js","sourceRoot":"","sources":["../../src/lib/onboarding-phases.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAIH,MAAM,CAAC,MAAM,iBAAiB,GAAwB;IACpD;QACE,EAAE,EAAE,OAAO;QACX,SAAS,EAAE;;iEAEkD;QAC7D,YAAY,EAAE;YACZ;gBACE,IAAI,EAAE,eAAe;gBACrB,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,KAAK,SAAS,IAAI,CAAC,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC;gBAC9F,QAAQ,EAAE,IAAI;aACf;SACF;QACD,YAAY,EAAE,CAAC;KAChB;IACD;QACE,EAAE,EAAE,SAAS;QACb,SAAS,EAAE;;;;;;mBAMI;QACf,YAAY,EAAE;YACZ;gBACE,IAAI,EAAE,wBAAwB;gBAC9B,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,gBAAgB;gBACxC,QAAQ,EAAE,IAAI;aACf;YACD;gBACE,IAAI,EAAE,wBAAwB;gBAC9B,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,oBAAoB;gBAC5C,QAAQ,EAAE,IAAI;aACf;SACF;QACD,YAAY,EAAE,CAAC;KAChB;IACD;QACE,EAAE,EAAE,QAAQ;QACZ,SAAS,EAAE;;;;;mBAKI;QACf,YAAY,EAAE;YACZ;gBACE,IAAI,EAAE,0BAA0B;gBAChC,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,kBAAkB;gBAC1C,QAAQ,EAAE,KAAK;aAChB;YACD;gBACE,IAAI,EAAE,4BAA4B;gBAClC,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,uBAAuB,IAAI,CAAC;gBACpD,QAAQ,EAAE,IAAI;aACf;SACF;QACD,YAAY,EAAE,CAAC;KAChB;IACD;QACE,EAAE,EAAE,QAAQ;QACZ,SAAS,EAAE;;;mBAGI;QACf,YAAY,EAAE;YACZ;gBACE,IAAI,EAAE,sBAAsB;gBAC5B,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,cAAc;gBACtC,QAAQ,EAAE,KAAK;aAChB;YACD;gBACE,IAAI,EAAE,oBAAoB;gBAC1B,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,cAAc,IAAI,EAAE;gBACpC,QAAQ,EAAE,IAAI;aACf;YACD;gBACE,IAAI,EAAE,4BAA4B;gBAClC,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,uBAAuB,IAAI,CAAC;gBACpD,QAAQ,EAAE,IAAI;aACf;SACF;QACD,YAAY,EAAE,CAAC;KAChB;IACD;QACE,EAAE,EAAE,QAAQ;QACZ,SAAS,EAAE;;;;;;;;;;;6EAW8D;QACzE,YAAY,EAAE;YACZ;gBACE,IAAI,EAAE,kBAAkB;gBACxB,KAAK,EAAE,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,cAAc,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC;gBACpD,QAAQ,EAAE,IAAI;aACf;SACF;QACD,YAAY,EAAE,CAAC;KAChB;CACF,CAAC;AAEF,4DAA4D;AAC5D,MAAM,aAAa,GAAG,CAAC,4DAA4D,CAAC,CAAC;AAErF,oDAAoD;AACpD,MAAM,UAAU,eAAe,CAAC,IAAY;IAC1C,OAAO,aAAa,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC;AACjD,CAAC"}

package/templates/archetypes/boundary.md

@@ -1,23 +0,0 @@
----
-name: chain-boundaries
-description: "{{entry_count}} system boundaries derived from Chain architecture entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived System Boundaries
-
-These {{entry_count}} architecture and decision entries define system boundaries for this workspace. Do not cross a boundary without understanding the contract it defines.
-
-**Boundary entries:** {{entry_ids}}
-
-{{boundary_summary}}
-
-## What this means
-
-- Boundaries define what a domain owns and what it does not own.
-- Cross-domain changes require explicit negotiation — check the Team APIs in `docs/system/domains/`.
-- Run `pb get <ID>` to read the full boundary entry before touching cross-domain seams.
-- If your change crosses a domain boundary, identify the owning domain first (domain-boundaries rule).
-
-**Source entries (names):** {{entry_names}}

package/templates/archetypes/constraint.md

@@ -1,23 +0,0 @@
----
-name: chain-constraints
-description: "{{entry_count}} implementation constraints derived from Chain governance entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived Constraints
-
-These {{entry_count}} governance entries constrain implementation in this workspace. Before writing code that touches any affected domain, check these entries on the Chain.
-
-**Constraint entries:** {{entry_ids}}
-
-{{constraint_summary}}
-
-## What this means
-
-- These standards and rules are non-negotiable. They constrain behavior across all slices.
-- Run `pb get <ID>` to read the full entry before implementing anything in its domain.
-- If your change conflicts with a constraint, capture a tension before proceeding.
-- "I didn't know" is not a valid defense when the constraint is on the Chain.
-
-**Source entries (names):** {{entry_names}}

package/templates/archetypes/convention.md

@@ -1,23 +0,0 @@
----
-name: chain-conventions
-description: "{{entry_count}} conventions derived from Chain decision and pattern entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived Conventions
-
-These {{entry_count}} decision and pattern entries establish conventions for this workspace. Follow them unless you have a decision on the Chain that says otherwise.
-
-**Convention entries:** {{entry_ids}}
-
-{{convention_summary}}
-
-## What this means
-
-- Conventions are established patterns, not suggestions. They reduce decision fatigue.
-- Before inventing a new pattern, search the Chain — it may already be a convention.
-- Run `pb get <ID>` to understand the rationale behind a convention before deviating.
-- If you must deviate, capture a DEC on the Chain explaining the new direction.
-
-**Source entries (names):** {{entry_names}}

package/templates/archetypes/policy.md

@@ -1,23 +0,0 @@
----
-name: chain-policies
-description: "{{entry_count}} operational policies derived from Chain policy and business-rule entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived Policies
-
-These {{entry_count}} policy and business-rule entries govern workflows and access in this workspace. Policies apply even when they are inconvenient.
-
-**Policy entries:** {{entry_ids}}
-
-{{policy_summary}}
-
-## What this means
-
-- Policies govern who can do what and under what conditions.
-- Security, auth, and access control policies are never optional.
-- Run `pb get <ID>` to read the full policy before implementing anything in its domain.
-- If a policy conflicts with a feature requirement, capture a TEN and escalate — do not quietly violate.
-
-**Source entries (names):** {{entry_names}}

package/templates/archetypes/quality-gate.md

@@ -1,23 +0,0 @@
----
-name: chain-quality-gates
-description: "{{entry_count}} quality gates derived from Chain standard and business-rule entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived Quality Gates
-
-These {{entry_count}} standard and business-rule entries define quality gates that must pass before shipping. No exceptions without a documented reason on the Chain.
-
-**Quality gate entries:** {{entry_ids}}
-
-{{quality_summary}}
-
-## What this means
-
-- Quality gates are pass/fail. They are not approximate.
-- Run `npm run build` and `npm run test` before every push — always.
-- Run `pb get <ID>` to read the specific acceptance criteria for a quality gate.
-- If a gate cannot pass due to a legitimate constraint, capture a TEN before shipping.
-
-**Source entries (names):** {{entry_names}}

package/templates/archetypes/workflow.md

@@ -1,23 +0,0 @@
----
-name: chain-workflows
-description: "{{entry_count}} required process flows derived from Chain flow entries"
-autoApply: true
-level: core
----
-
-# Chain-Derived Workflows
-
-These {{entry_count}} flow entries define required processes for this workspace. If a workflow entry exists for a process you are about to execute, follow it.
-
-**Workflow entries:** {{entry_ids}}
-
-{{workflow_summary}}
-
-## What this means
-
-- Workflows define the correct sequence of steps for key processes.
-- Skipping a step is not the same as completing the workflow.
-- Run `pb get <ID>` to read the full workflow before executing the process it defines.
-- If the workflow is incomplete or outdated, capture a TEN — do not silently deviate.
-
-**Source entries (names):** {{entry_names}}