@soulcraft/kits 1.0.0

package/kits/organization-chart/kit.json

@@ -0,0 +1,349 @@
+{
+  "$schema": "https://soulcraft.com/schemas/kit/v2.json",
+  "id": "organization-chart",
+  "type": "soulcraft",
+  "role": "primary",
+  "status": "released",
+  "name": "Organization Chart",
+  "description": "Company or team hierarchy with reporting structure visualization",
+  "longDescription": "Create an interactive organization chart that visualizes reporting lines and team structure. Perfect for companies, departments, clubs, or any hierarchical organization. Auto-opens in org chart layout.",
+  "version": "1.0.0",
+  "author": {
+    "name": "Soulcraft Labs",
+    "email": "kits@soulcraft.com",
+    "url": "https://soulcraft.com"
+  },
+  "icon": "🏢",
+  "tags": [
+    "organization",
+    "hierarchy",
+    "team",
+    "management"
+  ],
+  "variables": [
+    {
+      "key": "companyName",
+      "label": "Organization Name",
+      "description": "The name of your organization or company",
+      "type": "string",
+      "required": true,
+      "example": "Acme Corp"
+    },
+    {
+      "key": "industry",
+      "label": "Industry",
+      "description": "Your industry sector",
+      "type": "string",
+      "required": false,
+      "example": "Technology"
+    }
+  ],
+  "shared": {
+    "industry": "business-strategy",
+    "category": "business",
+    "glossary": {
+      "span of control": "The number of direct reports a manager oversees",
+      "reporting line": "The chain of authority from an employee to their manager"
+    },
+    "aiExpertise": [
+      "Organizational design principles",
+      "Team structure and hierarchy",
+      "Role definition and responsibilities",
+      "Reporting relationships",
+      "Org chart visualization"
+    ],
+    "dataModelHints": [
+      "person",
+      "thing",
+      "topic"
+    ],
+    "dataModel": {
+      "entities": [
+        {
+          "domain": "person",
+          "type": "Person",
+          "description": "An individual with a role, department, and reporting line",
+          "products": {
+            "workshop": {
+              "view": "gallery",
+              "icon": "👤"
+            },
+            "academy": {
+              "mapsTo": "learning-subject",
+              "assessable": false
+            }
+          }
+        },
+        {
+          "domain": "team",
+          "type": "Concept",
+          "description": "A team or department grouping multiple roles",
+          "products": {
+            "workshop": {
+              "view": "tree",
+              "icon": "👥"
+            },
+            "academy": {
+              "mapsTo": "knowledge-unit",
+              "assessable": false
+            }
+          }
+        },
+        {
+          "domain": "department",
+          "type": "Concept",
+          "description": "A division or department within the organisation",
+          "products": {
+            "workshop": {
+              "view": "tree",
+              "icon": "🏢"
+            },
+            "academy": {
+              "mapsTo": "knowledge-unit",
+              "assessable": false
+            }
+          }
+        }
+      ],
+      "relationships": [
+        {
+          "from": "person",
+          "to": "person",
+          "verb": "ReportsTo",
+          "description": "Direct reporting relationship"
+        },
+        {
+          "from": "person",
+          "to": "team",
+          "verb": "MemberOf",
+          "description": "Person is a member of this team"
+        },
+        {
+          "from": "team",
+          "to": "department",
+          "verb": "PartOf",
+          "description": "Team belongs to this department"
+        },
+        {
+          "from": "person",
+          "to": "person",
+          "verb": "WorksWith",
+          "description": "Cross-functional collaboration"
+        }
+      ]
+    },
+    "suggestions": [
+      {
+        "label": "Add a team member",
+        "prompt": "Help me add a new team member to the organization chart"
+      },
+      {
+        "label": "Define a department",
+        "prompt": "Help me create and structure a new department"
+      },
+      {
+        "label": "Map reporting lines",
+        "prompt": "Help me define reporting relationships between team members"
+      },
+      {
+        "label": "Plan restructuring",
+        "prompt": "Help me plan an organizational restructuring"
+      },
+      {
+        "label": "Identify gaps",
+        "prompt": "Analyze my org chart and identify potential gaps or redundancies"
+      },
+      {
+        "label": "View org chart",
+        "prompt": "Show me my organization chart in the tree view"
+      }
+    ]
+  },
+  "academy": {
+    "skillPath": "organizational-design",
+    "level": "intermediate",
+    "learningObjectives": [
+      "Map all roles with clear reporting relationships leaving no orphan nodes",
+      "Analyse spans of control and identify where reporting ratios are too wide or narrow",
+      "Define role responsibilities that eliminate overlap and cover all functions",
+      "Design a restructured hierarchy that improves decision-making speed or communication flow",
+      "Document cross-functional collaboration relationships beyond the formal reporting chain"
+    ],
+    "assessmentTypes": [
+      "portfolio",
+      "peer-review"
+    ],
+    "certificationSlug": "org-designer"
+  },
+  "workshop": {
+    "difficulty": "beginner",
+    "templateTier": 4,
+    "aiPersona": {
+      "role": "You are an expert organizational designer helping teams map, visualize, and optimize their reporting structures and team hierarchies.",
+      "expertise": [
+        "Organizational design and restructuring",
+        "Team hierarchy and reporting structures",
+        "Role definition and job design",
+        "Span of control analysis",
+        "Cross-functional collaboration mapping"
+      ],
+      "tone": "mentor"
+    },
+    "workspaceConfig": {
+      "paradigm": "analyst",
+      "defaultTab": "explore",
+      "defaultView": "tree",
+      "layout": {
+        "leftDock": "concepts",
+        "rightDock": "views"
+      },
+      "onboarding": {
+        "showGuide": true,
+        "highlightFeatures": [
+          "graph",
+          "export"
+        ],
+        "suggestedActions": [
+          "Add team members and their roles",
+          "Use Tree view to see reporting hierarchy",
+          "Track reporting relationships",
+          "Use Graph view for cross-functional teams"
+        ]
+      }
+    },
+    "graphGuidance": {
+      "conceptCreation": {
+        "triggers": [
+          "When user adds a person or role",
+          "When user creates a team or department",
+          "When user defines reporting relationship",
+          "When user notes cross-functional collaboration"
+        ],
+        "typeMapping": {
+          "person": "person",
+          "role": "role",
+          "team": "organization",
+          "department": "organization"
+        }
+      },
+      "relationshipPatterns": [
+        {
+          "from": "person",
+          "to": "person",
+          "verb": "reportsTo",
+          "description": "Direct reporting"
+        },
+        {
+          "from": "person",
+          "to": "organization",
+          "verb": "memberOf",
+          "description": "Team membership"
+        },
+        {
+          "from": "organization",
+          "to": "organization",
+          "verb": "partOf",
+          "description": "Department structure"
+        },
+        {
+          "from": "person",
+          "to": "person",
+          "verb": "worksWith",
+          "description": "Cross-functional"
+        }
+      ],
+      "rules": [
+        "Create person entities for each role holder",
+        "Track reporting relationships",
+        "Group people into teams",
+        "Note cross-functional collaborations"
+      ]
+    },
+    "qualityGates": {
+      "fileChecks": [
+        {
+          "path": "roles/*.md",
+          "required": [
+            "Reports To",
+            "Responsibilities"
+          ],
+          "optional": [
+            "Manages",
+            "Skills Required",
+            "Goals"
+          ]
+        }
+      ],
+      "projectChecks": [
+        "All roles have clear reporting relationships",
+        "No orphan nodes (disconnected roles)",
+        "No circular reporting chains",
+        "Manager spans of control are documented",
+        "Role responsibilities are defined"
+      ],
+      "exportReady": [
+        "All positions have role descriptions",
+        "Reporting relationships are complete",
+        "No placeholder names remain",
+        "Department structure is clear"
+      ]
+    },
+    "sampleData": {
+      "description": "Sample organization chart for a technology startup",
+      "entities": [
+        {
+          "type": "person",
+          "name": "Sarah Chen",
+          "properties": {
+            "role": "CEO",
+            "department": "Executive",
+            "hireDate": "2020-03-15",
+            "description": "Founder and Chief Executive Officer. Sets company vision and strategy.",
+            "status": "active"
+          }
+        },
+        {
+          "type": "person",
+          "name": "Michael Rodriguez",
+          "properties": {
+            "role": "CTO",
+            "department": "Engineering",
+            "hireDate": "2020-04-01",
+            "description": "Chief Technology Officer. Leads technical strategy and architecture.",
+            "status": "active"
+          }
+        },
+        {
+          "type": "organization",
+          "name": "Engineering",
+          "properties": {
+            "headcount": 5,
+            "description": "Technology and development department."
+          }
+        }
+      ],
+      "relationships": [
+        {
+          "from": "Michael Rodriguez",
+          "verb": "reportsTo",
+          "to": "Sarah Chen"
+        },
+        {
+          "from": "Michael Rodriguez",
+          "verb": "memberOf",
+          "to": "Engineering"
+        }
+      ]
+    },
+    "deploy": {
+      "provider": "cloud-run",
+      "buildCommand": "npm run build",
+      "outputDir": "build",
+      "config": {
+        "port": 3000,
+        "memory": "512Mi"
+      },
+      "oneClickCommand": "gcloud run deploy"
+    }
+  }
+}

package/kits/organization-chart/skills/add-role/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: Add New Role
+description: Add a new role to the organization chart
+type: invocable
+version: "1.0.0"
+parameters: [title, reportsTo]
+---
+
+## Add New Role
+
+Add a new role to the organization chart
+
+### Steps
+
+1. Define the role title following naming conventions
+2. Identify the reporting manager
+3. Write a clear role description with key responsibilities
+4. Determine if this is a new position or backfill
+5. Create the role file in roles/ directory
+6. Add the "reportsTo" relationship
+7. Update the knowledge graph with the new node
+8. If manager role, define expected span of control
+
+### Inputs Required
+
+- **title** (required): Role title
+- **reportsTo** (required): Who this role reports to
+- **isManager** (optional): Does this role have direct reports?
+
+### Expected Outputs
+
+- New role file in roles/
+- Updated org relationships
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "add role"
+- "new position"
+- "add team member"
+- "new hire"

package/kits/organization-chart/skills/analyze-span/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: Analyze Span of Control
+description: Analyze spans of control across the organization
+type: invocable
+version: "1.0.0"
+---
+
+## Analyze Span of Control
+
+Analyze spans of control across the organization
+
+### Steps
+
+1. Identify all people managers in the org
+2. Count direct reports for each manager
+3. Flag spans too wide (>12 reports)
+4. Flag spans too narrow (<3 reports)
+5. Calculate average span of control
+6. Identify potential rebalancing opportunities
+7. Consider role complexity in assessment
+8. Generate recommendations for optimal spans
+
+### Expected Outputs
+
+- Span of control analysis report
+- Rebalancing recommendations
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "span of control"
+- "too many reports"
+- "management layers"
+- "org efficiency"

package/kits/organization-chart/skills/create-raci/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: Create RACI Matrix
+description: Define responsibility assignment for a process or project
+type: invocable
+version: "1.0.0"
+parameters: [processName, activities]
+---
+
+## Create RACI Matrix
+
+Define responsibility assignment for a process or project
+
+### Steps
+
+1. Identify the process or project scope
+2. List all key activities/decisions
+3. List all roles/people involved
+4. For each activity, assign exactly one Accountable (A)
+5. Assign Responsible (R) - who does the work
+6. Assign Consulted (C) - who provides input
+7. Assign Informed (I) - who needs to know
+8. Validate: each row has exactly one A, at least one R
+9. Review with stakeholders for alignment
+10. Document the RACI matrix
+
+### Inputs Required
+
+- **processName** (required): Name of the process or project
+- **activities** (required): List of activities/decisions
+
+### Expected Outputs
+
+- RACI matrix document
+- Role clarity for the process
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "create RACI"
+- "who is responsible"
+- "accountability"
+- "decision rights"

package/kits/organization-chart/skills/kit-expertise/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: kit-expertise
+description: Domain expertise for Organization Chart - applied automatically when working in this kit
+type: background
+version: "1.0.0"
+---
+
+## Your Role
+
+Organizational Design Consultant helping you map and understand organizational structure and reporting relationships
+
+## Your Expertise
+
+- Organizational structure design
+- Reporting hierarchy mapping
+- Role and responsibility definition
+- Team composition analysis
+- Span of control optimization
+- Cross-functional relationships
+- Org chart visualization
+- Succession planning
+
+## Your Approach
+
+Assist the user with their requests efficiently
+
+## Things to Avoid
+
+- Creating unclear reporting lines
+- Missing key roles
+- Overly complex structures
+- Ignoring cross-functional relationships
+
+## Domain Knowledge
+
+### Key Terms
+
+**reporting line**
+Direct management relationship
+
+**span of control**
+Number of direct reports per manager
+
+**dotted line**
+Secondary or informal reporting
+
+**direct report**
+Employee reporting to a manager
+
+**functional team**
+Group organized by expertise
+
+**cross-functional**
+Spanning multiple departments
+
+**matrix organization**
+Dual reporting structure
+
+**organizational layer**
+Level in the hierarchy
+
+### Best Practices
+
+- Show clear reporting lines
+- Include all key roles
+- Indicate team boundaries
+- Note cross-functional relationships
+- Keep structure as flat as practical
+- Update when changes occur
+
+### Common Mistakes to Avoid
+
+- Unclear reporting relationships
+- Too many organizational layers
+- Missing roles or positions
+- Outdated org charts
+- No cross-functional visibility
+- Ignoring informal relationships