Menu
Deep research on a topic, creating persistent documentation for future reference. Use for technology decisions, competitive analysis, or complex topics.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
End-of-session reflection. Extracts memories, suggests updates to about-taylor.md and CLAUDE.md. Run before ending a long session or when context is getting full. Triggers on "debrief", "extract memories", "session summary".
Sync all git repos - my-life top repo and spaces/ projects
Morning routine check-in. Use at start of day to review yesterday, set up today's journal, and check learning reviews due. Triggers on "good morning", "morning", "start my day", "what's on for today".
Silently refresh AI context by reading project configuration and guidelines. Use when starting a new conversation, after context loss, or before major tasks.
Fetch and summarize latest articles from RSS feeds. Creates notes with article summaries as bullet points. Use to catch up on blogs without reading everything. Triggers on "rss catchup", "blog catchup", "check feeds", "summarize articles".
Fetch and summarize latest videos from priority YouTube channels. Creates notes with transcripts summarized as bullet points. Use to catch up on subscriptions without watching everything. Triggers on "youtube catchup", "video catchup", "check youtube", "summarize videos".
| name | research |
| description | Deep research on a topic, creating persistent documentation for future reference. Use for technology decisions, competitive analysis, or complex topics. |
| model | claude-opus-4-5-20251101 |
| allowed-tools | Read, Write, Edit, Glob, Grep, WebSearch, WebFetch |
Deep research creating persistent documentation for future reference. Uses Ultrathink for comprehensive analysis.
/research "authentication patterns for multi-tenant SaaS"
/research "real-time collaboration architectures"
/research "Jira vs Linear competitive analysis"
/research "WebSocket vs SSE trade-offs"
ideas/
├── [project]/notes/research/ # Project-specific
├── shared/docs/research/ # Cross-project
└── resources/research/ # General reference
Location rules:
ideas/{project}/notes/research/shared/docs/research/resources/research/grep -r "authentication" ideas/*/notes/research/
grep -r "authentication" shared/docs/research/
If found, ask: "Research exists. Update, view, or create new?"
Invoke research-specialist agent:
Research scope:
Volume: Read 20-30+ sources, distill to 3-5 pages
Naming: lowercase kebab-case (e.g., auth-patterns-saas.md)
Structure:
---
created: YYYY-MM-DD
updated: YYYY-MM-DD
sources: NUMBER
related:
- path/to/related/file.md
tags: ["primary-tag", "secondary-tag"]
---
# Research: [Topic]
## Executive Summary
[2-3 paragraphs of key findings]
## Detailed Findings
### [Subtopic 1]
[Analysis]
### [Subtopic 2]
[Analysis]
## Recommendations
[What to do based on research]
## Must-Read Resources
1. **[Title]** - [url]
- Why: [Reason]
- Key point: [Takeaway]
## Additional Resources
- [Title] - [url]
## Gotchas & Warnings
- [Warning 1]
## Decision Matrix (if comparing)
| Criteria | Option A | Option B |
|----------|----------|----------|
| Ease of use | ⭐⭐⭐ | ⭐⭐ |
| Scalability | ⭐⭐⭐⭐ | ⭐⭐⭐ |
If research relates to a spec or issue:
Good candidates:
Not needed for:
If research exists but is outdated:
Options:
1. Update existing (add new findings)
2. Replace entirely (fresh research)
3. View existing
4. Cancel
Research documents are discovered by:
/plan - Checks for relevant research before planning/spec - References research in technical notes/research "topic" → ideas/{project}/notes/research/topic.md
↓
Future work automatically references this