メニュー
Use when capturing a specific accomplishment for job searching, performance reviews, or interview prep. Triggered by "log accomplishment", "/log-accomplishment", "add to my accomplishments", or "remember this for my resume".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding a new data source to the daily summary — MCP tools, CLI commands, local file paths, or HTTP endpoints. Triggered by "add source", "/add-source", "add to my daily summary", or "connect [tool] to my daily summary".
Use when drafting the end-of-day summary. Reads today's meetings, Slack, and memory files to append a structured summary to today's daily note.
Use when setting up pm-ground-control for the first time. Creates the workspace folder structure, populates memory files through an interview, and installs skills.
Use when preparing for a job search, updating a resume, prepping for interviews, or doing a performance review. Triggered by "review accomplishments", "/accomplishments-review", "prepare for interviews", "update my resume", "performance review prep".
Use when synthesizing the week's daily notes into a weekly summary document. Run at end of week.
Use when drafting the weekly stakeholder update. Run after weekly-summary is complete.
| name | log-accomplishment |
| description | Use when capturing a specific accomplishment for job searching, performance reviews, or interview prep. Triggered by "log accomplishment", "/log-accomplishment", "add to my accomplishments", or "remember this for my resume". |
Capture a career-relevant accomplishment in the persistent log.
Read memory/me.md for the workspace path.
{{WORKSPACE_PATH}}/_accomplishments/YYYY.md where YYYY is the current year. Create the file if it doesn't exist.If the user described what happened, use it. If they just invoked the skill with no context, ask:
"What happened? Give me a quick description and I'll help frame it."
Probe for anything missing. Do not write the entry until you have all five:
If the user says they don't know a metric, write "metric TBD — [description of what to look up]" and flag it in the entry.
Append to _accomplishments/YYYY.md (current year):
## YYYY-MM-DD — [Project/Area]
**What I did:** [specific action with strong verb]
**Context:** [1-2 sentences: what the situation was and why it mattered]
**Impact:** [what changed or was enabled; include metrics if available]
**Draft bullet:** "[Action verb] [what] resulting in [outcome]"
**STAR notes:**
- **S:** [Situation — the context]
- **T:** [Task — what you were responsible for]
- **A:** [Action — what you specifically did]
- **R:** [Result — outcome, ideally with metric]
---
| Category | Verbs |
|---|---|
| Strategy / decisions | Defined, Designed, Prioritized, Scoped, Recommended, Proposed, Established |
| Alignment | Aligned, Negotiated, Facilitated, Resolved, Advocated, Drove consensus |
| Delivery | Shipped, Launched, Deployed, Completed, Delivered, Produced |
| Analysis | Diagnosed, Identified, Investigated, Synthesized, Surfaced |
| Improvement | Reduced, Increased, Streamlined, Eliminated, Automated, Optimized |
| Leadership | Led, Drove, Initiated, Coordinated, Influenced, Unblocked |
Reply with:
"Logged. Draft bullet: [the bullet]"
If a metric is missing and worth tracking down, flag it: "Worth finding the [X] number to strengthen this one."