القائمة
Weekly review process for reflection and planning. Use when: "weekly review", "week summary", "Friday review", "what happened this week", "plan week".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use Firecrawl for markdown-first web scraping, crawling, and site mapping. Use when: "firecrawl", "crawl docs", "scrape website to markdown", "map website", "rag crawl".
ThoughtMap pipeline, output interpretation, and MCP vector search tools. Use when: "thoughtmap", "thought clusters", "search thoughts", "what am I thinking about", "semantic search notes", "knowledge base", "vector search", "find context in notes", "cluster distances", "topic map", "thinking patterns".
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, and properties. Also supports plugin and theme development. Use when the user asks to interact with their Obsidian vault from the command line, manage notes, search vault content, or develop and debug Obsidian plugins and themes.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
| name | weekly-review |
| description | Weekly review process for reflection and planning. Use when: "weekly review", "week summary", "Friday review", "what happened this week", "plan week". |
Structured reflection at the end of each week. The purpose is to find patterns, not just list events.
Second Brain/Operations/Periodic Notes/Weekly/YYYY-Www.md
Collect data from:
Facts first:
This is the valuable part. Look for:
Capture patterns as bullet points — these feed into future planning.
Set up next week:
---
type: weekly
tags: [type/weekly]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
# YYYY-Www
## Next
- [ ] Commitment 1
- [ ] Commitment 2
- [ ] Commitment 3
## Wins
- What went well
## Patterns
- What you noticed
## Lessons
- What you'd do differently
## History
![[YYYY-MM-DD]]
![[YYYY-MM-DD]]
...
| Observation | Where It Goes |
|---|---|
| "I shipped feature X" | Weekly → Wins |
| "I keep getting stuck on Y" | Weekly → Patterns + project CONTEXT.md → Blockers |
| "I learned Z" | Weekly → Lessons + extract to project note if reusable |
| "I should change how I do W" | Update the relevant skill or instruction file |
| "Project A direction changed" | Project A CONTEXT.md → Past → Key Decisions |
See template.md for the full Obsidian Templater template.