Reverse weekly review for turning inbox noise, daily plans, diaries, calendars, annual plans, and long-range life plans into one happiness-and-peace-centered weekly plan. Use when the user asks for 週檢視, 反向週計劃, 8 Big Rocks, Inbox Zero weekly review, 幸福寧靜週, or wants to synthesize Todoist/inbox notes, daily diaries, calendars, yearly plans, and life plans into iMandalArt/FIRE/JSON outputs.
npx skills add https://github.com/twhsi/skills --skill weekly-reverse-review
Turn one week of evidence into the next week's meaningful plan by asking:
Is this making me prove myself, or bringing real happiness and peace?
This skill is a reverse planning skill. It does not start by adding tasks. It first gathers evidence from life, removes noise, checks long-range meaning, then produces a compact weekly plan.
Use the center phrase 幸福寧靜週 unless the user gives another five-Han-character center.
Default final question:
那件事情能帶來真正的幸福與寧靜?
Default operating sentence:
少說,陪伴,慢慢做。
Gather only the sources available in the user request or local context:
When source files are present, read them before synthesizing.
Use these skills when available and relevant:
fire-analysis-card: semantic analysis, numbering, index, route, evolution.imandalart: final 2.01 hard-line weekly 3x3 card.todays-daily-plan: daily plan and diary extraction.markdown-nine-grid-clipboard: Markdown table version of the weekly card.project-note-json-to-epub: publishing-ready project-note JSON when weekly reviews become manuscript material.person / theme / next step cards.references/output-json-schema.md.When generating iMandalArt weekly plans, use the user's weekly-domain layout, not the default process layout:
Ⓕ內在 Ⓒ財流 Ⓖ學習
...
...
Ⓑ工作 ◎◎◎◎◎ Ⓓ家庭
... 幸福寧靜週 ...
... ◎◎◎◎◎ ...
Ⓔ社群 Ⓐ健康 Ⓗ休閒
...
...
Read references/weekly-eight-domain-layout.md for the full mapping and phrase guidance.
Before finalizing, ask internally:
Read references/reverse-review-questions.md when the review needs deeper diagnosis.
For a normal weekly review, return:
Do not over-explain unless the user asks for a full analysis.
待證, 推論, or 需補.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take twhsi/weekly-reverse-review from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.