$npx -y skills add kv0906/pm-kit --skill dailyLog standup update with keyword detection. Multi-project daily notes with auto-blocker/decision detection. Use for "/daily project: shipped X, wip Y, blocked on Z".
| 1 | # /daily — Daily Standup Capture |
| 2 | |
| 3 | You are processing a daily standup update. This is an ATOMIC operation: capture → create note → done. |
| 4 | |
| 5 | ## Context |
| 6 | |
| 7 | Today's date: `!date +%Y-%m-%d` |
| 8 | Check existing daily: `!ls daily/*.md 2>/dev/null | tail -5` |
| 9 | |
| 10 | Reference template: @_templates/daily.md |
| 11 | Config: @_core/config.yaml |
| 12 | Processing logic: @_core/PROCESSING.md |
| 13 | |
| 14 | ## Input |
| 15 | |
| 16 | User input: $ARGUMENTS |
| 17 | |
| 18 | ## Session Task Progress |
| 19 | |
| 20 | Create tasks upfront for visibility: |
| 21 | |
| 22 | ``` |
| 23 | TaskCreate: "Parse standup input" |
| 24 | activeForm: "Parsing standup input..." |
| 25 | |
| 26 | TaskCreate: "Create/update daily note" |
| 27 | activeForm: "Updating daily note..." |
| 28 | |
| 29 | TaskCreate: "Process detected items" |
| 30 | activeForm: "Processing blockers and decisions..." |
| 31 | ``` |
| 32 | |
| 33 | ## Processing Steps |
| 34 | |
| 35 | 1. **Parse Input** |
| 36 | - Extract project name (before colon or first word) |
| 37 | - If project not provided or invalid, ask user to specify from config.yaml projects |
| 38 | - Segment content by keywords: |
| 39 | - **Shipped**: shipped, done, completed, finished, merged, deployed, released |
| 40 | - **WIP**: wip, working on, in progress, continuing, started, ongoing |
| 41 | - **Blocked**: blocked, stuck, waiting on, waiting for, need from, dependency |
| 42 | - **Decided**: decided, going with, chose, selected, agreed |
| 43 | |
| 44 | 2. **Check Existing** |
| 45 | - If daily note for today exists, update the project's section |
| 46 | - If not, create new daily with project sections |
| 47 | |
| 48 | 3. **Handle Blockers (AUTO-PROMPT)** |
| 49 | - For each blocked item detected: |
| 50 | - Search `blockers/{project}/*.md` for similar open blockers |
| 51 | - If similar exists: link to it |
| 52 | - If NEW blocker detected: |
| 53 | - **PROMPT USER**: "Blocker detected: '{text}'. Create blocker note? (y/n/details)" |
| 54 | - If **y**: Create blocker with severity=medium |
| 55 | - If **details**: Prompt for severity, owner, due date |
| 56 | - If **n**: Skip blocker creation |
| 57 | - Blocker path: `blockers/{project}/{date}-{slug}.md` |
| 58 | |
| 59 | 4. **Handle Decisions (AUTO-DETECT)** |
| 60 | - For each decision keyword detected: |
| 61 | - Suggest creating a decision note |
| 62 | - Link to daily if user confirms |
| 63 | |
| 64 | 5. **Create/Update Daily Note** |
| 65 | - Filename: `daily/{date}.md` — ONE file per day for ALL projects |
| 66 | - If file exists: Update the `## {project}` section only |
| 67 | - If new: Create from template |
| 68 | |
| 69 | 6. **Update Project Index** |
| 70 | - Add entry to `01-index/{project}.md` if index exists |
| 71 | |
| 72 | 7. **Append to Vault Log** |
| 73 | - Append entry to `01-index/_vault-log.md` (see `.claude/rules/vault-log.md`) |
| 74 | - Action: `daily` |
| 75 | - Details: summarize shipped/wip/blocked counts |
| 76 | |
| 77 | ## Output |
| 78 | |
| 79 | ``` |
| 80 | Updated: daily/{date}.md (section: {project}) |
| 81 | - Shipped: {count} items |
| 82 | - WIP: {count} items |
| 83 | - Blockers: {count} (linked/created) |
| 84 | - Decisions: {count} (detected) |
| 85 | ``` |