@compilr-dev/sdk 0.7.7 → 0.7.8

package/dist/index.d.ts

@@ -61,7 +61,7 @@ export type { AskUserQuestion, AskUserInput, AskUserResult, AskUserHandler, AskU
 export { createPlatformTools, createProjectTools, createWorkItemTools, createDocumentTools, createPlanTools, createBacklogTools, createAnchorTools, createArtifactTools, createEpisodeTools, ProjectAnchorStore, } from './platform/index.js';
 export type { ProjectAnchorStoreConfig } from './platform/index.js';
 export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getStepCriteria, formatStepDisplay, getStepNumber, } from './platform/index.js';
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, } from './skills/index.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, curriculumDesignSkill, lessonPlanSkill, assessmentDesignSkill, courseReviewSkill, } from './skills/index.js';
 export { ACTION_REGISTRY, getActionsForContext, getActionById, resolveActionPrompt, buildContextSummary, getSuggestedRole, } from './actions/index.js';
 export type { ActionContext, ActionDefinition } from './actions/index.js';
 export { PROJECT_TYPES, getProjectTypeConfig, getEnrichedProjectTypeConfig, getProjectTypesByCategory, generalConfig, softwareConfig, researchConfig, businessPlanConfig, contentConfig, techDocsConfig, courseConfig, ACTION_META_REGISTRY, SKILL_META_REGISTRY, resolveActionMeta, getSkillMeta, getAllSkillMeta, } from './project-types/index.js';

package/dist/index.js

@@ -139,7 +139,7 @@ export { STEP_ORDER, GUIDED_STEP_CRITERIA, getNextStep, isValidTransition, getSt
 // =============================================================================
 // Platform Skills (platform-specific prompt expansions)
 // =============================================================================
-export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, } from './skills/index.js';
+export { platformSkills, designSkill, sketchSkill, prdSkill, refineSkill, refineItemSkill, architectureSkill, sessionNotesSkill, buildSkill, scaffoldSkill, outlineSkill, literatureReviewSkill, draftSectionSkill, peerReviewSkill, researchScaffoldSkill, businessVisionSkill, marketAnalysisSkill, competitorAnalysisSkill, financialModelSkill, pitchOutlineSkill, businessReviewSkill, brandSetupSkill, contentStrategySkill, contentCalendarSkill, createContentSkill, contentReviewSkill, curriculumDesignSkill, lessonPlanSkill, assessmentDesignSkill, courseReviewSkill, } from './skills/index.js';
 // =============================================================================
 // Contextual Actions (skill invocations with context)
 // =============================================================================

package/dist/platform/sqlite/document-repository.js

@@ -120,6 +120,7 @@ export class SQLiteDocumentRepository {
             'research-model': 0,
             'business-model': 0,
             'brand-model': 0,
+            'curriculum-model': 0,
         };
         for (const row of results) {
             counts[row.doc_type] = row.count;

package/dist/platform/tools/document-tools.js

@@ -18,6 +18,7 @@ const DOC_TYPE_ENUM = [
     'research-model',
     'business-model',
     'brand-model',
+    'curriculum-model',
 ];
 // eslint-disable-next-line @typescript-eslint/explicit-function-return-type
 export function createDocumentTools(config) {

package/dist/platform/types.d.ts

@@ -19,7 +19,7 @@ export type WorkItemType = 'feature' | 'bug' | 'tech-debt' | 'chore';
 export type WorkItemStatus = 'backlog' | 'in_progress' | 'completed' | 'skipped';
 export type WorkItemPriority = 'critical' | 'high' | 'medium' | 'low';
 export type GuidedStep = 'plan' | 'implement' | 'test' | 'commit' | 'review';
-export type DocumentType = 'prd' | 'architecture' | 'design' | 'notes' | 'plan' | 'app-model' | 'research-model' | 'business-model' | 'brand-model';
+export type DocumentType = 'prd' | 'architecture' | 'design' | 'notes' | 'plan' | 'app-model' | 'research-model' | 'business-model' | 'brand-model' | 'curriculum-model';
 export type PlanStatus = 'draft' | 'approved' | 'in_progress' | 'completed' | 'abandoned';
 export interface Project {
     id: number;

package/dist/project-types/action-meta.js

@@ -64,6 +64,11 @@ export const ACTION_META_REGISTRY = {
     'content-calendar': { id: 'content-calendar', label: 'Calendar', icon: 'Calendar', description: 'Plan content' },
     'create-content': { id: 'create-content', label: 'Create', icon: 'PenTool', description: 'Write content' },
     'content-review': { id: 'content-review', label: 'Review', icon: 'CheckCircle', description: 'Check quality' },
+    // ── Course / Training actions ─────────────────────────────────────────────
+    'curriculum-design': { id: 'curriculum-design', label: 'Curriculum', icon: 'School', description: 'Define structure' },
+    'lesson-plan': { id: 'lesson-plan', label: 'Lessons', icon: 'BookOpen', description: 'Plan lessons' },
+    'assessment-design': { id: 'assessment-design', label: 'Assess', icon: 'ClipboardCheck', description: 'Create assessments' },
+    'course-review': { id: 'course-review', label: 'Review', icon: 'CheckCircle', description: 'Quality check' },
     'financial-model': { id: 'financial-model', label: 'Financials', icon: 'DollarSign', description: 'Build projections' },
     'pitch-outline': { id: 'pitch-outline', label: 'Pitch', icon: 'Rocket', description: 'Structure a pitch' },
     'business-review': { id: 'business-review', label: 'Review', icon: 'ShieldCheck', description: 'Validate the plan' },

package/dist/project-types/configs.js

@@ -577,47 +577,47 @@ export const courseConfig = {
         {
             id: 'curriculum',
             label: 'Curriculum',
-            description: 'Define learning objectives',
+            description: 'Define modules and learning objectives',
             completionCheck: 'has-document',
-            completionDocType: 'syllabus',
+            completionDocType: 'curriculum-model',
         },
         {
             id: 'lessons',
-            label: 'Lessons',
-            description: 'Create lesson content',
+            label: 'Lesson Plans',
+            description: 'Break modules into lessons',
             completionCheck: 'has-workitems',
         },
         {
-            id: 'exercises',
-            label: 'Exercises',
-            description: 'Create practice exercises',
+            id: 'content',
+            label: 'Content',
+            description: 'Write lesson materials',
             completionCheck: 'has-workitems',
         },
         {
             id: 'assessment',
             label: 'Assessment',
-            description: 'Create quizzes and tests',
+            description: 'Create exercises and quizzes',
             completionCheck: 'manual',
         },
-    ],
-    suggestedAgents: [
-        { role: 'instructor', label: 'Instructor', description: 'Course design and lesson planning' },
         {
-            role: 'content-designer',
-            label: 'Content Designer',
-            description: 'Exercise and assessment creation',
+            id: 'review',
+            label: 'Review',
+            description: 'Pedagogical quality review',
+            completionCheck: 'manual',
         },
-        { role: 'reviewer', label: 'Reviewer', description: 'Content review and quality assurance' },
+    ],
+    suggestedAgents: [
+        { role: 'instructor', label: 'Instructor', description: 'Curriculum design, sequencing, pedagogy' },
+        { role: 'content-designer', label: 'Content Designer', description: 'Lesson planning, exercises, assessments' },
+        { role: 'reviewer', label: 'Reviewer', description: 'Pedagogical quality, balance, coverage' },
     ],
     documentTemplates: [
-        { type: 'syllabus', label: 'Syllabus', description: 'Course overview and objectives' },
-        { type: 'lesson', label: 'Lesson', description: 'Lesson content' },
-        { type: 'exercise', label: 'Exercise', description: 'Practice exercise' },
-        { type: 'assessment', label: 'Assessment', description: 'Quiz or test' },
+        { type: 'curriculum-model', label: 'Curriculum', description: 'Course structure, modules, lessons, assessments' },
+        { type: 'notes', label: 'Lesson Notes', description: 'Lesson content and materials' },
         { type: 'session-notes', label: 'Session Notes', description: 'Summary of work done' },
     ],
-    projectActions: ['session-notes'],
-    workItemActions: ['explain'],
+    projectActions: ['curriculum-design', 'lesson-plan', 'assessment-design', 'course-review', 'session-notes'],
+    workItemActions: ['refine-item', 'explain'],
     workItemLabels: {
         feature: { short: 'LS', full: 'Lesson' },
         bug: { short: 'FX', full: 'Fix' },
@@ -625,34 +625,36 @@ export const courseConfig = {
         chore: { short: 'TK', full: 'Task' },
     },
     systemPromptContext: 'This is an educational project. The user is creating a course or training material. Focus on clear explanations, progressive complexity, and effective learning design.',
-    systemPromptSection: `## Project Context: Course / Training Material
+    systemPromptSection: `## Project Context: Course / Training
 
-You are assisting with an educational project. Your role is to help the user create an effective, well-structured learning experience.
+You are assisting with an educational project. Your role is to help the user create an effective, well-structured curriculum. You are a **curriculum designer**, not a subject matter expert — the user provides domain knowledge via the Knowledge Base.
+
+### Curriculum Model
+This project uses a Curriculum Model that tracks the course structure: modules (with learning objectives), lessons (typed: theory, hands-on, demo, discussion, reading), and assessments (quiz, exercise, project). Always read the model before making suggestions.
 
 ### Workflow
-1. **Curriculum Design** — Define learning objectives, prerequisites, progression
-2. **Module Structure** — Organize into modules/lessons with clear scope
-3. **Content Creation** — Write lessons with explanations, examples, visuals
-4. **Exercises** — Create practice activities, coding challenges, projects
-5. **Assessment** — Design quizzes, tests, rubrics
-6. **Review** — Pedagogical review, difficulty calibration, accessibility
+1. **Curriculum Design** — Define modules, learning objectives, prerequisites, progression
+2. **Lesson Plans** — Break modules into typed lessons with time estimates
+3. **Content** — Write lesson materials (user provides domain expertise, you help structure)
+4. **Assessment** — Design quizzes, exercises, projects linked to objectives
+5. **Review** — Check pedagogical quality, balance, coverage
 
 ### Work Items
-- **Lesson** (type: feature) — a lesson or module to create
-- **Fix** (type: bug) — corrections, confusing explanations to clarify
-- **Refactor** (type: tech-debt) — restructuring content flow or difficulty curve
-- **Task** (type: chore) — formatting, media assets, publishing
-
-### Writing Conventions
-- Start every lesson with clear learning objectives (use Bloom's taxonomy)
-- Build knowledge progressively — prerequisites before advanced concepts
-- Include hands-on exercises for every concept taught
-- Use varied examples — abstract + concrete, simple + complex
-- Provide "check your understanding" moments before moving forward
-- Consider different learning styles (reading, doing, watching)
+- **Lesson** (type: feature) — a lesson to develop
+- **Fix** (type: bug) — corrections, unclear explanations
+- **Refactor** (type: tech-debt) — restructuring content flow
+- **Task** (type: chore) — formatting, media, publishing
+
+### Pedagogical Principles
+- Every module needs clear learning objectives (what can the student DO after?)
+- Balance theory and practice — at least 40% hands-on
+- Build progressively — prerequisites before advanced concepts
+- Assess what you teach — every objective should be testable
+- Vary lesson types to maintain engagement
+- Check time balance — modules should be roughly similar in length
 
 ### Team Agents
-- **Instructor** — curriculum design, lesson planning, pedagogy
-- **Writer** — content creation, explanations, narratives
-- **Reviewer** — accuracy, difficulty assessment, completeness`,
+- **Instructor** — curriculum design, sequencing, pedagogy
+- **Content Designer** — lesson planning, exercises, assessments
+- **Reviewer** — pedagogical quality, balance, difficulty calibration`,
 };

package/dist/project-types/skill-meta.js

@@ -119,6 +119,11 @@ export const SKILL_META_REGISTRY = {
     'content-calendar': { id: 'content-calendar', label: 'Content Calendar', description: 'Plan content for a period', icon: 'Calendar', category: 'planning' },
     'create-content': { id: 'create-content', label: 'Create Content', description: 'Write copy and visual brief', icon: 'PenTool', category: 'development' },
     'content-review': { id: 'content-review', label: 'Content Review', description: 'Review for brand consistency', icon: 'CheckCircle', category: 'analysis' },
+    // ── Course / Training Skills ─────────────────────────────────────────────
+    'curriculum-design': { id: 'curriculum-design', label: 'Curriculum', description: 'Define modules and learning objectives', icon: 'School', category: 'planning' },
+    'lesson-plan': { id: 'lesson-plan', label: 'Lesson Plan', description: 'Break modules into lessons', icon: 'BookOpen', category: 'planning' },
+    'assessment-design': { id: 'assessment-design', label: 'Assessment', description: 'Create quizzes and exercises', icon: 'ClipboardCheck', category: 'planning' },
+    'course-review': { id: 'course-review', label: 'Course Review', description: 'Pedagogical quality check', icon: 'CheckCircle', category: 'analysis' },
     // ── Builtin Skills (agents library) ──────────────────────────────────────
     'code-review': {
         id: 'code-review',

package/dist/skills/business-skills.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Business Plan Skills
+ *
+ * business-vision, market-analysis, competitor-analysis, financial-model, pitch-outline, business-review
+ */
+export declare const businessVisionSkill: import("@compilr-dev/agents").Skill;
+export declare const marketAnalysisSkill: import("@compilr-dev/agents").Skill;
+export declare const competitorAnalysisSkill: import("@compilr-dev/agents").Skill;
+export declare const financialModelSkill: import("@compilr-dev/agents").Skill;
+export declare const pitchOutlineSkill: import("@compilr-dev/agents").Skill;
+export declare const businessReviewSkill: import("@compilr-dev/agents").Skill;

package/dist/skills/business-skills.js

@@ -0,0 +1,341 @@
+/**
+ * Business Plan Skills
+ *
+ * business-vision, market-analysis, competitor-analysis, financial-model, pitch-outline, business-review
+ */
+import { defineSkill } from '@compilr-dev/agents';
+export const businessVisionSkill = defineSkill({
+    name: 'business-vision',
+    description: 'Define the business identity, problem, solution, and value proposition',
+    prompt: `You are in BUSINESS VISION MODE. Help the user define and articulate their business idea.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "identity" to check if a model exists
+2. Report what's already defined
+
+## Step 2: Gather Core Information
+Ask in batches (only what's not already defined):
+- **Business name** and tagline
+- **Problem**: What specific pain point do your target customers experience?
+- **Solution**: How does your product/service solve this?
+- **Unique value**: Why you instead of alternatives? What's the unfair advantage?
+- **Target customer**: Who specifically are you building for?
+- **Stage**: idea, pre-seed, seed, series-a, growth, or established?
+- **Industry/sector**
+
+## Step 3: Craft the Value Proposition
+Help refine the problem-solution-uniqueValue into a compelling narrative:
+- Problem should be specific and relatable
+- Solution should directly address the problem
+- Unique value should differentiate from ALL alternatives (including doing nothing)
+
+## Step 4: Save to Model
+- \`business_model_update\` with op: "set_identity" for name, tagline, mission, stage, industry, sector
+- \`business_model_update\` with op: "set_value_proposition" for problem, solution, uniqueValue, targetCustomer
+
+## Step 5: Suggest Next Steps
+After saving, suggest:
+- "Run /market-analysis to size your market and define customer segments"
+- "Run /competitor-analysis to map the competitive landscape"
+
+## Rules
+- Interactive — ask questions, don't assume
+- Push back on vague answers ("everyone" is not a target customer)
+- A good value proposition is specific, measurable, and defensible`,
+    tags: ['business', 'planning', 'vision'],
+});
+export const marketAnalysisSkill = defineSkill({
+    name: 'market-analysis',
+    description: 'Analyze market size, trends, and customer segments',
+    prompt: `You are in MARKET ANALYSIS MODE. Help the user understand their market.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "overview" for context
+2. Use \`business_model_get\` with scope: "market" for existing market data
+3. Check Knowledge Base for market research sources
+
+## Step 2: Define Customer Segments
+For each segment:
+- Name and description
+- Estimated size (number of potential customers or revenue opportunity)
+- Key pain points (what problems they face)
+- Willingness to pay
+
+Save each: \`business_model_update\` with op: "segment_add", segment: { name, description, size, painPoints, willingness }
+
+## Step 3: Market Sizing
+Guide through TAM/SAM/SOM:
+- **TAM** (Total Addressable Market): If everyone who could use your product did, how big is the market?
+- **SAM** (Serviceable Addressable Market): Realistically, which portion can you reach?
+- **SOM** (Serviceable Obtainable Market): In the first 1-3 years, what share can you capture?
+
+Each should have a value (e.g., "$4.2B"), description, and source.
+Save: \`business_model_update\` with op: "set_market_size", market_size: { tam: {...}, sam: {...}, som: {...} }
+
+## Step 4: Trends and Growth
+- Identify 3-5 market trends relevant to the business
+- Estimate market growth rate
+Save: \`business_model_update\` with op: "set_market_size", market_size: { trends: [...], growthRate: "..." }
+
+## Step 5: Generate Work Items
+Create Milestone work items for:
+- "Validate segment: [name]" for each segment (priority: high)
+- "Source market data" if TAM/SAM/SOM need better sources (priority: medium)
+
+## Rules
+- Always ask for sources — investors will ask "where did you get that number?"
+- Challenge unrealistic sizing (a $100B TAM for a niche SaaS is suspicious)
+- Bottom-up sizing is more credible than top-down
+- Distinguish between potential customers and paying customers`,
+    tags: ['business', 'analysis', 'market'],
+});
+export const competitorAnalysisSkill = defineSkill({
+    name: 'competitor-analysis',
+    description: 'Map the competitive landscape — identify competitors, strengths, weaknesses, positioning',
+    prompt: `You are in COMPETITOR ANALYSIS MODE. Help the user understand their competition.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "competitors" for existing data
+2. Read Knowledge Base for competitor research, reports, articles
+3. Use \`business_model_get\` with scope: "identity" for context on the business
+
+## Step 2: Identify Competitors
+For each competitor (guide user to list 3-8):
+- Direct competitors (same product, same market)
+- Indirect competitors (different product, same problem)
+- Potential competitors (could enter the market)
+
+## Step 3: Analyze Each Competitor
+For each, gather:
+- **Name** and brief description
+- **Strengths** (2-4): what they do well
+- **Weaknesses** (2-4): where they fall short
+- **Market position**: leader, challenger, niche, or emerging
+- **Pricing** model/range
+- **URL** (if applicable)
+
+Save each: \`business_model_update\` with op: "competitor_add", competitor: { name, description, strengths, weaknesses, marketPosition, pricing, url }
+
+## Step 4: Define Competitive Advantages
+Based on the competitor analysis, what are YOUR advantages?
+- What do you do that no competitor does?
+- Where are the gaps in the market?
+- What would be hard for competitors to replicate?
+
+Save: \`business_model_update\` with op: "set_competitive_advantages", advantages: [...]
+
+## Step 5: Positioning Matrix
+Help the user define a 2D positioning matrix:
+- Ask: "What are the two most important dimensions in your market?" (e.g., price vs. features, simplicity vs. power, general vs. specialized)
+- Define axes with labels
+- Score each competitor (0-100) on both axes
+- Score the user's business position
+
+Save positioning: \`business_model_update\` op: "set_positioning", positioning: { xAxis: "Domain Specialization", yAxis: "Multi-Agent Capability", xLow: "General", xHigh: "Specialized", yLow: "Single", yHigh: "Multi-Agent", selfX: 85, selfY: 90 }
+
+Then update each competitor with position: \`business_model_update\` op: "competitor_update", competitor_id: "...", updates: { positionX: 30, positionY: 70 }
+
+This generates a visual positioning chart in the Business Model Viewer.
+
+## Step 6: Generate Work Items
+Create work items for:
+- "Deep-dive: [competitor name]" for competitors needing more research (type: Research)
+- "Validate advantage: [advantage]" for unproven competitive claims (type: Research)
+
+## Rules
+- "We have no competitors" is always wrong — there's always an alternative (even doing nothing)
+- Be honest about competitor strengths — investors will know
+- Focus on defensible advantages, not features that can be copied
+- Include both current competitors and potential future entrants`,
+    tags: ['business', 'analysis', 'competition'],
+});
+export const financialModelSkill = defineSkill({
+    name: 'financial-model',
+    description: 'Build revenue forecasts, cost structure, and break-even analysis',
+    prompt: `You are in FINANCIAL MODEL MODE. Help the user build financial projections.
+
+## Step 1: Assess Current State
+1. Use \`business_model_get\` with scope: "financials" for existing projections
+2. Use \`business_model_get\` with scope: "canvas" for revenue streams and cost structure
+3. Use \`business_model_get\` with scope: "overview" for business context
+
+## Step 2: Define Revenue Streams
+For each revenue stream (if not already defined):
+- Name, type (subscription, one-time, usage, etc.)
+- Projected revenue
+Save: \`business_model_update\` op: "revenue_stream_add"
+
+## Step 3: Build Revenue Forecasts
+For each revenue stream, guide through assumptions:
+- Number of customers per period
+- Average revenue per customer
+- Growth rate
+- Seasonality or ramp-up time
+
+Save forecasts: \`business_model_update\` op: "forecast_add", financials_field: { type: "revenue", period, category, amount }
+
+Use realistic time horizons:
+- Startup: monthly for Year 1, quarterly for Years 2-3
+- Growth stage: quarterly for 3 years
+- Established: yearly for 5 years
+
+## Step 4: Define Cost Structure
+Guide through expense categories:
+- **Fixed costs**: salaries, rent, subscriptions, insurance
+- **Variable costs**: hosting, transaction fees, marketing spend (scales with revenue)
+
+Save each: \`business_model_update\` op: "cost_item_add"
+Save forecasts: \`business_model_update\` op: "forecast_add", financials_field: { type: "expense", period, category, amount }
+
+## Step 5: Break-Even Analysis
+Calculate:
+- Monthly burn rate (total fixed + variable costs)
+- Monthly revenue at steady state
+- Break-even point (when cumulative revenue > cumulative costs)
+
+Save: \`business_model_update\` op: "set_financials_fields", financials_field: { breakEvenPoint: "Month 18", fundingNeeds: "$2M", useOfFunds: "70% product, 20% marketing, 10% ops" }
+
+## Step 6: Document Assumptions
+List all key assumptions made:
+- Customer acquisition rate
+- Churn rate
+- Pricing changes
+- Hiring timeline
+
+Save: \`business_model_update\` op: "set_financials_fields", financials_field: { assumptions: [...] }
+
+## Rules
+- Always state assumptions explicitly — hidden assumptions kill credibility
+- Use conservative estimates (investors multiply your timeline by 2x)
+- Revenue should be bottoms-up (customers × price), not top-down (% of TAM)
+- Include a "what if" scenario: what happens if growth is 50% slower?
+- Round to meaningful numbers — $1.2M not $1,237,849`,
+    tags: ['business', 'analysis', 'financial'],
+});
+export const pitchOutlineSkill = defineSkill({
+    name: 'pitch-outline',
+    description: 'Structure an investor pitch or executive summary from the Business Model',
+    prompt: `You are in PITCH OUTLINE MODE. Help the user create a compelling pitch from their Business Model.
+
+## Step 1: Assess Readiness
+1. Use \`business_model_get\` with scope: "full" to review the complete model
+2. Check completeness: identity, value prop, market, competitors, financials
+3. If major gaps exist, note them and suggest which skills to run first
+
+## Step 2: Choose Format
+Ask the user:
+- **Elevator pitch** (30 seconds — 3 sentences)
+- **Executive summary** (1 page — for email/document)
+- **Pitch deck narrative** (10-12 slides — investor presentation)
+
+## Step 3: Structure the Pitch
+For a pitch deck (adapt for other formats):
+
+1. **Problem** — The pain point (from valueProposition.problem)
+2. **Solution** — Your approach (from valueProposition.solution)
+3. **Market** — Size and opportunity (from market TAM/SAM/SOM)
+4. **Product** — What you've built / will build
+5. **Business Model** — How you make money (from canvas.revenueStreams)
+6. **Traction** — What you've achieved so far (milestones, users, revenue)
+7. **Competition** — Why you win (from competitors + competitiveAdvantages)
+8. **Team** — Why this team (from team)
+9. **Financials** — Projections and key metrics (from financials)
+10. **The Ask** — What you need (from financials.fundingNeeds + useOfFunds)
+
+## Step 4: Draft the Narrative
+For each section:
+- Write 2-3 sentences that tell a story
+- Lead with the strongest point
+- Use specific numbers, not vague claims
+- Save as a project document
+
+## Step 5: Generate Work Items
+Create Milestone work items:
+- "Draft: [section name]" for each pitch section
+- "Prepare: supporting data" for claims that need evidence
+
+## Rules
+- The pitch tells a STORY, not a list of facts
+- Start with emotion (the problem), end with opportunity (the ask)
+- Every claim should be backed by data from the Business Model
+- If financials are weak, lead with market size and traction instead
+- The ask should be specific: "$X for Y months to achieve Z"`,
+    tags: ['business', 'writing', 'pitch'],
+});
+export const businessReviewSkill = defineSkill({
+    name: 'business-review',
+    description: 'Validate the business plan — find gaps, weak assumptions, and missing elements',
+    prompt: `You are in BUSINESS REVIEW MODE. Critically evaluate the business plan like an investor would.
+
+## Step 1: Load and Assess
+1. Use \`business_model_get\` with scope: "full" to read everything
+2. Run \`business_model_validate\` for structural issues
+
+## Step 2: Completeness Check
+Score each section (Complete / Partial / Missing):
+- Identity & Value Proposition
+- Market Analysis (TAM/SAM/SOM, segments)
+- Competitive Analysis (competitors, advantages)
+- Business Model Canvas (revenue, costs, channels, partnerships)
+- Financial Projections (revenue, expenses, break-even)
+- Go-to-Market (phases, strategy)
+- Team
+
+Present a scorecard: "7/7 complete" or "5/7 — missing Financials and GTM"
+
+## Step 3: Assumption Audit
+For each key assumption:
+- Is it stated explicitly?
+- Is there evidence supporting it?
+- What happens if it's wrong?
+
+Flag assumptions that are:
+- **Optimistic** — "We'll capture 10% of the market in Year 1" (unlikely for most startups)
+- **Unvalidated** — claims without data or customer evidence
+- **Risky** — single points of failure
+
+## Step 4: Competitive Blind Spots
+- Are there competitors missing from the analysis?
+- Are competitive advantages truly defensible?
+- What would a well-funded competitor do to beat you?
+- Is the pricing competitive given the alternatives?
+
+## Step 5: Financial Reality Check
+- Do revenue projections match the market sizing? (can't project $100M revenue in a $50M SAM)
+- Is the cost structure realistic? (engineering salaries, cloud costs, marketing spend)
+- Is the break-even timeline achievable with the stated funding?
+- What's the burn rate, and how long does the funding last?
+
+## Step 6: Generate Review Report
+Structure as:
+
+### Scorecard
+Section-by-section completeness
+
+### Strengths (what's compelling)
+2-3 strongest elements
+
+### Critical Issues (must fix)
+Problems that would stop an investor
+
+### Major Issues (should fix)
+Significant weaknesses
+
+### Recommendations
+Prioritized action items
+
+Write report to a project document.
+
+## Step 7: Create Work Items
+- Type "Issue" (bug) for critical and major issues
+- Type "Research" (tech-debt) for unvalidated assumptions
+- Type "Milestone" (feature) for missing sections
+
+## Rules
+- Be constructive but honest — sugar-coating helps nobody
+- Think like an investor: "Would I put money into this?"
+- Every issue should have a specific recommendation
+- Acknowledge what's strong — it builds credibility for the critique
+- Focus on the 3-5 things that matter most, not a list of 20 nitpicks`,
+    tags: ['business', 'review', 'validation'],
+});

package/dist/skills/content-skills.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Content & Marketing Skills
+ *
+ * brand-setup, content-strategy, content-calendar, create-content, content-review
+ */
+export declare const brandSetupSkill: import("@compilr-dev/agents").Skill;
+export declare const contentStrategySkill: import("@compilr-dev/agents").Skill;
+export declare const contentCalendarSkill: import("@compilr-dev/agents").Skill;
+export declare const createContentSkill: import("@compilr-dev/agents").Skill;
+export declare const contentReviewSkill: import("@compilr-dev/agents").Skill;