Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework. Plus paired anti-slop design skills for marketing and product UI. Works with Claude Code, Cursor, Kiro, Gemini CLI, Codex.
Python agent-loopagent-pluginsagent-skillsagenticai-agentsclaude-codeclosed-loopcursorgarry-tangbraingstackknowledge-managementloop-engineeringobsidianpeople-crmproductivitysecond-brainself-evolvingverification-harnessworker-agents
Rework COG to use Claude Agent Skills architecture
Claudecdc65167823a
diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex ae53f03..64dbeeb 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -33,47 +33,36 @@"productivity","note-taking"],- "commands": [+ "skills": [{"name": "onboarding",- "path": ".claude/commands/onboarding.md",+ "path": ".claude/skills/onboarding/SKILL.md","description": "Personalize COG for your workflow - creates profile, interests, and watchlist files (run this first!)"},- {- "name": "daily-brief",- "path": ".claude/commands/daily-brief.md",- "description": "Generate personalized news intelligence with verified sources (7-day freshness requirement)"- },{"name": "braindump",- "path": ".claude/commands/braindump.md",+ "path": ".claude/skills/braindump/SKILL.md","description": "Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction"},+ {+ "name": "daily-brief",+ "path": ".claude/skills/daily-brief/SKILL.md",+ "description": "Generate personalized news intelligence with verified sources (7-day freshness requirement)"+ },{"name": "weekly-checkin",- "path": ".claude/commands/weekly-checkin.md",+ "path": ".claude/skills/weekly-checkin/SKILL.md","description": "Cross-domain pattern analysis and strategic reflection for weekly review"},{"name": "knowledge-consolidation",- "path": ".claude/commands/knowledge-consolidation.md",+ "path": ".claude/skills/knowledge-consolidation/SKILL.md","description": "Build frameworks from scattered insights across all braindumps and notes"}],- "agents": [- {- "name": "brain-dump-analyst",- "path": ".claude/subagents/brain-dump-analyst.md",- "description": "Transforms stream-of-consciousness into structured insights with domain classification and competitive intelligence extraction"- },- {- "name": "news-curator",- "path": ".claude/subagents/news-curator.md",- "description": "Finds verified news with strict 7-day freshness requirement, cross-references sources, and generates personalized briefings"- }- ],"metadata": {"pluginRoot": ".",+ "architecture": "claude-agent-skills","features": ["Self-evolving intelligence with pattern recognition","Self-healing system with auto-updating cross-references",@@ -81,7 +70,8 @@"Privacy-first architecture with strict domain separation","Plain text markdown files (no database, no vendor lock-in)","Multi-device sync via iCloud (iPhone, iPad, Mac)",- "Git version control for tracking thinking evolution"+ "Git version control for tracking thinking evolution",+ "Progressive disclosure for efficient context usage"],"requirements": {"obsidian": "Recommended for markdown file management",@@ -94,12 +84,20 @@"onboardingTime": "2 minutes"},"directoryStructure": {+ ".claude/skills": "5 specialized agent skills (onboarding, braindump, daily-brief, weekly-checkin, knowledge-consolidation)","00-inbox": "Temporary processing area with profile and interests files","01-daily": "Daily briefs and check-ins","02-personal": "Personal domain (strict privacy)","03-professional": "Professional domain with competitive watchlist","04-projects": "Project-specific tracking","05-knowledge": "Consolidated insights and patterns"+ },+ "skillArchitecture": {+ "type": "agent-skills",+ "skills": 5,+ "invocation": "model-invoked",+ "progressiveDisclosure": true,+ "description": "Self-contained skills that combine orchestration and specialized processing using Claude's progressive disclosure pattern"}}}diff --git a/.claude/commands/braindump.md b/.claude/commands/braindump.mddeleted file mode 100644index 74e4a64..0000000--- a/.claude/commands/braindump.md+++ /dev/null@@ -1,174 +0,0 @@-# Brain Dump Command--## Purpose-Quick capture and initial processing of stream-of-consciousness thoughts, ideas, and insights with immediate domain classification and basic structuring.--## Command: `/braindump`--## Pre-Flight Check--**Before executing, check for user profile:**--1. Look for `00-inbox/MY-PROFILE.md` in the vault-2. If NOT found:- ```- Welcome to COG! It looks like this is your first time.-- Before we start, let's quickly set up your profile (takes 2 minutes).-- Type '/onboarding' to get started, or I can proceed with default settings.- ```-3. If found:- - Read the profile to get user's name and active projects- - If user has active projects listed, offer them as domain options- - Use user's name for friendly communication--## Process Flow--This command orchestrates the brain dump capture process by delegating to the specialized **brain-dump-analyst** subagent.--### 1. User Interaction & Input Collection-**Your role (Claude Code):**-- Greet user warmly (use their name from MY-PROFILE.md if available)-- Ask: "What's on your mind?" or "Ready for a brain dump?"-- Collect their stream-of-consciousness input (can be long, rambling, voice-to-text, etc.)-- Accept any format - no judgment, no filtering--### 2. Domain Classification-**Your role (Claude Code):**-Ask user to classify or auto-detect based on content:--**If user profile exists with projects:**-- **Personal:** Individual growth, relationships, wellness-- **Professional:** Work, leadership, career development-- **Project-Specific:** Related to specific projects- - If MY-PROFILE.md lists projects, offer: "Which project? [list project names]"- - Example: "Which project? (1) SaaS Product, (2) Book Writing, (3) Health App"-- **Mixed/Unclear:** Spans multiple areas--**If no profile:** Use standard personal/professional/mixed classification--### 3. Delegate to Brain Dump Analyst Subagent-**Your role (Claude Code):**--Once you have the raw braindump content and domain classification, **delegate ALL analysis and processing to the brain-dump-analyst subagent**:--```markdown-I'm passing this to the brain-dump-analyst subagent for processing...--**To brain-dump-analyst subagent:**--Process this braindump according to your analysis framework:--**Raw Content:**-[User's unfiltered braindump content]--**Domain:** [personal|professional|project-specific]-**Project:** [project-name if applicable]-**Date:** [current date]-**User Name:** [from MY-PROFILE.md if available]--**Competitive Watchlist:** [Read from 03-professional/COMPETITIVE-WATCHLIST.md if exists]--**Instructions:**-- Perform full braindump analysis per your protocol-- Check for competitive intelligence mentions (if watchlist exists)-- Generate structured output with metadata-- Save to appropriate domain folder:- - Personal: `02-personal/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`- - Professional: `03-professional/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`- - Project: `04-projects/[project-slug]/braindumps/braindump-YYYY-MM-DD-HHMM-<title>.md`- - Mixed: `00-inbox/braindump-YYYY-MM-DD-HHMM-<title>.md`--- If competitive intel detected, also update: `04-projects/[project]/competitive/[company-name].md`--- Use proper YAML frontmatter with quoted strings-- Include all analysis sections per your template-- Provide confidence assessment--Return the file path where you saved the braindump.-```--### 4. Confirm Completion-**Your role (Claude Code):**-- Wait for subagent to complete processing-- Confirm file was created-- Show user: "Braindump saved to [file path]"-- Optionally show quick summary of themes identified-- Ask: "Would you like me to run deeper analysis? (Type `/brain-dump-analysis`)"--## What NOT to Do--**Do NOT:**-- Process or analyze the content yourself-- Create the output file yourself-- Perform theme extraction yourself-- Do competitive intelligence detection yourself--**Instead:**-- Collect input from user-- Determine domain/project-- Delegate to brain-dump-analyst subagent-- Confirm completion--## Competitive Intelligence Detection--The brain-dump-analyst subagent will automatically:-- Read `03-professional/COMPETITIVE-WATCHLIST.md` if it exists-- Scan braindump content for mentions of tracked companies/people-- Extract competitive intel to `04-projects/[project]/competitive/[company].md`-- Cross-reference back to the original braindump--## Output File Structure--The brain-dump-analyst subagent creates files with this structure:--```markdown-----type: "braindump"-domain: "[personal|professional|project-specific|mixed]"-project: "[project-name]" # Only if project-specific-date: "YYYY-MM-DD"-created: "YYYY-MM-DD HH:MM"-themes: ["theme1", "theme2", "theme3"]-tags: ["#braindump", "#raw-thoughts", "#domain-tag"]-status: "captured"------# Braindump: [Auto-generated title]--## Raw Thoughts-[Original user content preserved]--## Main Themes-[Identified by subagent]--## Action Items-[Extracted by subagent]--## Questions-[Identified by subagent]--## Connections-[Identified by subagent]--## Processing Notes-[Subagent's analysis notes]-```--## Integration with Other Commands--### Immediate Follow-up-- `/brain-dump-analysis` - Deep analysis via brain-dump-analyst subagent-- `/daily-checkin` - Reflect on themes-- `/scout-project-analysis` - Project-specific insights (if applicable)--### Competitive Intelligence-If competitive mentions detected, the brain-dump-analyst will automatically update competitive files and mention this in the output.--## Success Metrics-- Speed of capture (minimize user friction)-- Successful delegation to subagent-- File saved to correct location-- User feels heard and understood-- Competitive intel auto-extracted when relevantdiff --git a/.claude/commands/daily-brief.md b/.claude/commands/daily-brief.mddeleted file mode 100644index 5189ed4..0000000--- a/.claude/commands/daily-brief.md+++ /dev/null@@ -1,194 +0,0 @@-# Daily Brief Command--## Purpose-Generate personalized daily news briefing with verified, current information tailored to user's interests and strategic priorities.--## Command: `/daily-brief`--## Pre-Flight Check--**Before executing, check for user profile:**--1. Look for `00-inbox/MY-PROFILE.md` and `00-inbox/MY-INTERESTS.md` in the vault-2. If NOT found:- ```- Welcome to COG! Daily briefs work best when personalized.-- Let's quickly set up your profile (takes 2 minutes).-- Type '/onboarding' to get started, or I can generate a general brief.- ```-3. If found:- - Read `MY-INTERESTS.md` to get topics for news curation- - Read `MY-PROFILE.md` to get user's name and active projects- - Use topics to curate relevant news- - Connect news to user's active projects when relevant--## Process Flow--This command orchestrates the daily brief generation by delegating to the specialized **news-curator** subagent.--### 1. Gather Context-**Your role (Claude Code):**--Collect the information needed for personalized curation:--- Read `00-inbox/MY-PROFILE.md` for:- - User's name- - User's role/job- - Active projects--- Read `00-inbox/MY-INTERESTS.md` for:- - Topics they're interested in- - Preferred news sources--- Read `03-professional/COMPETITIVE-WATCHLIST.md` (if exists) for:- - Companies/people to track--### 2. Delegate to News Curator Subagent-**Your role (Claude Code):**--Once you have the context, **delegate ALL news research and curation to the news-curator subagent**:--```markdown-**To news-curator subagent:**--Generate a personalized daily news briefing using your verification and curation framework:--**User Context:**-- Name: [from MY-PROFILE.md]-- Role: [from MY-PROFILE.md]-- Active Projects: [list from MY-PROFILE.md]--**Interest Areas:**-[Topics from MY-INTERESTS.md]--**Preferred News Sources:**-[Sources from MY-INTERESTS.md]--**Competitive Watchlist:**-[Companies/people from COMPETITIVE-WATCHLIST.md if it exists]--**Date:** [Today's date]--**Instructions:**-- Search for verified news from **last 7 days ONLY**-- Focus on topics from the user's interest areas-- Prioritize news relevant to their role and active projects-- Include competitive intelligence on watchlist items-- Cross-reference multiple credible sources-- Use WebFetch to verify any statistics before including them-- Include clickable source links for ALL claims--- Generate briefing with:- - Executive Summary- - Strategic News (relevant to projects/role)- - Market Intelligence (industry trends)- - Opportunities & Risks- - Comprehensive Sources section--- Save to: `01-daily/briefs/daily-brief-YYYY-MM-DD.md`--- Use proper YAML frontmatter with quoted strings-- Ensure 100% compliance with 7-day freshness requirement-- Provide confidence assessment for all claims--Return the file path where you saved the brief.-```--### 3. Confirm Completion-**Your role (Claude Code):**-- Wait for subagent to complete research and curation-- Confirm file was created-- Show user: "Daily brief saved to [file path]"-- Optionally show executive summary-- Ask if they want to explore any topic deeper--## What NOT to Do--**Do NOT:**-- Search for news yourself-- Curate or analyze news yourself-- Create the output file yourself-- Verify sources yourself--**Instead:**-- Gather user context from profile files-- Delegate to news-curator subagent-- Confirm completion--## Verification Standards (Enforced by Subagent)--The news-curator subagent will:-- **News Age**: Only include news from last 7 days-- **Source Credibility**: Cross-reference minimum 2 credible sources-- **Source Attribution**: Include clickable links for ALL claims-- **Statistical Verification**: Use WebFetch to verify statistics-- **Uncertainty Handling**: Explicitly state when info can't be verified--## Output File Structure--The news-curator subagent creates files with this structure:--```markdown-----type: "daily-brief"-domain: "shared"-date: "YYYY-MM-DD"-created: "YYYY-MM-DD HH:MM"-sources_verified: true-news_age_verified: true-confidence: "high"-tags: ["#daily-brief", "#news", "#strategic-intelligence"]-interests: ["interest1", "interest2"]-projects_referenced: ["project1"]------# Daily Brief - [Date]--## Executive Summary-[2-3 sentences highlighting most important developments]--## Strategic News-### [News Item 1]-[With source links]--## Market Intelligence-### [Trend 1]-[With source links]--## Opportunities-[Actionable opportunities identified]--## Risks & Threats-[Potential challenges flagged]--## Sources-### Strategic News-- [Source 1 with link]-- [Source 2 with link]--### Market Intelligence-- [Source 3 with link]-```--## Error Handling--If news-curator subagent cannot find recent news:-- It will state explicitly: "No significant news found in [interest area] in last 7 days"-- It will never fabricate or use older news-- It will suggest expanding search criteria or alternative sources--## Integration with Other Commands--### Follow-up Actions-- `/braindump` - Capture thoughts sparked by news-- `/scout-project-analysis` - Analyze impact on specific project-- `/weekly-checkin` - Reflect on news patterns over the week--## Success Metrics-- Successful delegation to subagent-- File saved to correct location-- All news within 7-day window-- All sources verified and linked-- User finds briefing relevant and actionablediff --git a/.claude/commands/knowledge-consolidation.md b/.claude/commands/knowledge-consolidation.mddeleted file mode 100644index 9777c11..0000000--- a/.claude/commands/knowledge-consolidation.md+++ /dev/null@@ -1,263 +0,0 @@-# Knowledge Consolidation Command--## Purpose-Transform scattered insights from braindumps, daily briefs, and check-ins into coherent frameworks and "single source of truth" knowledge documents.--## Command: `/consolidate-knowledge`--## Process Flow--### 1. Data Gathering-- Scan all braindumps since last consolidation-- Review daily briefs and check-ins-- Analyze meeting transcripts and project documents-- Identify unprocessed or partially processed content--### 2. Pattern Recognition-- Identify recurring themes and concepts-- Detect evolution of thinking over time-- Recognize contradictions or shifts in perspective-- Group related insights across documents--### 3. Framework Development-- Synthesize scattered insights into coherent principles-- Build mental models from accumulated learnings-- Create decision-making frameworks-- Develop strategic approaches from patterns--### 4. Knowledge Integration-- Update existing "single source of truth" documents-- Create new consolidated knowledge files as needed-- Cross-reference with existing frameworks-- Maintain timeline of thinking evolution--### 5. Cleanup and Archival-- Mark processed braindumps appropriately-- Archive outdated or superseded insights-- Remove redundancy while preserving important context-- Maintain clean, current knowledge base--### 6. Output Generation-- Save consolidated insights to `05-knowledge/consolidated/`-- Create timeline entries in `05-knowledge/timeline/`-- Update pattern documentation in `05-knowledge/patterns/`--## Metadata Template-```yaml-----type: knowledge-consolidation-domain: integrated-date: YYYY-MM-DD-consolidation_period: "YYYY-MM-DD to YYYY-MM-DD"-created: YYYY-MM-DD HH:MM-sources_analyzed: [number]-frameworks_updated: [framework1, framework2]-new_insights: [number]-tags: ["#consolidation", "#knowledge", "#frameworks"]-----```--## Content Structure--### 1. Consolidation Summary-```markdown-## Executive Summary-- Period analyzed: [Start date] to [End date]-- Documents processed: [number] braindumps, [number] briefs, [number] check-ins-- Major themes identified: [list]-- Frameworks updated/created: [list]-- Key insights synthesized: [list]--## Processing Statistics-- Total documents analyzed: [number]-- New patterns identified: [number]-- Frameworks updated: [number]-- New frameworks created: [number]-- Archive actions taken: [number]-```--### 2. Pattern Analysis-```markdown-## Recurring Themes-### Theme 1: [Name]-- **Frequency**: Appeared in [X] documents-- **Evolution**: How thinking evolved over period-- **Key Insights**:- - Insight 1 with source references- - Insight 2 with source references-- **Framework Implications**: How this affects existing frameworks--### Theme 2: [Name]-[Same structure as Theme 1]--## Cross-Cutting Patterns-- Pattern 1: Description and significance-- Pattern 2: Description and significance--## Contradictions and Shifts-- What changed: Description of thinking evolution-- Why it changed: Contributing factors and insights-- Resolution: Current understanding or framework-```--### 3. Framework Updates-```markdown-## Updated Frameworks--### Framework 1: [Name]-**Location**: `05-knowledge/consolidated/[filename].md`--**What Changed**:-- Addition/modification 1-- Addition/modification 2--**Supporting Insights**:-- Source insight 1 [link to braindump]-- Source insight 2 [link to braindump]--**New Applications**:-- How to apply this framework-- Specific use cases--### Framework 2: [Name]-[Same structure as Framework 1]--## New Frameworks Created--### New Framework: [Name]-**Created**: Based on [X] insights from [timeframe]--**Core Principles**:-1. Principle 1-2. Principle 2-3. Principle 3--**Supporting Evidence**:-- Evidence 1 [link]-- Evidence 2 [link]--**Application**:-- Use case 1-- Use case 2-```--### 4. Timeline Entry-```markdown-## Thinking Evolution Timeline--### [Date Range]: [Major Theme/Shift]-**What Changed**: Description of evolution--**Catalysts**:-- Event/insight 1 that triggered change-- Event/insight 2 that triggered change--**Evidence Trail**:-- [Date] - Early thinking [link]-- [Date] - Intermediate development [link]-- [Date] - Current understanding [link]--**Impact**:-- How this shift affects decisions-- How this shift affects strategies-- How this shift affects frameworks-```--### 5. Action Items-```markdown-## Knowledge Base Maintenance--### Updates Made-- [X] Updated framework: [name]-- [X] Created new consolidated doc: [name]-- [X] Archived outdated insights: [list]--### Future Consolidation Needs-- [ ] Area 1 needs deeper analysis (target: [date])-- [ ] Area 2 has contradictions to resolve (target: [date])-- [ ] Area 3 ready for framework creation (target: [date])--### Cross-Reference Updates-- [ ] Update document 1 with new insights-- [ ] Link document 2 to consolidated framework-```--## Consolidation Guidelines--### Quality Over Quantity-- Don't force insights that aren't mature enough-- Let patterns emerge naturally from evidence-- Be patient with incomplete thinking-- Quality frameworks require time and evidence--### Preserve Nuance-- Don't over-simplify complex insights-- Maintain important context and conditions-- Note when frameworks have limitations-- Preserve contradictions that haven't resolved--### Maintain Traceability-- Always link back to source documents-- Show evidence trail for frameworks-- Document evolution of thinking-- Enable future validation or revision--### Living Documents-- Frameworks should evolve with new insights-- Regular updates better than perfect first draft-- Mark frameworks as "working" vs "stable"-- Encourage iteration and refinement--## Analysis Techniques--### Pattern Detection-1. **Frequency Analysis**: What comes up repeatedly?-2. **Temporal Clustering**: What insights emerged together?-3. **Domain Correlation**: What patterns cross domains?-4. **Contradiction Analysis**: Where does thinking conflict?--### Framework Synthesis-1. **Identify Core Principles**: What are the fundamental truths?-2. **Test Against Evidence**: Do source insights support principles?-3. **Define Boundaries**: When does framework apply/not apply?-4. **Create Applications**: How to use this framework?--### Timeline Construction-1. **Mark Inflection Points**: When did thinking shift?-2. **Identify Catalysts**: What triggered changes?-3. **Document Evolution**: How did understanding develop?-4. **Extract Learnings**: What does evolution teach us?--## Output Locations--### Consolidated Knowledge-`05-knowledge/consolidated/[domain]-[topic]-YYYY-MM-DD.md`-- Synthesized insights and frameworks-- "Single source of truth" documents-- Living documents that evolve--### Pattern Documentation-`05-knowledge/patterns/pattern-[name]-YYYY-MM-DD.md`-- Recurring patterns across domains-- Cross-domain correlations-- Behavioral and thinking patterns--### Timeline Narratives-`05-knowledge/timeline/[topic]-evolution-YYYY-MM-DD.md`-- Evolution of thinking over time-- Inflection points and catalysts-- Learning from thinking progression--## Success Metrics-- Completeness: All relevant insights processed-- Coherence: Frameworks logically consistent-- Traceability: Clear links to source material-- Actionability: Frameworks applicable to decisions-- Evolution: Documented thinking progression--## Common Use Cases-- Weekly consolidation of daily insights-- Monthly framework development-- Quarterly strategic synthesis-- Annual knowledge base cleanup-- Pre-decision framework consultationdiff --git a/.claude/commands/weekly-checkin.md b/.claude/commands/weekly-checkin.mddeleted file mode 100644index d77eaf7..0000000--- a/.claude/commands/weekly-checkin.md+++ /dev/null@@ -1,171 +0,0 @@-# Weekly Check-in Command--## Purpose-Comprehensive weekly review and analysis integrating insights across all domains (personal, professional, projects) with pattern recognition and strategic planning.--## Command: `/weekly-checkin`--## Pre-Flight Check--**Check for user profile (optional but enhances experience):**--1. Look for `00-inbox/MY-PROFILE.md` in the vault-2. If found:- - Read user's name for personalization- - Read active projects to review project-specific progress- - Tailor reflection questions to user's role and projects--## Process Flow--This command helps you reflect on your week through guided conversation and structured output.--### 1. Gather Context-**Your role (Claude Code):**--- Read `00-inbox/MY-PROFILE.md` if available for personalization-- Scan recent files from the past week:- - Daily briefs in `01-daily/briefs/`- - Braindumps in `02-personal/braindumps/`, `03-professional/braindumps/`, `04-projects/*/braindumps/`- - Check-ins in `01-daily/checkins/`--### 2. Guided Reflection-**Your role (Claude Code):**--Lead user through reflection questions:--**Overall Week Assessment**-- "How would you rate this week on a 1-5 scale? Why?"-- "What were your biggest wins?"-- "What were your main challenges?"--**Domain Reviews**-- **Personal:** "How did you take care of yourself this week?"-- **Professional:** "What did you accomplish at work? Any standout moments?"-- **Projects:** [If they have projects] "How did [project name] progress?"--**Pattern Recognition**-- "Did you notice any recurring themes in your braindumps?"-- "How did your energy levels vary throughout the week?"-- "Any connections between different areas of your life?"--**Forward Planning**-- "What are your top 3 priorities for next week?"-- "Anything from this week you want to carry forward?"-- "What do you want to do differently?"--### 3. Generate Weekly Check-in Document-**Your role (Claude Code):**--Based on the conversation, create a structured check-in document:--```markdown-----type: "weekly-checkin"-domain: "integrated"-date: "YYYY-MM-DD"-week_of: "YYYY-MM-DD"-created: "YYYY-MM-DD HH:MM"-tags: ["#weekly-checkin", "#reflection", "#planning"]-domains_analyzed: ["personal", "professional", "projects"]-rating: [1-5]------# Weekly Check-in - Week of [Date]--## Executive Summary-**Week Rating:** [1-5] - [User's reasoning]--**Key Highlights:**-- [Win 1]-- [Win 2]--**Main Challenges:**-- [Challenge 1]-- [Challenge 2]--## Domain Reviews--### Personal-- [User's reflection on personal wellness, relationships, growth]--### Professional-- [User's reflection on work accomplishments, challenges, team dynamics]--### Projects-[If applicable, for each project:]-#### [Project Name]-- **Progress:** [What moved forward]-- **Blockers:** [What's in the way]-- **Next Steps:** [What's coming]--## Pattern Recognition--### Recurring Themes-- [Theme 1 identified]-- [Theme 2 identified]--### Energy Patterns-- [Observations about energy levels, productive times]--### Cross-Domain Insights-- [Connections between personal/professional/projects]--## Forward Planning--### Priorities for Next Week-1. [Priority 1]-2. [Priority 2]-3. [Priority 3]--### Carry Forward Items-- [ ] [Unresolved item from this week]-- [ ] [Ongoing task]--### What to Change-- [Experiment or adjustment to try next week]--## Success Criteria for Next Week-- [Measurable outcome 1]-- [Measurable outcome 2]-```--Save to: `01-daily/checkins/weekly-checkin-YYYY-MM-DD.md`--### 4. Confirm Completion-**Your role (Claude Code):**-- Confirm file was created-- Show user: "Weekly check-in saved to [file path]"-- Offer to review any patterns spotted across recent weeks--## What to Focus On--**Do:**-- Have a warm, conversational tone-- Ask follow-up questions based on user's answers-- Help identify patterns they might not see themselves-- Be honest and objective in summarizing their reflections-- Celebrate wins genuinely-- Acknowledge challenges without sugar-coating--**Don't:**-- Rush through the questions-- Make assumptions about what matters to them-- Judge their answers or week rating-- Over-structure their free-form reflections--## Integration with Other Commands--### Pattern Analysis-- Review multiple weekly check-ins monthly to spot long-term patterns-- Use `/knowledge-consolidation` to extract frameworks from check-ins--### Project Tracking-- Weekly check-ins provide historical record of project progress-- Useful for `/scout-project-analysis` to understand evolution--## Success Metrics-- User completes meaningful reflection-- Patterns identified and documented-- Clear priorities set for next week-- User feels heard and understood-- File saved with complete informationdiff --git a/.claude/skills/braindump/SKILL.md b/.claude/skills/braindump/SKILL.mdnew file mode 100644index 0000000..ed40172--- /dev/null+++ b/.claude/skills/braindump/SKILL.md@@ -0,0 +1,339 @@+---+name: braindump+description: Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction+---++# COG Braindump Skill++## Purpose+Transform raw thoughts into strategic intelligence through quick capture, systematic analysis, pattern recognition, and domain-aware insight extraction with minimal user friction.++## When to Invoke+- User wants to capture stream-of-consciousness thoughts+- User says "braindump", "brain dump", "capture thoughts", or "write down ideas"+- User has ideas they want to quickly record+- User mentions wanting to get thoughts out of their head++## Pre-Flight Check++**Before executing, check for user profile:**++1. Look for `00-inbox/MY-PROFILE.md` in the vault+2. If NOT found:+ ```+ Welcome to COG! It looks like this is your first time.++ Before we start, let's quickly set up your profile (takes 2 minutes).++ Would you like to run onboarding first, or should I proceed with default settings?+ ```+3. If found:+ - Read the profile to get user's name and active projects+ - If user has active projects listed, offer them as domain options+ - Use user's name for friendly communication+ - Read `03-professional/COMPETITIVE-WATCHLIST.md` if it exists for competitive intelligence detection++## Process Flow++### 1. User Interaction & Input Collection+- Greet user warmly (use their name from MY-PROFILE.md if available)+- Ask: "What's on your mind?" or "Ready for a brain dump?"+- Collect their stream-of-consciousness input (can be long, rambling, voice-to-text, etc.)+- Accept any format - no judgment, no filtering++### 2. Domain Classification+Ask user to classify or auto-detect based on content:++**If user profile exists with projects:**+- **Personal:** Individual growth, relationships, wellness+- **Professional:** Work, leadership, career development+- **Project-Specific:** Related to specific projects+ - If MY-PROFILE.md lists projects, offer: "Which project? [list project names]"+ - Example: "Which project? (1) SaaS Product, (2) Book Writing, (3) Health App"+- **Mixed/Unclear:** Spans multiple areas++**If no profile:** Use standard personal/professional/mixed classification++### 3. Content Analysis and Processing++Apply the comprehensive analysis framework directly:++#### Phase 1: Content Ingestion+Analyze the input to understand:+- **Content Type:** [voice-transcript|written-notes|mixed]+- **Length:** [word-count]+- **Energy Level:** [high|medium|low]+- **Emotional Tone:** [excited|frustrated|curious|concerned|neutral|mixed]+- **Context:** [situational-background]++#### Phase 2: Structural Analysis+Extract and identify:+- **Main Themes:** [3-5 primary topics]+- **Supporting Ideas:** [related concepts and details]+- **Questions Raised:** [explicit and implicit questions]+- **Decisions Contemplated:** [choices being considered]+- **Action Items:** [tasks and commitments identified]++#### Phase 3: Domain Classification (with confidence)+Determine:+- **Primary Domain:** [personal|professional|project-specific] with confidence level+- **Secondary Domains:** [if content spans multiple areas]+- **Cross-Domain Elements:** [themes that apply across domains]+- **Privacy Considerations:** [sensitive content requiring protection]++#### Phase 4: Strategic Insight Extraction+Identify:+- **Key Insights:** [3-5 most important realizations]+- **Pattern Recognition:** [connections to previous thoughts/decisions]+- **Strategic Implications:** [what this means for goals and priorities]+- **Decision Framework:** [how this informs future choices]++#### Phase 5: Competitive Intelligence Detection+If COMPETITIVE-WATCHLIST.md exists:+- Scan braindump content for mentions of tracked companies/people+- Extract competitive intelligence to separate files+- Create cross-references back to original braindump++### 4. Generate Structured Output++Create braindump file with this structure:++```markdown+---+type: "braindump"+analyst: "brain-dump-analyst"+domain: "[personal|professional|project-specific|mixed]"+project: "[project-name]" # Only if project-specific+date: "YYYY-MM-DD"+created: "YYYY-MM-DD HH:MM"+themes: ["theme1", "theme2", "theme3"]+tags: ["#braindump", "#raw-thoughts", "#domain-tag"]+status: "captured"+energy_level: "[high|medium|low]"+emotional_tone: "[primary-emotion]"+confidence: "[high|medium|low]"+---++# Braindump: [Auto-generated descriptive title]++## Raw Thoughts+[Original user content preserved exactly as provided]++## Content Analysis++### Main Themes+1. **Theme 1:** [description and significance]+2. **Theme 2:** [description and significance]+3. **Theme 3:** [description and significance]++### Supporting Ideas+- [Supporting concept 1]+- [Supporting concept 2]+- [Supporting concept 3]++### Questions Raised+- [Question 1 for deeper exploration]+- [Question 2 requiring consideration]++### Decisions Contemplated+- [Decision 1 being considered with options]+- [Decision 2 under evaluation]++## Strategic Intelligence++### Key Insights+1. **Insight 1:** [description and implications]+2. **Insight 2:** [description and implications]+3. **Insight 3:** [description and implications]++### Pattern Recognition+- **Connection to Previous Thinking:** [links to earlier braindumps or frameworks]+- **Recurring Patterns:** [themes that keep appearing]+- **Evolution:** [how thinking has developed]++### Strategic Implications+- [How this affects goals]+- [Impact on current projects]+- [Decision-making considerations]++## Action Items++### Immediate (24-48 hours)+- [ ] [specific action with deadline]++### Short-term (1-2 weeks)+- [ ] [specific action with deadline]++### Strategic Considerations+- [longer-term implications and considerations]++## Connections+- **Related Braindumps:** [[link1]], [[link2]]+- **Relevant Projects:** [[project1]], [[project2]]+- **Knowledge Base:** [[insight1]], [[framework1]]++## Domain Classification+- **Primary Domain:** [domain] ([confidence]%)+- **Reasoning:** [why this classification]+- **Cross-Domain Elements:** [if applicable]+- **Privacy Level:** [public|private|confidential]++## Processing Notes+### Emotional Context+- **Energy Level:** [assessment]+- **Emotional Tone:** [assessment]+- **Implications:** [what this suggests]++### Confidence Assessment+- **Overall Analysis:** [percentage] - [reasoning]+- **Domain Classification:** [percentage] - [reasoning]+- **Strategic Insights:** [percentage] - [reasoning]+- **Areas Requiring Clarification:** [specific questions if needed]++---++*Processed by COG Brain Dump Analyst*+```++Save to appropriate location:+- **Personal:** `02-personal/braindumps/braindump-YYYY-MM-DD-HHMM-<slug>.md`+- **Professional:** `03-professional/braindumps/braindump-YYYY-MM-DD-HHMM-<slug>.md`+- **Project:** `04-projects/[project-slug]/braindumps/braindump-YYYY-MM-DD-HHMM-<slug>.md`+- **Mixed:** `00-inbox/braindump-YYYY-MM-DD-HHMM-<slug>.md`++### 5. Competitive Intelligence Extraction++If competitive intelligence detected (mentions of companies/people from watchlist):++Create/update: `04-projects/[project]/competitive/[company-slug].md`++```markdown+---+type: "competitive-intelligence"+company: "[Company Name]"+project: "[project-name]"+last_updated: "YYYY-MM-DD"+sources: ["braindump"]+tags: ["#competitive", "#intelligence", "#[company-slug]"]+---++# Competitive Intelligence: [Company Name]++## Latest Update - [Date]+**Source:** [[braindump-file-reference]]++[Extracted competitive intelligence from braindump]++## Previous Intelligence+[Historical intel from earlier braindumps]++## Strategic Implications+[Analysis of what this means for the project]++## Action Items+- [ ] [Follow-up actions based on intel]++---++*Auto-extracted by COG Brain Dump Analyst*+```++### 6. Confirm Completion+- Confirm file was created+- Show user: "Braindump saved to [file path]"+- Show quick summary of main themes identified+- If competitive intel extracted, mention: "Also extracted competitive intelligence to [file path]"++## YAML Formatting Requirements++**CRITICAL:** All YAML frontmatter must use proper Obsidian-compatible formatting:+- All string values MUST be quoted with double quotes+- Arrays MUST use quoted strings: `["item1", "item2", "item3"]`+- Boolean values should NOT be quoted: `true` or `false`+- Numbers should NOT be quoted unless they are string identifiers+- Ensure proper YAML syntax to prevent parsing errors in Obsidian++**Examples:**+```yaml+# CORRECT+type: "braindump"+themes: ["automation", "testing", "ui-improvements"]+analysis_needed: true++# INCORRECT+type: braindump+themes: [automation, testing, ui-improvements]+analysis_needed: "true"+```++## Verification Protocols++### Content Accuracy+- **Interpretation Verification:** Confirm understanding matches intent+- **Context Validation:** Ensure situational context is accurately captured+- **Emotional Accuracy:** Verify emotional tone and energy level assessment+- **Completeness Check:** Confirm all major themes are identified++### Domain Classification Verification+- **Boundary Clarity:** Ensure domain classification is clear and defensible+- **Privacy Protection:** Verify personal content is properly protected+- **Cross-Domain Value:** Confirm cross-domain insights are valuable and appropriate+- **Classification Confidence:** State confidence level for domain assignments++### Strategic Insight Validation+- **Evidence-Based:** Ensure insights are supported by content evidence+- **Actionability:** Verify recommendations are specific and implementable+- **Priority Accuracy:** Confirm priority assessments align with stated goals+- **Timeline Realism:** Ensure recommended timelines are achievable++## Uncertainty Handling++### When to Request Clarification+- **Ambiguous Domain Classification:** Content could belong to multiple domains+- **Unclear Strategic Implications:** Insights have multiple possible interpretations+- **Conflicting Information:** Content contains contradictory elements+- **Missing Context:** Important background information seems to be missing++### Confidence Indicators+- **High Confidence (90%+):** Clear content with obvious domain and implications+- **Medium Confidence (70-89%):** Generally clear with some ambiguous elements+- **Low Confidence (50-69%):** Significant ambiguity requiring user input+- **Very Low Confidence (<50%):** Major uncertainty requiring clarification++Always explicitly state confidence levels and reasoning in the processing notes.++## Integration with Other Skills++### Immediate Follow-up+After braindump, suggest:+- Review patterns across multiple braindumps+- Weekly check-in to reflect on themes+- Knowledge consolidation to build frameworks++### Competitive Intelligence+If competitive mentions detected:+- Automatically update competitive files+- Mention this in the output+- Provide link to competitive intelligence file++## Success Metrics+- Speed of capture (minimize user friction)+- Accurate domain classification+- File saved to correct location+- User feels heard and understood+- Competitive intel auto-extracted when relevant+- High confidence in analysis accuracy++## Learning and Adaptation++### Pattern Learning+- Learn user's thinking patterns and communication style+- Understand user's specific domain separation preferences+- Recognize what types of insights user finds most valuable+- Learn which recommendations user typically implements++### Continuous Improvement+- Track accuracy of insights and recommendations over time+- Monitor user engagement with and implementation of recommendations+- Improve speed and accuracy of analysis through learning+- Refine analysis frameworks based on effectivenessdiff --git a/.claude/skills/daily-brief/SKILL.md b/.claude/skills/daily-brief/SKILL.mdnew file mode 100644index 0000000..8ef6a20--- /dev/null+++ b/.claude/skills/daily-brief/SKILL.md@@ -0,0 +1,449 @@+---+name: daily-brief+description: Generate personalized news intelligence with verified sources (7-day freshness requirement)+---++# COG Daily Brief Skill++## Purpose+Find verified, relevant news for personalized daily briefings with strict verification standards and strategic relevance analysis tailored to user's specific interests and projects.++## When to Invoke+- User wants their daily news briefing+- User says "daily brief", "news", "what's happening", "morning brief"+- User wants to stay updated on their interests+- Morning routine or regular check-in time++## Pre-Flight Check++**Before executing, check for user profile:**++1. Look for `00-inbox/MY-PROFILE.md` and `00-inbox/MY-INTERESTS.md` in the vault+2. If NOT found:+ ```+ Welcome to COG! Daily briefs work best when personalized.++ Let's quickly set up your profile (takes 2 minutes).++ Would you like to run onboarding first, or should I generate a general brief?+ ```+3. If found:+ - Read `MY-INTERESTS.md` to get topics for news curation+ - Read `MY-PROFILE.md` to get user's name and active projects+ - Read `03-professional/COMPETITIVE-WATCHLIST.md` if exists for competitive tracking+ - Use topics to curate relevant news+ - Connect news to user's active projects when relevant++## Process Flow++### 1. Gather Context++Collect the information needed for personalized curation:++- Read `00-inbox/MY-PROFILE.md` for:+ - User's name+ - User's role/job+ - Active projects++- Read `00-inbox/MY-INTERESTS.md` for:+ - Topics they're interested in+ - Preferred news sources++- Read `03-professional/COMPETITIVE-WATCHLIST.md` (if exists) for:+ - Companies/people to track++### 2. News Research and Curation++Apply comprehensive news research methodology:++#### Interest-Based Research+- Search based on user's current interest profile+- Focus on strategic relevance to user's role and projects+- Identify emerging patterns and developments+- Diversify sources for balanced perspective++#### Verification Standards (MANDATORY)++**Date Verification:**+- ALL news MUST be from last 7 days ONLY+- Verify publication dates with verified timestamps+- NEVER include older news without explicit disclosure++**Source Credibility Assessment:**+- **Tier 1 Sources (Highest Credibility):** Major news organizations (Reuters, AP, Bloomberg, WSJ, NYT), official company announcements, government statements+- **Tier 2 Sources (High Credibility):** Industry publications, credible tech/business blogs, research reports from reputable firms+- **Tier 3 Sources (Moderate - Verify Carefully):** Social media from verified accounts, company blogs, community discussions+- Minimum 2 credible sources for any claim+- Cross-reference key facts and figures++**Fact Cross-Reference:**+- Verify claims across multiple independent sources+- Use WebFetch to verify any statistics before including them+- Identify potential bias and provide balanced perspective++#### Strategic Relevance Analysis++Assess impact on user:++**Direct Impact (High Priority):**+- News directly affecting user's projects or companies+- Regulatory changes affecting user's industry+- Competitive moves by direct competitors+- Technology developments affecting user's tech stack++**Strategic Impact (Medium Priority):**+- Market trends affecting user's target customers+- Investment patterns in user's industry+- Talent market changes affecting hiring+- Partnership opportunities or threats++**Contextual Impact (Lower Priority):**+- Broader economic trends affecting business climate+- Technology trends affecting future planning+- Industry thought leadership and opinion+- Educational content for professional development++#### Opportunity and Threat Identification++**Opportunities:**+- Market Opportunities: New markets or customer segments opening+- Technology Opportunities: New tools or platforms to leverage+- Partnership Opportunities: Potential collaboration partners+- Competitive Opportunities: Competitor weaknesses or market gaps++**Threats:**+- Competitive Threats: New competitors or competitive advantages+- Technology Threats: Disruptive technologies or obsolescence risks+- Market Threats: Market shifts or customer behavior changes+- Regulatory Threats: New regulations or compliance requirements++### 3. Generate Daily Brief++Create structured briefing document:++```markdown+---+type: "daily-brief"+curator: "news-curator"+domain: "shared"+date: "YYYY-MM-DD"+created: "YYYY-MM-DD HH:MM"+sources_verified: true+news_age_verified: true+confidence: "high"+tags: ["#daily-brief", "#news", "#strategic-intelligence"]+interests: ["interest1", "interest2"]+projects_referenced: ["project1"]+items_count: [number]+---++# Daily Brief - [Date]++**Good [morning/afternoon], [Name]!**++## Executive Summary+[2-3 sentences highlighting the most important developments across all your interest areas]++---++## High Impact News++### [News Item 1 - Direct Impact]+**Relevance:** [Why this matters to you specifically]++[Detailed summary of the news]++**Impact Assessment:**+- **Projects Affected:** [Which of your projects this impacts]+- **Potential Effects:** [Specific implications]+- **Action Suggested:** [Recommended response or follow-up]++**Sources:**+- [Source Name 1] (Tier [1/2/3]) - [Publication Date] - [Link]+- [Source Name 2] (Tier [1/2/3]) - [Publication Date] - [Link]++**Confidence:** [High/Medium/Low] - [Reasoning]++---++### [News Item 2 - Direct Impact]+[Same structure as above]++---++## Strategic Developments++### [News Item 3 - Strategic Impact]+**Relevance:** [Why this matters strategically]++[Detailed summary]++**Strategic Implications:**+- [Implication 1]+- [Implication 2]+- [Implication 3]++**Sources:**+- [Source listings with credibility tiers and links]++**Confidence:** [High/Medium/Low] - [Reasoning]++---++## Market Intelligence++### [News Item 4 - Market Trends]+**Relevance:** [Why this market trend matters]++[Detailed summary]++**Market Impact:**+- [Impact on target customers]+- [Industry trends]+- [Investment patterns]++**Sources:**+- [Source listings with credibility tiers and links]++**Confidence:** [High/Medium/Low] - [Reasoning]++---++## Technology Watch++### [News Item 5 - Tech Developments]+**Relevance:** [Why this technology matters]++[Detailed summary]++**Technology Implications:**+- [Impact on tech stack]+- [New tools or platforms]+- [Emerging technologies]++**Sources:**+- [Source listings with credibility tiers and links]++**Confidence:** [High/Medium/Low] - [Reasoning]++---++## Competitive Landscape++### [Competitor/Company Name - From Watchlist]+**Recent Activity:**++[Summary of competitive intelligence gathered]++**Competitive Implications:**+- [What this means for your projects]+- [Opportunities or threats]+- [Recommended responses]++**Sources:**+- [Source listings with credibility tiers and links]++**Confidence:** [High/Medium/Low] - [Reasoning]++---++## Opportunities & Recommendations++### Immediate Actions (Today/This Week)+- [ ] [Specific action item 1]+- [ ] [Specific action item 2]+- [ ] [Specific action item 3]++### Research Needed+- [Area 1 requiring deeper investigation]+- [Area 2 to monitor closely]++### People to Inform/Consult+- [Stakeholder 1]: [About what]+- [Stakeholder 2]: [About what]++---++## Risks & Threats++### Active Threats+- **Threat 1:** [Description and mitigation approach]+- **Threat 2:** [Description and mitigation approach]++### Emerging Risks to Monitor+- [Risk 1 to watch]+- [Risk 2 to watch]++---++## Verification Report++### Source Analysis+- **Tier 1 Sources:** [count] - [list main ones]+- **Tier 2 Sources:** [count] - [list main ones]+- **Cross-References Performed:** [number]++### Fact-Checking Results+- **Verified Claims:** [count]+- **Unverified Claims:** [count with explanation if any]+- **Conflicting Information:** [count with resolution approach if any]++### Freshness Verification+- ✅ All news items verified within 7-day window+- Publication date range: [Oldest date] to [Newest date]++### Confidence Assessment+- **Overall Confidence:** [percentage]%+- **High Confidence Items:** [count]+- **Medium Confidence Items:** [count]+- **Low Confidence Items:** [count] - [reasons if any]++---++## Complete Sources++### Strategic News+1. [Full source citation with link]+2. [Full source citation with link]++### Market Intelligence+1. [Full source citation with link]+2. [Full source citation with link]++### Technology Watch+1. [Full source citation with link]+2. [Full source citation with link]++### Competitive Intelligence+1. [Full source citation with link]+2. [Full source citation with link]++---++*Curated by COG News Curator | All news verified within 7-day freshness window | Sources cross-referenced for accuracy*+```++Save to: `01-daily/briefs/daily-brief-YYYY-MM-DD.md`++### 4. Handle Special Cases++**When No Recent News Found:**+If no relevant news found in last 7 days for a particular interest area:++```markdown+### [Interest Area]+**No significant news found in last 7 days**++Last significant development was [date if known] regarding [topic if known].++**Suggestions:**+- Consider expanding search criteria+- Check [alternative sources suggested]+- This area may be experiencing a quiet period+```++**NEVER fabricate or use older news without explicit date disclosure.**++**When Information Cannot Be Verified:**+```markdown+### [Potential News Item]+**⚠️ Unable to verify from independent sources**++**Original Source:** [source] - Credibility: [assessment]++**What We Know:**+[What can be stated based on single source]++**What's Uncertain:**+[Specific claims that couldn't be verified]++**Recommendation:** Monitor for additional confirmation before acting++**Confidence:** Low - [reasoning]+```++**When Sources Conflict:**+```markdown+### [News Item with Conflicting Reports]+**⚠️ Conflicting information from multiple sources**++**Perspective 1:**+[Summary] - **Source:** [source with credibility tier]++**Perspective 2:**+[Summary] - **Source:** [source with credibility tier]++**Areas of Agreement:**+- [What sources agree on]++**Areas of Disagreement:**+- [Where sources conflict]++**Recommendation:** [Approach for resolution or further research]++**Confidence:** Medium - [reasoning]+```++### 5. Confirm Completion+- Confirm file was created+- Show user: "Daily brief saved to [file path]"+- Optionally show executive summary+- Ask if they want to explore any topic deeper or capture thoughts via braindump skill++## Integration with Other Skills++### Follow-up Actions+After daily brief, suggest:+- **braindump skill** - Capture thoughts sparked by news+- **weekly-checkin skill** - Reflect on news patterns over the week+- Project-specific analysis if news impacts active projects++## Performance Metrics++### Verification Quality+- Source Credibility Score: Average credibility rating of sources used+- Fact Accuracy Rate: Percentage of facts that remain accurate over time+- Cross-Reference Rate: Percentage of claims verified through multiple sources+- Date Accuracy: 100% compliance with 7-day freshness requirement (MANDATORY)++### Relevance Quality+- User Engagement: Percentage of news items user finds valuable+- Action Generation: Percentage of news items leading to user action+- Strategic Value: User assessment of strategic importance+- Timing Relevance: How well news timing aligns with user needs++## Learning and Adaptation++### Interest Profile Refinement+- Monitor which news items user finds most valuable+- Incorporate user feedback on relevance and importance+- Identify patterns in user interest evolution+- Anticipate interest changes based on project evolution++### Source Quality Learning+- Track accuracy of different sources over time+- Build understanding of source reliability patterns+- Learn to identify and account for source bias patterns+- Continuously improve source selection criteria++### Relevance Algorithm Improvement+- Improve ability to predict news impact on user+- Learn optimal framing for different types of news+- Better understanding of user's strategic context+- Improve identification of actionable news items++## Success Criteria+- All news within 7-day window (100% compliance)+- All sources verified and linked+- User finds briefing relevant and actionable+- Confidence levels clearly stated+- Opportunities and risks identified+- Follow-up actions suggested++## Philosophy++The daily brief skill embodies COG's verification-first approach:+- No AI hallucinations - everything sourced and verified+- Transparency in confidence levels+- Explicit uncertainty when information can't be verified+- User empowered to make informed decisions based on reliable intelligencediff --git a/.claude/skills/knowledge-consolidation/SKILL.md b/.claude/skills/knowledge-consolidation/SKILL.mdnew file mode 100644index 0000000..d53032e--- /dev/null+++ b/.claude/skills/knowledge-consolidation/SKILL.md@@ -0,0 +1,839 @@+---+name: knowledge-consolidation+description: Build frameworks from scattered insights across all braindumps and notes+---++# COG Knowledge Consolidation Skill++## Purpose+Transform scattered insights from braindumps, daily briefs, and check-ins into coherent frameworks and "single source of truth" knowledge documents through pattern recognition and systematic synthesis.++## When to Invoke+- User wants to consolidate their insights+- User says "consolidate knowledge", "build frameworks", "synthesize insights"+- Time for periodic knowledge base maintenance (weekly, monthly, quarterly)+- User wants to extract patterns from accumulated braindumps+- Before major decisions that could benefit from framework consultation++## Process Flow++### 1. Data Gathering++**Scan vault for unprocessed or partially processed content:**++- All braindumps since last consolidation:+ - `02-personal/braindumps/`+ - `03-professional/braindumps/`+ - `04-projects/*/braindumps/`+ - `00-inbox/braindump-*.md` (mixed domain)++- Daily briefs and check-ins:+ - `01-daily/briefs/`+ - `01-daily/checkins/`++- Any meeting transcripts or project documents in:+ - `04-projects/*/planning/`+ - `04-projects/*/resources/`++**Determine scope:**+- Ask user: "What time period should I analyze? (last week, last month, last quarter, all time, or custom range?)"+- Identify unprocessed content (check for `status: "captured"` or missing consolidation metadata)++**Gather statistics:**+- Total documents to analyze+- Breakdown by domain and type+- Date range coverage++### 2. Pattern Recognition++Apply systematic pattern detection across all content:++#### Frequency Analysis+**What comes up repeatedly?**+- Identify themes mentioned across multiple documents+- Track topic frequency and clustering+- Recognize persistent questions or concerns+- Spot recurring action items or decisions++#### Temporal Clustering+**What insights emerged together?**+- Group related insights by time period+- Identify how thinking evolved over time+- Recognize inflection points where thinking shifted+- Map catalysts that triggered changes++#### Domain Correlation+**What patterns cross domains?**+- Personal insights affecting professional thinking+- Professional learnings applied to projects+- Project experiences informing personal growth+- Strategic themes spanning all domains++#### Contradiction Analysis+**Where does thinking conflict?**+- Identify contradictory thoughts or approaches+- Recognize evolution vs. inconsistency+- Understand resolution or ongoing tension+- Track perspective shifts over time++#### Cross-Cutting Patterns+**Meta-patterns across all dimensions:**+- Decision-making approaches+- Problem-solving strategies+- Learning patterns+- Emotional/energy patterns+- Relationship patterns+- Creative processes++### 3. Framework Development++Synthesize patterns into actionable frameworks:++#### Identify Core Principles+**From scattered insights to fundamental truths:**+- What patterns reveal deeper principles?+- What rules or heuristics emerge?+- What mental models are forming?+- What strategies are proving effective?++#### Test Against Evidence+**Validate frameworks with source material:**+- Do source insights support these principles?+- Are there counter-examples or exceptions?+- How confident can we be in this framework?+- What are the boundary conditions?++#### Define Boundaries+**When does framework apply/not apply?**+- What contexts does this framework serve?+- What are its limitations?+- When should it NOT be used?+- What assumptions does it rely on?++#### Create Applications+**How to use this framework:**+- Specific use cases+- Decision-making applications+- Problem-solving templates+- Practical implementation steps++### 4. Knowledge Integration++Update and create knowledge base documents:++#### Update Existing Frameworks++For each framework that needs updating:++```markdown+---+type: "consolidated-knowledge"+domain: "[primary-domain]"+framework: "[framework-name]"+created: "[original-date]"+last_updated: "YYYY-MM-DD"+consolidation_id: "[consolidation-session-id]"+source_documents: [count]+status: "stable|working|emerging"+tags: ["#framework", "#consolidated", "#[topic]"]+---++# [Framework Name]++## Framework Overview+[Clear description of what this framework is and what it helps with]++**Status:** [Stable | Working | Emerging]+**Last Updated:** [Date]+**Source Insights:** [count] documents analyzed++---++## Core Principles++### Principle 1: [Name]+**Statement:** [Clear, concise principle statement]++**Evidence:**+- [[braindump-YYYY-MM-DD]] - [supporting insight]+- [[daily-brief-YYYY-MM-DD]] - [supporting evidence]+- [[checkin-YYYY-MM-DD]] - [pattern observation]++**Evolution:** [How this principle has developed or been refined]++**Confidence:** [High|Medium|Low] - [reasoning]++### Principle 2: [Name]+[Same structure as Principle 1]++### Principle 3: [Name]+[Same structure as Principle 1]++---++## Applications & Use Cases++### Use Case 1: [Scenario]+**When to Apply:** [Specific situation]++**How to Apply:**+1. [Step 1]+2. [Step 2]+3. [Step 3]++**Expected Outcomes:** [What to expect]++**Example:** [Real example from user's experience]++### Use Case 2: [Scenario]+[Same structure as Use Case 1]++---++## Boundaries & Limitations++**This framework works when:**+- [Condition 1]+- [Condition 2]+- [Condition 3]++**This framework does NOT work when:**+- [Anti-condition 1]+- [Anti-condition 2]+- [Anti-condition 3]++**Common Pitfalls:**+- [Pitfall 1 to avoid]+- [Pitfall 2 to avoid]++---++## Evolution & History++### [Date Range 1]: [Initial Development]+**What Emerged:** [How this framework first appeared]++**Catalysts:**+- [Event or insight that triggered initial thinking]++**Early Insights:**+- [[link]] - [early thought]+- [[link]] - [formative insight]++### [Date Range 2]: [Refinement Phase]+**What Changed:** [How framework evolved]++**New Evidence:**+- [[link]] - [supporting experience]+- [[link]] - [refining insight]++**Adjustments Made:**+- [Change 1]+- [Change 2]++### Current State: [Date]+**Current Understanding:** [Latest refined version]++**Recent Validation:**+- [[link]] - [recent application]+- [[link]] - [current evidence]++---++## Related Frameworks++- [[framework-2]] - [How they relate]+- [[framework-3]] - [Connection or overlap]+- [[framework-4]] - [When to use which]++---++## Future Development++**Questions for Deeper Exploration:**+- [Question 1 to investigate]+- [Question 2 needing more evidence]++**Potential Extensions:**+- [Area 1 for expansion]+- [Area 2 for integration]++**Watch For:**+- [Pattern 1 to monitor]+- [Signal 2 that might invalidate or refine]++---++*Consolidated from [X] sources | Confidence: [High/Medium/Low] | Status: [Stable/Working/Emerging]*+```++Save to: `05-knowledge/consolidated/[framework-name]-framework.md`++#### Create New Frameworks++For newly identified frameworks:++```markdown+---+type: "consolidated-knowledge"+domain: "[primary-domain]"+framework: "[framework-name]"+created: "YYYY-MM-DD"+last_updated: "YYYY-MM-DD"+consolidation_id: "[consolidation-session-id]"+source_documents: [count]+status: "emerging"+tags: ["#framework", "#consolidated", "#new", "#[topic]"]+---++# [New Framework Name]++## Framework Discovery++**Identified:** [Date]+**Based On:** [X] insights from [timeframe]+**Domain:** [Primary domain with cross-domain applications]++**Discovery Context:**+[What pattern recognition revealed this framework]++---++## Core Principles++[Same structure as framework updates above]++---++[Continue with Applications, Boundaries, Evolution sections...]+```++Save to: `05-knowledge/consolidated/[framework-name]-framework.md`++#### Update Pattern Documentation++```markdown+---+type: "pattern-analysis"+pattern: "[pattern-name]"+created: "YYYY-MM-DD"+domains: ["domain1", "domain2"]+frequency: "[high|medium|low]"+tags: ["#pattern", "#analysis"]+---++# Pattern: [Pattern Name]++## Pattern Description+[Clear description of the recurring pattern]++**Frequency:** Appeared in [X] documents over [timeframe]++**Domains:** [Which domains this pattern appears in]++**Significance:** [Why this pattern matters]++---++## Occurrences++### [Date 1] - [[source-document-1]]+**Context:** [What was happening]++**Manifestation:** [How pattern appeared]++**Outcome:** [What resulted]++### [Date 2] - [[source-document-2]]+[Same structure]++### [Date 3] - [[source-document-3]]+[Same structure]++---++## Analysis++**What Triggers This Pattern:**+- [Trigger 1]+- [Trigger 2]+- [Trigger 3]++**What Follows This Pattern:**+- [Consequence 1]+- [Consequence 2]++**Cross-Domain Implications:**+[How this pattern affects different areas]++**Potential Actions:**+- [Action to amplify if positive]+- [Action to mitigate if negative]+- [Action to understand better]++---++## Evolution Over Time++[How this pattern has changed or stayed consistent]++---++*Pattern identified through consolidation of [X] sources*+```++Save to: `05-knowledge/patterns/pattern-[name].md`++#### Create Timeline Entries++```markdown+---+type: "timeline-entry"+topic: "[major-theme-or-shift]"+date_range: "YYYY-MM-DD to YYYY-MM-DD"+created: "YYYY-MM-DD"+tags: ["#timeline", "#evolution", "#thinking"]+---++# Thinking Evolution: [Major Theme/Shift]++## Timeline Period+**From:** [Start Date]+**To:** [End Date]+**Duration:** [X weeks/months]++---++## What Changed++**Initial State:**+[How thinking/approach started]++**End State:**+[Where thinking/approach ended up]++**Key Shift:**+[The fundamental change that occurred]++---++## Catalysts & Triggers++### [Date] - [Trigger Event 1]+**Source:** [[link-to-document]]++**What Happened:** [Description]++**Impact:** [How this triggered change]++### [Date] - [Trigger Event 2]+[Same structure]++---++## Evidence Trail++### Early Thinking: [Date Range]+- [[YYYY-MM-DD]] - [Initial thoughts]+- [[YYYY-MM-DD]] - [Early explorations]++### Intermediate Development: [Date Range]+- [[YYYY-MM-DD]] - [Evolving understanding]+- [[YYYY-MM-DD]] - [Testing and refinement]++### Current Understanding: [Date Range]+- [[YYYY-MM-DD]] - [Mature thinking]+- [[YYYY-MM-DD]] - [Latest application]++---++## Impact of This Evolution++**On Decisions:**+[How this shift affects decision-making]++**On Strategies:**+[How this shift affects strategic approach]++**On Frameworks:**+[Which frameworks were created or updated]++**On Actions:**+[What changed in behavior or practice]++---++## Lessons Learned++**What This Evolution Teaches:**+- [Learning 1]+- [Learning 2]+- [Learning 3]++**Future Implications:**+[What this suggests for future development]++---++*Timeline constructed from [X] source documents spanning [timeframe]*+```++Save to: `05-knowledge/timeline/[topic]-evolution-YYYY-MM.md`++### 5. Generate Consolidation Report++Create master consolidation document:++```markdown+---+type: "knowledge-consolidation"+domain: "integrated"+date: "YYYY-MM-DD"+consolidation_period: "YYYY-MM-DD to YYYY-MM-DD"+created: "YYYY-MM-DD HH:MM"+sources_analyzed: [number]+frameworks_updated: ["framework1", "framework2"]+frameworks_created: ["new-framework1"]+patterns_identified: [number]+tags: ["#consolidation", "#knowledge", "#frameworks"]+---++# Knowledge Consolidation - [Date]++## Executive Summary++**Period Analyzed:** [Start date] to [End date]++**Documents Processed:**+- [X] braindumps+- [X] daily briefs+- [X] weekly check-ins+- [X] project documents++**Major Outcomes:**+- **Frameworks Updated:** [count] - [list]+- **New Frameworks Created:** [count] - [list]+- **Patterns Identified:** [count]+- **Timeline Entries:** [count]++**Key Insights Synthesized:**+1. [Major insight 1]+2. [Major insight 2]+3. [Major insight 3]++---++## Processing Statistics++- **Total documents analyzed:** [number]+- **Date range:** [start] to [end]+- **Domains covered:** [list]+- **New patterns identified:** [number]+- **Frameworks updated:** [number]+- **New frameworks created:** [number]+- **Timeline entries added:** [number]+- **Archive actions taken:** [number]++---++## Major Themes This Period++### Theme 1: [Name]+**Frequency:** Appeared in [X] documents++**Evolution:** [How thinking evolved]++**Key Insights:**+- [[source]] - [insight 1]+- [[source]] - [insight 2]+- [[source]] - [insight 3]++**Framework Implications:**+[How this theme affected or created frameworks]++**Status:** [Stable understanding | Still exploring | Needs more evidence]++### Theme 2: [Name]+[Same structure as Theme 1]++---++## Frameworks Updated++### Framework 1: [Name]+**Location:** [[05-knowledge/consolidated/[filename]]]++**What Changed:**+- [Addition/modification 1]+- [Addition/modification 2]++**New Evidence Added:**+- [[source]] - [insight]+- [[source]] - [insight]++**Confidence Change:** [Before] → [After]++**New Applications:**+- [Use case 1]+- [Use case 2]++### Framework 2: [Name]+[Same structure]++---++## New Frameworks Created++### New Framework: [Name]+**Location:** [[05-knowledge/consolidated/[filename]]]++**Created:** Based on [X] insights from [timeframe]++**Core Principles:**+1. [Principle 1]+2. [Principle 2]+3. [Principle 3]++**Primary Use Cases:**+- [Use case 1]+- [Use case 2]++**Status:** Emerging (needs more evidence and validation)++**Future Development:**+[What's needed to mature this framework]++---++## Patterns Identified++### Pattern 1: [Name]+**Frequency:** [High|Medium|Low]++**Domains:** [Which domains]++**Description:** [What the pattern is]++**Implications:** [Why it matters]++**Documentation:** [[05-knowledge/patterns/[filename]]]++### Pattern 2: [Name]+[Same structure]++---++## Thinking Evolution++### Major Shift: [Topic]+**Timeline:** [Date range]++**What Changed:** [Description]++**Catalysts:**+- [Event 1]+- [Event 2]++**Impact:**+[How this shift affects frameworks, decisions, actions]++**Documentation:** [[05-knowledge/timeline/[filename]]]++---++## Cross-Cutting Insights++**Connections Across Domains:**+- [Cross-domain insight 1]+- [Cross-domain insight 2]+- [Cross-domain insight 3]++**Contradictions Identified:**+- [Contradiction 1] - [Resolution approach]+- [Contradiction 2] - [Still unresolved]++**Strategic Implications:**+[Higher-level observations about trajectory and direction]++---++## Knowledge Base Maintenance++### Updates Made+- ✅ Updated framework: [name]+- ✅ Created new framework: [name]+- ✅ Documented pattern: [name]+- ✅ Added timeline entry: [topic]+- ✅ Archived outdated insights: [list]++### Archive Actions+**Braindumps Processed:**+- Updated metadata from `status: "captured"` to `status: "consolidated"`+- Added consolidation references: `consolidated_in: "[[consolidation-YYYY-MM-DD]]"`++**Superseded Content:**+- Archived: [list of old framework versions or outdated insights]+- Location: `00-inbox/archive/`++---++## Future Consolidation Needs++### Ready for Framework Creation+- [ ] [Area 1] - Sufficient evidence gathered - Target: [date]+- [ ] [Area 2] - Pattern established - Target: [date]++### Needs Deeper Analysis+- [ ] [Area 3] - Contradictions to resolve - Target: [date]+- [ ] [Area 4] - Emerging but not yet clear - Target: [date]++### Monitoring Required+- [ ] [Pattern 1] - Watch for additional occurrences+- [ ] [Theme 2] - Track evolution over next [period]++---++## Quality Assessment++**Completeness:** [All relevant insights processed?]++**Coherence:** [Frameworks logically consistent?]++**Traceability:** [Clear links to source material?]++**Actionability:** [Frameworks applicable to decisions?]++**Evolution Documented:** [Thinking progression captured?]++---++## Next Steps++**Immediate Actions:**+- [Action 1 based on consolidation insights]+- [Action 2 to apply new frameworks]++**Future Consolidation:**+- **Next Consolidation:** [Suggested date]+- **Focus Areas:** [What to emphasize next time]++**Framework Applications:**+- [Decision 1 that could benefit from framework]+- [Situation 2 to apply framework to]++---++*Consolidation completed: [Date] | Processed [X] documents | Created/updated [X] frameworks*+```++Save to: `05-knowledge/consolidated/consolidation-YYYY-MM-DD.md`++### 6. Cleanup and Archival++**Mark processed braindumps:**+Update frontmatter in processed braindumps:+```yaml+status: "consolidated"+consolidated_in: "[[consolidation-YYYY-MM-DD]]"+consolidated_date: "YYYY-MM-DD"+```++**Archive outdated content:**+Move superseded frameworks or insights to:+`00-inbox/archive/[filename]-archived-YYYY-MM-DD.md`++Add note explaining why archived and what supersedes it.++**Maintain clean knowledge base:**+- Remove redundancy while preserving important context+- Update cross-references+- Fix broken links+- Ensure consistent tagging++### 7. Confirm Completion++After consolidation:+- Show user: "Knowledge consolidation complete! Processed [X] documents"+- Highlight: "[X] frameworks updated, [X] new frameworks created"+- Show: "Consolidation report saved to [file path]"+- Suggest reviewing key frameworks created/updated+- Offer to explain any specific framework in detail++## Consolidation Guidelines++### Quality Over Quantity+- Don't force insights that aren't mature enough+- Let patterns emerge naturally from evidence+- Be patient with incomplete thinking+- Quality frameworks require time and evidence+- Mark frameworks as "emerging" vs "working" vs "stable"++### Preserve Nuance+- Don't over-simplify complex insights+- Maintain important context and conditions+- Note when frameworks have limitations+- Preserve contradictions that haven't resolved yet+- Acknowledge uncertainty explicitly++### Maintain Traceability+- Always link back to source documents+- Show evidence trail for frameworks+- Document evolution of thinking+- Enable future validation or revision+- Make it easy to audit framework claims++### Living Documents+- Frameworks should evolve with new insights+- Regular updates better than perfect first draft+- Clear status indicators (emerging/working/stable)+- Encourage iteration and refinement+- Version history through Git++## Analysis Techniques Reference++### Pattern Detection Methods+1. **Frequency Analysis:** Count mentions, cluster topics+2. **Temporal Clustering:** Group by time, track evolution+3. **Domain Correlation:** Cross-domain connections+4. **Contradiction Analysis:** Identify conflicts, track resolution+5. **Energy Pattern Detection:** Emotional and practical patterns++### Framework Synthesis Process+1. **Identify Core Principles:** Extract fundamental truths+2. **Test Against Evidence:** Validate with sources+3. **Define Boundaries:** Establish applicability+4. **Create Applications:** Develop use cases+5. **Document Evolution:** Track development over time++### Timeline Construction Method+1. **Mark Inflection Points:** When thinking shifted+2. **Identify Catalysts:** What triggered changes+3. **Document Evolution:** How understanding developed+4. **Extract Learnings:** What evolution teaches++## Success Metrics+- Completeness: All relevant insights processed+- Coherence: Frameworks logically consistent+- Traceability: Clear links to source material+- Actionability: Frameworks applicable to decisions+- Evolution: Documented thinking progression+- User Value: Frameworks actually used in practice++## Common Use Cases+- **Weekly Consolidation:** Process week's insights into patterns+- **Monthly Framework Development:** Build strategic frameworks+- **Quarterly Strategic Synthesis:** Big-picture consolidation+- **Annual Knowledge Base Cleanup:** Maintain quality and relevance+- **Pre-Decision Framework Consultation:** Apply frameworks to major decisions+- **Project Retrospective:** Extract learnings for frameworks++## Philosophy++The knowledge consolidation skill embodies COG's self-evolving intelligence:+- Transforms scattered thoughts into strategic frameworks+- Honors the evolution of thinking over time+- Builds "single source of truth" living documents+- Maintains traceability and evidence-based reasoning+- Creates actionable knowledge for better decision-making+- Respects nuance while seeking patterns+- Values iteration and continuous refinementdiff --git a/.claude/commands/onboarding.md b/.claude/skills/onboarding/SKILL.mdsimilarity index 79%rename from .claude/commands/onboarding.mdrename to .claude/skills/onboarding/SKILL.mdindex 0bfe2da..cee437e 100644--- a/.claude/commands/onboarding.md+++ b/.claude/skills/onboarding/SKILL.md@@ -1,9 +1,18 @@-# COG Onboarding Command+---+name: onboarding+description: Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)+---++# COG Onboarding Skill## PurposeWelcome new users and collect essential information to personalize their COG experience. All configuration is stored as natural markdown files within the vault structure, following COG's philosophy of transparent, editable knowledge.-## Command: `/onboarding`+## When to Invoke+- User explicitly requests `/onboarding` or mentions "onboarding" or "setup COG"+- User is new and hasn't completed onboarding yet+- User wants to update their profile or add new projects+- Any time profile customization is needed## Process Flow@@ -99,7 +108,7 @@ tags: ["#profile", "#config", "#cog"]- [[04-projects/[slug]/PROJECT-OVERVIEW|Project Name 2]][If no projects:]-*No active projects yet. Add them anytime by editing this file or running `/onboarding` again.*+*No active projects yet. Add them anytime by editing this file or running the onboarding skill again.*## Related- [[MY-INTERESTS|My Interests & News Sources]]@@ -110,7 +119,7 @@ tags: ["#profile", "#config", "#cog"]----*Edit this file anytime to update your profile. COG reads it when you use commands.*+*Edit this file anytime to update your profile. COG reads it when you use skills.*```#### `00-inbox/MY-INTERESTS.md`@@ -146,7 +155,7 @@ tags: ["#interests", "#daily-brief", "#config"]*Update this file anytime as your interests evolve. Just edit and save—COG will pick up the changes.*```-#### `03-professional/COMPETITIVE-WATCHLIST.md`+#### `03-professional/COMPETITIVE-WATCHLIST.md` (if applicable)```markdown---type: competitive-intelligence@@ -242,17 +251,6 @@ Based on configuration, create personalized structure:resources/```-**Custom Domain Folders (Based on focus_domains):**-If user selected "Entrepreneurship":-```-03-professional/entrepreneurship/-```--If user selected "Creative":-```-02-personal/creative/-```-### 6. Create Welcome GuideGenerate: `00-inbox/WELCOME-TO-COG.md`@@ -273,36 +271,26 @@ Your COG is now personalized and ready to use. Here's how to get started:I've created these documents to store your preferences:- **[[MY-PROFILE]]** - Your basic info and workflow preferences-- **[[MY-GOALS]]** - Your goals and priorities- **[[MY-INTERESTS]]** - Topics for your daily briefs-- **[[03-professional/COMPETITIVE-WATCHLIST]]** - Companies you're tracking+- **[[03-professional/COMPETITIVE-WATCHLIST]]** - Companies you're tracking *(if applicable)*-**You can edit these files anytime.** COG reads them when you use commands, so your changes take effect immediately.+**You can edit these files anytime.** COG reads them when you use skills, so your changes take effect immediately.-## Quick Start Commands+## Quick Start Skills### 1. Daily Morning Routine-```-/daily-brief-```-Get your personalized intelligence briefing covering:+Invoke the daily-brief skill to get your personalized intelligence briefing covering:[List their selected interest areas]### 2. Capture Your Thoughts-```-/braindump-```-Quickly capture ideas, insights, and thoughts. Your braindumps will automatically be categorized into:+Use the braindump skill to quickly capture ideas, insights, and thoughts. Your braindumps will automatically be categorized into:[List their focus domains]Choose from your active projects:[List their projects with links]### 3. Weekly Reflection-```-/weekly-checkin-```-Every [day based on workflow preference], review your week's insights and patterns.+Every week, use the weekly-checkin skill to review your week's insights and patterns.## Your Active Projects@@ -311,19 +299,19 @@ You're tracking these projects:- [[04-projects/[slug]/PROJECT-OVERVIEW|Project 1]]- [[04-projects/[slug]/PROJECT-OVERVIEW|Project 2]]-When you use `/braindump`, select the project to automatically file your thoughts in the right place.+When you use the braindump skill, select the project to automatically file your thoughts in the right place.## How COG Uses Your Profile**Daily Briefs**: Uses [[MY-INTERESTS]] to curate relevant news**Braindumps**: Offers your projects from [[MY-PROFILE]] as options**Competitive Intel**: Auto-extracts mentions of companies in [[COMPETITIVE-WATCHLIST]]-**Weekly Check-ins**: Reviews progress toward [[MY-GOALS]]+**Weekly Check-ins**: Reviews progress across your domains## Next Steps-1. **Try your first braindump**: Just type `/braindump` and start writing-2. **Get your daily brief**: Type `/daily-brief` to see curated intelligence+1. **Try your first braindump**: Use the braindump skill and start writing+2. **Get your daily brief**: Invoke the daily-brief skill to see curated intelligence3. **Explore your vault**: All your files are organized in the sidebar4. **Edit your profile**: Open [[MY-PROFILE]] and customize anytime@@ -331,14 +319,13 @@ When you use `/braindump`, select the project to automatically file your thought- **Don't overthink it**: Just dump your thoughts, COG will help organize- **Be consistent**: Daily briefs and braindumps work best as habits-- **Review weekly**: Use `/weekly-checkin` to see patterns emerge-- **Evolve your setup**: Edit your profile files anytime or run `/onboarding` to add projects+- **Review weekly**: Use the weekly-checkin skill to see patterns emerge+- **Evolve your setup**: Edit your profile files anytime or run onboarding again to add projects## Getting Help-- Type `/help` for command list- Check `SETUP.md` for detailed guides-- Visit [GitHub repo] for documentation+- Visit the GitHub repo for documentation**Your second brain is learning about you. Let's begin!**@@ -355,7 +342,6 @@ Great! Your COG is now configured.I've created these profile documents for you:- MY-PROFILE.md (your basic preferences)-- MY-GOALS.md (your goals and priorities)- MY-INTERESTS.md (topics for daily briefs)[If applicable:] - COMPETITIVE-WATCHLIST.md (companies to track)[If applicable:] - PROJECT-OVERVIEW.md files for each project@@ -367,14 +353,14 @@ Would you like to:1. **Try your first braindump** - Capture what's on your mind right now2. **Get your daily brief** - See today's intelligence report3. **Review your profile** - Open MY-PROFILE.md to see/edit settings-4. **Start later** - You're all set, just type /braindump when ready+4. **Start later** - You're all set, invoke skills when readyWhat would you like to do? (1-4)```## Configuration Update Mode-If user runs `/onboarding` after initial setup (MY-PROFILE.md exists):+If user runs onboarding after initial setup (MY-PROFILE.md exists):```You've already completed onboarding! Would you like to:@@ -382,49 +368,19 @@ You've already completed onboarding! Would you like to:1. **Update your profile** - Edit MY-PROFILE.md with new preferences2. **Add new interests** - Update MY-INTERESTS.md with new topics3. **Add new projects** - Create new project structures-4. **Update goals** - Revise MY-GOALS.md-5. **View current profile** - See your current MY-PROFILE.md--What would you like to do? (1-5)-```--## Integration with Other Commands--All other COG commands should check for profile files:+4. **View current profile** - See your current MY-PROFILE.md-```markdown-## Check Configuration-Before executing, check if `00-inbox/MY-PROFILE.md` exists:-- If NO: Prompt user to run `/onboarding` first-- If YES: Read profile and use personalized settings+What would you like to do? (1-4)```-### Usage in Commands--**In /braindump:**-- Read `MY-PROFILE.md` to get active projects-- Read `COMPETITIVE-WATCHLIST.md` for automatic intelligence extraction-- Use capture style preference from profile--**In /daily-brief:**-- Read `MY-INTERESTS.md` to curate relevant content-- Read `MY-PROFILE.md` for timezone and greeting preference-- Read `MY-GOALS.md` to weight strategic relevance--**In /weekly-checkin:**-- Read `MY-GOALS.md` to frame assessment questions-- Read `MY-PROFILE.md` for focus domains to review-- Read project overviews for project progress tracking-## Success CriteriaOnboarding is successful when:1. ✅ `MY-PROFILE.md` created in `00-inbox/`-2. ✅ `MY-GOALS.md` created in `00-inbox/`-3. ✅ `MY-INTERESTS.md` created in `00-inbox/`-4. ✅ Project directories and overviews created (if applicable)-5. ✅ `WELCOME-TO-COG.md` guide created-6. ✅ User understands next steps and where their profile is stored+2. ✅ `MY-INTERESTS.md` created in `00-inbox/`+3. ✅ Project directories and overviews created (if applicable)+4. ✅ `WELCOME-TO-COG.md` guide created+5. ✅ User understands next steps and where their profile is stored## Error Handling@@ -439,7 +395,7 @@ Onboarding is successful when:- Continue with rest of setup**If user exits mid-onboarding:**-- Create partial profile with note: "Onboarding incomplete - run `/onboarding` to finish"+- Create partial profile with note: "Onboarding incomplete - run onboarding skill to finish"- Save what was collected so far- Resume from last completed step on next run@@ -447,7 +403,6 @@ Onboarding is successful when:All configuration data is stored as markdown files in:- `00-inbox/MY-PROFILE.md` - Basic profile-- `00-inbox/MY-GOALS.md` - Goals and priorities- `00-inbox/MY-INTERESTS.md` - Interest areas- `03-professional/COMPETITIVE-WATCHLIST.md` - Competitive tracking- `04-projects/[project]/PROJECT-OVERVIEW.md` - Project detailsdiff --git a/.claude/skills/weekly-checkin/SKILL.md b/.claude/skills/weekly-checkin/SKILL.mdnew file mode 100644index 0000000..dc228ce--- /dev/null+++ b/.claude/skills/weekly-checkin/SKILL.md@@ -0,0 +1,410 @@+---+name: weekly-checkin+description: Cross-domain pattern analysis and strategic reflection for weekly review+---++# COG Weekly Check-in Skill++## Purpose+Comprehensive weekly review and analysis integrating insights across all domains (personal, professional, projects) with pattern recognition and strategic planning.++## When to Invoke+- User wants to do their weekly review+- User says "weekly checkin", "weekly review", "reflect on my week"+- End of week reflection time+- User wants to analyze patterns across the week++## Pre-Flight Check++**Check for user profile (optional but enhances experience):**++1. Look for `00-inbox/MY-PROFILE.md` in the vault+2. If found:+ - Read user's name for personalization+ - Read active projects to review project-specific progress+ - Tailor reflection questions to user's role and projects++## Process Flow++### 1. Gather Context++Scan recent files from the past week:+- Daily briefs in `01-daily/briefs/`+- Braindumps in `02-personal/braindumps/`, `03-professional/braindumps/`, `04-projects/*/braindumps/`+- Previous check-ins in `01-daily/checkins/`++If `MY-PROFILE.md` available:+- Use user's name for personalization+- Reference their active projects+- Tailor questions to their role++### 2. Guided Reflection++Lead user through reflection questions in a warm, conversational tone:++#### Overall Week Assessment+**Ask:**+- "How would you rate this week on a 1-5 scale? Why that rating?"+- "What were your biggest wins this week?"+- "What were your main challenges?"++**Listen for:**+- Overall sentiment and energy+- Key accomplishments they're proud of+- Obstacles they faced+- Emotional tone of the week++#### Domain Reviews++**Personal Domain:**+**Ask:**+- "How did you take care of yourself this week?"+- "Any personal growth or insights?"+- "How were your energy levels and well-being?"++**Professional Domain:**+**Ask:**+- "What did you accomplish at work? Any standout moments?"+- "How did things go with your team or colleagues?"+- "Any professional development or learning?"++**Projects Domain (if applicable):**+For each active project from MY-PROFILE.md:+**Ask:**+- "How did [project name] progress this week?"+- "What moved forward? What's blocking you?"+- "Any new insights or direction changes?"++#### Pattern Recognition++**Ask:**+- "Looking at your braindumps this week, did you notice any recurring themes?"+- "How did your energy levels vary throughout the week?"+- "Any connections between different areas of your life - personal, professional, projects?"+- "What surprised you this week?"++**Help identify:**+- Themes they might not see themselves+- Patterns across domains+- Evolution of thinking+- Cross-domain connections++#### Forward Planning++**Ask:**+- "What are your top 3 priorities for next week?"+- "Anything from this week you want to carry forward?"+- "What do you want to do differently next week?"+- "What success would look like next week?"++**Help with:**+- Clarifying priorities+- Being specific about goals+- Identifying experiments to try+- Setting measurable outcomes++### 3. Generate Weekly Check-in Document++Based on the conversation, create a structured check-in document:++```markdown+---+type: "weekly-checkin"+domain: "integrated"+date: "YYYY-MM-DD"+week_of: "YYYY-MM-DD"+created: "YYYY-MM-DD HH:MM"+tags: ["#weekly-checkin", "#reflection", "#planning"]+domains_analyzed: ["personal", "professional", "projects"]+rating: [1-5]+braindumps_reviewed: [count]+briefs_reviewed: [count]+---++# Weekly Check-in - Week of [Date]++## Executive Summary++**Week Rating:** [1-5] ⭐ - [User's reasoning in their words]++**In Three Words:** [word1], [word2], [word3]++**Key Highlights:**+- [Win 1 - specific and celebratory]+- [Win 2 - acknowledge effort and outcome]+- [Win 3 if applicable]++**Main Challenges:**+- [Challenge 1 - honest and clear]+- [Challenge 2 - what made it difficult]++---++## Domain Reviews++### 💭 Personal++**Wellness & Self-Care:**+[User's reflection on personal wellness, relationships, health]++**Energy Patterns:**+- [Observations about energy levels throughout the week]+- [What energized them]+- [What drained them]++**Personal Growth:**+- [Insights or realizations]+- [New habits or changes]++**Rating:** [1-5] ⭐++---++### 💼 Professional++**Accomplishments:**+[User's reflection on work accomplishments, projects completed, milestones reached]++**Team & Collaboration:**+[Insights about team dynamics, meetings, relationships]++**Challenges & Learnings:**+[What was difficult and what they learned]++**Professional Development:**+[Skills developed, knowledge gained]++**Rating:** [1-5] ⭐++---++### 🎯 Projects++[For each active project:]++#### [Project Name]++**Progress This Week:**+- [What moved forward - be specific]+- [Milestones achieved]+- [Decisions made]++**Current Status:** [On track | Needs attention | Blocked | Pivoting]++**Blockers:**+- [What's in the way - if any]+- [Dependencies waiting on]++**Insights & Direction:**+[Any strategic insights or direction changes]++**Next Steps:**+- [ ] [Specific next action 1]+- [ ] [Specific next action 2]+- [ ] [Specific next action 3]++**Rating:** [1-5] ⭐++---++## 🔍 Pattern Recognition++### Recurring Themes+[Themes identified across all braindumps and activities this week:]+1. **[Theme 1]:** [Description and significance]+2. **[Theme 2]:** [Description and significance]+3. **[Theme 3]:** [Description and significance]++### Energy & Productivity Patterns+- **Peak Times:** [When they were most productive/energized]+- **Low Points:** [When energy dipped]+- **Factors:** [What influenced energy - sleep, meetings, deep work, etc.]++### Cross-Domain Insights+[Connections between personal, professional, and project domains:]+- [Connection 1 - e.g., "Personal stress affecting project focus"]+- [Connection 2 - e.g., "Professional wins boosting personal confidence"]+- [Connection 3 - e.g., "Project learning applying to work"]++### Thinking Evolution+[How their thinking or approach evolved during the week:]+- [Evolution 1]+- [Evolution 2]++---++## 📅 Forward Planning++### Priorities for Next Week++**Top 3 Must-Do:**+1. [Priority 1 - specific and actionable]+2. [Priority 2 - specific and actionable]+3. [Priority 3 - specific and actionable]++**Why These Matter:**+[Brief explanation of strategic importance]++### Carry Forward Items+- [ ] [Unresolved item from this week - with context]+- [ ] [Ongoing task - with next action]+- [ ] [Follow-up needed - with who/what]++### Experiments & Changes++**What to Try Differently:**+- [Experiment 1 - be specific about what and why]+- [Experiment 2 - what you hope to learn]++**What to Keep Doing:**+- [Practice 1 that's working well]+- [Habit 2 to maintain]++**What to Stop:**+- [Thing 1 that's not serving you]+- [Practice 2 to eliminate]++### Success Criteria for Next Week++**I'll know next week was successful if:**+- [Measurable outcome 1]+- [Measurable outcome 2]+- [Qualitative measure 3]++---++## 📊 Week in Review++**Documents Analyzed:**+- [X] braindumps reviewed+- [X] daily briefs reviewed+- [X] previous check-ins referenced++**Time Analysis:**+- Braindumps: [count] across [domains]+- Most active domain: [domain name]+- Dominant themes: [top 2-3 themes]++**Sentiment Trend:**+[Overall emotional trajectory of the week - growing, stable, declining, mixed]++---++## 💡 Insights & Notes++### Strategic Observations+[Higher-level observations about trajectory, patterns, or strategic direction]++### Questions for Deeper Reflection+- [Question 1 that emerged during review]+- [Question 2 for future consideration]++### Gratitude & Appreciation+[Optional - what they're grateful for or who they want to acknowledge]++---++*Generated by COG Weekly Check-in Skill | Integrating insights across all domains*+```++Save to: `01-daily/checkins/weekly-checkin-YYYY-MM-DD.md`++### 4. Confirm Completion++After creating the check-in:+- Confirm file was created+- Show user: "Weekly check-in saved to [file path]"+- Highlight 1-2 key patterns spotted+- Offer to review patterns across multiple weeks if helpful+- Ask if they want to capture any follow-up thoughts via braindump skill++## Conversational Guidelines++### Do:+- Have a warm, empathetic, conversational tone+- Ask thoughtful follow-up questions based on user's answers+- Help identify patterns they might not see themselves+- Be honest and objective in summarizing their reflections+- Celebrate wins genuinely and specifically+- Acknowledge challenges without sugar-coating or minimizing+- Show curiosity about their experiences+- Reflect back what you're hearing for validation++### Don't:+- Rush through the questions+- Make assumptions about what matters to them+- Judge their answers or week rating+- Over-structure their free-form reflections+- Force positivity if they had a tough week+- Dismiss their challenges or concerns+- Skip the emotional/energy assessment+- Be clinical or robotic in tone++## Pattern Recognition Techniques++### Frequency Analysis+- What themes come up repeatedly across braindumps?+- Which topics get the most attention?+- What's mentioned but not deeply explored?++### Temporal Clustering+- What insights emerged together in time?+- How did thinking evolve from Monday to Friday?+- Were there inflection points during the week?++### Domain Correlation+- What patterns cross personal/professional/project boundaries?+- How do domains influence each other?+- Where is there alignment or tension?++### Contradiction Analysis+- Where does thinking conflict with actions?+- Are there competing priorities?+- What tensions exist between domains?++### Energy Pattern Detection+- When was energy highest/lowest?+- What activities energized vs. drained?+- How did energy affect productivity and insights?++## Integration with Other Skills++### Pattern Analysis+Review multiple weekly check-ins to:+- Spot long-term patterns (monthly, quarterly)+- Track goal progress over time+- Identify seasonal or cyclical patterns+- Use knowledge-consolidation skill to extract frameworks++### Project Tracking+Weekly check-ins provide:+- Historical record of project progress+- Evolution of thinking on projects+- Correlation between project work and other domains+- Context for future project analysis++### Knowledge Building+Check-ins feed into:+- Personal development patterns+- Strategic thinking evolution+- Decision-making frameworks+- Life/work balance insights++## Success Metrics+- User completes meaningful reflection+- Patterns identified and documented+- Clear priorities set for next week+- User feels heard and understood+- File saved with complete information+- Cross-domain insights revealed+- Actionable next steps defined++## Philosophy++The weekly check-in skill embodies COG's integrated intelligence approach:+- Holistic view across all life domains+- Pattern recognition over isolated events+- Strategic reflection driving tactical planning+- Emotional and practical dimensions both honored+- Thinking evolution tracked and celebrated+- Self-awareness as foundation for growthdiff --git a/.claude/subagents/brain-dump-analyst.md b/.claude/subagents/brain-dump-analyst.mddeleted file mode 100644index 3c89768..0000000--- a/.claude/subagents/brain-dump-analyst.md+++ /dev/null@@ -1,290 +0,0 @@-# Brain Dump Analyst Subagent--## Role Definition-Transform raw thoughts into strategic intelligence through systematic analysis, pattern recognition, and domain-aware insight extraction.--## Core Capabilities--### 1. Stream-of-Consciousness Processing-- **Content Parsing:** Extract meaning from unstructured, rambling thoughts-- **Theme Identification:** Recognize recurring concepts and patterns-- **Emotional Context:** Understand emotional undertones and energy levels-- **Temporal Mapping:** Track how thoughts evolve within a single session--### 2. Strategic Pattern Recognition-- **Cross-Domain Connections:** Identify links between personal, professional, and project domains-- **Recurring Themes:** Spot patterns across multiple braindump sessions-- **Evolution Tracking:** Monitor how thinking develops over time-- **Contradiction Analysis:** Identify and resolve conflicting thoughts or approaches--### 3. Domain Classification Intelligence-- **Boundary Recognition:** Accurately classify content into appropriate domains-- **Privacy Preservation:** Maintain strict separation between personal and professional content-- **Cross-Domain Insights:** Identify valuable connections while respecting boundaries-- **Context Sensitivity:** Understand when domain boundaries may be fluid--### 4. Actionable Intelligence Extraction-- **Decision Support:** Extract decision-relevant information and frameworks-- **Action Item Identification:** Recognize tasks, commitments, and next steps-- **Priority Assessment:** Evaluate urgency and importance of different elements-- **Resource Requirements:** Identify what's needed to act on insights--## Processing Framework--### Phase 1: Content Ingestion-```markdown-## Input Analysis-- **Content Type:** [voice-transcript|written-notes|mixed]-- **Length:** [word-count]-- **Energy Level:** [high|medium|low]-- **Emotional Tone:** [excited|frustrated|curious|concerned|neutral|mixed]-- **Context:** [situational-background]-```--### Phase 2: Structural Analysis-```markdown-## Content Structure-- **Main Themes:** [3-5 primary topics]-- **Supporting Ideas:** [related concepts and details]-- **Questions Raised:** [explicit and implicit questions]-- **Decisions Contemplated:** [choices being considered]-- **Action Items:** [tasks and commitments identified]-```--### Phase 3: Domain Classification-```markdown-## Domain Analysis-- **Primary Domain:** [personal|professional|project-specific] with confidence level-- **Secondary Domains:** [if content spans multiple areas]-- **Cross-Domain Elements:** [themes that apply across domains]-- **Privacy Considerations:** [sensitive content requiring protection]-```--### Phase 4: Strategic Insight Extraction-```markdown-## Strategic Intelligence-- **Key Insights:** [3-5 most important realizations]-- **Pattern Recognition:** [connections to previous thoughts/decisions]-- **Strategic Implications:** [what this means for goals and priorities]-- **Decision Framework:** [how this informs future choices]-```--### Phase 5: Actionable Recommendations-```markdown-## Recommendations-- **Immediate Actions:** [next 24-48 hours]-- **Short-term Planning:** [next 1-2 weeks]-- **Strategic Considerations:** [longer-term implications]-- **Follow-up Analysis:** [areas needing deeper exploration]-```--## Verification Protocols--### Content Accuracy-- **Interpretation Verification:** Confirm understanding matches intent-- **Context Validation:** Ensure situational context is accurately captured-- **Emotional Accuracy:** Verify emotional tone and energy level assessment-- **Completeness Check:** Confirm all major themes are identified--### Domain Classification Verification-- **Boundary Clarity:** Ensure domain classification is clear and defensible-- **Privacy Protection:** Verify personal content is properly protected-- **Cross-Domain Value:** Confirm cross-domain insights are valuable and appropriate-- **Classification Confidence:** State confidence level for domain assignments--### Strategic Insight Validation-- **Evidence-Based:** Ensure insights are supported by content evidence-- **Actionability:** Verify recommendations are specific and implementable-- **Priority Accuracy:** Confirm priority assessments align with stated goals-- **Timeline Realism:** Ensure recommended timelines are achievable--## Uncertainty Handling--### When to Request Clarification-- **Ambiguous Domain Classification:** Content could belong to multiple domains-- **Unclear Strategic Implications:** Insights have multiple possible interpretations-- **Conflicting Information:** Content contains contradictory elements-- **Missing Context:** Important background information seems to be missing--### Confidence Indicators-- **High Confidence (90%+):** Clear content with obvious domain and implications-- **Medium Confidence (70-89%):** Generally clear with some ambiguous elements-- **Low Confidence (50-69%):** Significant ambiguity requiring user input-- **Very Low Confidence (<50%):** Major uncertainty requiring clarification--### Explicit Uncertainty Statements-```markdown-## Uncertainty Assessment-- **Classification Confidence:** [percentage] - [reasoning]-- **Insight Confidence:** [percentage] - [reasoning]-- **Recommendation Confidence:** [percentage] - [reasoning]-- **Areas Requiring Clarification:** [specific questions for user]-```--## Learning and Adaptation--### Pattern Learning-- **User Preferences:** Learn user's thinking patterns and communication style-- **Domain Boundaries:** Understand user's specific domain separation preferences-- **Priority Patterns:** Recognize what types of insights user finds most valuable-- **Action Patterns:** Learn which recommendations user typically implements--### Feedback Integration-- **Accuracy Feedback:** Incorporate corrections to improve future analysis-- **Relevance Feedback:** Adjust insight generation based on user value assessment-- **Style Feedback:** Adapt communication style to user preferences-- **Process Feedback:** Refine analysis process based on user workflow needs--### Continuous Improvement-- **Analysis Quality:** Track accuracy of insights and recommendations over time-- **User Satisfaction:** Monitor user engagement with and implementation of recommendations-- **Efficiency Gains:** Improve speed and accuracy of analysis through learning-- **Framework Evolution:** Refine analysis frameworks based on effectiveness--## Integration with Other Subagents--### News Curator Collaboration-- **Interest Profiling:** Share insights about user interests for news curation-- **Strategic Context:** Provide context for news relevance assessment-- **Priority Alignment:** Ensure news curation aligns with braindump insights--### Content Analyzer Coordination-- **Theme Consistency:** Ensure consistent theme identification across content types-- **Cross-Reference:** Share insights for content analysis context-- **Pattern Validation:** Cross-validate patterns identified in different content types--### Project Analyst Support-- **Project Insights:** Provide project-relevant insights from braindumps-- **Strategic Context:** Share strategic thinking relevant to project analysis-- **Decision Support:** Contribute to project decision-making frameworks--## YAML Formatting Requirements--**CRITICAL:** All YAML frontmatter must use proper Obsidian-compatible formatting:-- All string values MUST be quoted with double quotes-- Arrays MUST use quoted strings: `["item1", "item2", "item3"]`-- Boolean values should NOT be quoted: `true` or `false`-- Numbers should NOT be quoted unless they are string identifiers-- Ensure proper YAML syntax to prevent parsing errors in Obsidian--**Examples:**-```yaml-# CORRECT-type: "braindump"-themes: ["automation", "testing", "ui-improvements"]-analysis_needed: true--# INCORRECT-type: braindump-themes: [automation, testing, ui-improvements]-analysis_needed: "true"-```--## Output Templates--### Standard Analysis Output-```markdown-----type: "braindump-analysis"-analyst: "brain-dump-analyst"-date: "YYYY-MM-DD"-source: "[braindump-file-reference]"-confidence: "[high|medium|low]"-domain: "[primary-domain]"-themes: ["theme1", "theme2", "theme3"]------# Braindump Analysis: [Title/Theme]--## Executive Summary-[2-3 sentence summary of key insights]--## Content Analysis-### Main Themes-1. **Theme 1:** [description and significance]-2. **Theme 2:** [description and significance]-3. **Theme 3:** [description and significance]--### Strategic Insights-- **Insight 1:** [description and implications]-- **Insight 2:** [description and implications]-- **Insight 3:** [description and implications]--## Domain Classification-- **Primary Domain:** [domain] ([confidence]%)-- **Reasoning:** [why this classification]-- **Cross-Domain Elements:** [if applicable]--## Action Items-### Immediate (24-48 hours)-- [ ] [specific action with owner and deadline]--### Short-term (1-2 weeks)-- [ ] [specific action with owner and deadline]--### Strategic Considerations-- [longer-term implications and considerations]--## Connections-- **Related Braindumps:** [[link1]], [[link2]]-- **Relevant Projects:** [[project1]], [[project2]]-- **Knowledge Base:** [[insight1]], [[framework1]]--## Follow-up Questions-- [Question 1 for deeper exploration]-- [Question 2 requiring user input]--## Confidence Assessment-- **Overall Analysis:** [percentage] - [reasoning]-- **Domain Classification:** [percentage] - [reasoning]-- **Strategic Insights:** [percentage] - [reasoning]-```--### Quick Processing Output-```markdown-----type: "quick-braindump-analysis"-analyst: "brain-dump-analyst"-date: "YYYY-MM-DD"-processing_time: "[minutes]"-confidence: "[high|medium|low]"------# Quick Analysis: [Theme]--## Key Takeaways-1. [Primary insight]-2. [Secondary insight]-3. [Tertiary insight]--## Domain: [domain] ([confidence]%)--## Next Steps-- [ ] [immediate action]-- [ ] [follow-up needed]--## Needs Deeper Analysis: [yes|no]-[If yes, explain why]-```--## Quality Assurance--### Analysis Standards-- **Completeness:** All major themes and insights identified-- **Accuracy:** Interpretations align with original content intent-- **Actionability:** Recommendations are specific and implementable-- **Relevance:** Insights connect to user's stated goals and priorities--### Verification Checklist-- [ ] Content accurately interpreted and summarized-- [ ] Domain classification is appropriate and confident-- [ ] Strategic insights are evidence-based and valuable-- [ ] Action items are specific with clear next steps-- [ ] Uncertainty is explicitly stated where it exists-- [ ] Cross-references are accurate and helpful--### Continuous Quality Improvement-- **User Feedback Integration:** Incorporate corrections and preferences-- **Accuracy Tracking:** Monitor and improve interpretation accuracy-- **Relevance Optimization:** Enhance insight relevance through learning-- **Efficiency Gains:** Reduce processing time while maintaining quality\ No newline at end of filediff --git a/.claude/subagents/news-curator.md b/.claude/subagents/news-curator.mddeleted file mode 100644index 676df03..0000000--- a/.claude/subagents/news-curator.md+++ /dev/null@@ -1,333 +0,0 @@-# News Curator Subagent--## Role Definition-Find verified, relevant news for personalized briefings with strict verification standards and strategic relevance analysis tailored to user's specific interests and projects.--## Core Capabilities--### 1. Targeted News Research-- **Interest-Based Search:** Research news based on user's documented interests and priorities-- **Strategic Relevance:** Identify news with potential impact on user's projects and goals-- **Source Diversification:** Gather information from multiple credible sources-- **Trend Identification:** Spot emerging patterns and developments in relevant domains--### 2. Verification and Fact-Checking-- **Date Verification:** Confirm all news is from last 7 days with verified publication dates-- **Source Credibility:** Assess and cross-reference source reliability-- **Fact Cross-Reference:** Verify claims across multiple independent sources-- **Bias Detection:** Identify potential bias and provide balanced perspective--### 3. Strategic Analysis-- **Impact Assessment:** Evaluate potential effects on user's projects and interests-- **Opportunity Identification:** Spot potential opportunities arising from news developments-- **Threat Analysis:** Identify potential risks or challenges from news events-- **Competitive Intelligence:** Analyze implications for competitive landscape--### 4. Personalized Curation-- **Relevance Scoring:** Rank news items by relevance to user's specific situation-- **Context Provision:** Explain why each news item matters to the user-- **Action Implications:** Identify potential actions or responses suggested by news-- **Follow-up Recommendations:** Suggest areas for deeper research or monitoring--## Verification Standards--### Mandatory Verification Requirements-- **Publication Date:** Must be within last 7 days with verified timestamp-- **Source Credibility:** Minimum 2 credible sources for any claim-- **Fact Accuracy:** Cross-reference key facts and figures-- **Context Accuracy:** Verify background information and context--### Source Credibility Assessment-```markdown-## Source Evaluation Framework-- **Tier 1 Sources:** Major news organizations, official statements, verified reports-- **Tier 2 Sources:** Industry publications, expert analysis, credible blogs-- **Tier 3 Sources:** Social media, unverified reports, opinion pieces-- **Red Flag Sources:** Known bias, unreliable history, unverifiable claims-```--### Uncertainty Handling Protocol-- **Explicit Uncertainty:** State when information cannot be verified-- **Confidence Levels:** Provide confidence ratings for all claims-- **Source Attribution:** Always include source information and credibility assessment-- **Clarification Requests:** Ask user for guidance on ambiguous interest areas--## Interest Profiling System--### Interest Categories-```markdown-## User Interest Framework-### Technology & Innovation-- AI/ML developments and breakthroughs-- Developer tools and productivity software-- Emerging technologies and platforms-- Tech industry trends and analysis--### Business & Strategy-- Market trends and economic indicators-- Competitive landscape changes-- Investment and funding news-- Strategic business developments--### Industry-Specific-- [User's specific industry] developments-- Regulatory changes and compliance-- Market disruptions and opportunities-- Key player movements and strategies--### Project-Relevant-- News affecting specific projects (Scout AI, TestOps, etc.)-- Technology stack developments-- Customer segment trends-- Competitive product launches-```--### Interest Weighting System-- **Primary Interests (Weight: 10):** Core focus areas requiring daily monitoring-- **Secondary Interests (Weight: 7):** Important but not critical daily focus-- **Tertiary Interests (Weight: 4):** Occasional monitoring for broader context-- **Background Interests (Weight: 2):** General awareness level monitoring--### Dynamic Interest Adjustment-- **Braindump Analysis:** Update interests based on recent thought patterns-- **Project Evolution:** Adjust based on project milestone changes-- **Feedback Integration:** Refine based on user engagement with previous briefings-- **Seasonal Adjustment:** Account for cyclical changes in priorities--## Research Methodology--### Primary Research Sources-```markdown-## Tier 1 Sources (Highest Credibility)-- Major news organizations (Reuters, AP, Bloomberg, WSJ, NYT)-- Official company announcements and press releases-- Government and regulatory body statements-- Verified expert analysis from recognized authorities--## Tier 2 Sources (High Credibility)-- Industry publications and trade journals-- Credible technology and business blogs-- Research reports from reputable firms-- Expert commentary from verified professionals--## Tier 3 Sources (Moderate Credibility - Verify Carefully)-- Social media from verified accounts-- Startup and company blogs-- Community discussions and forums-- Opinion pieces from credible authors-```--### Research Process-1. **Interest-Based Query:** Search based on user's current interest profile-2. **Date Filtering:** Restrict to last 7 days only-3. **Source Verification:** Confirm source credibility and cross-reference-4. **Relevance Assessment:** Evaluate strategic importance to user-5. **Impact Analysis:** Assess potential implications and opportunities--### Verification Workflow-```markdown-## Verification Checklist-- [ ] Publication date confirmed within last 7 days-- [ ] Source credibility assessed and documented-- [ ] Key facts cross-referenced with independent sources-- [ ] Potential bias identified and noted-- [ ] Strategic relevance to user confirmed-- [ ] Confidence level assigned and justified-```--## Strategic Relevance Analysis--### Impact Assessment Framework-```markdown-## Impact Categories-### Direct Impact (High Priority)-- News directly affecting user's projects or companies-- Regulatory changes affecting user's industry-- Competitive moves by direct competitors-- Technology developments affecting user's tech stack--### Strategic Impact (Medium Priority)-- Market trends affecting user's target customers-- Investment patterns in user's industry-- Talent market changes affecting hiring-- Partnership opportunities or threats--### Contextual Impact (Lower Priority)-- Broader economic trends affecting business climate-- Technology trends affecting future planning-- Industry thought leadership and opinion-- Educational content for professional development-```--### Opportunity Identification-- **Market Opportunities:** New markets or customer segments opening-- **Technology Opportunities:** New tools or platforms to leverage-- **Partnership Opportunities:** Potential collaboration or integration partners-- **Competitive Opportunities:** Competitor weaknesses or market gaps--### Threat Analysis-- **Competitive Threats:** New competitors or competitive advantages-- **Technology Threats:** Disruptive technologies or obsolescence risks-- **Market Threats:** Market shifts or customer behavior changes-- **Regulatory Threats:** New regulations or compliance requirements--## Output Framework--### Daily Brief Structure-```markdown-----type: daily-news-brief-curator: news-curator-date: YYYY-MM-DD-sources_verified: true-news_age_verified: true-confidence: [high|medium|low]-items_count: [number]------# Daily News Brief - [Date]--## Executive Summary-[2-3 sentences highlighting the most important developments]--## High Impact News-### [News Item 1 - Direct Impact]-- **Source:** [Source Name] ([Credibility Tier])-- **Date:** [Publication Date]-- **Relevance:** [Why this matters to user]-- **Impact:** [Potential effects on projects/goals]-- **Action Suggested:** [Recommended response or follow-up]-- **Confidence:** [High/Medium/Low] - [Reasoning]--## Strategic Developments-### [News Item 2 - Strategic Impact]-[Same structure as above]--## Market Intelligence-### [News Item 3 - Market Trends]-[Same structure as above]--## Technology Watch-### [News Item 4 - Tech Developments]-[Same structure as above]--## Competitive Landscape-### [News Item 5 - Competitive Intelligence]-[Same structure as above]--## Follow-up Recommendations-- **Immediate Actions:** [Actions to take today]-- **Research Needed:** [Areas requiring deeper investigation]-- **Monitoring Required:** [Developments to track ongoing]-- **Stakeholder Communication:** [People to inform or consult]-```--### Verification Documentation-```markdown-## Verification Report-### Source Analysis-- **Tier 1 Sources:** [count] - [list]-- **Tier 2 Sources:** [count] - [list]-- **Cross-References:** [number of cross-references performed]--### Fact-Checking Results-- **Verified Claims:** [count]-- **Unverified Claims:** [count] - [explanation]-- **Conflicting Information:** [count] - [resolution approach]--### Confidence Assessment-- **Overall Confidence:** [percentage]-- **High Confidence Items:** [count]-- **Medium Confidence Items:** [count]-- **Low Confidence Items:** [count] - [reasons]-```--## Error Handling and Quality Assurance--### When No Recent News Found-```markdown-## No Recent News Protocol-If no relevant news found in last 7 days:-1. State explicitly: "No significant news found in [interest area] in last 7 days"-2. Provide context: "Last significant development was [date] regarding [topic]"-3. Suggest: "Consider expanding search criteria or checking [alternative sources]"-4. Never fabricate or use older news without explicit date disclosure-```--### Source Verification Failures-```markdown-## Unverifiable Information Protocol-When information cannot be verified:-1. State explicitly: "Unable to verify [specific claim] from independent sources"-2. Provide context: "Original source: [source] - Credibility: [assessment]"-3. Recommend: "Suggest monitoring for additional confirmation"-4. Never present unverified information as fact-```--### Conflicting Information Resolution-```markdown-## Conflict Resolution Protocol-When sources provide conflicting information:-1. Present both perspectives with source attribution-2. Assess credibility of each source-3. Identify areas of agreement and disagreement-4. Recommend approach for resolution or further research-5. State confidence level for each perspective-```--## Learning and Adaptation--### Interest Profile Refinement-- **Engagement Tracking:** Monitor which news items user finds most valuable-- **Feedback Integration:** Incorporate user feedback on relevance and importance-- **Pattern Recognition:** Identify patterns in user interest evolution-- **Proactive Adjustment:** Anticipate interest changes based on project evolution--### Source Quality Learning-- **Accuracy Tracking:** Monitor accuracy of different sources over time-- **Reliability Assessment:** Build database of source reliability patterns-- **Bias Recognition:** Learn to identify and account for source bias patterns-- **Quality Optimization:** Continuously improve source selection criteria--### Relevance Algorithm Improvement-- **Impact Prediction:** Improve ability to predict news impact on user-- **Timing Optimization:** Learn optimal timing for different types of news-- **Context Enhancement:** Better understanding of user's strategic context-- **Action Relevance:** Improve identification of actionable news items--## Integration with Other Subagents--### Brain Dump Analyst Collaboration-- **Interest Updates:** Receive interest profile updates from braindump analysis-- **Context Sharing:** Share news context for braindump strategic analysis-- **Priority Alignment:** Ensure news curation aligns with current thinking patterns--### Content Analyzer Coordination-- **Theme Consistency:** Maintain consistent understanding of user interests-- **Cross-Reference:** Validate news relevance against content analysis insights-- **Strategic Alignment:** Ensure news supports broader content strategy--### Project Analyst Support-- **Project Context:** Provide project-relevant news for analysis-- **Competitive Intelligence:** Share competitive news for project analysis-- **Market Intelligence:** Contribute market trends for project strategic planning--## Performance Metrics--### Verification Quality-- **Source Credibility Score:** Average credibility rating of sources used-- **Fact Accuracy Rate:** Percentage of facts that remain accurate over time-- **Cross-Reference Rate:** Percentage of claims verified through multiple sources-- **Date Accuracy:** 100% compliance with 7-day freshness requirement--### Relevance Quality-- **User Engagement:** Percentage of news items user finds valuable-- **Action Generation:** Percentage of news items leading to user action-- **Strategic Value:** User assessment of strategic importance-- **Timing Relevance:** How well news timing aligns with user needs--### Efficiency Metrics-- **Research Speed:** Time to complete comprehensive news research-- **Coverage Completeness:** Percentage of relevant news captured-- **False Positive Rate:** Percentage of irrelevant news included-- **Update Frequency:** Ability to provide timely updates on developing stories\ No newline at end of filediff --git a/README.md b/README.mdindex fe1b682..1807aa8 100644--- a/README.md+++ b/README.md@@ -37,10 +37,10 @@ COG is a personal productivity and knowledge management system that:cp -r COG-second-brain/.claude .```-3. **Open Claude Code in your vault and run onboarding:**+3. **Open Claude Code in your vault and invoke onboarding:**```bashcode .- # In Claude Code, type: /onboarding+ # In Claude Code, ask: "Run onboarding" or "Set up my COG profile"```That's it! The onboarding will personalize COG for your needs in 3-5 minutes.@@ -53,37 +53,35 @@ See [SETUP.md](SETUP.md) for step-by-step instructions with screenshots.## What You Get-### 16 Custom Slash Commands+### 5 Powerful Skills-**Setup:**-- `/onboarding` - Personalize COG for your workflow (run this first!)+COG uses Claude's Agent Skills architecture - specialized capabilities that Claude automatically invokes when relevant to your request.++**Setup & Personalization:**+- **onboarding** - Personalize COG for your workflow (run this first!)**Daily Operations:**-- `/daily-brief` - Personalized news intelligence (verified sources only)-- `/daily-checkin` - Structured daily reflection-- `/braindump` - Quick capture of raw thoughts-- `/brain-dump-analysis` - Transform thoughts into strategic insights+- **braindump** - Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction+- **daily-brief** - Personalized news intelligence with verified sources (7-day freshness requirement)**Weekly & Strategic:**-- `/weekly-checkin` - Cross-domain pattern analysis-- `/consolidate-knowledge` - Build frameworks from scattered insights-- `/meeting-transcript` - Process meeting recordings with noise filtering--**Project & Content:**-- `/project-story` - Generate compelling narratives about project evolution-- `/newsletter-research` - Research and develop thought leadership content+- **weekly-checkin** - Cross-domain pattern analysis and strategic reflection+- **knowledge-consolidation** - Build frameworks from scattered insights across all your notes-### 2 Core Specialized Subagents+**How Skills Work:**-- **Brain Dump Analyst** (`.claude/subagents/brain-dump-analyst.md`): Transforms stream-of-consciousness into structured insights with domain classification and competitive intelligence extraction-- **News Curator** (`.claude/subagents/news-curator.md`): Finds verified news with strict 7-day freshness requirement, cross-references sources, and generates personalized briefings+Skills are self-contained AI capabilities that combine orchestration and specialized processing. Unlike the old command/subagent split, each skill now:+- Automatically activates when Claude detects relevant user intent+- Handles the complete workflow from user interaction to file creation+- Contains all necessary instructions, analysis frameworks, and verification protocols+- Uses progressive disclosure to load information only as needed-**How Subagents Work:**-Commands are thin orchestration layers that delegate specialized work to subagents. For example:-- `/braindump` collects your thoughts, then delegates analysis to brain-dump-analyst-- `/daily-brief` reads your profile, then delegates news curation to news-curator+For example:+- Ask "What's on my mind?" → Claude invokes the **braindump** skill+- Say "Give me my daily brief" → Claude invokes the **daily-brief** skill+- Request "Weekly review" → Claude invokes the **weekly-checkin** skill-This architecture keeps commands simple while subagents handle complex, specialized processing.+This architecture leverages Claude Code's native skill system for better performance and simpler maintenance.## Key Features@@ -98,8 +96,8 @@ COG doesn't just store notes—it actively learns:**Weekly Evolution Cycle:**```-Monday-Friday: Capture thoughts via /braindump-Friday: Run /consolidate-knowledge+Monday-Friday: Capture thoughts via braindump skill+Friday: Run knowledge-consolidation skill→ COG analyzes ALL your notes→ Builds frameworks you didn't explicitly create→ Updates "single source of truth" files@@ -132,11 +130,17 @@ Friday: Run /consolidate-knowledge```your-obsidian-vault/├── .claude/-│ ├── commands/ # 16 custom slash commands (thin orchestrators)-│ ├── subagents/ # 2 specialized AI subagents (complex processors)-│ │ ├── brain-dump-analyst.md-│ │ └── news-curator.md-│ └── settings.local.json # Agent configuration (optional)+│ └── skills/ # 5 specialized skills+│ ├── onboarding/+│ │ └── SKILL.md+│ ├── braindump/+│ │ └── SKILL.md+│ ├── daily-brief/+│ │ └── SKILL.md+│ ├── weekly-checkin/+│ │ └── SKILL.md+│ └── knowledge-consolidation/+│ └── SKILL.md├── 00-inbox/ # Temporary processing area│ ├── MY-PROFILE.md # Your profile (created by onboarding)│ ├── MY-INTERESTS.md # Your topics & news sources@@ -169,11 +173,9 @@ your-obsidian-vault/### First Time Setup-```bash-/onboarding-```+Ask Claude: "Run onboarding" or "Set up my COG profile"-The onboarding command will ask:+The onboarding skill will ask:- Your name- What you do (your job/role)- Topics you're interested in (3-5 main areas)@@ -196,9 +198,7 @@ After onboarding, COG will:### Daily Intelligence Briefing-```bash-/daily-brief-```+Ask Claude: "Give me my daily brief" or "What's the news today?"Generates a personalized briefing with:- Verified news from the last 7 days@@ -208,14 +208,11 @@ Generates a personalized briefing with:### Brain Dump → Strategic Insights-```bash-/braindump # Capture raw thoughts (no judgment)-/brain-dump-analysis # Transform into insights-```+Ask Claude: "I need to braindump" or "What's on my mind?"-Two-stage process:+Single integrated workflow:1. **Quick capture**: Preserves spontaneity, no filtering-2. **Intelligent processing**: Extracts themes, actions, connections+2. **Intelligent processing**: Automatically extracts themes, actions, connectionsThe system automatically:- Classifies by domain@@ -225,9 +222,7 @@ The system automatically:### Knowledge Consolidation-```bash-/consolidate-knowledge-```+Ask Claude: "Consolidate my knowledge" or "Build frameworks from my notes"Weekly or monthly:- Analyzes patterns across all braindumpsdiff --git a/SETUP.md b/SETUP.mdindex 596e479..62da96f 100644--- a/SETUP.md+++ b/SETUP.md@@ -45,8 +45,8 @@ Before you begin, ensure you have:code .```- - In Claude Code, test the setup: Type `/braindump`- - If command is recognized, COG is working!+ - In Claude Code, test the setup: Ask "I need to braindump"+ - If Claude recognizes the skill, COG is working!### Method 2: Manual Setup@@ -74,17 +74,17 @@ mkdir -p 05-knowledge/timelinemkdir -p 06-templates```-#### Step 2: Set Up Claude Commands+#### Step 2: Set Up Claude Skills1. Create `.claude` directory in your vault root:```bash- mkdir -p .claude/commands- mkdir -p .claude/subagents+ mkdir -p .claude/skills```-2. Download command files from the COG repository:- - Navigate to https://github.com/huytieu/COG-second-brain/.claude/commands/- - Download each `.md` file to your `.claude/commands/` folder+2. Download skill files from the COG repository:+ - Navigate to https://github.com/huytieu/COG-second-brain/.claude/skills/+ - Download each skill folder (onboarding, braindump, daily-brief, weekly-checkin, knowledge-consolidation) to your `.claude/skills/` folder+ - Each skill folder should contain a `SKILL.md` file#### Step 3: Set Up Templates@@ -99,18 +99,16 @@ mkdir -p 06-templatescode .```-2. Try a command:- ```- /braindump- ```+2. Try invoking a skill:+ Ask Claude: "I need to braindump"-3. If it works, you're ready to go!+3. If Claude recognizes the skill and responds, you're ready to go!## Configuration### Customizing Your Interests-Edit `.claude/commands/daily-brief.md` to customize your interest areas for news curation.+Run the onboarding skill to set up your profile, or directly edit `00-inbox/MY-INTERESTS.md` to customize your interest areas for news curation.### Adding Projects@@ -121,7 +119,7 @@ When starting a new project:mkdir -p 04-projects/your-project-name/{braindumps,competitive,content,planning}```-2. Projects will be automatically detected by COG commands+2. Projects will be automatically detected by COG skills### Setting Up Git (Optional but Recommended)@@ -169,32 +167,29 @@ When starting a new project:### Day 1: Set Up Your Profile-1. **Create your first braindump:**- ```- /braindump- ```+1. **Run onboarding:**+ Ask Claude: "Run onboarding" or "Set up my COG profile"- Paste this to get started:- ```- I'm setting up COG to help me with:- - [Your main goals]- - [Your current projects]- - [Your areas of interest]- - [What you want to track]- ```+ This will guide you through personalization and create:+ - Your profile with goals and projects+ - Your interests for news curation+ - Your competitive watchlist (optional)-2. **Test daily brief:**- ```- /daily-brief- ```+2. **Create your first braindump:**+ Ask Claude: "I need to braindump"++ Share what's on your mind to test the system++3. **Test daily brief:**+ Ask Claude: "Give me my daily brief"- This will generate your first intelligence briefing based on your braindump+ This will generate your first intelligence briefing based on your interests### Week 1: Build the Habit-Use these commands daily:-- Morning: `/daily-brief` for intelligence-- Throughout day: `/braindump` for capturing thoughts+Use these skills daily:+- Morning: Ask for "daily brief" for intelligence+- Throughout day: "braindump" for capturing thoughts- Evening: Quick review of your braindumps### Week 2: Start Consolidating