get-claudia 1.0.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/LICENSE +201 -0
- package/README.md +231 -0
- package/assets/README.md +17 -0
- package/bin/index.js +85 -0
- package/package.json +40 -0
- package/template-v2/.claude/commands/capture-meeting.md +140 -0
- package/template-v2/.claude/commands/draft-reply.md +129 -0
- package/template-v2/.claude/commands/follow-up-draft.md +127 -0
- package/template-v2/.claude/commands/meeting-prep.md +103 -0
- package/template-v2/.claude/commands/morning-brief.md +92 -0
- package/template-v2/.claude/commands/new-person.md +115 -0
- package/template-v2/.claude/commands/summarize-doc.md +172 -0
- package/template-v2/.claude/commands/weekly-review.md +127 -0
- package/template-v2/.claude/commands/what-am-i-missing.md +110 -0
- package/template-v2/.claude/hooks/hooks.json +48 -0
- package/template-v2/.claude/rules/claudia-principles.md +279 -0
- package/template-v2/.claude/skills/README.md +50 -0
- package/template-v2/.claude/skills/archetypes/consultant.md +396 -0
- package/template-v2/.claude/skills/archetypes/creator.md +518 -0
- package/template-v2/.claude/skills/archetypes/executive.md +476 -0
- package/template-v2/.claude/skills/archetypes/founder.md +491 -0
- package/template-v2/.claude/skills/archetypes/solo.md +525 -0
- package/template-v2/.claude/skills/capability-suggester.md +279 -0
- package/template-v2/.claude/skills/commitment-detector.md +210 -0
- package/template-v2/.claude/skills/memory-manager.md +267 -0
- package/template-v2/.claude/skills/onboarding.md +189 -0
- package/template-v2/.claude/skills/pattern-recognizer.md +244 -0
- package/template-v2/.claude/skills/relationship-tracker.md +140 -0
- package/template-v2/.claude/skills/risk-surfacer.md +251 -0
- package/template-v2/.claude/skills/structure-generator.md +408 -0
- package/template-v2/.mcp.json.example +25 -0
- package/template-v2/CLAUDE.md +363 -0
- package/template-v2/LICENSE +190 -0
- package/template-v2/NOTICE +7 -0
|
@@ -0,0 +1,140 @@
|
|
|
1
|
+
# Capture Meeting
|
|
2
|
+
|
|
3
|
+
Process meeting notes or transcript to extract decisions, commitments, and insights.
|
|
4
|
+
|
|
5
|
+
## Trigger
|
|
6
|
+
|
|
7
|
+
- "Here's a transcript from [client/person]"
|
|
8
|
+
- "Process these meeting notes"
|
|
9
|
+
- "Here are my notes from the call with [person]"
|
|
10
|
+
- `/capture-meeting`
|
|
11
|
+
|
|
12
|
+
## Input
|
|
13
|
+
|
|
14
|
+
User provides one of:
|
|
15
|
+
- Full transcript (from Otter, Granola, etc.)
|
|
16
|
+
- Meeting notes (manual)
|
|
17
|
+
- Voice memo summary
|
|
18
|
+
- Memory/verbal recap
|
|
19
|
+
|
|
20
|
+
## Processing Steps
|
|
21
|
+
|
|
22
|
+
### 1. Identify Participants
|
|
23
|
+
- Who was in the meeting?
|
|
24
|
+
- Which person files to update?
|
|
25
|
+
- Any new people to track?
|
|
26
|
+
|
|
27
|
+
### 2. Extract Key Information
|
|
28
|
+
|
|
29
|
+
**Decisions Made:**
|
|
30
|
+
- What was decided?
|
|
31
|
+
- Who made the decision?
|
|
32
|
+
- Any conditions or context?
|
|
33
|
+
|
|
34
|
+
**Commitments Created:**
|
|
35
|
+
- What did you promise? (→ `context/commitments.md`)
|
|
36
|
+
- What did they promise? (→ `context/waiting.md`)
|
|
37
|
+
- Deadlines (explicit or implied)
|
|
38
|
+
|
|
39
|
+
**Blockers Surfaced:**
|
|
40
|
+
- What's in the way?
|
|
41
|
+
- Who can unblock?
|
|
42
|
+
|
|
43
|
+
**Sentiment Signals:**
|
|
44
|
+
- Enthusiasm, concern, resistance
|
|
45
|
+
- Energy level
|
|
46
|
+
- Relationship health indicators
|
|
47
|
+
|
|
48
|
+
**Key Topics:**
|
|
49
|
+
- Main themes discussed
|
|
50
|
+
- Important context shared
|
|
51
|
+
|
|
52
|
+
### 3. Organize
|
|
53
|
+
|
|
54
|
+
- Save notes to appropriate location
|
|
55
|
+
- Update person files with new context
|
|
56
|
+
- Link commitments and waiting items
|
|
57
|
+
|
|
58
|
+
### 4. Synthesize
|
|
59
|
+
|
|
60
|
+
Create a summary that captures:
|
|
61
|
+
- What happened (brief)
|
|
62
|
+
- What was decided
|
|
63
|
+
- What's next (actions)
|
|
64
|
+
- How it went (sentiment)
|
|
65
|
+
|
|
66
|
+
## Output Format
|
|
67
|
+
|
|
68
|
+
```
|
|
69
|
+
## Meeting Capture: [Meeting Name/Person]
|
|
70
|
+
### [Date]
|
|
71
|
+
|
|
72
|
+
**Attendees:** [Names]
|
|
73
|
+
**Duration:** [Approximate]
|
|
74
|
+
**Context:** [Brief — what was this meeting about?]
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
### Summary
|
|
79
|
+
[2-3 sentence overview of what happened]
|
|
80
|
+
|
|
81
|
+
### Decisions Made
|
|
82
|
+
- [Decision] — decided by [who]
|
|
83
|
+
- [Decision]
|
|
84
|
+
|
|
85
|
+
### Action Items
|
|
86
|
+
|
|
87
|
+
**You:**
|
|
88
|
+
- [ ] [Action] — by [date]
|
|
89
|
+
- [ ] [Action] — by [date]
|
|
90
|
+
|
|
91
|
+
**Them:**
|
|
92
|
+
- [ ] [Action] — by [date]
|
|
93
|
+
|
|
94
|
+
### Key Discussion Points
|
|
95
|
+
- [Point 1]
|
|
96
|
+
- [Point 2]
|
|
97
|
+
- [Point 3]
|
|
98
|
+
|
|
99
|
+
### Sentiment
|
|
100
|
+
[Brief read on how the meeting went, relationship health]
|
|
101
|
+
|
|
102
|
+
---
|
|
103
|
+
|
|
104
|
+
### File Updates
|
|
105
|
+
|
|
106
|
+
Shall I:
|
|
107
|
+
- [ ] Add commitments to tracking? [List them]
|
|
108
|
+
- [ ] Add waiting items? [List them]
|
|
109
|
+
- [ ] Update [person]'s file with new context?
|
|
110
|
+
- [ ] Create files for new people mentioned?
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
*Meeting notes saved to: [location]*
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
## Judgment Points
|
|
118
|
+
|
|
119
|
+
Ask for confirmation on:
|
|
120
|
+
- Adding commitments (user must own promises)
|
|
121
|
+
- Adding waiting items (setting expectations)
|
|
122
|
+
- Updating sentiment in person files (subjective)
|
|
123
|
+
- Flagging concerns (interpretation required)
|
|
124
|
+
- File location (if ambiguous)
|
|
125
|
+
|
|
126
|
+
## Quality Checklist
|
|
127
|
+
|
|
128
|
+
- [ ] Every action item has an owner
|
|
129
|
+
- [ ] Every commitment has a deadline (even approximate)
|
|
130
|
+
- [ ] Sentiment signals noted but not over-interpreted
|
|
131
|
+
- [ ] Summary is actionable, not just descriptive
|
|
132
|
+
- [ ] Related person files flagged for update
|
|
133
|
+
- [ ] No unexplained jargon or unclear references
|
|
134
|
+
|
|
135
|
+
## Tone
|
|
136
|
+
|
|
137
|
+
- Efficient — respect user's time
|
|
138
|
+
- Accurate — don't add or assume
|
|
139
|
+
- Helpful — surface the useful parts
|
|
140
|
+
- Action-oriented — what needs to happen next
|
|
@@ -0,0 +1,129 @@
|
|
|
1
|
+
# Draft Reply
|
|
2
|
+
|
|
3
|
+
Draft a response to an email or message.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
`/draft-reply`
|
|
7
|
+
|
|
8
|
+
Then provide:
|
|
9
|
+
- The email/message to respond to
|
|
10
|
+
- Any specific direction for the response
|
|
11
|
+
|
|
12
|
+
## Context Gathering
|
|
13
|
+
|
|
14
|
+
### From the Message
|
|
15
|
+
- Who is it from? (Check `people/` for context)
|
|
16
|
+
- What are they asking or saying?
|
|
17
|
+
- What's the underlying need?
|
|
18
|
+
- Any urgency indicators?
|
|
19
|
+
|
|
20
|
+
### From Relationship
|
|
21
|
+
- Communication style preferences
|
|
22
|
+
- Relationship history
|
|
23
|
+
- Current context with this person
|
|
24
|
+
|
|
25
|
+
### From User
|
|
26
|
+
- "What's your goal with this response?"
|
|
27
|
+
- "Any constraints?" (Timeline, tone, etc.)
|
|
28
|
+
- "Anything to avoid?"
|
|
29
|
+
|
|
30
|
+
## Output Format
|
|
31
|
+
|
|
32
|
+
```
|
|
33
|
+
## Reply Draft
|
|
34
|
+
|
|
35
|
+
**To:** [Name] <[email]>
|
|
36
|
+
**Re:** [Subject]
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
[The drafted response]
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
**Notes:**
|
|
45
|
+
- Tone: [Professional / Warm / Direct / etc.]
|
|
46
|
+
- Key points addressed: [List]
|
|
47
|
+
- [Any considerations about timing or approach]
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
Adjustments needed? Ready to send?
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
## Response Types
|
|
55
|
+
|
|
56
|
+
### Information Request
|
|
57
|
+
- Provide what's asked clearly
|
|
58
|
+
- Offer additional helpful context
|
|
59
|
+
- Easy to scan
|
|
60
|
+
|
|
61
|
+
### Decision Needed
|
|
62
|
+
- Clear options if applicable
|
|
63
|
+
- Your recommendation
|
|
64
|
+
- Easy to respond yes/no
|
|
65
|
+
|
|
66
|
+
### Scheduling
|
|
67
|
+
- Propose specific times
|
|
68
|
+
- Flexible alternatives
|
|
69
|
+
- Clear next step
|
|
70
|
+
|
|
71
|
+
### Difficult Message
|
|
72
|
+
- Acknowledge their perspective
|
|
73
|
+
- Address concerns directly
|
|
74
|
+
- Professional and measured
|
|
75
|
+
|
|
76
|
+
### Decline/No
|
|
77
|
+
- Respectful but clear
|
|
78
|
+
- Brief explanation if appropriate
|
|
79
|
+
- Leave door open if warranted
|
|
80
|
+
|
|
81
|
+
### Thank You/Acknowledgment
|
|
82
|
+
- Genuine appreciation
|
|
83
|
+
- Specific about what you valued
|
|
84
|
+
- Forward-looking if appropriate
|
|
85
|
+
|
|
86
|
+
## Tone Matching
|
|
87
|
+
|
|
88
|
+
Consider:
|
|
89
|
+
- Their tone in the original message
|
|
90
|
+
- Your relationship history
|
|
91
|
+
- Cultural context
|
|
92
|
+
- The topic sensitivity
|
|
93
|
+
|
|
94
|
+
Options:
|
|
95
|
+
- **Formal:** "I appreciate your inquiry..."
|
|
96
|
+
- **Professional:** "Thanks for reaching out..."
|
|
97
|
+
- **Casual:** "Hey! Great question..."
|
|
98
|
+
- **Warm:** "So good to hear from you..."
|
|
99
|
+
|
|
100
|
+
## Length Calibration
|
|
101
|
+
|
|
102
|
+
Match the energy:
|
|
103
|
+
- Short message → Short response
|
|
104
|
+
- Detailed message → Address all points
|
|
105
|
+
- Simple question → Simple answer
|
|
106
|
+
- Complex topic → Thorough but organized
|
|
107
|
+
|
|
108
|
+
General rule: Shorter is usually better.
|
|
109
|
+
|
|
110
|
+
## Structure for Long Responses
|
|
111
|
+
|
|
112
|
+
If multiple points to address:
|
|
113
|
+
1. Opening acknowledgment
|
|
114
|
+
2. Point-by-point responses (numbered or bulleted)
|
|
115
|
+
3. Summary of any actions
|
|
116
|
+
4. Clear next step
|
|
117
|
+
5. Warm close
|
|
118
|
+
|
|
119
|
+
## Safety Note
|
|
120
|
+
|
|
121
|
+
I'll show you the draft first. I will NOT send anything without your explicit approval.
|
|
122
|
+
|
|
123
|
+
## Quick Options
|
|
124
|
+
|
|
125
|
+
"Want me to:
|
|
126
|
+
1. Draft as written
|
|
127
|
+
2. Adjust tone to [more formal / more casual]
|
|
128
|
+
3. Make it shorter
|
|
129
|
+
4. Add/remove something specific"
|
|
@@ -0,0 +1,127 @@
|
|
|
1
|
+
# Follow-Up Draft
|
|
2
|
+
|
|
3
|
+
Draft a post-meeting follow-up or thank-you email.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
`/follow-up-draft [person name]`
|
|
7
|
+
|
|
8
|
+
## Context Gathering
|
|
9
|
+
|
|
10
|
+
### Check Existing Context
|
|
11
|
+
1. Recent meeting notes with this person
|
|
12
|
+
2. Their file in `people/`
|
|
13
|
+
3. Any commitments made
|
|
14
|
+
4. Topics discussed
|
|
15
|
+
|
|
16
|
+
### Ask If Needed
|
|
17
|
+
- "What was the meeting about?"
|
|
18
|
+
- "Any specific commitments to confirm?"
|
|
19
|
+
- "Anything particular to emphasize?"
|
|
20
|
+
|
|
21
|
+
## Output Format
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
## Follow-Up Email: [Person Name]
|
|
25
|
+
### Re: [Meeting/Topic]
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
**To:** [Name] <[email if known]>
|
|
30
|
+
**Subject:** [Suggested subject line]
|
|
31
|
+
|
|
32
|
+
---
|
|
33
|
+
|
|
34
|
+
Hi [Name],
|
|
35
|
+
|
|
36
|
+
[Opening — thank them, reference the conversation]
|
|
37
|
+
|
|
38
|
+
[Key points or takeaways from discussion]
|
|
39
|
+
|
|
40
|
+
[Confirm any commitments — what you'll do, what they mentioned]
|
|
41
|
+
|
|
42
|
+
[Next steps or call to action]
|
|
43
|
+
|
|
44
|
+
[Warm close]
|
|
45
|
+
|
|
46
|
+
[Your name]
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
**Notes:**
|
|
51
|
+
- [Any context about tone or relationship]
|
|
52
|
+
- [Timing suggestion for sending]
|
|
53
|
+
|
|
54
|
+
**Before sending:**
|
|
55
|
+
- [ ] Confirm accuracy of commitments mentioned
|
|
56
|
+
- [ ] Check tone matches relationship
|
|
57
|
+
- [ ] Verify email address
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
Ready to send? Let me know if you want adjustments.
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
## Email Types
|
|
65
|
+
|
|
66
|
+
### Thank You + Recap
|
|
67
|
+
After a productive meeting:
|
|
68
|
+
- Express appreciation
|
|
69
|
+
- Summarize key points
|
|
70
|
+
- Confirm next steps
|
|
71
|
+
|
|
72
|
+
### Commitment Confirmation
|
|
73
|
+
When specific promises were made:
|
|
74
|
+
- Clearly state what each party committed to
|
|
75
|
+
- Include deadlines
|
|
76
|
+
- Suggest follow-up touchpoint
|
|
77
|
+
|
|
78
|
+
### Continued Discussion
|
|
79
|
+
When more conversation needed:
|
|
80
|
+
- Reference where you left off
|
|
81
|
+
- Propose next steps
|
|
82
|
+
- Offer availability
|
|
83
|
+
|
|
84
|
+
### Re-engagement
|
|
85
|
+
After time has passed:
|
|
86
|
+
- Reference last interaction
|
|
87
|
+
- Share relevant update
|
|
88
|
+
- Propose reconnection
|
|
89
|
+
|
|
90
|
+
## Tone Calibration
|
|
91
|
+
|
|
92
|
+
Based on relationship:
|
|
93
|
+
- **New relationship:** More formal, clear context
|
|
94
|
+
- **Established:** Warmer, can be briefer
|
|
95
|
+
- **Client:** Professional, confirm value
|
|
96
|
+
- **Peer:** Conversational, mutual respect
|
|
97
|
+
- **Mentor/Senior:** Appreciative, respectful
|
|
98
|
+
|
|
99
|
+
Based on meeting outcome:
|
|
100
|
+
- **Positive:** Enthusiastic, forward-looking
|
|
101
|
+
- **Neutral:** Professional, clear next steps
|
|
102
|
+
- **Challenging:** Diplomatic, solution-focused
|
|
103
|
+
|
|
104
|
+
## Length
|
|
105
|
+
|
|
106
|
+
- Keep short: 100-200 words
|
|
107
|
+
- Get to the point quickly
|
|
108
|
+
- One clear ask or next step
|
|
109
|
+
- Easy to respond to
|
|
110
|
+
|
|
111
|
+
## Common Patterns
|
|
112
|
+
|
|
113
|
+
### "Great to meet you"
|
|
114
|
+
For first-time meetings, new relationships
|
|
115
|
+
|
|
116
|
+
### "Thanks for your time"
|
|
117
|
+
For meetings where they gave valuable input
|
|
118
|
+
|
|
119
|
+
### "Following up on our discussion"
|
|
120
|
+
For ongoing conversations
|
|
121
|
+
|
|
122
|
+
### "Wanted to confirm"
|
|
123
|
+
When specific commitments need clarity
|
|
124
|
+
|
|
125
|
+
## Safety Note
|
|
126
|
+
|
|
127
|
+
I'll draft the email and show it to you. I will NOT send anything without your explicit approval.
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# Meeting Prep
|
|
2
|
+
|
|
3
|
+
One-page briefing before a call or meeting.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
`/meeting-prep [person or meeting name]`
|
|
7
|
+
|
|
8
|
+
## What to Gather
|
|
9
|
+
|
|
10
|
+
### 1. Person Context
|
|
11
|
+
From `people/[person].md`:
|
|
12
|
+
- Role and organization
|
|
13
|
+
- Relationship history
|
|
14
|
+
- Last contact and topics
|
|
15
|
+
- Communication style
|
|
16
|
+
- What matters to them
|
|
17
|
+
|
|
18
|
+
### 2. Open Items
|
|
19
|
+
- Commitments to them
|
|
20
|
+
- Commitments from them
|
|
21
|
+
- Waiting items
|
|
22
|
+
|
|
23
|
+
### 3. Recent Context
|
|
24
|
+
- Last meeting notes (if any)
|
|
25
|
+
- Recent email threads (if available)
|
|
26
|
+
- Any project/client context
|
|
27
|
+
|
|
28
|
+
### 4. Strategic Context
|
|
29
|
+
- What's the purpose of this meeting?
|
|
30
|
+
- What outcome would be good?
|
|
31
|
+
- Any concerns to be aware of?
|
|
32
|
+
|
|
33
|
+
## Output Format
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
## Meeting Prep: [Person/Meeting Name]
|
|
37
|
+
### [Day, Date] at [Time]
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
**Who:** [Name, Role, Organization]
|
|
42
|
+
**Last Contact:** [Date] — [Context]
|
|
43
|
+
**Relationship:** [Current state/health]
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
### Context
|
|
48
|
+
[Brief summary of relationship and recent history]
|
|
49
|
+
|
|
50
|
+
### Open Items
|
|
51
|
+
|
|
52
|
+
**You Owe Them:**
|
|
53
|
+
- [Item] — due [date]
|
|
54
|
+
|
|
55
|
+
**They Owe You:**
|
|
56
|
+
- [Item] — expected [date]
|
|
57
|
+
|
|
58
|
+
### Key Points from Last Interaction
|
|
59
|
+
- [Point 1]
|
|
60
|
+
- [Point 2]
|
|
61
|
+
|
|
62
|
+
### What Matters to Them
|
|
63
|
+
- [Priority 1]
|
|
64
|
+
- [Priority 2]
|
|
65
|
+
|
|
66
|
+
### Suggested Topics
|
|
67
|
+
1. [Topic based on context]
|
|
68
|
+
2. [Topic based on open items]
|
|
69
|
+
3. [Topic based on their priorities]
|
|
70
|
+
|
|
71
|
+
### Watch For
|
|
72
|
+
- [Concern or sensitivity]
|
|
73
|
+
- [Opportunity]
|
|
74
|
+
|
|
75
|
+
### Outcome to Aim For
|
|
76
|
+
[What would make this meeting successful?]
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
*Anything else to prepare?*
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## Tone
|
|
84
|
+
|
|
85
|
+
- Concise — one page max
|
|
86
|
+
- Actionable — clear talking points
|
|
87
|
+
- Contextual — relevant history surfaced
|
|
88
|
+
- Strategic — not just facts but suggested approach
|
|
89
|
+
|
|
90
|
+
## Without Prior Context
|
|
91
|
+
|
|
92
|
+
If no file exists for this person:
|
|
93
|
+
"I don't have context on [Person] yet. Would you like to:
|
|
94
|
+
1. Tell me about them now (quick capture)
|
|
95
|
+
2. Create a full person file
|
|
96
|
+
3. Proceed with what you know"
|
|
97
|
+
|
|
98
|
+
## Group Meetings
|
|
99
|
+
|
|
100
|
+
For meetings with multiple people:
|
|
101
|
+
- Brief context on key attendees
|
|
102
|
+
- Focus on meeting purpose
|
|
103
|
+
- Common threads across attendees
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# Morning Brief
|
|
2
|
+
|
|
3
|
+
Provide a concise morning brief to start the day with clarity. Surface what matters, flag what's at risk, and set up the day for focus.
|
|
4
|
+
|
|
5
|
+
## What to Surface
|
|
6
|
+
|
|
7
|
+
### 1. Warnings First
|
|
8
|
+
Check for urgent items:
|
|
9
|
+
- **Overdue commitments** — Anything past due in `context/commitments.md`
|
|
10
|
+
- **Due today** — Commitments due today
|
|
11
|
+
- **48-hour warnings** — Commitments due within 48 hours
|
|
12
|
+
- **Overdue waiting items** — Things you're waiting on that haven't arrived
|
|
13
|
+
|
|
14
|
+
### 2. Today's Commitments
|
|
15
|
+
From `context/commitments.md`:
|
|
16
|
+
- What's due today
|
|
17
|
+
- What's due this week that needs attention today
|
|
18
|
+
- Any blocked items that need unblocking
|
|
19
|
+
|
|
20
|
+
### 3. Relationship Cooling Alerts
|
|
21
|
+
Check `people/` files for:
|
|
22
|
+
- Anyone not contacted in 60+ days who should be
|
|
23
|
+
- Key relationships that might be cooling
|
|
24
|
+
- Follow-ups promised but not done
|
|
25
|
+
|
|
26
|
+
### 4. Today's Meetings (if calendar integration available)
|
|
27
|
+
For each meeting:
|
|
28
|
+
- Check `people/` for relevant relationship context
|
|
29
|
+
- Note any commitments to or from attendees
|
|
30
|
+
- Check `context/waiting.md` for pending items
|
|
31
|
+
- Suggest 1-2 talking points based on history
|
|
32
|
+
|
|
33
|
+
### 5. Waiting Items at Risk
|
|
34
|
+
From `context/waiting.md`:
|
|
35
|
+
- Anything overdue that needs follow-up
|
|
36
|
+
- Anything due today that hasn't arrived
|
|
37
|
+
- Patterns (who consistently delivers late)
|
|
38
|
+
|
|
39
|
+
### 6. Pattern Observations
|
|
40
|
+
If any patterns from `context/patterns.md` are relevant to today:
|
|
41
|
+
- Mention briefly
|
|
42
|
+
- Connect to specific activities
|
|
43
|
+
|
|
44
|
+
## Format
|
|
45
|
+
|
|
46
|
+
Keep it scannable. Lead with warnings.
|
|
47
|
+
|
|
48
|
+
```
|
|
49
|
+
## Morning Brief — [Day, Date]
|
|
50
|
+
|
|
51
|
+
### ⚠️ Needs Attention
|
|
52
|
+
- [OVERDUE] [Commitment] was due [date]
|
|
53
|
+
- [DUE TODAY] [Commitment] to [person]
|
|
54
|
+
- [WARNING] [Commitment] due in [X] hours
|
|
55
|
+
|
|
56
|
+
### Today's Focus
|
|
57
|
+
- [Key commitment or priority]
|
|
58
|
+
- [Second priority if applicable]
|
|
59
|
+
|
|
60
|
+
### Meetings
|
|
61
|
+
- **[Time]** [Who/What] — [One-line context]
|
|
62
|
+
- Last talked: [date]
|
|
63
|
+
- Open items: [any commitments/waiting]
|
|
64
|
+
|
|
65
|
+
### Relationships to Reconnect
|
|
66
|
+
- [Person] — last contact [X] days ago
|
|
67
|
+
|
|
68
|
+
### Waiting On
|
|
69
|
+
- [Item] from [Person] — expected [date], now [status]
|
|
70
|
+
|
|
71
|
+
### Something to Consider
|
|
72
|
+
[Pattern or observation if relevant]
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
## Tone
|
|
76
|
+
|
|
77
|
+
- **Warnings first** — Don't bury urgent items
|
|
78
|
+
- **Concise** — Respect their time
|
|
79
|
+
- **Actionable** — What do they need to know/do?
|
|
80
|
+
- **Not overwhelming** — 5-10 items max
|
|
81
|
+
- **Warm** — "Here's what I see for today" not robotic
|
|
82
|
+
|
|
83
|
+
## If Nothing is Pressing
|
|
84
|
+
|
|
85
|
+
Say so warmly:
|
|
86
|
+
"Your calendar is clear today and nothing is overdue. Good day for deep work, or maybe reconnect with someone who's been on your mind."
|
|
87
|
+
|
|
88
|
+
## Without Calendar Integration
|
|
89
|
+
|
|
90
|
+
If no calendar MCP is available:
|
|
91
|
+
- Focus on commitments, waiting items, and relationship health
|
|
92
|
+
- Ask: "Any meetings today I should know about?"
|
|
@@ -0,0 +1,115 @@
|
|
|
1
|
+
# New Person
|
|
2
|
+
|
|
3
|
+
Create a new relationship file for tracking someone.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
`/new-person [name]`
|
|
7
|
+
|
|
8
|
+
## Quick Flow
|
|
9
|
+
|
|
10
|
+
### 1. Basic Information
|
|
11
|
+
"Tell me about [Name]. A few quick things:"
|
|
12
|
+
- What's their role?
|
|
13
|
+
- How do you know them?
|
|
14
|
+
- What's the relationship type? (Client, Colleague, Friend, Prospect, etc.)
|
|
15
|
+
|
|
16
|
+
### 2. Optional Details
|
|
17
|
+
"Anything else I should capture?"
|
|
18
|
+
- Contact info
|
|
19
|
+
- What matters to them
|
|
20
|
+
- Communication preferences
|
|
21
|
+
- Current context
|
|
22
|
+
|
|
23
|
+
### 3. Create File
|
|
24
|
+
Save to `people/[name-slug].md`
|
|
25
|
+
|
|
26
|
+
## Template
|
|
27
|
+
|
|
28
|
+
```markdown
|
|
29
|
+
# [Person Name]
|
|
30
|
+
|
|
31
|
+
**Role:** [Their title/position]
|
|
32
|
+
**Organization:** [Company/org]
|
|
33
|
+
**How we met:** [Context]
|
|
34
|
+
**Relationship type:** [Client, Colleague, Friend, Prospect, etc.]
|
|
35
|
+
|
|
36
|
+
## Quick Stats
|
|
37
|
+
|
|
38
|
+
| Field | Value |
|
|
39
|
+
|-------|-------|
|
|
40
|
+
| Last Contact | [Today's date] |
|
|
41
|
+
| Relationship Health | 🟢 Active |
|
|
42
|
+
| Sentiment | Positive / Neutral / Unknown |
|
|
43
|
+
|
|
44
|
+
## Contact
|
|
45
|
+
|
|
46
|
+
| Channel | Details |
|
|
47
|
+
|---------|---------|
|
|
48
|
+
| Email | [If provided] |
|
|
49
|
+
| Phone | [If provided] |
|
|
50
|
+
| LinkedIn | [If provided] |
|
|
51
|
+
| Preferred | [If known] |
|
|
52
|
+
|
|
53
|
+
## Communication Style
|
|
54
|
+
[How they prefer to communicate, if known]
|
|
55
|
+
|
|
56
|
+
## What Matters to Them
|
|
57
|
+
[Their priorities, if known]
|
|
58
|
+
|
|
59
|
+
## Current Context
|
|
60
|
+
*Last updated: [Today]*
|
|
61
|
+
|
|
62
|
+
[What they're working on, if known]
|
|
63
|
+
|
|
64
|
+
## Our History
|
|
65
|
+
|
|
66
|
+
| Date | Event | Notes |
|
|
67
|
+
|------|-------|-------|
|
|
68
|
+
| [Today] | [Initial context] | Created file |
|
|
69
|
+
|
|
70
|
+
## Commitments
|
|
71
|
+
|
|
72
|
+
### I owe them
|
|
73
|
+
- [None yet]
|
|
74
|
+
|
|
75
|
+
### They owe me
|
|
76
|
+
- [None yet]
|
|
77
|
+
|
|
78
|
+
## Notes
|
|
79
|
+
[Any other context worth remembering]
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
*Created: [Today's date]*
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
## After Creation
|
|
87
|
+
|
|
88
|
+
"Created file for [Name] at `people/[name-slug].md`
|
|
89
|
+
|
|
90
|
+
Want me to:
|
|
91
|
+
- Add more details?
|
|
92
|
+
- Note any commitments?
|
|
93
|
+
- Set a reminder to follow up?"
|
|
94
|
+
|
|
95
|
+
## Name Handling
|
|
96
|
+
|
|
97
|
+
- Create slug from name: "Sarah Chen" → "sarah-chen.md"
|
|
98
|
+
- Handle duplicates: Add identifier if needed ("sarah-chen-acme.md")
|
|
99
|
+
- Non-Latin names: Preserve original, add romanization if provided
|
|
100
|
+
|
|
101
|
+
## Minimal vs. Full
|
|
102
|
+
|
|
103
|
+
**Minimal** (quick capture):
|
|
104
|
+
- Name, role, how you met
|
|
105
|
+
- Creates basic file
|
|
106
|
+
- Fills in more over time
|
|
107
|
+
|
|
108
|
+
**Full** (when user has time):
|
|
109
|
+
- All template fields
|
|
110
|
+
- Contact information
|
|
111
|
+
- Communication preferences
|
|
112
|
+
- Current context
|
|
113
|
+
- History
|
|
114
|
+
|
|
115
|
+
Ask: "Quick capture or full profile?"
|