daily-okr

$npx mdskill add Mark393295827/third-brain-v5-skills/daily-okr

Executes a daily knowledge compound closed loop for input, cognition, wiki update, action, output, and feedback.

  • Solves the problem of managing daily knowledge inputs and outputs efficiently.
  • Depends on user input and internal logic to determine actions and updates.
  • Decides what to do based on predefined key results and user preferences.
  • Delivers a concise daily artifact including insights, wiki updates, actions, ideas, and scores.

SKILL.md

.github/skills/daily-okrView on GitHub ↗
---
name: daily-okr
description: Execute a V6 daily knowledge compound closed loop — 7 Key Results from input to feedback with scoring, evidence, wiki write-back, and optional scheduled Obsidian daily-loop note. Use when the user wants to do a daily review, plan their day, run a knowledge workflow, or complete the generated daily knowledge-management loop.
version: "6.0"
updated: "2026-06-27"
assumes: "The user wants a daily loop that connects knowledge capture, action, output, and review."
conflicts_with: "Do not let daily scoring replace verify-before-claim for completion claims or wiki-lint for vault health."
---

# Daily OKR — Knowledge Compound Closed Loop

Run a complete 7-KR cycle: Input → Cognition → Wiki → Behavior → Creativity → Output → Feedback.

## Usage Template

**Prompt**
```text
Run daily-okr in compact mode. Produce one insight, one wiki update, one action under 15 minutes, one reusable output, and a final score.
```

**Use Case**
- Starting or closing a knowledge-work day with a repeatable compounding loop.

**Expected Result**
- The agent addresses all 7 KRs and leaves a concise daily artifact.

**Output Example**
- A 7-KR scorecard with one captured input, one insight, one wiki update, one action, one idea, one output, and one review.

**Verification Case**
- KR3 has a wiki update, KR4 has a concrete action, KR7 includes evidence for completed claims, and the score is calculated.

**Verified Effect**
- A scattered workday becomes one captured insight, one action, one reusable output, and one feedback score.

## Success Metrics

- All 7 KRs have an explicit result, score, or skipped-with-reason status.
- KR3 names the wiki update, KR4 names a concrete action, and KR7 states evidence for any completion claim.
- Daily artifact includes a final score and one improvement for tomorrow.
- When a scheduled daily-loop note exists, the final score references its queue, health snapshot, or evidence section.

## When to Use

- User says "start my daily OKR", "daily review", "today's workflow"
- Beginning of a work session focused on knowledge work
- User wants to capture, think, act, and reflect

## The 7 KR Cycle

```
KR1 输入    → 记录 1-3 条高质量信息          [5 min]
KR2 认知    → 提炼 1 句话摘要 + 1 个洞察      [5 min]
KR3 Wiki   → 新增/更新 1 个 Wiki 页面         [5 min]
KR4 行为    → 设计并执行 1 个 15 分钟行动       [5 min]
KR5 创意    → 写下 1 个新想法                 [1 min]
KR6 输出    → 留下 1 个可复用成果              [2 min]
KR7 反馈    → 3 行复盘 + 验证证据              [3 min]
```

> Minimum bar: **1 input + 1 insight + 1 action + 1 review.**

## V6 Scheduled Daily Loop

If `system/daily/YYYY-MM-DD-daily-knowledge-loop.md` exists, use it as the starting artifact:

1. Read the automated snapshot for clipping queue, P0/P1 debt, changed files, and rule candidates.
2. Pick one focused KR3 wiki update or one P0/P1 repair.
3. Keep automated blocks intact; write only in manual KR sections or append a log entry.
4. Do not promote system rules from daily signals alone. Queue candidates for supervised review.
5. End with evidence: changed files, diff, command output, dashboard metric, or skipped-with-reason.

### The Stop Doing List (Warren Buffett & Charlie Munger)

> "The difference between successful people and very successful people is that very successful people say 'no' to almost everything." — Warren Buffett

> "It is remarkable how much long-term advantage people have gotten by trying to be consistently not stupid, instead of trying to be very intelligent." — Charlie Munger

During KR7, in addition to reviewing what was done, ask:

| Question | Purpose | Master Who Used It |
|----------|---------|-------------------|
| What should I NOT have done today? | Identify time-wasting activities | Buffett: "Avoiding stupidity is easier than seeking brilliance" |
| What habit should I stop? | Break bad patterns | Munger: "Invert, always invert" |
| What commitment should I decline? | Protect time and energy | Peter Drucker: "The most important decision is what not to do" |
| What investment should I cut losses on? | Avoid sunk cost fallacy | Graham: "The intelligent investor sells when a stock reaches its intrinsic value" |

**The Wisdom of Not Doing:**
- Saying no is harder than saying yes, but far more effective
- Knowing what to ignore lets you focus on what matters
- "The stock market is a device for transferring money from the impatient to the patient." — Buffett

### KR1 — Input
- Record 1-3 high-quality information items
- At least 1 from external world (article/report/video/data)
- At least 1 from personal experience (observation/conversation/project)
- Note the source and why it matters

### KR2 — Cognition
- Select 1 item for deep understanding
- Extract: 1-sentence summary + 1 insight/judgment

### KR3 — Wiki
- Create or update 1 wiki page
- Add tags and ≥2 wikilinks
- Set status (seed/growing/evergreen)

### KR4 — Behavior
- Derive 1 actionable item from today's knowledge
- Break it down to ≤15 minutes
- Execute or schedule it

### KR5 — Creativity
- Generate 1-3 ideas based on today's knowledge
- At least 1 from cross-domain analogy
- Select 1 worth pursuing

### KR6 — Output
- Produce 1 small reusable artifact
- State which long-term goal it serves
- Judge reusability

### KR7 — Feedback + Verification
- Write 3 lines of retrospective
- ⭐ **Verification**: For every "completed" claim, show evidence (command output, diff, screenshot)
- Anti-pattern: "should be fine" without proof
- Update the daily log

## Daily Scoring Card

```
输入 +1 | 认知 +1 | Wiki +2 | 行为 +2 | 创意 +1 | 输出 +2 | 反馈 +1 = /10
3=still going  5=minimal loop  7=quality loop  10=compounding flywheel
```

## Quality Gates

- [ ] All 7 KRs addressed (even briefly)
- [ ] KR3: page has ≥2 `[[wikilinks]]`
- [ ] KR4: action is ≤15 minutes
- [ ] KR6: output is reusable
- [ ] KR7: every done-claim has evidence
- [ ] Score calculated
- [ ] Scheduled daily-loop note respected when present; automated snapshot not overwritten

More from Mark393295827/third-brain-v5-skills

SkillDescription
agent-teams-commandCommand V6 multi-agent work with bounded roles, ownership, worktree isolation, IPC, integration gates, cleanup, attention budgets, and verification loops. Use when the user needs Claude Code Agent Teams, parallel agents, delegation strategy, Ender-style commander training, von Neumann-style command architecture, Palantir-style ontology command boards, FDE field discovery, EDD integration gates, dynamic workflow tradeoffs, or multi-agent orchestration grounded in Obsidian wiki operating rules.
ai-six-sigma-property-osDesign an AI Six Sigma Black Belt operating model for property service, maintenance dispatch, environmental testing, quote generation, CRM follow-up, and workflow quality dashboards. Use when the user needs a Property Agent OS, AI + Ontology + DMAIC management system, CTQ metrics, agent-team roles, work-order states, or MVP roadmap for operations quality.
anthropic-osImprove a personal or team operating system with self-evolving loops, CASH allocation, 3B creativity, predictive coding, and diagnostics. Use when the user wants to redesign a work method, learning loop, or cognitive operating system.
behavior-designDesign a behavior change system — decompose a goal into minimum habits, define triggers, build SOPs, and set up review cycles. Use when the user wants to build a habit, change behavior, or achieve a personal goal.
cognitive-compileDeep learning compile framework — transforms raw information into actionable judgment. Use when the user wants to deeply understand a topic, not just capture it.
context-managerManage the LLM's context window — token budgeting, prompt assembly, truncation strategies. Use when approaching context limits or optimizing prompt costs.
creativity-engineGenerate, validate, and output new ideas based on existing knowledge. Combines combinatorial creativity, cross-domain analogy, and minimum experiments. Use when the user wants fresh ideas, new product concepts, or creative solutions.
loop-engineeringTurn a repeatable task into a bounded, evidence-driven agent loop. Use when Codex needs to decide whether a task merits a Goal, Loop, Automation, or AutoResearch pattern; define a loop contract; check trigger/state/tools/codebase readiness; choose single-agent versus maker-checker versus manager-workers topology; prevent runaway iteration; or repair a loop that stalls, self-grades, exceeds review budget, or writes without verified evidence.
session-learnExtract reusable knowledge from a work session and save concepts, entities, corrections, patterns, ideas, decisions, and gaps to the wiki. Use when ending a session or when the user says to extract knowledge.
startup-evaluationEvaluate startup health using entrepreneurship, VC, and execution frameworks. Use when assessing a startup idea, company, pitch, due diligence target, fundraising readiness, or business model health.