Show last month's data and ask the user to pick focus areas and projects. AI does NOT generate focus areas, set targets, or pick projects. User decides; AI formats.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-second-brain:monthly-plannerThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Your job: **show last month's data, ask sharp questions, format the user's decisions.**
Your job: show last month's data, ask sharp questions, format the user's decisions. NOT your job: pick focus areas, choose projects, set targets, generate "Why/Target/When" content.
Current month or upcoming month being planned.
Pull these. No interpretation.
## Monthly Review section from the previous month's note (the user's own words from the user-driven monthly-review skill)01_Project/*.md frontmatter, list:
Doing)Planned, Todo)Done)02_Area/, count projects with AREA: "[[Area Name]]" whose project-status changed last month[ ] (not done)## [Month YYYY] Planning — Last Month Data
Last month's review (your words):
[paste the user's verbatim "Headline" from last monthly review]
[paste their "Pattern" answer]
[paste their "Start/Stop" decisions]
Last month performance:
- Must Complete: X/Y done
- Should Progress: X/Y done
- Habits avg: [habit]: X% | [habit]: X% | ...
Projects right now:
- Active (Doing): [list]
- Planned/Todo: [list]
- Overdue: [list with how many days overdue]
Area touchpoints last month:
- [Area name]: X projects active
- [Area name]: X projects active
Carry-over from last month (still open):
- [list of [ ] tasks]
No commentary. No "trends". No suggestions.
Wait for each answer.
✅ Ask:
❌ Never:
If the user picks ≥4 focus areas OR ≥4 Must Complete projects, ask once:
"Last month you completed X/Y. With 4+ focus areas you're planning ~3× last month's output. Sure?"
User says yes → accept it, move on. Don't ask again.
For each focus area picked, ask:
"Target for [area]? (e.g., '15 min/day', '2 sessions/week', or 'no target')"
User answers in their own words. Do NOT suggest. If they say "no target", accept it.
Write to the monthly note. Use the user's exact wording.
# [Month YYYY] Plan
## Theme
[User's Q1 answer, verbatim]
## Focus Areas
1. [User's Q2 answer] — Target: [user's target or "no target"]
2. [User's Q3 answer if not "none"] — Target: [...]
3. [User's Q4 answer if not "none"] — Target: [...]
## Monthly Tasks
### Must Complete
- [ ] [Project from Q5]
- [ ] [Project from Q5]
- [ ] [Project from Q5]
### Should Progress
- [ ] [Project from Q6]
- [ ] [Project from Q6]
### Carry-over from last month
- [ ] [tasks user said carry]
- ~~[tasks user said drop]~~ (dropped)
Write the file. Do NOT add a "Validation Questions" section. Do NOT ask "are these targets realistic" — that was the question you already asked in Step 4 if applicable.
A monthly plan's value is the user deciding what matters this month. If you decide for them, they execute someone else's plan — and execution rates collapse.
Show data → ask picks → format choices. That's the entire job.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub thongntit/prompts --plugin obsidian-second-brain