plugins/workflow-skills/skills/weekly-review/SKILL.md
Guided weekly review covering inbox audit, session summary, task review, vault health check, and brag candidates. Use when the user says "weekly review", "review my week", "Friday review", or "weekly summary".
npx skillsauth add arosenkranz/claude-code-config weekly-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Refer to ~/.claude/skills/obsidian-core/SKILL.md for CLI patterns, preflight checks, and error handling.
Check the user's invocation:
Work through each phase one at a time. After each phase, wait for the user's response before moving to the next.
obsidian files folder=Inbox 2>/dev/null
Show the list of inbox items. For each item, suggest a destination folder or action (file it, archive it, delete it). Ask: "Want me to move any of these? Tell me which ones and where, or say 'skip' to move on."
Wait for response. Execute confirmed moves before proceeding.
obsidian files folder=Sessions 2>/dev/null
Filter to files from the past 7 days (date prefix YYYY-MM-DD-*). Summarize: what topics were worked on, what was completed, any patterns noticed.
Then ask:
Wait for response before continuing.
obsidian tasks todo 2>/dev/null
Identify stale tasks (from daily notes older than 3 days). Present them in batches of 5, not all at once. For each batch, ask: "For these tasks: carry forward, archive, or close? You can answer per-item or say 'all forward', 'all close', etc."
Wait for response after each batch before showing the next.
obsidian orphans 2>/dev/null
obsidian unresolved 2>/dev/null
Report counts of orphaned notes and unresolved links. Show the list of orphaned notes. Ask: "Want me to clean any of these up, or just note them for now?"
Wait for response. Do not auto-delete anything.
obsidian search:context query="completed" path="Sessions" format=json limit=5 2>/dev/null
obsidian search:context query="shipped" path="Sessions" format=json limit=5 2>/dev/null
Surface any notable accomplishments found this week. Then ask: "Anything else you shipped or accomplished this week that you're proud of? Anything that felt like a win, even if it's not in a session note?"
Wait for response.
Ask each of these questions one at a time, waiting for a response between each:
Summarize the key decisions and insights from the review (moves made, tasks closed/archived, retrospective answers, brag candidates noted).
Then ask: "Want me to write a weekly review note to Sessions/YYYY-MM-DD-weekly-review.md capturing the highlights, decisions, and retrospective answers?"
If yes, write the note using the Write tool at the appropriate path under /Users/alex.rosenkranz/Documents/main-vault/Sessions/.
## Weekly Review — Week of [YYYY-MM-DD]
### Inbox (N items)
- [item]: suggested action
### Sessions This Week
- [YYYY-MM-DD-topic]: [brief outcome]
### Stale Tasks
- [task]: from [date] — keep / archive / close?
### Vault Health
- Orphaned notes: N
- Unresolved links: N
### Potential Brag Candidates
- [accomplishment summary]
tools
Lightweight orchestrator for spec-before-plan workflow. Use when starting a feature with ambiguous requirements. Walks SPEC.md → PLAN.md → execute, delegating to /superpowers:writing-plans and /superpowers:executing-plans. Invoke when asked to "spec this out", "spec-first", "spec and plan for X", or when feature requirements are vague.
tools
Problem Statement Co-Authoring Skill
development
Structure and maintain professional brag documents with clear templates for accomplishments, projects, and growth tracking. Use when documenting achievements, creating brag document entries, formatting accomplishments, or tracking career progress.
development
Analyze technical documentation for clarity, conciseness, and effectiveness using Google Technical Writing principles. Use when reviewing documentation, checking writing quality, improving docs, or providing writing feedback.