crewly 1.2.3 → 1.2.6

package/config/templates/core-team/demo-script.md

@@ -0,0 +1,41 @@
+# Crewly 3-Agent 5-Minute Demo Script
+
+**Scenario**: Build a modern, responsive "Product Launch" Landing Page from a single prompt.
+**Agents**: PM (Mia), Dev (Sam), Reviewer (Iris).
+
+---
+
+## Phase 1: Initiation (0:00 - 0:45)
+1. **User Prompt**: "I need a landing page for my new AI-powered task manager called 'TaskAI'. It should have a hero section, feature list, pricing, and a CTA. Use a dark theme with indigo accents."
+2. **Dashboard Visual**: Show the Orchestrator receiving the message.
+3. **PM Action**: Mia analyzes the prompt and creates a task breakdown in the chat.
+4. **Wow Moment**: The PM automatically delegates the "Implementation" task to Sam. The audience sees the task appear on Sam's status in the dashboard.
+
+## Phase 2: Live Terminal Coding (0:45 - 3:00)
+1. **Dev Action**: Sam starts implementing the page.
+2. **Visual Focus**: **Switch to Sam's Live Terminal**.
+3. **Wow Moment**: The audience sees Sam (Claude Code) rapidly writing HTML/Tailwind CSS. The terminal is "alive" with `cat`, `write`, and `ls` commands.
+4. **Dashboard**: Sam's status changes to "Implementing UI". The budget tracker (tokens) starts moving.
+
+## Phase 3: Handoff & Review (3:00 - 4:00)
+1. **Dev Action**: Sam finishes `index.html` and sends a message: "Mia, I've finished the implementation. Iris, please review."
+2. **Reviewer Action**: Iris begins the review.
+3. **Visual Focus**: Dashboard shows Iris's status changing to "Reviewing Code".
+4. **Wow Moment**: Iris provides specific feedback on the contrast ratio of the indigo button or suggests a minor copy fix in the terminal/chat.
+
+## Phase 4: Final Polish (4:00 - 4:45)
+1. **Dev Action**: Sam applies the fix (if any).
+2. **Reviewer Action**: Iris marks the task as **Approved**.
+3. **Dashboard**: The task status moves from "In Progress" to "Completed".
+
+## Phase 5: Result (4:45 - 5:00)
+1. **User Action**: The Orchestrator (Mia) provides the link/path to the `index.html`.
+2. **Visual Focus**: Open the generated `index.html` in a browser to show the result.
+3. **Conclusion**: Summary of total time, cost (tokens), and agent interactions.
+
+---
+
+## Visual Cues for Presenter
+- **Dashboard**: Keep it on a large screen to show state changes (Idle -> Working -> Done).
+- **Terminal**: Use a split view or switch focus to the Developer's terminal during Phase 2 to show the "Vibe" of the agents working.
+- **Budget**: Point out the real-time token/cost calculation as a "Control" feature for SMB owners.

package/config/templates/core-team/goals.md

@@ -0,0 +1,20 @@
+# Crewly 3-Agent Demo Goals
+
+The primary objective of this demo is to showcase Crewly's unique value proposition to SMB owners and developers through a fast-paced, 5-minute collaboration sequence.
+
+## 1. Core Demo Objectives
+- **Demonstrate Team-as-a-Service**: Show how multiple AI agents (PM, Dev, Reviewer) can work autonomously as a cohesive unit.
+- **Showcase Terminal Transparency**: Highlight the Live Terminal feature to prove the "work" is actually happening and is visible in real-time.
+- **Exhibit Dashboard Control**: Use the Team Dashboard to monitor status, tasks, and budget/token usage.
+- **Verify Quality Gates**: Show that code review isn't optional - it's a built-in step for reliability.
+
+## 2. Targeted "Wow" Moments
+- **The "Auto-Delegate"**: When the user provides a prompt, the PM (Mia) immediately breaks it down and delegates it to the Developer (Sam). The task "travels" from the prompt to the dashboard in seconds.
+- **The "Coding Sprint"**: Seeing the Developer (Sam) rapidly generate a 300+ line index.html with Tailwind CSS in the terminal.
+- **The "Constructive Review"**: When the Reviewer (Iris) actually finds something to fix or improve, proving the team is more than just a single prompt.
+- **The "Final Product"**: Seeing a high-quality, responsive landing page delivered in under 5 minutes for a few cents in API tokens.
+
+## 3. Key Takeaways for Audience
+- **Control**: Real-time budget and task tracking make AI predictable.
+- **Scale**: You don't just have an "AI chatbot"; you have an "AI Team".
+- **Trust**: You can see every command the agent runs; no "black box" execution.

package/config/templates/core-team/team.json

@@ -0,0 +1,22 @@
+{
+  "id": "core-team",
+  "name": "Crewly Core Team (Demo)",
+  "description": "3-Agent Demo Flow: PM + Dev + Reviewer working together to build a landing page in under 5 minutes. Optimized for Live Terminal and Dashboard visibility.",
+  "members": [
+    {
+      "name": "PM (Mia)",
+      "role": "product-manager",
+      "systemPrompt": "You are Mia, the Product Manager. Your goal is to lead the team to build a high-conversion landing page. 1) Analyze the user's high-level request. 2) Create a structured task breakdown (UI, copy, basic interaction). 3) Delegate the implementation task to the Developer (Sam). 4) Monitor progress via the dashboard. 5) Final check against acceptance criteria. Be concise and professional."
+    },
+    {
+      "name": "Dev (Sam)",
+      "role": "developer",
+      "systemPrompt": "You are Sam, the Lead Developer. Your goal is to implement the landing page as a single-file React/Tailwind HTML. 1) Receive the requirement from Mia. 2) Write the code (HTML/Tailwind/JS) in a single index.html. 3) Use placeholders for images if needed. 4) Once done, notify Mia and request a review from the Reviewer (Iris). You are the star of the 'Live Terminal' - let the user see your rapid coding process."
+    },
+    {
+      "name": "Reviewer (Iris)",
+      "role": "qa-engineer",
+      "systemPrompt": "You are Iris, the QA/Reviewer. Your goal is to ensure the landing page is perfect. 1) Wait for Sam to finish. 2) Read the code in index.html. 3) Check for responsive design, color contrast, and any potential bugs. 4) Provide constructive feedback or an 'Approved' status. 5) If approved, report to Mia that the task is ready for delivery."
+    }
+  ]
+}

package/config/templates/dev-fullstack/template.json

@@ -0,0 +1,115 @@
+{
+  "id": "dev-fullstack",
+  "name": "Fullstack Development Team",
+  "description": "Team Leader + developers + QA for building web applications",
+  "category": "development",
+  "version": "1.0.0",
+  "tags": ["development", "web", "fullstack", "testing"],
+  "icon": "laptop",
+  "hierarchical": true,
+  "defaultRuntime": "claude-code",
+  "roles": [
+    {
+      "role": "team-leader",
+      "label": "Tech Lead",
+      "defaultName": "Tech Lead",
+      "count": 1,
+      "hierarchyLevel": 1,
+      "canDelegate": true,
+      "defaultSkills": [
+        "decompose-goal",
+        "delegate-task",
+        "verify-output",
+        "aggregate-results",
+        "handle-failure",
+        "code-review"
+      ],
+      "enableBrowser": true
+    },
+    {
+      "role": "developer",
+      "label": "Developer",
+      "defaultName": "Developer",
+      "count": 2,
+      "hierarchyLevel": 2,
+      "canDelegate": false,
+      "reportsTo": "team-leader",
+      "defaultSkills": [
+        "report-status",
+        "complete-task",
+        "request-help"
+      ],
+      "enableBrowser": false
+    },
+    {
+      "role": "qa-engineer",
+      "label": "QA Engineer",
+      "defaultName": "QA",
+      "count": 1,
+      "hierarchyLevel": 2,
+      "canDelegate": false,
+      "reportsTo": "team-leader",
+      "defaultSkills": [
+        "report-status",
+        "complete-task",
+        "request-help"
+      ],
+      "enableBrowser": true
+    }
+  ],
+  "verificationPipeline": {
+    "name": "Development Quality Pipeline",
+    "steps": [
+      {
+        "id": "quality-gates",
+        "name": "Quality Gates",
+        "description": "Run typecheck, unit tests, lint, and build",
+        "method": "quality_gates",
+        "critical": true,
+        "config": {
+          "gates": ["typecheck", "tests", "build"]
+        }
+      },
+      {
+        "id": "code-review",
+        "name": "Code Review",
+        "description": "TL reviews code diff for patterns and quality",
+        "method": "code_review",
+        "critical": true,
+        "config": {
+          "maxDiffLines": 500,
+          "checkPatterns": true
+        }
+      },
+      {
+        "id": "browser-test",
+        "name": "Browser Verification",
+        "description": "Open in browser, screenshot, verify UI matches spec",
+        "method": "browser_test",
+        "critical": false,
+        "config": {
+          "screenshotTool": "computer-use",
+          "viewports": ["desktop"]
+        }
+      },
+      {
+        "id": "e2e",
+        "name": "E2E Tests",
+        "description": "Run Playwright end-to-end test suite",
+        "method": "e2e_test",
+        "critical": false,
+        "config": {
+          "framework": "playwright",
+          "testDir": "tests/e2e"
+        }
+      }
+    ],
+    "passPolicy": "critical_only",
+    "maxRetries": 2
+  },
+  "monitoringDefaults": {
+    "idleEvent": true,
+    "fallbackCheckMinutes": 5
+  },
+  "maxWorkersPerLeader": 4
+}

package/config/templates/education-smb/README.md

@@ -0,0 +1,27 @@
+# Education SMB Team Template
+
+This template provides a complete AI team setup for small and medium-sized education businesses. It covers the entire lifecycle of educational service delivery, from curriculum design to student engagement and performance analytics.
+
+## 🏗️ Team Composition
+- **Curriculum Designer (Alex)**: Focuses on structure and pedagogy.
+- **Content Creator (Casey)**: Produces engaging lesson materials.
+- **Student Engagement Manager (Sam)**: Manages community and feedback.
+- **Analytics Specialist (Skyler)**: Provides data-driven insights.
+
+## 🔄 Included Workflows
+1. **Course Content Generation**: End-to-end flow from curriculum design to finalized content.
+2. **Student Communication**: Automates feedback loops and announcements.
+3. **Weekly/Monthly Reporting**: Generates operational and performance insights.
+
+## 📚 Bundled Knowledge
+- **Education Industry Context**: Industry-standard SOPs and terminology.
+- **Content Quality Standards**: Guidelines for pedagogical alignment and accessibility.
+
+## 🚀 Quick Start
+To instantiate this team, use the Crewly CLI:
+```bash
+npx crewly create team --template education-smb
+```
+
+## 🎯 Default Goals
+See `goals.md` for the pre-set OKRs designed to drive growth and efficiency in an educational SMB context.

package/config/templates/education-smb/goals.md

@@ -0,0 +1,16 @@
+# Education SMB Team OKRs
+
+## Objective 1: Deliver High-Quality, Scalable Educational Content
+- **KR1**: Complete the curriculum design and content production for [Course Name] within 30 days.
+- **KR2**: Achieve a 100% compliance rate with FERPA/COPPA standards across all content.
+- **KR3**: Maintain a minimum quality score of 4.5/5 across all peer reviews.
+
+## Objective 2: Maximize Student Engagement and Satisfaction
+- **KR1**: Increase average student completion rates for new courses by 20%.
+- **KR2**: Reduce response time to student queries to under 4 hours on average.
+- **KR3**: Maintain a Net Promoter Score (NPS) of 75 or higher.
+
+## Objective 3: Optimize Operational Efficiency through AI
+- **KR1**: Reduce the time-to-market for a new 10-lesson module from 3 weeks to 1 week.
+- **KR2**: Automate 80% of routine student notifications and progress reports.
+- **KR3**: Maintain an AI team token ROI of at least 5x compared to manual labor costs.

package/config/templates/education-smb/knowledge/docs/content-standards.md

@@ -0,0 +1,24 @@
+# Education Content Quality Standards
+
+## 1. Pedagogical Alignment
+- Content must align with the stated learning objectives of the curriculum.
+- Materials should follow an "Instructional Scaffolding" approach (moving from simple to complex).
+
+## 2. Reading Level and Accessibility
+- **Parent Content**: Target Grade 8 reading level.
+- **Student Content**: Target the specific grade level of the target audience.
+- **Teacher Content**: Can use professional terminology but must remain clear and actionable.
+
+## 3. Engagement and Interactivity
+- Use active voice and direct address.
+- Include knowledge checks or reflection prompts every 10-15 minutes of content.
+- Use diverse examples that represent various backgrounds and cultures.
+
+## 4. Compliance and Safety
+- No student PII (Personally Identifiable Information) in public-facing or AI-generated content.
+- All links must be verified for safety and relevance.
+- Content must be free of bias and stereotypes.
+
+## 5. Visual Consistency
+- Use consistent branding and formatting for all course materials.
+- All images must have alt-text for accessibility.

package/config/templates/education-smb/knowledge/docs/education-industry-context.md

@@ -0,0 +1,13 @@
+# Education Industry Context
+
+## Common SOPs
+1. **Curriculum Review Cycle**: Curricula should be reviewed every 6 months to ensure relevance and alignment with current standards.
+2. **Student Privacy Protection**: All student data must be handled according to FERPA (Family Educational Rights and Privacy Act) and COPPA (Children's Online Privacy Protection Act) guidelines.
+3. **Inclusive Design**: Educational materials must be accessible to students with diverse learning needs, following ADA (Americans with Disabilities Act) standards.
+
+## Key Terminology
+- **LMS (Learning Management System)**: Software for the administration, documentation, tracking, and delivery of educational courses.
+- **SIS (Student Information System)**: Management information system for education establishments to manage student data.
+- **IEP (Individualized Education Program)**: A document that is developed for each public school child who needs special education.
+- **Pedagogy**: The method and practice of teaching, especially as an academic subject or theoretical concept.
+- **Blended Learning**: A style of education in which students learn via electronic and online media as well as traditional face-to-face teaching.

package/config/templates/education-smb/knowledge/index.json

@@ -0,0 +1,24 @@
+{
+  "version": "1.0.0",
+  "lastUpdated": "2026-03-04T00:00:00.000Z",
+  "documents": [
+    {
+      "id": "edu-industry-context",
+      "title": "Education Industry Context",
+      "path": "docs/education-industry-context.md",
+      "category": "terminology",
+      "tags": ["education", "sop", "terminology"],
+      "summary": "Common education industry SOPs and terms.",
+      "createdAt": "2026-03-04T00:00:00.000Z"
+    },
+    {
+      "id": "edu-content-standards",
+      "title": "Education Content Quality Standards",
+      "path": "docs/content-standards.md",
+      "category": "best-practice",
+      "tags": ["content", "quality", "standards"],
+      "summary": "Guidelines for educational content quality.",
+      "createdAt": "2026-03-04T00:00:00.000Z"
+    }
+  ]
+}

package/config/templates/education-smb/learned-patterns.json

@@ -0,0 +1,16 @@
+{
+  "version": "1.0.0",
+  "lastUpdated": "2026-03-04T00:00:00.000Z",
+  "patterns": [
+    {
+      "id": "lp-edu-001",
+      "title": "Use conversational tone for parent communication",
+      "category": "best-practice",
+      "context": "Parent newsletters often feel overly formal or academic, leading to low engagement.",
+      "recommendation": "Use a friendly, conversational tone and focus on student achievements. Avoid heavy administrative jargon.",
+      "impact": "medium",
+      "discoveredAt": "2026-03-04T00:00:00.000Z",
+      "tags": ["communication", "parents"]
+    }
+  ]
+}

package/config/templates/education-smb/quality-gates.yaml

@@ -0,0 +1,66 @@
+version: "1.0.0"
+
+settings:
+  runInParallel: false
+  stopOnFirstFailure: true
+
+gates:
+  curriculum-quality:
+    name: Curriculum Quality Gate
+    description: Ensures the curriculum is structured and aligned with objectives.
+    type: manual
+    required: true
+    criteria:
+      - Clear learning objectives for each module.
+      - Logical progression of lessons.
+      - Inclusion of assessment points.
+    reviewer: "Curriculum Designer (Alex)"
+    onFailure: block
+
+  content-quality:
+    name: Content Quality Gate
+    description: Validates lesson materials against content standards.
+    type: manual
+    required: true
+    criteria:
+      - Alignment with curriculum outline.
+      - Reading level appropriate for target audience.
+      - No placeholders or unfinished sections.
+    reviewer: "Curriculum Designer (Alex)"
+    onFailure: block
+
+  final-approval:
+    name: Final Content Approval
+    description: Final sign-off before content deployment.
+    type: manual
+    required: true
+    criteria:
+      - All peer review comments addressed.
+      - Visual assets suggested or integrated.
+      - Compliance check completed.
+    reviewer: "Curriculum Designer (Alex)"
+    onFailure: block
+
+  compliance-check:
+    name: Compliance & Privacy Gate
+    description: Verify communication is FERPA/COPPA compliant.
+    type: manual
+    required: true
+    criteria:
+      - No student PII exposed.
+      - Clear and professional tone.
+      - Necessary privacy disclosures included.
+    reviewer: "Student Engagement Manager (Sam)"
+    onFailure: block
+
+  reporting-quality:
+    name: Report Quality Gate
+    description: Ensures report accuracy and clarity.
+    type: manual
+    required: true
+    criteria:
+      - All key metrics included.
+      - Insights are data-backed.
+      - Actionable recommendations provided.
+    reviewer: "Analytics Specialist (Skyler)"
+    onFailure: block

package/config/templates/education-smb/roles/analytics-specialist.md

@@ -0,0 +1,6 @@
+You are Skyler, the Analytics Specialist. Your goal is to provide data-driven insights into student performance and business growth.
+1. Track and report on key educational metrics (completion rates, assessment scores).
+2. Generate weekly and monthly reports for the management team.
+3. Identify trends in student engagement and curriculum effectiveness.
+4. Recommend data-backed optimizations for the curriculum and content.
+5. Monitor token usage and ROI for the AI team operations.

package/config/templates/education-smb/roles/content-creator.md

@@ -0,0 +1,6 @@
+You are Casey, the Content Creator. Your goal is to produce engaging, high-quality educational content.
+1. Create lesson materials, video scripts, and interactive exercises based on the curriculum.
+2. Adapt the tone and reading level for different audiences (Students, Parents, Teachers).
+3. Optimize content for SEO when creating public-facing blog posts or marketing materials.
+4. Ensure all content meets the "Content Standards" knowledge base requirements.
+5. Use multimedia skills to suggest visual assets for lessons.

package/config/templates/education-smb/roles/curriculum-designer.md

@@ -0,0 +1,6 @@
+You are Alex, the Curriculum Designer. Your goal is to design structured, pedagogically sound educational programs.
+1. Define clear learning objectives and outcomes.
+2. Structure courses into logical modules and lessons.
+3. Ensure alignment with educational standards (e.g., K-12, Higher Ed).
+4. Coordinate with Content Creators to ensure materials match the curriculum design.
+5. Focus on instructional design principles (e.g., Bloom's Taxonomy, ADDIE model).

package/config/templates/education-smb/roles/engagement-manager.md

@@ -0,0 +1,6 @@
+You are Sam, the Student Engagement Manager. Your goal is to foster a positive and productive learning community.
+1. Manage student communications, notifications, and onboarding.
+2. Analyze student feedback and sentiment to identify areas for improvement.
+3. Proactively address student queries and provide support.
+4. Design engagement strategies (e.g., discussion prompts, newsletters).
+5. Ensure compliance with data privacy regulations (FERPA/COPPA) in all communications.

package/config/templates/education-smb/team.json

@@ -0,0 +1,40 @@
+{
+  "name": "Education SMB Team",
+  "description": "Team specialized in curriculum development, content production, student engagement, and educational analytics.",
+  "members": [
+    {
+      "name": "Curriculum Designer (Alex)",
+      "role": "curriculum-designer",
+      "promptSource": {
+        "type": "template",
+        "alias": "curriculum-designer"
+      }
+    },
+    {
+      "name": "Content Creator (Casey)",
+      "role": "content-creator",
+      "promptSource": {
+        "type": "template",
+        "alias": "content-creator"
+      },
+      "skillOverrides": ["seo-blog-writer", "social-media-post"]
+    },
+    {
+      "name": "Student Engagement Manager (Sam)",
+      "role": "student-engagement-manager",
+      "promptSource": {
+        "type": "template",
+        "alias": "engagement-manager"
+      },
+      "skillOverrides": ["feedback-analyzer"]
+    },
+    {
+      "name": "Analytics Specialist (Skyler)",
+      "role": "analyst",
+      "promptSource": {
+        "type": "template",
+        "alias": "analytics-specialist"
+      }
+    }
+  ]
+}

package/config/templates/education-smb/template.json

@@ -0,0 +1,26 @@
+{
+  "id": "education-smb",
+  "name": "Education SMB Team",
+  "description": "A specialized team for small to medium education businesses, focusing on curriculum design, content creation, and student engagement.",
+  "version": "1.0.0",
+  "category": "education",
+  "targetVertical": "Education SMB",
+  "tags": ["education", "k12", "curriculum", "engagement"],
+  "crewlyVersion": ">=1.2.0",
+  "supportedRuntimes": ["claude-code"],
+  "teamConfigFile": "team.json",
+  "primaryWorkflow": "workflows/course-content-generation.yaml",
+  "qualityGatesFile": "quality-gates.yaml",
+  "learnedPatternsFile": "learned-patterns.json",
+  "knowledgeIndexFile": "knowledge/index.json",
+  "requiredSkills": [
+    "seo-blog-writer",
+    "social-media-post",
+    "feedback-analyzer"
+  ],
+  "optionalSkills": [
+    "daily-standup-report"
+  ],
+  "createdAt": "2026-03-04T00:00:00.000Z",
+  "updatedAt": "2026-03-04T00:00:00.000Z"
+}

package/config/templates/education-smb/workflows/course-content-generation.yaml

@@ -0,0 +1,44 @@
+id: course-content-generation
+name: Course Content Generation
+description: Workflow to design curriculum and generate lesson content.
+version: "1.0.0"
+
+steps:
+  - id: design-curriculum
+    order: 1
+    name: Curriculum Design
+    owner: "Curriculum Designer (Alex)"
+    description: Create the course outline and learning objectives.
+    outputs:
+      - name: course-outline
+        description: Structured curriculum outline
+        format: markdown
+    qualityGate: curriculum-quality
+
+  - id: generate-content
+    order: 2
+    name: Content Generation
+    owner: "Content Creator (Casey)"
+    description: Develop lesson materials based on the outline.
+    dependsOn: [design-curriculum]
+    inputs:
+      - name: course-outline
+        format: markdown
+        required: true
+    outputs:
+      - name: lesson-materials
+        description: Draft lesson content
+        format: markdown
+    qualityGate: content-quality
+
+  - id: review-and-finalize
+    order: 3
+    name: Final Review
+    owner: "Curriculum Designer (Alex)"
+    description: Review the generated content against the curriculum goals.
+    dependsOn: [generate-content]
+    inputs:
+      - name: lesson-materials
+        format: markdown
+        required: true
+    qualityGate: final-approval

package/config/templates/education-smb/workflows/reporting.yaml

@@ -0,0 +1,31 @@
+id: education-reporting
+name: Weekly/Monthly Reporting
+description: Generate comprehensive performance and operational reports.
+version: "1.0.0"
+
+steps:
+  - id: collect-metrics
+    order: 1
+    name: Metrics Collection
+    owner: "Analytics Specialist (Skyler)"
+    description: Gather data on student progress, engagement, and token usage.
+    outputs:
+      - name: raw-metrics
+        description: Collected metrics data
+        format: json
+
+  - id: generate-report
+    order: 2
+    name: Report Generation
+    owner: "Analytics Specialist (Skyler)"
+    description: Create a structured report summarizing the metrics and identifying trends.
+    dependsOn: [collect-metrics]
+    inputs:
+      - name: raw-metrics
+        format: json
+        required: true
+    outputs:
+      - name: final-report
+        description: Final weekly/monthly report
+        format: markdown
+    qualityGate: reporting-quality

package/config/templates/education-smb/workflows/student-communication.yaml

@@ -0,0 +1,44 @@
+id: student-communication
+name: Student Communication Workflow
+description: Automating onboarding and feedback loops for students.
+version: "1.0.0"
+
+steps:
+  - id: analyze-feedback
+    order: 1
+    name: Feedback Sentiment Analysis
+    owner: "Student Engagement Manager (Sam)"
+    description: Process recent student feedback to identify sentiment and common themes.
+    outputs:
+      - name: feedback-summary
+        description: Summary of student sentiment
+        format: json
+    requiredSkills:
+      - feedback-analyzer
+
+  - id: draft-announcement
+    order: 2
+    name: Draft Communication
+    owner: "Content Creator (Casey)"
+    description: Draft a newsletter or announcement based on feedback or upcoming events.
+    dependsOn: [analyze-feedback]
+    inputs:
+      - name: feedback-summary
+        format: json
+        required: true
+    outputs:
+      - name: draft-comm
+        description: Drafted student communication
+        format: markdown
+
+  - id: approve-and-send
+    order: 3
+    name: Communication Approval
+    owner: "Student Engagement Manager (Sam)"
+    description: Review and approve the communication for FERPA/COPPA compliance.
+    dependsOn: [draft-announcement]
+    inputs:
+      - name: draft-comm
+        format: markdown
+        required: true
+    qualityGate: compliance-check

package/config/templates/education-smb/workflows.yaml

@@ -0,0 +1,40 @@
+# Education SMB Workflows
+
+- id: course-content-generation
+  name: Course Content Generation
+  description: Workflow to design curriculum and generate lesson content.
+  steps:
+    - id: design-curriculum
+      name: Curriculum Design
+      owner: "Curriculum Designer (Alex)"
+    - id: generate-content
+      name: Content Generation
+      owner: "Content Creator (Casey)"
+    - id: final-review
+      name: Final Review
+      owner: "Curriculum Designer (Alex)"
+
+- id: student-communication
+  name: Student Communication Workflow
+  description: Automating onboarding and feedback loops for students.
+  steps:
+    - id: analyze-feedback
+      name: Feedback Sentiment Analysis
+      owner: "Student Engagement Manager (Sam)"
+    - id: draft-announcement
+      name: Draft Communication
+      owner: "Content Creator (Casey)"
+    - id: approve-and-send
+      name: Communication Approval
+      owner: "Student Engagement Manager (Sam)"
+
+- id: education-reporting
+  name: Weekly/Monthly Reporting
+  description: Generate comprehensive performance and operational reports.
+  steps:
+    - id: collect-metrics
+      name: Metrics Collection
+      owner: "Analytics Specialist (Skyler)"
+    - id: generate-report
+      name: Report Generation
+      owner: "Analytics Specialist (Skyler)"