Menu
Wrap-up, implementation summary, or final handoff. Use after build/test/review to explain what changed and what remains.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this skill when the user asks to analyze, create, or update an investment asset/company in Notion Assets / Investments. Produces professional-grade, evidence-backed asset research and then creates or updates the matching Notion asset page after confirmation.
Cartography, deep codebase map, repo map, onboarding map, or navigation index. Use for explicit codebase mapping/onboarding requests that need multiple cartography subagents and docs/indexes.
Comment code, explain functions, or add documentation comments. Use to make code understandable after implementation.
Commit, git commit message, or staged changes summary. Use by github agent only when the user explicitly requests a commit.
Medium article, long-form article, essay, or article from notes. Use when the user asks to create/write a Medium-style article using Content Vault evidence, positioning, and humanization rules.
LinkedIn post, social post, short content draft, or post from notes. Use when the user asks to write/create a LinkedIn/social post using the Content Vault voice, evidence, and anti-AI-writing rules.
| name | wrap-up |
| description | Wrap-up, implementation summary, or final handoff. Use after build/test/review to explain what changed and what remains. |
## Summary
- <what was done>
## Files changed
- `<path>` — <purpose of change>
## Commands run
- `<command>` — <result and what it proved>
## State updates
- Repo progress: `PROGRESS.md` updated / not present / skipped — <why>
- Feature list: `feature_list.json` updated / not present / skipped — <why>
- Vault progress: ObsidianMemory Dev Vault/PM records updated / not configured / skipped — <why>
- Kanban task: <path/status updated> / none matched / skipped — <why>
## Failures or remaining risks
- <failure/risk or `None`>
## Follow-ups
- <optional next action or `None`>
## Confidence
- low / medium / high
Mention if docs/index/memory/progress/kanban/commit/PR were skipped or require explicit user request.
PROGRESS.md and feature_list.json or explain why not.