Add 3 new skills (basecamp, brainstorming, plan-writing) and update agent model

- basecamp: Basecamp project management via MCP (todos, kanban, projects)
- brainstorming: General-purpose ideation with Anytype save
- plan-writing: Project planning with templates (kickoff, stakeholders, tasks, risks)
- Update agent model from GPT-4o to minimax-m2.1-free
- Update README with new skills
This commit is contained in:
m3tm3re
2026-01-13 14:50:04 +01:00
parent d53031bfc9
commit cfa0f8f942
15 changed files with 1741 additions and 6 deletions

165
skill/plan-writing/SKILL.md Normal file
View File

@@ -0,0 +1,165 @@
---
name: plan-writing
description: "Transform ideas into comprehensive, actionable project plans with templates. Use when: (1) creating project kickoff documents, (2) structuring new projects, (3) building detailed task breakdowns, (4) documenting project scope and stakeholders, (5) setting up project for execution. Triggers: project plan, kickoff document, plan out, structure project, project setup, create plan for, what do I need to start."
compatibility: opencode
---
# Plan Writing
Transform brainstormed ideas into comprehensive, actionable project plans using modular templates.
## Quick Reference
| Project Type | Templates to Use |
|--------------|------------------|
| Solo, <2 weeks | project-brief, todo-structure |
| Solo, >2 weeks | project-brief, todo-structure, risk-register |
| Team, any size | project-kickoff, stakeholder-map, todo-structure, risk-register |
## Process
### 1. Intake
Gather initial context:
- What project are we planning?
- Check for existing brainstorming output in `docs/brainstorms/`
- If starting fresh, gather basic context first
### 2. Scope Assessment
Ask these questions (one at a time):
1. **Solo or team project?**
- Solo → lighter documentation
- Team → need alignment docs (kickoff, stakeholders)
2. **Rough duration estimate?**
- <2 weeks → skip risk register
- >2 weeks → include risk planning
3. **Known deadline or flexible?**
- Hard deadline → prioritize milestone planning
- Flexible → focus on phased approach
4. **Which PARA area does this belong to?** (optional)
- Helps categorization and later task-management integration
### 3. Component Selection
Based on scope, select appropriate templates:
```
"Based on [team project, 6 weeks], I'll include:
✓ Project Kickoff (team alignment)
✓ Stakeholder Map (communication planning)
✓ Todo Structure (task breakdown)
✓ Risk Register (duration >2 weeks)
Shall I proceed with this structure?"
```
See [references/component-guide.md](references/component-guide.md) for selection logic.
### 4. Draft Generation
For each selected template:
1. Load template from `assets/templates/`
2. Fill with project-specific content
3. Present each major section for validation
4. Adjust based on feedback
Work through templates in this order:
1. Kickoff/Brief (establishes context)
2. Stakeholders (who's involved)
3. Todos (what needs doing)
4. Risks (what could go wrong)
### 5. Output
Generate final documents:
- Create `docs/plans/<project-name>/` directory
- Write each component as separate file
- Create `index.md` linking all components
```
docs/plans/<project-name>/
├── index.md # Links to all components
├── kickoff.md # or brief.md for solo projects
├── stakeholders.md # if team project
├── tasks.md # task breakdown
├── risks.md # if >2 weeks duration
└── updates/ # for future progress updates
└── YYYY-MM-DD.md
```
### 6. Handoff (Optional)
After plan is complete, offer next steps:
> "Ready to create this project in Basecamp? I can:
> - Create todo lists from the task structure
> - Set up card table columns from phases
> - Add initial cards/todos with due dates"
This triggers the basecamp skill for execution.
## Templates
All templates in `assets/templates/`:
| Template | Purpose | When to Include |
|----------|---------|-----------------|
| project-kickoff.md | Comprehensive 8-section kickoff | Team projects |
| project-brief.md | 1-page summary | Solo or simple projects |
| stakeholder-map.md | Who needs what, when | Team projects |
| risk-register.md | Risks and mitigations | Projects >2 weeks |
| todo-structure.md | Hierarchical task breakdown | Always |
| progress-update.md | Status update template | For ongoing tracking |
## PARA Integration (Optional)
If user wants PARA integration:
1. Prompt for Area assignment (from their defined Areas)
2. Can trigger task-management skill to create Anytype entries
3. Include Area reference in kickoff/brief document
This is optional - not all users use PARA.
## Integration with Other Skills
| From | To plan-writing | Output |
|------|-----------------|--------|
| brainstorming | Decision/context | Informs kickoff scope |
| plan-writing | → basecamp | Todo lists, cards |
| plan-writing | → task-management | Anytype tasks (optional) |
## Example Workflow
```
User: "Create a project plan for launching the Q2 training program"
AI: "I'll help structure this project. First, a few questions:
Is this a solo project or will others be involved?"
User: "Team - 3 people"
AI: "Duration estimate?
a) Less than 2 weeks
b) 2-4 weeks
c) More than a month"
User: "B - about 3 weeks"
AI: "Got it. For a 3-week team project, I'll include:
✓ Project Kickoff (team alignment)
✓ Stakeholder Map (communication)
✓ Todo Structure (task breakdown)
✓ Risk Register (3 weeks warrants this)
Shall I proceed?"
User: "Yes"
AI: [Proceeds through each template, filling with project details]
```

View File

@@ -0,0 +1,89 @@
# Progress Update: [Project Name]
**Period**: [Date] to [Date]
**Author**: [Name]
**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked
---
## Summary
[2-3 sentence executive summary: Where are we, what's the headline?]
**Overall Progress**: [X]% complete
---
## Completed This Period
- [x] [Task/milestone completed] - [Impact or note]
- [x] [Task completed]
- [x] [Task completed]
**Highlights**:
- [Notable achievement or win]
---
## In Progress
| Task | Owner | Progress | Expected Complete |
|------|-------|----------|-------------------|
| [Task 1] | [Name] | [X]% | [Date] |
| [Task 2] | [Name] | [X]% | [Date] |
| [Task 3] | [Name] | [X]% | [Date] |
---
## Blockers & Risks
### Active Blockers
| Blocker | Impact | Owner | Action Needed | ETA |
|---------|--------|-------|---------------|-----|
| [Blocker 1] | [High/Med/Low] | [Name] | [What's needed] | [Date] |
### Emerging Risks
| Risk | Probability | Mitigation |
|------|-------------|------------|
| [Risk 1] | [H/M/L] | [Action] |
---
## Next Period Plan
**Focus**: [Main focus for next period]
| Priority | Task | Owner | Target Date |
|----------|------|-------|-------------|
| 1 | [Highest priority task] | [Name] | [Date] |
| 2 | [Second priority] | [Name] | [Date] |
| 3 | [Third priority] | [Name] | [Date] |
---
## Metrics
| Metric | Target | Current | Trend |
|--------|--------|---------|-------|
| [Metric 1] | [X] | [Y] | ↑/↓/→ |
| [Metric 2] | [X] | [Y] | ↑/↓/→ |
| Tasks Complete | [X] | [Y] | ↑ |
---
## Decisions Needed
- [ ] [Decision 1]: [Options and recommendation] - Need by: [Date]
- [ ] [Decision 2]: [Context] - Need by: [Date]
---
## Notes / Context
[Any additional context, changes in scope, stakeholder feedback, etc.]
---
*Next update: [Date]*

View File

@@ -0,0 +1,48 @@
# Project Brief: [Project Name]
**Owner**: [Name]
**Timeline**: [Start Date] → [Target Date]
**Area**: [PARA Area, if applicable]
## Goal
[One clear sentence: What will be true when this project is complete?]
## Success Criteria
How we'll know it's done:
- [ ] [Criterion 1 - specific and measurable]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Scope
**Included**:
- [Deliverable 1]
- [Deliverable 2]
**Not Included**:
- [Exclusion 1]
## Key Milestones
| Milestone | Target Date | Status |
|-----------|-------------|--------|
| [Milestone 1] | [Date] | [ ] |
| [Milestone 2] | [Date] | [ ] |
| [Complete] | [Date] | [ ] |
## Initial Tasks
1. [ ] [First task to start] - Due: [Date]
2. [ ] [Second task]
3. [ ] [Third task]
## Notes
[Any context, constraints, or references worth capturing]
---
*Created: [Date]*

View File

@@ -0,0 +1,106 @@
# Project Kickoff: [Project Name]
## 1. Project Essentials
| Field | Value |
|-------|-------|
| **Project Name** | [Name] |
| **Owner** | [Name] |
| **Start Date** | [YYYY-MM-DD] |
| **Target Completion** | [YYYY-MM-DD] |
| **PARA Area** | [Area, if applicable] |
### Overview
[2-3 sentence description of what this project will accomplish and why it matters.]
## 2. Goals and Success Criteria
**Primary Goal**: [One sentence describing the end state - what does "done" look like?]
**Success Criteria**:
- [ ] [Measurable criterion 1]
- [ ] [Measurable criterion 2]
- [ ] [Measurable criterion 3]
**Out of Scope** (explicitly):
- [Item that might be assumed but is NOT included]
- [Another exclusion]
## 3. Stakeholders
| Role | Person | Involvement Level |
|------|--------|-------------------|
| Project Owner | [Name] | High - decisions |
| Core Team | [Names] | High - execution |
| Informed | [Names] | Low - updates only |
| Approver | [Name, if any] | Medium - sign-off |
## 4. Timeline and Milestones
| Milestone | Target Date | Dependencies | Owner |
|-----------|-------------|--------------|-------|
| [Milestone 1] | [Date] | None | [Who] |
| [Milestone 2] | [Date] | Milestone 1 | [Who] |
| [Milestone 3] | [Date] | Milestone 2 | [Who] |
| **Project Complete** | [Date] | All above | [Owner] |
### Key Dates
- **Kickoff**: [Date]
- **First Review**: [Date]
- **Final Deadline**: [Date]
## 5. Scope
### In Scope
- [Deliverable 1]: [Brief description]
- [Deliverable 2]: [Brief description]
- [Deliverable 3]: [Brief description]
### Out of Scope
- [Explicitly excluded item 1]
- [Explicitly excluded item 2]
### Assumptions
- [Assumption 1 - e.g., "Budget approved"]
- [Assumption 2 - e.g., "Team available full-time"]
## 6. Risks
| Risk | Probability | Impact | Mitigation | Owner |
|------|-------------|--------|------------|-------|
| [Risk 1] | H/M/L | H/M/L | [Plan] | [Who] |
| [Risk 2] | H/M/L | H/M/L | [Plan] | [Who] |
*See detailed risk register if needed: [link to risks.md]*
## 7. Communication Plan
| What | Audience | Frequency | Channel | Owner |
|------|----------|-----------|---------|-------|
| Status Update | All stakeholders | Weekly | [Email/Basecamp] | [Who] |
| Team Sync | Core team | [Daily/2x week] | [Meeting/Slack] | [Who] |
| Milestone Review | Approvers | At milestone | [Meeting] | [Who] |
### Escalation Path
1. First: [Team lead/Owner]
2. Then: [Manager/Sponsor]
3. Finally: [Executive, if applicable]
## 8. Next Steps
Immediate actions to kick off the project:
- [ ] [Action 1] - @[owner] - Due: [date]
- [ ] [Action 2] - @[owner] - Due: [date]
- [ ] [Action 3] - @[owner] - Due: [date]
---
*Document created: [Date]*
*Last updated: [Date]*

View File

@@ -0,0 +1,104 @@
# Risk Register: [Project Name]
## Risk Summary
| ID | Risk | Probability | Impact | Risk Score | Status |
|----|------|-------------|--------|------------|--------|
| R1 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
| R2 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
| R3 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
**Risk Score**: Probability × Impact (H×H=Critical, H×M or M×H=High, M×M=Medium, others=Low)
---
## Detailed Risk Analysis
### R1: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1 to reduce probability or impact]
- [Action 2]
**Contingency Plan** (if risk occurs):
- [Fallback action 1]
- [Fallback action 2]
**Owner**: [Name]
**Review Date**: [Date]
---
### R2: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1]
- [Action 2]
**Contingency Plan**:
- [Fallback action]
**Owner**: [Name]
**Review Date**: [Date]
---
### R3: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1]
- [Action 2]
**Contingency Plan**:
- [Fallback action]
**Owner**: [Name]
**Review Date**: [Date]
---
## Risk Categories
| Category | Examples |
|----------|----------|
| **Technical** | Technology doesn't work, integration issues, performance |
| **Resource** | Key person unavailable, skill gaps, overcommitment |
| **External** | Vendor delays, regulatory changes, dependencies |
| **Schedule** | Delays, unrealistic timeline, competing priorities |
| **Budget** | Cost overruns, funding cuts, unexpected expenses |
## Review Schedule
- **Weekly**: Quick scan of high risks
- **Bi-weekly**: Full risk register review
- **At milestones**: Comprehensive reassessment
---
*Created: [Date]*
*Last reviewed: [Date]*
*Next review: [Date]*

View File

@@ -0,0 +1,72 @@
# Stakeholder Map: [Project Name]
## Stakeholder Matrix
| Stakeholder | Role | Interest Level | Influence | Information Needs |
|-------------|------|----------------|-----------|-------------------|
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
## Communication Plan by Stakeholder
### [Stakeholder 1: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often: daily, weekly, at milestones] |
| **Channel** | [Email, Basecamp, meeting, Slack] |
| **Format** | [Brief update, detailed report, presentation] |
| **Owner** | [Who communicates with them] |
### [Stakeholder 2: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often] |
| **Channel** | [Preferred channel] |
| **Format** | [Format preference] |
| **Owner** | [Who communicates] |
### [Stakeholder 3: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often] |
| **Channel** | [Preferred channel] |
| **Format** | [Format preference] |
| **Owner** | [Who communicates] |
## RACI Matrix
| Decision/Task | [Person 1] | [Person 2] | [Person 3] | [Person 4] |
|---------------|------------|------------|------------|------------|
| [Decision 1] | R | A | C | I |
| [Decision 2] | I | R | A | C |
| [Task 1] | R | I | I | A |
**Legend**:
- **R** = Responsible (does the work)
- **A** = Accountable (final decision maker)
- **C** = Consulted (input required)
- **I** = Informed (kept updated)
## Escalation Path
1. **First Level**: [Name/Role] - for [types of issues]
2. **Second Level**: [Name/Role] - if unresolved in [timeframe]
3. **Executive**: [Name/Role] - for [critical blockers only]
## Notes
- [Any stakeholder-specific considerations]
- [Political or relationship notes]
- [Historical context if relevant]
---
*Created: [Date]*
*Last updated: [Date]*

View File

@@ -0,0 +1,94 @@
# Task Structure: [Project Name]
## Overview
| Metric | Value |
|--------|-------|
| **Total Tasks** | [X] |
| **Phases** | [Y] |
| **Timeline** | [Start] → [End] |
---
## Phase 1: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 1.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
| 1.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 1.1 | [ ] |
| 1.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Phase 2: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 2.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | Phase 1 | [ ] |
| 2.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 2.1 | [ ] |
| 2.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Phase 3: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 3.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | Phase 2 | [ ] |
| 3.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 3.1 | [ ] |
| 3.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | 3.1 | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Unphased / Ongoing Tasks
| # | Task | Owner | Frequency | Notes |
|---|------|-------|-----------|-------|
| O.1 | [Recurring task] | [Name] | Weekly | [Notes] |
| O.2 | [Monitoring task] | [Name] | Daily | [Notes] |
---
## Dependencies Summary
```
Phase 1 ──────► Phase 2 ──────► Phase 3
│ │
├── 1.1 ► 1.2 ├── 2.1 ► 2.2
└── 1.3 └── 2.3 (parallel)
```
## Milestone Checklist
- [ ] **Milestone 1**: [Name] - [Date]
- [ ] [Required task 1.1]
- [ ] [Required task 1.2]
- [ ] **Milestone 2**: [Name] - [Date]
- [ ] [Required task 2.1]
- [ ] [Required task 2.2]
- [ ] **Project Complete** - [Date]
- [ ] All phases complete
- [ ] Success criteria met
- [ ] Handoff complete
---
*Created: [Date]*
*Last updated: [Date]*

View File

@@ -0,0 +1,117 @@
# Component Selection Guide
Decision matrix for which templates to include based on project characteristics.
## Decision Matrix
| Question | If Yes | If No |
|----------|--------|-------|
| Team project (>1 person)? | +kickoff, +stakeholders | Use brief instead of kickoff |
| Duration >2 weeks? | +risk-register | Skip risks |
| External stakeholders? | +stakeholders (detailed) | Stakeholders optional |
| Complex dependencies? | +detailed todos with deps | Simple todo list |
| Ongoing tracking needed? | +progress-update template | One-time plan |
## Quick Selection by Project Type
### Solo, Short (<2 weeks)
```
✓ project-brief.md
✓ todo-structure.md
```
### Solo, Medium (2-4 weeks)
```
✓ project-brief.md
✓ todo-structure.md
✓ risk-register.md
```
### Solo, Long (>4 weeks)
```
✓ project-brief.md (or kickoff for complex)
✓ todo-structure.md
✓ risk-register.md
✓ progress-update.md (for self-tracking)
```
### Team, Any Duration
```
✓ project-kickoff.md (always for team alignment)
✓ stakeholder-map.md
✓ todo-structure.md
✓ risk-register.md (if >2 weeks)
✓ progress-update.md (for status updates)
```
## Template Purposes
### project-kickoff.md
Full 8-section document for team alignment:
1. Project essentials (name, owner, dates)
2. Goals and success criteria
3. Stakeholders overview
4. Timeline and milestones
5. Scope (in/out)
6. Risks overview
7. Communication plan
8. Next steps
**Use when**: Multiple people need alignment on what/why/how.
### project-brief.md
1-page summary for simpler projects:
- Goal statement
- Success criteria
- Key milestones
- Initial tasks
**Use when**: Solo project or simple scope that doesn't need formal kickoff.
### stakeholder-map.md
Communication matrix:
- Who needs information
- What they need to know
- How often
- Which channel
**Use when**: Team projects with multiple stakeholders needing different information.
### risk-register.md
Risk tracking table:
- Risk description
- Probability (H/M/L)
- Impact (H/M/L)
- Mitigation plan
- Owner
**Use when**: Projects >2 weeks or high-stakes projects of any duration.
### todo-structure.md
Hierarchical task breakdown:
- Phases or milestones
- Tasks under each phase
- Subtasks if needed
- Metadata: owner, estimate, due date, dependencies
**Use when**: Always. Every project needs task breakdown.
### progress-update.md
Status reporting template:
- Completed since last update
- In progress
- Blockers
- Next steps
- Metrics/progress %
**Use when**: Projects needing regular status updates (weekly, sprint-based, etc.).
## Customization Notes
Templates are starting points. Common customizations:
- Remove sections that don't apply
- Add project-specific sections
- Adjust detail level based on audience
- Combine templates for simpler output
The goal is useful documentation, not template compliance.