@soulcraft/kits 1.0.0

package/kits/product-requirements-doc/skills/user-stories/SKILL.md

@@ -0,0 +1,198 @@
+---
+id: user-stories
+name: user-stories
+description: Write effective user stories using INVEST criteria
+version: "1.0.0"
+type: invocable
+requiresVision: true
+requiresData: false
+---
+
+## User Stories Skill
+
+When the user invokes `/story`, help them write clear, effective user stories that meet INVEST criteria.
+
+### Invocation Patterns
+
+- `/story` - Write user story for current feature
+- `/story [feature]` - Write story for specific feature
+- `/story split` - Split large story into smaller stories
+- `/story review` - Review story for quality
+
+### User Story Format
+
+**Standard Template**
+```
+As a [type of user],
+I want [action/capability],
+So that [benefit/value].
+```
+
+**Extended Template**
+```
+As a [persona/role],
+I want to [action],
+So that [business value/user benefit].
+
+Acceptance Criteria:
+- Given [context], when [action], then [outcome]
+- [Additional criteria]
+```
+
+### INVEST Criteria
+
+**I - Independent**
+- Can be developed in any order
+- Doesn't depend on other stories
+- Self-contained value
+
+**N - Negotiable**
+- Details can be discussed
+- Not a rigid contract
+- Conversation starter
+
+**V - Valuable**
+- Delivers value to user or business
+- Outcome-focused, not task-focused
+- Worth doing on its own
+
+**E - Estimable**
+- Team can estimate effort
+- Clear enough to size
+- Understood well enough
+
+**S - Small**
+- Fits in a sprint
+- Typically 1-5 days of work
+- Can demonstrate completion
+
+**T - Testable**
+- Clear acceptance criteria
+- Know when it's done
+- Can verify functionality
+
+### Output Format
+
+```markdown
+## User Story: [Short Title]
+
+### Story
+**As a** [user type/persona],
+**I want to** [action/capability],
+**So that** [benefit/reason].
+
+### INVEST Check
+| Criterion | Status | Notes |
+|-----------|--------|-------|
+| Independent | ✓/⚠️/✗ | [Note] |
+| Negotiable | ✓/⚠️/✗ | [Note] |
+| Valuable | ✓/⚠️/✗ | [Note] |
+| Estimable | ✓/⚠️/✗ | [Note] |
+| Small | ✓/⚠️/✗ | [Note] |
+| Testable | ✓/⚠️/✗ | [Note] |
+
+### Acceptance Criteria
+
+**Scenario 1: [Scenario Name]**
+- Given [precondition]
+- When [action]
+- Then [expected result]
+- And [additional result]
+
+**Scenario 2: [Scenario Name]**
+- Given [precondition]
+- When [action]
+- Then [expected result]
+
+### Edge Cases
+- [Edge case 1]: [Expected behavior]
+- [Edge case 2]: [Expected behavior]
+
+### Out of Scope
+- [What this story does NOT include]
+- [Explicitly excluded functionality]
+
+### Technical Notes
+[Any technical considerations for implementation]
+
+### Dependencies
+- [Dependency 1]
+- [Dependency 2]
+
+### Story Points
+**Estimate**: [X points]
+**Rationale**: [Why this size]
+```
+
+### Writing Good Stories
+
+**Focus on User Value**
+- Bad: "As a developer, I want to refactor the database..."
+- Good: "As a user, I want faster search results..."
+
+**Be Specific About the "Who"**
+- Bad: "As a user..."
+- Good: "As a first-time buyer..."
+
+**Outcome Over Implementation**
+- Bad: "I want a dropdown menu..."
+- Good: "I want to filter products by category..."
+
+### Splitting Large Stories
+
+**Split by Workflow Step**
+- Registration, Profile creation, Email verification
+
+**Split by Operation**
+- Create, Read, Update, Delete
+
+**Split by Business Rule**
+- Basic validation, Complex validation, Edge cases
+
+**Split by Data Type**
+- Text posts, Image posts, Video posts
+
+**Split by Interface**
+- Web version, Mobile version, API
+
+**Split by Role**
+- Admin view, User view, Guest view
+
+### Common Anti-Patterns
+
+**Technical Stories**
+- "As a developer, I want to upgrade the framework..."
+- Fix: Frame in terms of user benefit
+
+**Compound Stories**
+- Story covers multiple features
+- Fix: Split into separate stories
+
+**Solution-Oriented**
+- "I want a blue button in the header..."
+- Fix: Focus on the problem/need
+
+**No Clear Value**
+- "I want to click a button..."
+- Fix: Explain the benefit
+
+### Story Examples
+
+**Good Example**
+```
+As a returning customer,
+I want to see my previous orders,
+So that I can quickly reorder items I've bought before.
+
+Acceptance Criteria:
+- Given I am logged in, when I click "Order History",
+  then I see my last 20 orders
+- Given I am viewing an order, when I click "Reorder",
+  then items are added to my cart
+```
+
+**Needs Improvement**
+```
+As a user, I want better performance.
+```
+Why: Not specific, not testable, who is the user?

package/kits/project-timeline/kit.json

@@ -0,0 +1,367 @@
+{
+  "$schema": "https://soulcraft.com/schemas/kit/v2.json",
+  "id": "project-timeline",
+  "type": "soulcraft",
+  "role": "primary",
+  "status": "released",
+  "name": "Project Timeline / Roadmap",
+  "description": "Visual project timeline with milestones and dependencies",
+  "longDescription": "Create an interactive project timeline showing milestones, deadlines, and dependencies. Perfect for project planning, product roadmaps, or event planning. Visualizes as a sequence in timeline layout with dependency tracking and risk documentation.",
+  "version": "1.0.0",
+  "author": {
+    "name": "Soulcraft Labs",
+    "email": "kits@soulcraft.com",
+    "url": "https://soulcraft.com"
+  },
+  "icon": "📅",
+  "tags": [
+    "project",
+    "timeline",
+    "planning",
+    "roadmap"
+  ],
+  "variables": [
+    {
+      "key": "projectName",
+      "label": "Project Name",
+      "description": "The name of your project",
+      "type": "string",
+      "required": true,
+      "example": "Product Launch"
+    },
+    {
+      "key": "startDate",
+      "label": "Start Date",
+      "description": "Project start date in ISO format",
+      "type": "string",
+      "required": false,
+      "example": "2025-01-01",
+      "default": ""
+    },
+    {
+      "key": "endDate",
+      "label": "End Date",
+      "description": "Project end date in ISO format",
+      "type": "string",
+      "required": false,
+      "example": "2025-06-01",
+      "default": ""
+    }
+  ],
+  "shared": {
+    "industry": "business-strategy",
+    "category": "business",
+    "aiExpertise": [
+      "Project planning and milestone setting",
+      "Dependency analysis and critical path",
+      "Risk identification and mitigation",
+      "Resource planning",
+      "Project status reporting"
+    ],
+    "dataModelHints": [
+      "event",
+      "task",
+      "concept",
+      "person"
+    ],
+    "dataModel": {
+      "entities": [
+        {
+          "domain": "task",
+          "type": "Event",
+          "description": "A unit of work with status, owner, and dates",
+          "products": {
+            "workshop": {
+              "view": "board",
+              "icon": "✅"
+            },
+            "academy": {
+              "mapsTo": "practice-session",
+              "assessable": true
+            }
+          }
+        },
+        {
+          "domain": "milestone",
+          "type": "Event",
+          "description": "A key project checkpoint or delivery date",
+          "products": {
+            "workshop": {
+              "view": "timeline",
+              "icon": "🏁"
+            },
+            "academy": {
+              "mapsTo": "practice-session",
+              "assessable": true
+            }
+          }
+        },
+        {
+          "domain": "phase",
+          "type": "Concept",
+          "description": "A named project phase grouping related tasks",
+          "products": {
+            "workshop": {
+              "view": "timeline",
+              "icon": "📅"
+            },
+            "academy": {
+              "mapsTo": "knowledge-unit",
+              "assessable": false
+            }
+          }
+        },
+        {
+          "domain": "deliverable",
+          "type": "Thing",
+          "description": "A tangible output produced by a task or phase",
+          "products": {
+            "workshop": {
+              "view": "gallery",
+              "icon": "📦"
+            },
+            "academy": {
+              "mapsTo": "resource",
+              "assessable": false
+            }
+          }
+        }
+      ],
+      "relationships": [
+        {
+          "from": "task",
+          "to": "task",
+          "verb": "DependsOn",
+          "description": "Task cannot start until this task is complete"
+        },
+        {
+          "from": "task",
+          "to": "milestone",
+          "verb": "Precedes",
+          "description": "Task must be done before this milestone"
+        },
+        {
+          "from": "task",
+          "to": "phase",
+          "verb": "PartOf",
+          "description": "Task belongs to this project phase"
+        }
+      ]
+    },
+    "suggestions": [
+      {
+        "label": "Add a milestone",
+        "prompt": "Help me add a new milestone to my project timeline"
+      },
+      {
+        "label": "Plan a phase",
+        "prompt": "Help me plan the tasks and deliverables for a project phase"
+      },
+      {
+        "label": "Identify risks",
+        "prompt": "Help me identify potential risks and create mitigation plans"
+      },
+      {
+        "label": "Track dependencies",
+        "prompt": "Help me map out dependencies between project tasks"
+      },
+      {
+        "label": "Status update",
+        "prompt": "Help me write a project status update based on current progress"
+      },
+      {
+        "label": "View timeline",
+        "prompt": "Show me my project timeline in the timeline view"
+      }
+    ]
+  },
+  "academy": {
+    "skillPath": "project-management",
+    "level": "beginner",
+    "learningObjectives": [
+      "Define project scope with a clear start milestone and measurable end criteria",
+      "Break work into phases, tasks, and milestones with realistic date estimates",
+      "Map task dependencies and identify the critical path through a project",
+      "Document project risks with probability, impact, and a concrete mitigation plan"
+    ],
+    "assessmentTypes": [
+      "portfolio",
+      "peer-review"
+    ],
+    "certificationSlug": "project-manager"
+  },
+  "workshop": {
+    "difficulty": "beginner",
+    "templateTier": 4,
+    "aiPersona": {
+      "role": "You are a project manager helping teams plan, track, and deliver projects on time with clear milestones, dependencies, and risk management.",
+      "expertise": [
+        "Project planning",
+        "Milestone setting",
+        "Dependency analysis",
+        "Risk management",
+        "Status reporting"
+      ],
+      "tone": "collaborator"
+    },
+    "workspaceConfig": {
+      "paradigm": "planner",
+      "defaultTab": "explore",
+      "defaultView": "timeline",
+      "defaultFile": "milestones/kickoff.md",
+      "layout": {
+        "leftDock": "files",
+        "rightDock": "views"
+      },
+      "onboarding": {
+        "showGuide": true,
+        "highlightFeatures": [
+          "timeline",
+          "board"
+        ],
+        "suggestedActions": [
+          "Define your key milestones first",
+          "Set dependencies between milestones",
+          "Use Timeline view to see the schedule",
+          "Track progress in Board view"
+        ]
+      }
+    },
+    "graphGuidance": {
+      "conceptCreation": {
+        "triggers": [
+          "When user creates a task or milestone",
+          "When user defines a phase",
+          "When user identifies a dependency",
+          "When user assigns an owner"
+        ],
+        "typeMapping": {
+          "task": "task",
+          "milestone": "event",
+          "phase": "concept",
+          "deliverable": "thing"
+        }
+      },
+      "relationshipPatterns": [
+        {
+          "from": "task",
+          "to": "task",
+          "verb": "dependsOn",
+          "description": "Task dependency"
+        },
+        {
+          "from": "task",
+          "to": "event",
+          "verb": "precedes",
+          "description": "Task before milestone"
+        },
+        {
+          "from": "task",
+          "to": "concept",
+          "verb": "partOf",
+          "description": "Task in phase"
+        },
+        {
+          "from": "task",
+          "to": "person",
+          "verb": "attributedTo",
+          "description": "Task owner"
+        }
+      ],
+      "rules": [
+        "Create task entities for work items",
+        "Track dependencies between tasks",
+        "Link tasks to their milestones",
+        "Note phase groupings"
+      ]
+    },
+    "qualityGates": {
+      "fileChecks": [
+        {
+          "path": "milestones/*.md",
+          "required": [
+            "Date",
+            "Status"
+          ],
+          "optional": [
+            "Depends On",
+            "Deliverable",
+            "Owner",
+            "Tasks"
+          ]
+        }
+      ],
+      "projectChecks": [
+        "Start and end milestones are defined",
+        "All milestones are connected (no orphans)",
+        "Critical path is documented",
+        "Each milestone has an owner",
+        "Status is current for all items"
+      ],
+      "exportReady": [
+        "All milestones have dates",
+        "Dependencies are complete",
+        "No blocked items without documented blockers",
+        "Status is up to date",
+        "Risks are documented with mitigations"
+      ]
+    },
+    "sampleData": {
+      "description": "Sample project timeline for a product launch",
+      "entities": [
+        {
+          "type": "event",
+          "name": "Project Kickoff",
+          "properties": {
+            "date": "2025-01-15",
+            "status": "done",
+            "description": "Initial project kickoff meeting with stakeholders.",
+            "milestone_type": "start"
+          }
+        },
+        {
+          "type": "event",
+          "name": "Design Complete",
+          "properties": {
+            "date": "2025-02-28",
+            "status": "in_progress",
+            "description": "UI/UX designs finalized and approved.",
+            "milestone_type": "milestone"
+          }
+        },
+        {
+          "type": "event",
+          "name": "Launch",
+          "properties": {
+            "date": "2025-04-30",
+            "status": "todo",
+            "description": "Product goes live.",
+            "milestone_type": "end"
+          }
+        }
+      ],
+      "relationships": [
+        {
+          "from": "Project Kickoff",
+          "verb": "precedes",
+          "to": "Design Complete"
+        },
+        {
+          "from": "Design Complete",
+          "verb": "precedes",
+          "to": "Launch"
+        }
+      ]
+    },
+    "deploy": {
+      "provider": "cloud-run",
+      "buildCommand": "npm run build",
+      "outputDir": "build",
+      "config": {
+        "port": 3000,
+        "memory": "512Mi"
+      },
+      "oneClickCommand": "gcloud run deploy"
+    }
+  }
+}

package/kits/project-timeline/skills/add-milestone/SKILL.md

@@ -0,0 +1,44 @@
+---
+id: add-milestone
+name: Add Milestone
+description: Add a new milestone to the project timeline
+version: "1.0.0"
+type: invocable
+parameters: [name, date]
+requiresVision: false
+requiresData: false
+---
+
+## Add Milestone
+
+Add a new milestone to the project timeline
+
+### Steps
+
+1. Define the milestone name and target date
+2. Describe the deliverable that marks completion
+3. Identify what must be complete before this milestone (dependencies)
+4. Identify what depends on this milestone
+5. Assign an owner responsible for the milestone
+6. Create the milestone file in milestones/ directory
+7. Add "precedes" or "depends-on" relationships
+8. Update the timeline view
+
+### Inputs Required
+
+- **name** (required): Milestone name
+- **date** (required): Target date
+- **dependsOn** (optional): Prerequisites
+
+### Expected Outputs
+
+- New milestone file
+- Updated timeline relationships
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "add milestone"
+- "new milestone"
+- "add checkpoint"
+- "add deadline"

package/kits/project-timeline/skills/add-task/SKILL.md

@@ -0,0 +1,43 @@
+---
+id: add-task
+name: Add Task
+description: Add a task under a milestone
+version: "1.0.0"
+type: invocable
+parameters: [taskName, milestone]
+requiresVision: false
+requiresData: false
+---
+
+## Add Task
+
+Add a task under a milestone
+
+### Steps
+
+1. Identify the parent milestone
+2. Define the task name and description
+3. Estimate effort (hours or days)
+4. Assign an owner
+5. Identify task dependencies
+6. Set start and end dates based on dependencies
+7. Add the task to the milestone file or create separate task file
+8. Update task relationships in the graph
+
+### Inputs Required
+
+- **taskName** (required): Task name
+- **milestone** (required): Parent milestone
+- **effort** (optional): Estimated effort
+
+### Expected Outputs
+
+- Task documented under milestone
+- Updated dependencies
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "add task"
+- "new task"
+- "break down milestone"

package/kits/project-timeline/skills/assess-risks/SKILL.md

@@ -0,0 +1,39 @@
+---
+id: assess-risks
+name: Assess Project Risks
+description: Identify and plan for schedule risks
+version: "1.0.0"
+type: invocable
+requiresVision: false
+requiresData: false
+---
+
+## Assess Project Risks
+
+Identify and plan for schedule risks
+
+### Steps
+
+1. Review all milestones and dependencies
+2. Identify external dependencies (other teams, vendors)
+3. Assess technical risks (unknowns, complexity)
+4. Evaluate resource risks (availability, skills)
+5. Rate each risk by probability and impact
+6. Create mitigation plan for high risks
+7. Add buffer where risks are highest
+8. Document risks in a risk register
+9. Plan regular risk review checkpoints
+
+### Expected Outputs
+
+- Risk register
+- Mitigation plans
+- Recommended buffers
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "risks"
+- "what could go wrong"
+- "schedule risks"
+- "blockers"