ワンクリックで
prep
Generate a performance review narrative from logged work
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Generate a performance review narrative from logged work
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Log a work achievement as a linked note in the vault — for performance reviews
End-of-day check-in — pulls GitHub activity, compares to existing logs, and creates missing entries
Log a concrete task with an optional deadline — surfaces in daily briefings
Morning planning session - reads recent vault activity, flags urgent items, plans the day
Initialise claudia for a new user — walks through prerequisites, then uses the Obsidian CLI to set up the vault
Weekly review - flags forgotten ideas/tasks, summarises the week
| name | prep |
| description | Generate a performance review narrative from logged work |
| argument-hint | ["time range","e.g. \"Q1 2026\" or \"last 3 months\""] |
Generate a performance review narrative. Today: !date +%Y-%m-%d.
Input: $ARGUMENTS
Determine the time range:
Read the Work atlas:
obsidian read file="Atlas/Work"
Collect all entries within the time range.
Read each work and decision note found in the range:
obsidian read path="Notes/[note-name].md"
Extract: what, impact, tag, PRs, related projects, ticket references.
Read active and completed projects that overlap the time range:
obsidian search query="type:project" --output paths
Read each and note progress (steps completed, work entries linked).
Group achievements by tag:
work/shipped) — things deliveredwork/unblocked) — blockers removed for otherswork/led) — decisions made, initiatives driven, reviews donework/learned) — significant insights gainedwork/improved) — process, codebase, or team improvementsGenerate the narrative:
## Performance Summary — [time range]
### Highlights
[3-5 most impactful achievements, each with specific evidence from the notes]
### Shipped
[Bulleted list with what + impact for each]
### Led & Decided
[Decisions made, initiatives driven — include rationale from decision notes]
### Unblocked
[Blockers removed — who/what was unblocked]
### Improved
[Process and codebase improvements]
### Learned
[Key technical or professional insights]
### Projects
[Status of each project active during this period — what was accomplished, what remains]
### By the Numbers
- [N] work entries logged
- [N] decisions documented
- [N] projects advanced
- [N] PRs shipped
Show the narrative and ask: "Want me to save this as a note, or adjust anything?"
If saving:
obsidian create name="prep-[range-slug]" path="Notes/" content="---
date: [today]
type: prep
tags: [status/done]
---
[narrative content]
"
Use specific evidence from the notes — names, PR links, dates. No vague filler. This is the payoff of the entire system.