feat(basecamp-project): add launch workflow skill
This commit is contained in:
37
skills/basecamp-project/references/status-tracking.md
Normal file
37
skills/basecamp-project/references/status-tracking.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# Status Tracking Reference
|
||||
|
||||
Use moderate status tracking: enough rhythm to keep work visible and unblock decisions, without creating heavy governance unless project complexity requires it.
|
||||
|
||||
## Default Check-ins
|
||||
|
||||
Create lightweight weekly Automatic Check-ins unless an equivalent prompt already exists.
|
||||
|
||||
### Weekly focus check-in
|
||||
|
||||
Ask each active participant what they are focused on this week and whether their priorities have changed.
|
||||
|
||||
### Weekly progress and blocker check-in
|
||||
|
||||
Ask each active participant what progressed, what is blocked, and what support or decision is needed.
|
||||
|
||||
## Status Updates
|
||||
|
||||
Status updates go on the Message Board and are owned by the project DRI. Use a consistent, short format so stakeholders can scan progress quickly.
|
||||
|
||||
```markdown
|
||||
### Status
|
||||
Green | Yellow | Red
|
||||
|
||||
### What changed
|
||||
...
|
||||
|
||||
### What is next
|
||||
...
|
||||
|
||||
### Decisions or help needed
|
||||
...
|
||||
```
|
||||
|
||||
## Governance Level
|
||||
|
||||
Keep the cadence practical. Add extra reporting, approval tracking, or steering updates only when the project has high risk, many teams, external commitments, or complex dependencies.
|
||||
Reference in New Issue
Block a user