get-claudia 1.0.0

package/template-v2/.claude/skills/capability-suggester.md

@@ -0,0 +1,279 @@
+# Capability Suggester Skill
+
+**Purpose:** Notice repeated user behaviors and suggest new commands, workflows, or structure to streamline their work.
+
+**Triggers:** Activates when patterns of repeated behavior reach a threshold.
+
+---
+
+## What I Watch For
+
+### Repeated Tasks
+
+**Detection:**
+- Same type of request 3+ times in a week
+- Manual process that could be templated
+- Multi-step workflow repeated frequently
+
+**Examples:**
+```
+"I notice you draft LinkedIn posts almost daily.
+Want me to add a /linkedin-quick command for faster posting?"
+
+"You've asked me to summarize meeting notes 5 times this week.
+Should we add this to your standard meeting capture flow?"
+```
+
+### Frequent Queries
+
+**Detection:**
+- Same question asked regularly
+- Status checks on specific topics
+- Information retrieval patterns
+
+**Examples:**
+```
+"You often ask about project status on Mondays.
+Should I add a project summary to your morning brief automatically?"
+
+"You check on pipeline status frequently.
+Want me to create a /pipeline-quick command for a one-line summary?"
+```
+
+### Workflow Gaps
+
+**Detection:**
+- Steps that are often forgotten
+- Manual connections between automated parts
+- Handoffs that could be smoother
+
+**Examples:**
+```
+"After meetings, you usually update commitments manually.
+Should I automatically suggest commitment updates after /capture-meeting?"
+
+"You often forget to update the client file after calls.
+Want me to prompt for client file updates after meeting captures?"
+```
+
+### Structure Needs
+
+**Detection:**
+- Topics that don't have a home
+- Files that are getting too long
+- Categories that are emerging
+
+**Examples:**
+```
+"You've mentioned 'partnerships' in several contexts but don't
+have a dedicated folder. Should we create partnerships/ ?"
+
+"Your patterns.md is getting long. Want me to split it into
+work-patterns.md and relationship-patterns.md?"
+```
+
+---
+
+## Suggestion Flow
+
+### 1. Observe Pattern
+
+Track behavior without mentioning it until threshold reached:
+- 3+ occurrences for simple tasks
+- 2+ for complex workflows
+- Immediate for obvious improvements
+
+### 2. Propose Enhancement
+
+**Format:**
+```
+"I've noticed [observation].
+
+Would you like me to [specific solution]?
+
+This would [benefit]."
+```
+
+**Examples:**
+
+```
+"I've noticed you check client health status at the start of each week.
+
+Would you like me to add a client health summary to your Monday morning brief?
+
+This would save you from manually checking each client file."
+```
+
+```
+"You often draft follow-up emails after sales calls.
+
+Would you like me to create a /sales-followup command that:
+- Uses the meeting notes as context
+- Drafts a templated follow-up
+- Suggests next steps based on the conversation
+
+I could have this ready for your next call."
+```
+
+### 3. Accept Response
+
+**If yes:**
+- Create the enhancement
+- Explain how to use it
+- Note in learnings.md
+
+**If no:**
+- Acknowledge gracefully
+- Don't suggest again for a while
+- Note preference in learnings.md
+
+**If "maybe later":**
+- Note for future
+- Remind in a week or when context is relevant
+
+---
+
+## Types of Suggestions
+
+### New Commands
+
+**Template:**
+```markdown
+# [Command Name]
+
+[Brief description of what it does]
+
+## When to Use
+[Trigger conditions]
+
+## What It Does
+[Step by step]
+
+## Output
+[What user gets]
+```
+
+**Process:**
+1. Draft command based on observed pattern
+2. Propose to user with explanation
+3. If approved, create in `.claude/commands/`
+4. Confirm creation and explain usage
+
+### Workflow Enhancements
+
+**Modifications to existing flows:**
+- Add steps to existing commands
+- Connect previously separate processes
+- Add automation triggers
+
+**Example:**
+```
+"Currently /capture-meeting extracts decisions and commitments.
+
+Want me to enhance it to also:
+- Update the person file with meeting date
+- Add any new people mentioned to your list
+- Suggest follow-up timing based on meeting content?"
+```
+
+### Structure Changes
+
+**New folders or files:**
+- Create folder for emerging category
+- Split growing files
+- Add templates for new types
+
+**Example:**
+```
+"You've started tracking vendor relationships separately from clients.
+
+Should I create:
+- vendors/ folder with similar structure to clients/
+- /vendor-status command for quick checks?"
+```
+
+---
+
+## Learning Integration
+
+### What Gets Stored
+
+In `context/learnings.md`:
+
+```markdown
+## Suggested Capabilities
+
+### Accepted
+- /linkedin-quick command (created Jan 15)
+- Auto-client-update after meetings (enabled Jan 18)
+
+### Declined
+- Partnership folder (user prefers flat structure)
+- Automatic deadline reminders (user finds them annoying)
+
+### Pending
+- Sales follow-up template (user said "maybe later" - Jan 20)
+```
+
+### Feedback Loop
+
+Track whether suggestions are used:
+- Command created but never used → Note for learning
+- Command used frequently → Validated pattern
+- Enhancement enabled then disabled → Preference noted
+
+---
+
+## Guardrails
+
+### Don't Overwhelm
+
+- Max 1 suggestion per session (unless asked)
+- Space out suggestions over time
+- Don't repeat declined suggestions
+
+### Don't Over-Engineer
+
+- Start with simple solutions
+- Only suggest what's clearly needed
+- Avoid adding complexity for its own sake
+
+### Respect User Style
+
+- Some users like lots of structure
+- Some prefer minimal tooling
+- Learn and adapt to their preference
+
+---
+
+## Proactive vs. Reactive
+
+### Proactive (I bring it up)
+- When pattern is clear and benefit is obvious
+- During natural pauses in work
+- At start of session if something significant
+
+### Reactive (when asked)
+```
+User: "Is there anything you think we should add?"
+User: "What could we do to make this easier?"
+User: "Any suggestions for improving my workflow?"
+```
+
+Provide comprehensive list of observed opportunities.
+
+---
+
+## Integration
+
+### With Pattern Recognizer
+- Feed patterns into capability analysis
+- Notice when patterns suggest tooling needs
+
+### With Memory Manager
+- Persist suggestions and responses
+- Track what works over time
+
+### With Onboarding
+- During initial setup, note user preferences for suggestions
+- Some users want lots of suggestions, others want minimal

package/template-v2/.claude/skills/commitment-detector.md

@@ -0,0 +1,210 @@
+# Commitment Detector Skill
+
+**Purpose:** Automatically detect promises and commitments in conversation and offer to track them.
+
+**Triggers:** Activates when language patterns suggest a commitment has been made.
+
+---
+
+## Detection Patterns
+
+### Explicit Promises
+
+**High confidence patterns:**
+- "I'll [action] by [time]"
+- "I'll send you [thing] by [day/date]"
+- "I promised to [action]"
+- "I committed to [action]"
+- "I need to [action] by [deadline]"
+- "I told them I would [action]"
+
+**Examples:**
+- "I'll send the proposal by Friday" → Track: proposal, Friday
+- "I promised Sarah I'd review her doc" → Track: review doc, for Sarah, needs deadline
+- "I told the team I'd have feedback by EOD" → Track: feedback, EOD today
+
+### Implicit Obligations
+
+**Medium confidence patterns:**
+- "Let me get back to you on that"
+- "I should follow up on [thing]"
+- "I need to [action]" (without deadline)
+- "I'll think about [topic] and respond"
+
+**Response:** Ask for clarification
+```
+"Sounds like a commitment. When should this be done?"
+```
+
+### What NOT to Track
+
+**Vague intentions (skip):**
+- "We should explore that someday"
+- "That might be worth looking into"
+- "Maybe I'll try that"
+- "I've been meaning to..."
+
+**These don't have accountability attached.**
+
+---
+
+## Tracking Flow
+
+### When I Detect a Commitment
+
+1. **Surface what I heard:**
+   ```
+   "I heard a commitment: Send proposal to Sarah by Friday.
+   Should I track this?"
+   ```
+
+2. **If confirmed, capture:**
+   - What: The specific deliverable
+   - To: Who it's for (if anyone)
+   - Due: Deadline
+   - Context: Any relevant notes
+
+3. **Add to context/commitments.md**
+
+4. **Link to person file if relevant**
+
+### If Deadline is Unclear
+
+```
+"I'll track: Review Sarah's document.
+When should this be done?"
+```
+
+Options:
+- Specific date/time → Use that
+- "Soon" or "ASAP" → Ask for actual date
+- "No rush" → Don't track (vague intention)
+
+---
+
+## Commitment Types
+
+### You Owe Others
+Stored in `context/commitments.md`
+
+```markdown
+## Due Soon
+
+| Commitment | To | Due | Status |
+|------------|-----|-----|--------|
+| Send proposal draft | Sarah | Fri Jan 24 | On track |
+| Review contract | Legal team | Mon Jan 27 | Needs attention |
+```
+
+### Others Owe You
+Stored in `context/waiting.md`
+
+**Detection patterns:**
+- "They said they'd [action] by [time]"
+- "[Person] owes me [thing]"
+- "Waiting on [person] for [thing]"
+- "They promised to [action]"
+
+```
+"I heard: Waiting on Sarah's feedback by Thursday.
+Should I track this in your waiting list?"
+```
+
+---
+
+## Warning System
+
+### 48-Hour Warning
+Two days before deadline, surface in morning brief:
+
+```
+### ⚠️ Due Soon
+- [WARNING] Proposal to Sarah due in 48 hours (Friday)
+```
+
+### Day-Of Reminder
+On due date:
+
+```
+### ⚠️ Due Today
+- [DUE TODAY] Proposal to Sarah
+```
+
+### Overdue Escalation
+When past due:
+
+```
+### ⚠️ OVERDUE
+- [OVERDUE] Proposal to Sarah was due Friday (2 days ago)
+  → Suggested action: Send what you have, or communicate delay
+```
+
+---
+
+## Recovery Suggestions
+
+When something is overdue, offer recovery options:
+
+```
+The proposal for Sarah is 2 days overdue. Options:
+
+1. Send it now (if ready)
+2. Send partial progress + timeline for rest
+3. Communicate delay with new ETA
+4. Acknowledge and ask for extension
+
+What would you like to do?
+```
+
+---
+
+## Commitment Lifecycle
+
+```
+Detected → Confirmed → Tracked → Warning → Due → Completed/Overdue
+                                    ↓
+                              Recovery (if overdue)
+```
+
+### Marking Complete
+
+When user mentions completing something:
+- "I sent that proposal to Sarah"
+- "Done with the contract review"
+
+```
+"Got it. Marking the proposal to Sarah as complete.
+Anything to note about how it went?"
+```
+
+Move from active to completed section with date.
+
+---
+
+## Integration
+
+### With Relationship Tracker
+- Link commitments to people files
+- Show open commitments when person is mentioned
+
+### With Morning Brief
+- Surface warnings and due-todays
+- Highlight overdue items
+
+### With Pattern Recognizer
+- Notice if certain commitments consistently slip
+- Track estimation accuracy over time
+
+---
+
+## Settings
+
+Can be configured in `context/me.md`:
+
+```yaml
+commitment_tracking:
+  warning_days: 2              # Days before deadline to warn
+  auto_detect: true            # Automatically detect or only when asked
+  track_waiting: true          # Also track what others owe
+  completion_notes: optional   # Ask for notes on completion
+```