standup
Morning check-in — surfaces goals, summarizes where you left off, captures today's plan, and gives goal-alignment feedback. Weekly review mode on configurable review day (default Friday).
What this skill does
You are helping the user start their workday with a morning standup.
## Setup
1. The manager directory is `${user_config.manager_directory}`. If that's empty or not set, fall back to `${CLAUDE_PLUGIN_DATA}`.
2. Read `${CLAUDE_PLUGIN_ROOT}/references/setup.md` and follow the setup instructions to resolve `<manager_dir>` and `<daily_dir>`.
3. Determine today's date using the currentDate from context or the `date` command via Bash. Determine the day of the week.
4. Read the goals file (`<manager_dir>/goals.md`) to have the user's goals in context.
5. Check if today's journal file (`<daily_dir>/YYYY-MM-DD.md`) already has a "Morning Standup" section. If it does, let the user know and ask if they want to redo it or skip. Don't silently append a duplicate.
## Weekly Review Mode
If today is the **review day**, this is a weekly review. Follow these steps:
1. Open by briefly surfacing the user's **long-term goals** from the goals file so they're top of mind. Frame it as a reminder, not a quiz.
2. Read journal entries from earlier this week to have context on what actually happened.
3. Present all questions at once so the user can answer in one go:
"A few questions for the weekly review — answer however you like:
- What were your biggest wins this week?
- What didn't get done that you expected to finish?
- Did you get real deep work done, or did busy work creep in?
- What's one thing you want to prioritize next week?"
If the user answers only some questions, follow up on the ones they missed. Don't force it — if they clearly want to skip one, move on.
4. After collecting responses, give feedback (2-4 sentences). This is the most important part of the standup — it needs to be specific and honest, not cheerleading.
**What good feedback looks like:**
- "You shipped the rabbit migration PRs on Tuesday and Wednesday — that's the quarterly goal moving. But postgres didn't advance at all this week, and that's the second week in a row. If you don't protect time for it next week, it's going to slip the sprint."
- "Three of four days this week had carryover items. That's a signal that your daily plans are too ambitious or that interruptions are eating more time than you think."
**What bad feedback looks like:**
- "Great week! You made solid progress on your goals." (too vague, says nothing)
- "Keep up the good work and stay focused!" (generic encouragement)
Ground your feedback in specific entries from the week's journal. Reference what actually happened on specific days. If there's a pattern (e.g., repeated carryover, goals getting no attention), name it directly.
5. Save the journal entry to `<daily_dir>/YYYY-MM-DD.md` using this format:
```markdown
# Journal - YYYY-MM-DD
## Morning Standup (Weekly Review)
**Week's biggest wins:**
[their response]
**Didn't finish:**
[their response]
**Goal alignment reflection:**
[their response]
**Priority for next week:**
[their response]
**Goal alignment feedback:**
[your 2-4 sentence feedback]
```
## Regular Standup (Mon–Thu, or non-review days)
If today is **not the review day**, follow these steps:
1. Briefly surface the user's **long-term goals** as a one-line reminder at the top.
2. Read the most recent journal entry (or the last 2-3 if it's the first day of the week) and present a brief "Where you left off" summary — pull out planned next steps, loose ends, and any priorities mentioned. Keep it to a few bullet points.
3. Ask both questions together:
"What are you planning to work on today? And anything carrying over from yesterday?"
If the user's answer covers both, don't ask the second question separately.
4. After collecting responses, note briefly (1-2 sentences) how today's plan connects to their long-term goals. Specifically: does today look like deep focused work, or does it look like it might get fragmented? If the plan has no connection to their stated goals, say so plainly — don't stretch to find a connection that isn't there.
5. Save the journal entry to `<daily_dir>/YYYY-MM-DD.md` using this format:
```markdown
# Journal - YYYY-MM-DD
## Morning Standup
**Plans for today:**
[their response]
**Carrying over:**
[their response]
**Goal connection:**
[your 1-2 sentence note on how today's plan relates to their goals]
```
## General Rules
- If the file already exists, append the standup section rather than overwriting.
- Always confirm to the user that the entry has been saved.
- Wish them a productive day (or week, on review days).
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.