cog-weekly-reflection
The cog-weekly-reflection skill conducts structured weekly reviews by analyzing vault entries across personal, professional, and project domains to identify patterns in energy levels, career development, and project progress. Use this skill to synthesize cross-domain insights, spot connections between life areas, and generate actionable recommendations with confidence ratings for comprehensive self-assessment.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/cog-weekly-reflection && cp -r /tmp/cog-weekly-reflection/library/methodologies/cog-second-brain/skills/weekly-reflection ~/.claude/skills/cog-weekly-reflectionSKILL.md
# COG Weekly Reflection Skill
Perform weekly check-in with cross-domain pattern analysis spanning personal, professional, and project domains.
## Capabilities
- Gather and analyze the past week's vault entries across all sections
- Identify patterns in personal domain (energy, mood, productivity)
- Identify patterns in professional domain (skills, career, industry)
- Identify patterns in project domain (velocity, blockers, progress)
- Synthesize cross-domain connections
- Generate actionable insights with confidence levels
- Quality-gated reflection with iterative refinement
## Tool Use Instructions
1. Use `file-read` to load entries from 01-daily, 02-personal, 03-professional, 04-projects
2. Use `file-search` to find related entries across sections
3. Analyze patterns within each domain independently
4. Synthesize cross-domain connections
5. Use `file-write` to create weekly check-in in 01-daily
6. Add cross-references to identified patterns
7. Use `git-commit` to commit reflection
## Examples
```json
{
"vaultPath": "./cog-vault",
"mode": "weekly-checkin",
"userName": "Alex",
"rolePack": "engineer",
"targetQuality": 80
}
```Review TypeScript code changes for consistency, type safety, and monorepo patterns across babysitter packages
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
Architect code review with DRY, YAGNI, abstraction, and test coverage principle enforcement