feat(basecamp-project): add launch workflow skill
This commit is contained in:
43
skills/basecamp-project/references/kickoff-patterns.md
Normal file
43
skills/basecamp-project/references/kickoff-patterns.md
Normal file
@@ -0,0 +1,43 @@
|
||||
# Kickoff Patterns
|
||||
|
||||
## Adaptive Kickoff Tone
|
||||
|
||||
Default to a practical and energizing kickoff: clear enough to start work immediately, positive enough to create momentum, and grounded enough to avoid hype.
|
||||
|
||||
Choose the tone that fits the audience and project risk:
|
||||
|
||||
- **Practical/direct:** Best for internal teams, operational work, and projects where speed and clarity matter most.
|
||||
- **Motivational/energizing:** Best for launches, creative work, and moments where the team needs shared momentum.
|
||||
- **Calm/reassuring:** Best for complex, delayed, sensitive, or high-risk projects where confidence and steadiness matter.
|
||||
- **Formal/client-safe:** Best for external stakeholders, executive audiences, regulated work, or contractual delivery.
|
||||
- **German business casual:** Best for German-language teams that need professional clarity with a friendly, collaborative tone.
|
||||
|
||||
## Kickoff Structure
|
||||
|
||||
Use this structure for a kickoff message or kickoff document:
|
||||
|
||||
1. **Why this matters:** Explain the reason for the project and the value of doing it now.
|
||||
2. **Goal:** State the main outcome in one clear sentence.
|
||||
3. **Success criteria:** List the conditions that will make the project successful.
|
||||
4. **Timeline:** Give key dates, milestones, and near-term expectations.
|
||||
5. **Roles:** Name the DRI, named owners, reviewers, approvers, and any role placeholders that still need staffing.
|
||||
6. **Basecamp usage:** Explain where To-dos, messages, docs, schedules, and files should go.
|
||||
7. **First actions:** List the first concrete steps and owners.
|
||||
8. **Status update pattern:** State when updates happen, where they are posted, and what format they should follow.
|
||||
9. **Invitation for questions:** Make it easy to raise questions, risks, gaps, and decisions needed.
|
||||
|
||||
## Project Brief Rule
|
||||
|
||||
Use a kickoff message only for small projects with low ambiguity, few stakeholders, and limited risk.
|
||||
|
||||
Create a Project Brief for medium, complex, external, or high-risk projects. The brief should carry the durable project context, while the kickoff points people to the brief and highlights the immediate next actions.
|
||||
|
||||
## German `Vorlagen` Adaptation
|
||||
|
||||
When adapting kickoff patterns for German `Vorlagen`:
|
||||
|
||||
- Preserve the original structure and intent.
|
||||
- Write naturally in the target language.
|
||||
- Adapt examples, formality, and phrasing to the audience instead of translating mechanically.
|
||||
- Keep Basecamp usage instructions practical and explicit.
|
||||
- Use German business casual tone unless the stakeholder context calls for more formality.
|
||||
Reference in New Issue
Block a user