From thinking-frameworks-skills
Drafts a unified-diff proposal for updating goals.md based on quarterly review conclusions. Never writes directly — writer applies manually.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thinking-frameworks-skills:goal-reset-proposalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
After the three questions + bet + kill list are drafted:
- [ ] Step 1: Read current goals.md line by line
- [ ] Step 2: For each goal, ask:
- Is it still true?
- Has it been met?
- Is it vestigial?
- Is it inconsistent with this review's conclusions?
- [ ] Step 3: Propose changes as unified-diff block with prose justification
- [ ] Step 4: Keep goals list short — if diff adds >2 goals without removing any, reject and retry
- Goal: {old line}
+ Goal: {new line}
+ Goal: {added goal}
Followed by one paragraph justifying the changes, explicitly naming which review conclusion drove each change.
- Goal: Reach 1,000 subscribers by end of 2026
+ Goal: Reach 500 subscribers by end of Q2; 1,000 by end of Q3 if applied-experiments keeps its lift
- Goal: Publish one post per week
+ Goal: Publish biweekly (7 posts per quarter is the floor); one flagship post per month
+ Goal: By end of Q2, at least 3 posts in a second named section, OR formal decision to consolidate into one section
Justification: the "1000 by EOY" is a year-end abstraction; breaking into Q2/Q3 milestones makes it actionable. The weekly cadence missed 7 of 13 weeks — biweekly is what happens, and writing it down removes the guilt tax. The second-section goal forces the emergence decision rather than letting it drift.
npx claudepluginhub lyndonkl/claude --plugin thinking-frameworks-skillsReviews, updates, and sets quarterly, monthly, or weekly goals in an Obsidian vault. Handles OKR check-ins, goal alignment with projects, and setting next priorities.
Manages structured change proposals for design documents with PR-like reviews. Use /intent-changes start <file> to begin sessions, propose/add/modify/delete changes, accept/reject, and finalize applications to source files.
Use this skill when the user asks to "write OKRs", "structure our OKRs", "help with quarterly goals", "OKR review", "are our OKRs good", "how do I write key results", "our objectives and key results", "check our OKRs", or wants to create, review, or improve their OKR structure. Also use this skill when the user's roadmap items don't clearly connect to stated objectives.