@soulcraft/kits 1.0.0

package/kits/project-timeline/skills/dependency-analysis/SKILL.md

@@ -0,0 +1,176 @@
+---
+id: dependency-analysis
+name: dependency-analysis
+description: Identify and manage task/milestone dependencies in project timelines
+version: "1.0.0"
+type: invocable
+requiresVision: false
+requiresData: false
+---
+
+## Dependency Analysis Skill
+
+When the user invokes `/dependencies`, help them identify, map, and manage dependencies in their project timeline.
+
+### Invocation Patterns
+
+- `/dependencies` - Analyze all project dependencies
+- `/dependencies [task]` - Find dependencies for specific task
+- `/dependencies critical` - Identify critical path
+- `/dependencies risks` - Dependency risk analysis
+
+### Dependency Types
+
+**Finish-to-Start (FS)**
+- Most common
+- Task B can't start until Task A finishes
+- A → B
+
+**Start-to-Start (SS)**
+- Task B can't start until Task A starts
+- Both can run in parallel after
+- A ⇢ B
+
+**Finish-to-Finish (FF)**
+- Task B can't finish until Task A finishes
+- Can start independently
+- A ⇝ B
+
+**Start-to-Finish (SF)**
+- Task B can't finish until Task A starts
+- Rare, used for just-in-time
+
+### Output Format
+
+```markdown
+## Dependency Analysis: [Project Name]
+
+### Dependency Overview
+- **Total tasks**: X
+- **Dependencies identified**: X
+- **Critical path length**: X tasks
+- **Parallel paths**: X
+
+### Dependency Matrix
+
+| Task | Depends On | Type | Blocks | Lag |
+|------|------------|------|--------|-----|
+| A | - | - | B, C | - |
+| B | A | FS | D | - |
+| C | A | FS | D | 2 days |
+| D | B, C | FS | E | - |
+
+### Dependency Graph
+```
+[A] ───→ [B] ───→ [D] ───→ [E]
+  └────→ [C] ─────┘
+```
+
+### Critical Path
+The longest sequence determining minimum duration:
+
+**A → B → D → E** (X days total)
+
+| Task | Duration | Start | End | Float |
+|------|----------|-------|-----|-------|
+| A | 3d | Day 1 | Day 3 | 0 |
+| B | 5d | Day 4 | Day 8 | 0 |
+| D | 4d | Day 9 | Day 12 | 0 |
+| E | 2d | Day 13 | Day 14 | 0 |
+
+### Non-Critical Paths
+Tasks with float (can slip without affecting end date):
+
+| Path | Duration | Float |
+|------|----------|-------|
+| A → C → D | 10 days | 2 days |
+
+### Dependency Details
+
+#### [Task A]: [Task Name]
+**Predecessors**: None (start task)
+**Successors**: [B], [C]
+**Dependency Type**: -
+**Critical Path**: ✓
+
+#### [Task B]: [Task Name]
+**Predecessors**: [A] (FS)
+**Successors**: [D]
+**Dependency Type**: Finish-to-Start
+**Lag**: None
+**Critical Path**: ✓
+**Why this dependency**: [Explanation]
+
+[Continue for each task...]
+
+### Risk Analysis
+
+#### High-Risk Dependencies
+| Dependency | Risk | Impact | Mitigation |
+|------------|------|--------|------------|
+| A → B | Single resource | High | Cross-train |
+| C → D | External delivery | Medium | Early order |
+
+#### Bottlenecks
+Tasks with multiple predecessors (wait for all):
+- **[Task D]**: Waiting on [B] AND [C]
+  - Mitigation: [Strategy]
+
+#### Resource Conflicts
+Where same resource is needed on parallel tasks:
+- [Resource] needed for [Task X] and [Task Y]
+  - Resolution: [Strategy]
+
+### Optimization Opportunities
+
+**Can Run in Parallel**
+- [Task X] and [Task Y] currently sequential but could parallelize
+
+**Dependency Can Be Removed**
+- [Task A] → [Task B] dependency might not be necessary if [condition]
+
+**Fast-Tracking Options**
+- Start [Task B] when [Task A] is 80% complete
+```
+
+### Dependency Questions
+
+**To Identify Dependencies**
+- What must be complete before this can start?
+- What does this enable?
+- What external inputs are needed?
+- Who else needs to finish something?
+- What decisions must be made first?
+
+### Critical Path Method
+
+**Finding Critical Path**
+1. List all tasks with durations
+2. Map all dependencies
+3. Forward pass (earliest start/finish)
+4. Backward pass (latest start/finish)
+5. Calculate float (latest - earliest)
+6. Zero float = critical path
+
+**Why Critical Path Matters**
+- Determines minimum project duration
+- These tasks can't slip
+- Focus management attention
+- Buffer other paths, not this one
+
+### Managing Dependencies
+
+**Reduce Dependencies**
+- Question if dependency is real
+- Find alternative approaches
+- Pre-work to remove blockers
+
+**Fast-Tracking**
+- Overlap dependent tasks
+- Start before predecessor fully complete
+- Increases risk but saves time
+
+**Crashing**
+- Add resources to critical path tasks
+- Costs more but reduces duration
+- Only effective on critical path

package/kits/project-timeline/skills/identify-critical-path/SKILL.md

@@ -0,0 +1,37 @@
+---
+id: identify-critical-path
+name: Identify Critical Path
+description: Find the longest chain of dependent tasks
+version: "1.0.0"
+type: invocable
+requiresVision: false
+requiresData: false
+---
+
+## Identify Critical Path
+
+Find the longest chain of dependent tasks
+
+### Steps
+
+1. List all milestones and tasks with their durations
+2. Map all dependencies between items
+3. Calculate earliest start/finish for each item
+4. Calculate latest start/finish for each item
+5. Identify items where earliest = latest (zero slack)
+6. The chain of zero-slack items is the critical path
+7. Document the critical path in README
+8. Recommend protecting critical path activities
+
+### Expected Outputs
+
+- Critical path documentation
+- Risk assessment for critical items
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "critical path"
+- "longest path"
+- "what drives the deadline"
+- "schedule risk"

package/kits/project-timeline/skills/kit-expertise/SKILL.md

@@ -0,0 +1,81 @@
+---
+id: kit-expertise
+name: kit-expertise
+description: Domain expertise for Project Timeline / Roadmap - applied automatically when working in this kit
+version: "1.0.0"
+type: background
+requiresVision: false
+requiresData: false
+---
+
+## Your Role
+
+Project Planning Specialist helping you create realistic timelines and track project milestones
+
+## Your Expertise
+
+- Project timeline creation
+- Milestone definition
+- Dependency mapping
+- Critical path analysis
+- Resource allocation
+- Risk identification
+- Progress tracking
+- Schedule optimization
+
+## Your Approach
+
+Work alongside the user as a creative partner
+
+## Things to Avoid
+
+- Unrealistic timelines
+- Missing dependencies
+- Ignoring resource constraints
+- No buffer time for risks
+
+## Domain Knowledge
+
+### Key Terms
+
+**milestone**
+Significant checkpoint in the project
+
+**dependency**
+Task that must complete before another
+
+**critical path**
+Longest sequence of dependent tasks
+
+**buffer**
+Extra time for unexpected delays
+
+**deliverable**
+Tangible output of work
+
+**phase**
+Major section of the project
+
+**sprint**
+Time-boxed iteration of work
+
+**blocker**
+Issue preventing progress
+
+### Best Practices
+
+- Define clear milestones
+- Map all dependencies
+- Include buffer time
+- Identify the critical path
+- Assign owners to tasks
+- Review and adjust regularly
+
+### Common Mistakes to Avoid
+
+- No dependencies mapped
+- Overly optimistic estimates
+- Missing milestones
+- No buffer for risks
+- Ignoring resource constraints
+- Static plans that never update

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

@@ -0,0 +1,169 @@
+---
+id: milestone-planning
+name: milestone-planning
+description: Define meaningful project milestones with clear criteria
+version: "1.0.0"
+type: invocable
+requiresVision: false
+requiresData: false
+---
+
+## Milestone Planning Skill
+
+When the user invokes `/milestones`, help them define meaningful project milestones with clear success criteria.
+
+### Invocation Patterns
+
+- `/milestones` - Define milestones for current project
+- `/milestones [phase]` - Define milestones for specific phase
+- `/milestones review` - Review and validate existing milestones
+
+### What Makes a Good Milestone
+
+**Characteristics**
+- Clear, binary completion (done/not done)
+- Represents meaningful progress
+- Has specific deliverables
+- Enables celebration and assessment
+- Creates natural review point
+
+**Not Good Milestones**
+- "50% complete" (arbitrary percentage)
+- "Working on design" (activity, not outcome)
+- "Meeting held" (event, not achievement)
+
+### Output Format
+
+```markdown
+## Project Milestones: [Project Name]
+
+### Project Overview
+- **Project goal**: [Ultimate outcome]
+- **Timeline**: [Start] → [End]
+- **Total milestones**: [X]
+
+### Milestone Map
+```
+[MS1] ────→ [MS2] ────→ [MS3] ────→ [MS4] ────→ [Complete]
+  │           │           │           │
+ Week 2     Week 4      Week 8      Week 12
+```
+
+### Milestone Definitions
+
+#### M1: [Milestone Name]
+**Target Date**: [Date]
+**Status**: [Not Started / In Progress / Complete]
+
+**Description**:
+[What this milestone represents in 1-2 sentences]
+
+**Deliverables**:
+- [ ] [Deliverable 1]
+- [ ] [Deliverable 2]
+- [ ] [Deliverable 3]
+
+**Success Criteria**:
+- [How you know it's truly done]
+- [Measurable condition]
+
+**Dependencies**:
+- Depends on: [What must come first]
+- Enables: [What this unlocks]
+
+**Key Risks**:
+- [Risk 1]: [Mitigation]
+
+---
+
+#### M2: [Milestone Name]
+[Same format...]
+
+---
+
+### Milestone Summary Table
+| # | Milestone | Target | Deliverables | Dependencies |
+|---|-----------|--------|--------------|--------------|
+| 1 | [Name] | [Date] | [Count] | None |
+| 2 | [Name] | [Date] | [Count] | M1 |
+| 3 | [Name] | [Date] | [Count] | M2 |
+
+### Critical Path
+These milestones are on the critical path:
+- [M1] → [M2] → [M4]
+
+### Buffer Assessment
+- **Total project duration**: [X weeks]
+- **Buffer built in**: [Y weeks]
+- **Highest risk milestone**: [Name]
+```
+
+### Milestone Types
+
+**Phase Gates**
+- End of distinct project phase
+- Approval/review checkpoint
+- Go/no-go decision point
+
+**Deliverable Milestones**
+- Specific output complete
+- Product or artifact created
+- Can be demonstrated
+
+**Integration Milestones**
+- Components come together
+- Systems connected
+- End-to-end working
+
+**Validation Milestones**
+- Testing complete
+- Acceptance achieved
+- Quality confirmed
+
+### Planning Approach
+
+**Work Backward**
+1. Start with final deliverable
+2. Identify last milestone before delivery
+3. Work backward to start
+4. Validate timeline
+
+**Work Forward**
+1. Start with known first steps
+2. Identify natural phase boundaries
+3. Add integration/validation points
+4. Extend to completion
+
+### Milestone Quantity Guidelines
+
+| Project Length | Suggested Milestones |
+|---------------|---------------------|
+| 1-4 weeks | 2-3 |
+| 1-3 months | 4-6 |
+| 3-6 months | 6-10 |
+| 6-12 months | 8-15 |
+
+**Rule of Thumb**: Major milestone every 2-4 weeks
+
+### Success Criteria Writing
+
+**Good Criteria**
+- Binary (yes/no determinable)
+- Observable/demonstrable
+- Independent of opinion
+- Specific enough to test
+
+**Examples**
+- "API returns correct response for all test cases"
+- "Three stakeholders have signed off on design"
+- "System handles 100 concurrent users"
+- "All P1 bugs resolved"
+
+### Common Milestone Mistakes
+
+- Too many milestones (micromanaging)
+- Too few milestones (no checkpoints)
+- Vague criteria (hard to assess)
+- Missing dependencies
+- No buffer for delays
+- Activity-based not outcome-based

package/kits/project-timeline/skills/status-update/SKILL.md

@@ -0,0 +1,39 @@
+---
+id: status-update
+name: Create Status Update
+description: Generate a project status report
+version: "1.0.0"
+type: invocable
+requiresVision: false
+requiresData: false
+---
+
+## Create Status Update
+
+Generate a project status report
+
+### Steps
+
+1. Review current milestone status (On Track/At Risk/Blocked/Complete)
+2. Calculate overall project health
+3. Identify completed work since last update
+4. List in-progress work with expected completion
+5. Document any blockers or risks
+6. Update variance (planned vs. actual) for completed items
+7. Forecast impact on future milestones
+8. List action items and owners
+9. Generate summary for stakeholders
+
+### Expected Outputs
+
+- Status report
+- Updated milestone statuses
+- Action items
+
+### When to Use
+
+This workflow is helpful when the user mentions:
+- "status update"
+- "project status"
+- "where are we"
+- "progress report"