get-claudia 1.2.6 → 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/memory-daemon/scripts/install.sh +22 -4
- package/package.json +1 -1
- package/template-v2/.claude/commands/accountability-check.md +142 -0
- package/template-v2/.claude/commands/client-health.md +197 -0
- package/template-v2/.claude/commands/financial-snapshot.md +137 -0
- package/template-v2/.claude/commands/pipeline-review.md +102 -0
- package/template-v2/.claude/skills/archetypes/consultant.md +545 -7
- package/template-v2/.claude/skills/archetypes/creator.md +363 -2
- package/template-v2/.claude/skills/archetypes/executive.md +451 -5
- package/template-v2/.claude/skills/archetypes/founder.md +393 -3
- package/template-v2/.claude/skills/archetypes/solo.md +257 -2
- package/template-v2/.claude/skills/onboarding.md +72 -2
- package/template-v2/.claude/skills/structure-evolution.md +303 -0
- package/template-v2/.claude/skills/structure-generator.md +974 -13
|
@@ -93,16 +93,34 @@ random_message() {
|
|
|
93
93
|
echo "${MESSAGES[$RANDOM % ${#MESSAGES[@]}]}"
|
|
94
94
|
}
|
|
95
95
|
|
|
96
|
-
# Check Python
|
|
96
|
+
# Check Python - prefer Homebrew Python on macOS (supports SQLite extensions)
|
|
97
97
|
echo -e "${BOLD}Step 1/8: Environment Check${NC}"
|
|
98
98
|
echo
|
|
99
|
-
|
|
100
|
-
|
|
99
|
+
PYTHON=""
|
|
100
|
+
if [[ "$OSTYPE" == "darwin"* ]]; then
|
|
101
|
+
# Homebrew Python supports SQLite extension loading (needed for vector search)
|
|
102
|
+
if [ -x "/opt/homebrew/bin/python3" ]; then
|
|
103
|
+
PYTHON="/opt/homebrew/bin/python3"
|
|
104
|
+
echo -e " ${GREEN}✓${NC} Using Homebrew Python (vector search supported)"
|
|
105
|
+
elif [ -x "/usr/local/bin/python3" ]; then
|
|
106
|
+
PYTHON="/usr/local/bin/python3"
|
|
107
|
+
echo -e " ${GREEN}✓${NC} Using Homebrew Python (vector search supported)"
|
|
108
|
+
fi
|
|
109
|
+
fi
|
|
110
|
+
|
|
111
|
+
if [ -z "$PYTHON" ]; then
|
|
112
|
+
if command -v python3 &> /dev/null; then
|
|
113
|
+
PYTHON=$(command -v python3)
|
|
114
|
+
fi
|
|
115
|
+
fi
|
|
116
|
+
|
|
117
|
+
if [ -n "$PYTHON" ]; then
|
|
101
118
|
PYTHON_VERSION=$($PYTHON --version 2>&1 | awk '{print $2}')
|
|
102
|
-
echo -e " ${GREEN}✓${NC} Python $PYTHON_VERSION"
|
|
119
|
+
echo -e " ${GREEN}✓${NC} Python $PYTHON_VERSION ($PYTHON)"
|
|
103
120
|
else
|
|
104
121
|
echo -e " ${RED}✗${NC} Python 3 not found"
|
|
105
122
|
echo -e " Please install Python 3.10 or later"
|
|
123
|
+
echo -e " ${DIM}On macOS: brew install python${NC}"
|
|
106
124
|
exit 1
|
|
107
125
|
fi
|
|
108
126
|
|
package/package.json
CHANGED
|
@@ -0,0 +1,142 @@
|
|
|
1
|
+
# Accountability Check
|
|
2
|
+
|
|
3
|
+
Surface all commitments, overdue items, and things you're waiting on from others.
|
|
4
|
+
|
|
5
|
+
## What to Check
|
|
6
|
+
|
|
7
|
+
### 1. My Commitments
|
|
8
|
+
From `context/commitments.md` and `accountability/commitments.md`:
|
|
9
|
+
- What I've promised
|
|
10
|
+
- To whom
|
|
11
|
+
- When it's due
|
|
12
|
+
- Current status
|
|
13
|
+
|
|
14
|
+
### 2. Overdue Items
|
|
15
|
+
From `accountability/overdue.md` and scanning commitment dates:
|
|
16
|
+
- Anything past due
|
|
17
|
+
- Days overdue
|
|
18
|
+
- Impact level
|
|
19
|
+
|
|
20
|
+
### 3. Waiting On Others
|
|
21
|
+
From `context/waiting.md`:
|
|
22
|
+
- What I'm waiting for
|
|
23
|
+
- From whom
|
|
24
|
+
- How long I've been waiting
|
|
25
|
+
- Last follow-up
|
|
26
|
+
|
|
27
|
+
### 4. Per-Client/Project Commitments
|
|
28
|
+
Scan relevant folders for:
|
|
29
|
+
- Client-specific commitments
|
|
30
|
+
- Project deliverables
|
|
31
|
+
- Meeting follow-ups
|
|
32
|
+
|
|
33
|
+
## Output Format
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
## Accountability Check — [Date]
|
|
37
|
+
|
|
38
|
+
### Summary
|
|
39
|
+
- My commitments: X total (Y due this week)
|
|
40
|
+
- Overdue items: X (oldest: Y days)
|
|
41
|
+
- Waiting on others: X items
|
|
42
|
+
|
|
43
|
+
### 🔴 Overdue (Needs Immediate Attention)
|
|
44
|
+
|
|
45
|
+
| What | To | Was Due | Days Late | Impact |
|
|
46
|
+
|------|-----|---------|-----------|--------|
|
|
47
|
+
| [Item] | [Person] | [Date] | X | High/Med/Low |
|
|
48
|
+
|
|
49
|
+
**Recovery Actions:**
|
|
50
|
+
- [Item]: [What to do now]
|
|
51
|
+
|
|
52
|
+
### 🟡 Due This Week
|
|
53
|
+
|
|
54
|
+
| What | To | Due | Status | Notes |
|
|
55
|
+
|------|-----|-----|--------|-------|
|
|
56
|
+
| [Item] | [Person] | [Date] | On Track / At Risk | |
|
|
57
|
+
|
|
58
|
+
### 🟢 Due Later
|
|
59
|
+
|
|
60
|
+
| What | To | Due | Notes |
|
|
61
|
+
|------|-----|-----|-------|
|
|
62
|
+
| [Item] | [Person] | [Date] | |
|
|
63
|
+
|
|
64
|
+
### Waiting On Others
|
|
65
|
+
|
|
66
|
+
| What | From | Since | Days Waiting | Last Follow-up |
|
|
67
|
+
|------|------|-------|--------------|----------------|
|
|
68
|
+
| [Item] | [Person] | [Date] | X | [Date or "None"] |
|
|
69
|
+
|
|
70
|
+
**Follow-up Needed:**
|
|
71
|
+
- [Item from Person]: [Suggested action]
|
|
72
|
+
|
|
73
|
+
### By Relationship
|
|
74
|
+
|
|
75
|
+
#### [Person/Client Name]
|
|
76
|
+
**I Owe:**
|
|
77
|
+
- [Item] — due [Date]
|
|
78
|
+
|
|
79
|
+
**They Owe:**
|
|
80
|
+
- [Item] — since [Date]
|
|
81
|
+
|
|
82
|
+
[Repeat for key relationships with open items]
|
|
83
|
+
|
|
84
|
+
### Patterns Noticed
|
|
85
|
+
|
|
86
|
+
- [Any patterns: always late on X, person Y is slow to respond, etc.]
|
|
87
|
+
|
|
88
|
+
### Recommended Actions
|
|
89
|
+
|
|
90
|
+
1. **Today:** [Most urgent action]
|
|
91
|
+
2. **This Week:** [Important but not urgent]
|
|
92
|
+
3. **Follow-up:** [People to nudge]
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
## Checking Process
|
|
96
|
+
|
|
97
|
+
1. Read `context/commitments.md` and `accountability/commitments.md`
|
|
98
|
+
2. Read `context/waiting.md`
|
|
99
|
+
3. Scan client/project folders for commitments sections
|
|
100
|
+
4. Check meeting notes from past 2 weeks for promises made
|
|
101
|
+
5. Cross-reference dates against today
|
|
102
|
+
|
|
103
|
+
## Red Flags to Surface
|
|
104
|
+
|
|
105
|
+
- Any item 3+ days overdue
|
|
106
|
+
- Any commitment with no clear due date
|
|
107
|
+
- Any "waiting on" item with no follow-up scheduled
|
|
108
|
+
- Same item appearing overdue multiple times (recurring problem)
|
|
109
|
+
- Important relationships with imbalanced commitments
|
|
110
|
+
|
|
111
|
+
## Tone
|
|
112
|
+
|
|
113
|
+
- Direct, not judgmental
|
|
114
|
+
- Focus on recovery, not blame
|
|
115
|
+
- Prioritize by relationship importance and impact
|
|
116
|
+
- Suggest specific actions
|
|
117
|
+
|
|
118
|
+
## When to Run
|
|
119
|
+
|
|
120
|
+
- Start of each day (abbreviated version)
|
|
121
|
+
- Start of week (full version)
|
|
122
|
+
- Before meeting with someone (filter to that person)
|
|
123
|
+
- When feeling overwhelmed about what's owed
|
|
124
|
+
|
|
125
|
+
## Usage Variations
|
|
126
|
+
|
|
127
|
+
**Full check:**
|
|
128
|
+
```
|
|
129
|
+
/accountability-check
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
**For specific person:**
|
|
133
|
+
```
|
|
134
|
+
/accountability-check [person name]
|
|
135
|
+
```
|
|
136
|
+
Filters to only show commitments involving that person.
|
|
137
|
+
|
|
138
|
+
**Quick overdue only:**
|
|
139
|
+
```
|
|
140
|
+
/accountability-check overdue
|
|
141
|
+
```
|
|
142
|
+
Shows only overdue items and immediate recovery actions.
|
|
@@ -0,0 +1,197 @@
|
|
|
1
|
+
# Client Health
|
|
2
|
+
|
|
3
|
+
Health check across all active client engagements. Available for Consultant and Solo Professional archetypes.
|
|
4
|
+
|
|
5
|
+
## What to Check
|
|
6
|
+
|
|
7
|
+
For each client folder in `clients/`:
|
|
8
|
+
|
|
9
|
+
### 1. Engagement Health
|
|
10
|
+
- Current status and phase
|
|
11
|
+
- Milestone progress (if milestone-plan.md exists)
|
|
12
|
+
- Any overdue deliverables
|
|
13
|
+
- Contract/engagement end dates approaching
|
|
14
|
+
|
|
15
|
+
### 2. Relationship Health
|
|
16
|
+
- Last contact date
|
|
17
|
+
- Communication frequency
|
|
18
|
+
- Stakeholder sentiment (if stakeholders.md exists)
|
|
19
|
+
- Any concerns or red flags
|
|
20
|
+
|
|
21
|
+
### 3. Commitment Status
|
|
22
|
+
- Open commitments from overview.md
|
|
23
|
+
- Overdue items
|
|
24
|
+
- Items waiting on client
|
|
25
|
+
- Upcoming deliverables
|
|
26
|
+
|
|
27
|
+
### 4. Financial Health (if tracked)
|
|
28
|
+
- Outstanding invoices
|
|
29
|
+
- Payment status
|
|
30
|
+
- Upcoming billing
|
|
31
|
+
|
|
32
|
+
### 5. Blockers (if blockers.md exists)
|
|
33
|
+
- Active blockers
|
|
34
|
+
- Resolution progress
|
|
35
|
+
- Impact on deliverables
|
|
36
|
+
|
|
37
|
+
## Output Format
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
## Client Health — [Date]
|
|
41
|
+
|
|
42
|
+
### Summary
|
|
43
|
+
|
|
44
|
+
| Status | Count | Details |
|
|
45
|
+
|--------|-------|---------|
|
|
46
|
+
| 🟢 On Track | X | [Names] |
|
|
47
|
+
| 🟡 Attention Needed | X | [Names] |
|
|
48
|
+
| 🔴 At Risk | X | [Names] |
|
|
49
|
+
|
|
50
|
+
- **Total active clients:** X
|
|
51
|
+
- **Open commitments:** X
|
|
52
|
+
- **Overdue items:** X
|
|
53
|
+
- **Outstanding invoices:** $X
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
### 🟢 On Track
|
|
58
|
+
|
|
59
|
+
#### [Client Name]
|
|
60
|
+
**Phase:** [Current phase]
|
|
61
|
+
**Last Contact:** [Date]
|
|
62
|
+
**Health:** All good
|
|
63
|
+
|
|
64
|
+
**Active Work:**
|
|
65
|
+
- [Deliverable] — on track for [Date]
|
|
66
|
+
|
|
67
|
+
**Open Items:** X (none overdue)
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
### 🟡 Attention Needed
|
|
72
|
+
|
|
73
|
+
#### [Client Name]
|
|
74
|
+
**Phase:** [Current phase]
|
|
75
|
+
**Last Contact:** [Date] — X days ago
|
|
76
|
+
**Health:** Needs attention
|
|
77
|
+
|
|
78
|
+
**Concerns:**
|
|
79
|
+
- [Issue 1]
|
|
80
|
+
- [Issue 2]
|
|
81
|
+
|
|
82
|
+
**Open Items:**
|
|
83
|
+
- [Overdue or at-risk item]
|
|
84
|
+
|
|
85
|
+
**Suggested Action:**
|
|
86
|
+
- [What to do]
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
### 🔴 At Risk
|
|
91
|
+
|
|
92
|
+
#### [Client Name]
|
|
93
|
+
**Phase:** [Current phase]
|
|
94
|
+
**Issues:**
|
|
95
|
+
- [Critical issue]
|
|
96
|
+
- [Critical issue]
|
|
97
|
+
|
|
98
|
+
**Immediate Actions:**
|
|
99
|
+
1. [Urgent action]
|
|
100
|
+
2. [Follow-up action]
|
|
101
|
+
|
|
102
|
+
---
|
|
103
|
+
|
|
104
|
+
### Cross-Client View
|
|
105
|
+
|
|
106
|
+
#### Deliverables Due This Week
|
|
107
|
+
|
|
108
|
+
| Client | Deliverable | Due | Status |
|
|
109
|
+
|--------|-------------|-----|--------|
|
|
110
|
+
| | | | On Track / At Risk / Overdue |
|
|
111
|
+
|
|
112
|
+
#### Outstanding Invoices
|
|
113
|
+
|
|
114
|
+
| Client | Amount | Sent | Due | Status |
|
|
115
|
+
|--------|--------|------|-----|--------|
|
|
116
|
+
| | $X | [Date] | [Date] | Outstanding / Overdue |
|
|
117
|
+
|
|
118
|
+
#### Relationships Needing Touch
|
|
119
|
+
|
|
120
|
+
| Client | Last Contact | Days | Suggested Action |
|
|
121
|
+
|--------|--------------|------|------------------|
|
|
122
|
+
| | [Date] | X | [Action] |
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
### Patterns
|
|
127
|
+
|
|
128
|
+
- [Cross-client observation]
|
|
129
|
+
- [Recurring issue across clients]
|
|
130
|
+
|
|
131
|
+
### Capacity Check
|
|
132
|
+
|
|
133
|
+
- **Current active clients:** X
|
|
134
|
+
- **Total active engagements:** X
|
|
135
|
+
- **Hours committed this week:** X
|
|
136
|
+
- **Available bandwidth:** [Assessment]
|
|
137
|
+
- **Upcoming endings:** [Client] ends [Date]
|
|
138
|
+
- **Pipeline:** X prospects (see /pipeline-review)
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
## Health Scoring
|
|
142
|
+
|
|
143
|
+
### 🟢 On Track
|
|
144
|
+
- Recent contact (within expected cadence)
|
|
145
|
+
- No overdue deliverables
|
|
146
|
+
- Positive or neutral stakeholder sentiment
|
|
147
|
+
- No active blockers
|
|
148
|
+
- Invoices paid or not yet due
|
|
149
|
+
|
|
150
|
+
### 🟡 Attention Needed
|
|
151
|
+
- Contact overdue by 1 week+
|
|
152
|
+
- Deliverable at risk (due soon, not complete)
|
|
153
|
+
- Stakeholder concerns raised
|
|
154
|
+
- Minor blocker active
|
|
155
|
+
- Invoice overdue by less than 2 weeks
|
|
156
|
+
|
|
157
|
+
### 🔴 At Risk
|
|
158
|
+
- Contact overdue by 2+ weeks
|
|
159
|
+
- Deliverable overdue
|
|
160
|
+
- Stakeholder actively unhappy
|
|
161
|
+
- Major blocker preventing progress
|
|
162
|
+
- Invoice overdue by 2+ weeks
|
|
163
|
+
- Engagement ending without renewal discussion
|
|
164
|
+
|
|
165
|
+
## Tone
|
|
166
|
+
|
|
167
|
+
- Factual, scannable
|
|
168
|
+
- Lead with concerns (don't bury bad news)
|
|
169
|
+
- Specific action suggestions
|
|
170
|
+
- Don't sugarcoat problems
|
|
171
|
+
- Acknowledge what's going well
|
|
172
|
+
|
|
173
|
+
## When to Run
|
|
174
|
+
|
|
175
|
+
- Weekly (Monday or Friday)
|
|
176
|
+
- Before client meetings (filtered to that client)
|
|
177
|
+
- When feeling uncertain about client status
|
|
178
|
+
- During weekly review
|
|
179
|
+
|
|
180
|
+
## Usage Variations
|
|
181
|
+
|
|
182
|
+
**All clients:**
|
|
183
|
+
```
|
|
184
|
+
/client-health
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
**Specific client:**
|
|
188
|
+
```
|
|
189
|
+
/client-health [client name]
|
|
190
|
+
```
|
|
191
|
+
Deep dive on single client with full history.
|
|
192
|
+
|
|
193
|
+
**Quick overview:**
|
|
194
|
+
```
|
|
195
|
+
/client-health summary
|
|
196
|
+
```
|
|
197
|
+
Just the summary stats and any red/yellow flags.
|
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
# Financial Snapshot
|
|
2
|
+
|
|
3
|
+
Quick view of your financial position: revenue, expenses, invoicing, and cash flow.
|
|
4
|
+
|
|
5
|
+
## What to Check
|
|
6
|
+
|
|
7
|
+
### 1. Revenue (`finances/overview.md`)
|
|
8
|
+
- This month's revenue
|
|
9
|
+
- Month-over-month trend
|
|
10
|
+
- Active revenue streams
|
|
11
|
+
|
|
12
|
+
### 2. Outstanding (`finances/invoicing.md` if exists)
|
|
13
|
+
- Unpaid invoices
|
|
14
|
+
- Overdue amounts
|
|
15
|
+
- Upcoming invoices to send
|
|
16
|
+
|
|
17
|
+
### 3. Expenses (`finances/expenses.md` if exists)
|
|
18
|
+
- This month's expenses
|
|
19
|
+
- Major categories
|
|
20
|
+
- Unusual items
|
|
21
|
+
|
|
22
|
+
### 4. Cash Flow
|
|
23
|
+
- Net position (revenue - expenses)
|
|
24
|
+
- Runway or buffer
|
|
25
|
+
- Upcoming obligations
|
|
26
|
+
|
|
27
|
+
## Output Format
|
|
28
|
+
|
|
29
|
+
```
|
|
30
|
+
## Financial Snapshot — [Date]
|
|
31
|
+
|
|
32
|
+
### This Month: [Month Year]
|
|
33
|
+
|
|
34
|
+
| Metric | Amount | vs Last Month |
|
|
35
|
+
|--------|--------|---------------|
|
|
36
|
+
| Revenue | $X | +/-X% |
|
|
37
|
+
| Expenses | $X | +/-X% |
|
|
38
|
+
| Net | $X | +/-X% |
|
|
39
|
+
|
|
40
|
+
### Revenue Breakdown
|
|
41
|
+
|
|
42
|
+
| Source | Amount | Status |
|
|
43
|
+
|--------|--------|--------|
|
|
44
|
+
| [Client/Stream] | $X | Received / Outstanding |
|
|
45
|
+
|
|
46
|
+
**Total Received:** $X
|
|
47
|
+
**Total Outstanding:** $X
|
|
48
|
+
|
|
49
|
+
### Outstanding Invoices
|
|
50
|
+
|
|
51
|
+
| Invoice | Client | Amount | Sent | Due | Status |
|
|
52
|
+
|---------|--------|--------|------|-----|--------|
|
|
53
|
+
| [#] | [Client] | $X | [Date] | [Date] | Upcoming / Due / Overdue |
|
|
54
|
+
|
|
55
|
+
**Total Outstanding:** $X
|
|
56
|
+
**Overdue:** $X
|
|
57
|
+
|
|
58
|
+
### Invoices to Send
|
|
59
|
+
|
|
60
|
+
| Client | Work | Est. Amount | Ready? |
|
|
61
|
+
|--------|------|-------------|--------|
|
|
62
|
+
| [Client] | [Description] | $X | Yes/No |
|
|
63
|
+
|
|
64
|
+
### Expenses This Month
|
|
65
|
+
|
|
66
|
+
| Category | Amount | Notes |
|
|
67
|
+
|----------|--------|-------|
|
|
68
|
+
| [Category] | $X | |
|
|
69
|
+
|
|
70
|
+
**Total Expenses:** $X
|
|
71
|
+
|
|
72
|
+
### Cash Flow Summary
|
|
73
|
+
|
|
74
|
+
- **Revenue this month:** $X
|
|
75
|
+
- **Expenses this month:** $X
|
|
76
|
+
- **Net this month:** $X
|
|
77
|
+
- **Outstanding receivables:** $X
|
|
78
|
+
- **Expected cash in:** $X (next 30 days)
|
|
79
|
+
|
|
80
|
+
### Alerts
|
|
81
|
+
|
|
82
|
+
- [Any financial concerns or actions needed]
|
|
83
|
+
|
|
84
|
+
### Tax Set-Aside (if applicable)
|
|
85
|
+
|
|
86
|
+
- **Should set aside:** $X (at X% rate)
|
|
87
|
+
- **Actually set aside:** $X
|
|
88
|
+
- **Next quarterly due:** [Date]
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
## Archetype Variations
|
|
92
|
+
|
|
93
|
+
### Consultant/Solo
|
|
94
|
+
Focus on client invoicing, project-based revenue, and utilization-based capacity.
|
|
95
|
+
|
|
96
|
+
### Founder
|
|
97
|
+
Include runway calculation, burn rate, and path to next fundraise.
|
|
98
|
+
|
|
99
|
+
```
|
|
100
|
+
### Runway Check
|
|
101
|
+
|
|
102
|
+
- **Cash on hand:** $X
|
|
103
|
+
- **Monthly burn:** $X
|
|
104
|
+
- **Runway:** X months (until [Date])
|
|
105
|
+
- **Next milestone before raise:** [What]
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
### Executive
|
|
109
|
+
Focus on budget tracking, department spend, and initiative costs if applicable.
|
|
110
|
+
|
|
111
|
+
### Creator
|
|
112
|
+
Break down by revenue stream: sponsorships, products, affiliate, etc.
|
|
113
|
+
|
|
114
|
+
```
|
|
115
|
+
### Revenue by Stream
|
|
116
|
+
|
|
117
|
+
| Stream | This Month | Last Month | Trend |
|
|
118
|
+
|--------|------------|------------|-------|
|
|
119
|
+
| Sponsorships | $X | $X | ↑/→/↓ |
|
|
120
|
+
| Products | $X | $X | ↑/→/↓ |
|
|
121
|
+
| Affiliate | $X | $X | ↑/→/↓ |
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
## Tone
|
|
125
|
+
|
|
126
|
+
- Numbers-focused, clear
|
|
127
|
+
- Highlight concerns prominently
|
|
128
|
+
- Actionable recommendations
|
|
129
|
+
- No judgment about spending
|
|
130
|
+
|
|
131
|
+
## When to Run
|
|
132
|
+
|
|
133
|
+
- Weekly or biweekly
|
|
134
|
+
- End of month
|
|
135
|
+
- Before making financial decisions
|
|
136
|
+
- When feeling uncertain about cash position
|
|
137
|
+
- Before quarterly tax payments
|
|
@@ -0,0 +1,102 @@
|
|
|
1
|
+
# Pipeline Review
|
|
2
|
+
|
|
3
|
+
Review your active pipeline, opportunities, and capacity.
|
|
4
|
+
|
|
5
|
+
## What to Check
|
|
6
|
+
|
|
7
|
+
### 1. Active Pipeline (`pipeline/active.md`)
|
|
8
|
+
- Current engagements or deals
|
|
9
|
+
- Stage of each
|
|
10
|
+
- Health status
|
|
11
|
+
- Next actions needed
|
|
12
|
+
|
|
13
|
+
### 2. Prospecting (`pipeline/prospecting.md` if exists)
|
|
14
|
+
- Warm leads
|
|
15
|
+
- Outreach in progress
|
|
16
|
+
- Follow-ups needed
|
|
17
|
+
|
|
18
|
+
### 3. Capacity
|
|
19
|
+
- Current utilization
|
|
20
|
+
- Available bandwidth
|
|
21
|
+
- Upcoming endings or starts
|
|
22
|
+
|
|
23
|
+
### 4. Stalled Items
|
|
24
|
+
- Opportunities with no activity in 2+ weeks
|
|
25
|
+
- Deals that need nudging or closing
|
|
26
|
+
|
|
27
|
+
## Output Format
|
|
28
|
+
|
|
29
|
+
```
|
|
30
|
+
## Pipeline Review — [Date]
|
|
31
|
+
|
|
32
|
+
### Summary
|
|
33
|
+
- Active engagements: X ($Y total value)
|
|
34
|
+
- In prospecting: X ($Y potential)
|
|
35
|
+
- Capacity: X% utilized
|
|
36
|
+
- Stalled items: X need attention
|
|
37
|
+
|
|
38
|
+
### Active Engagements
|
|
39
|
+
|
|
40
|
+
| Client/Deal | Stage | Value | Health | Next Action |
|
|
41
|
+
|-------------|-------|-------|--------|-------------|
|
|
42
|
+
| [Name] | [Stage] | $X | 🟢/🟡/🔴 | [Action] |
|
|
43
|
+
|
|
44
|
+
### Prospecting Pipeline
|
|
45
|
+
|
|
46
|
+
| Opportunity | Stage | Est. Value | Last Touch | Next Step |
|
|
47
|
+
|-------------|-------|------------|------------|-----------|
|
|
48
|
+
| [Name] | [Stage] | $X | [Date] | [Action] |
|
|
49
|
+
|
|
50
|
+
### Stalled (2+ Weeks Inactive)
|
|
51
|
+
|
|
52
|
+
| Item | Last Activity | Days Stalled | Recommendation |
|
|
53
|
+
|------|---------------|--------------|----------------|
|
|
54
|
+
| [Name] | [Date] | X | [What to do] |
|
|
55
|
+
|
|
56
|
+
### Capacity Check
|
|
57
|
+
|
|
58
|
+
- **Current utilization:** X%
|
|
59
|
+
- **Available for:** [type of work/hours]
|
|
60
|
+
- **Upcoming changes:**
|
|
61
|
+
- [Date]: [Engagement ending/starting]
|
|
62
|
+
|
|
63
|
+
### Upcoming Closings
|
|
64
|
+
|
|
65
|
+
| Deal | Expected Close | Value | Probability |
|
|
66
|
+
|------|----------------|-------|-------------|
|
|
67
|
+
| [Name] | [Date] | $X | High/Med/Low |
|
|
68
|
+
|
|
69
|
+
### Actions This Week
|
|
70
|
+
|
|
71
|
+
1. [Highest priority pipeline action]
|
|
72
|
+
2. [Second priority]
|
|
73
|
+
3. [Third priority]
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
## Archetype Variations
|
|
77
|
+
|
|
78
|
+
### Consultant/Solo
|
|
79
|
+
Focus on client pipeline, engagement renewals, and billable capacity.
|
|
80
|
+
|
|
81
|
+
### Founder
|
|
82
|
+
Focus on investor pipeline, fundraising progress, and deal stages.
|
|
83
|
+
|
|
84
|
+
### Executive
|
|
85
|
+
Focus on initiative pipeline, strategic project status, and resource allocation.
|
|
86
|
+
|
|
87
|
+
### Creator
|
|
88
|
+
Focus on partnership pipeline, sponsorship opportunities, and content deals.
|
|
89
|
+
|
|
90
|
+
## Tone
|
|
91
|
+
|
|
92
|
+
- Business-focused, not chatty
|
|
93
|
+
- Prioritize by urgency and value
|
|
94
|
+
- Flag stalled items prominently
|
|
95
|
+
- Suggest specific actions
|
|
96
|
+
|
|
97
|
+
## When to Run
|
|
98
|
+
|
|
99
|
+
- Weekly (Monday mornings ideal)
|
|
100
|
+
- Before capacity planning
|
|
101
|
+
- When feeling uncertain about workload
|
|
102
|
+
- Before taking on new work
|