[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWPJP195PPSMNZ36T81GRE":3,"skill-same:01M6WWPJP195PPSMNZ36T81GRE":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":74,"install":75,"resources":88},"01M6WWPJP195PPSMNZ36T81GRE","standup-context",null,"Writes a structured standup update as a session.standup LogEntry — capturing\nwhat was done, what is in progress, what comes next, and any blockers. Use\nwhen the user says \"write a standup\", \"standup update\", \"what did I do today\",\n\"write a status update for the team\", or at the end of a session on projects\nthat run daily standups.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"standup context","standup","context","log","when","at","next steps","progress","end","next","done","query","workitem","write","work","projects","team","update","run","generate","2026-11-10 10:12:30",false,"---\nname: standup-context\ndescription: |\n  Writes a structured standup update as a session.standup LogEntry — capturing\n  what was done, what is in progress, what comes next, and any blockers. Use\n  when the user says \"write a standup\", \"standup update\", \"what did I do today\",\n  \"write a status update for the team\", or at the end of a session on projects\n  that run daily standups.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-standup-context\n    version: \"1.0.0\"\n    created: 2026-04-08T00:00:00Z\n    category: processkit\n    layer: 2\n    uses:\n      - skill: event-log\n        purpose: Write the session.standup LogEntry with the structured details schema.\n      - skill: workitem-management\n        purpose: Query completed and in-progress WorkItems to populate done\u002Fdoing accurately.\n    commands:\n      - name: pk-standup\n        args: \"\"\n        description: \"Generate a standup update (done \u002F doing \u002F next \u002F blockers)\"\n      - name: pk-status\n        args: \"\"\n        description: \"Generate a status update: current progress, blockers, and recommended next steps\"\n---\n\n# Standup Context\n\n## Intro\n\nA standup update is a brief, structured record of session progress — written\nfor the team record and for any downstream skill (like `status-briefing`)\nthat reconstructs what happened. It lives in `context\u002Flogs\u002F` as a\n`session.standup` LogEntry. It is NOT a flat `context\u002FSTANDUPS.md` file.\n\n## Overview\n\n### The four fields\n\nEvery standup has exactly four fields:\n\n- **done** — what was completed since the last standup. Past tense, specific.\n  \"Merged BACK-042 auth refactor\" not \"worked on auth.\"\n- **doing** — what is currently in progress. These are the items that\n  will appear in the next standup's \"done\" if work continues.\n- **next** — what comes immediately after the current work. One or two items.\n  Gives the team visibility on direction.\n- **blockers** — anything preventing progress. Empty list if none.\n  Be specific: \"waiting for Alice to review PR #88\" not \"blocked on review.\"\n\n### Writing the LogEntry\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: LogEntry\nmetadata:\n  id: LOG-\u003Cnext-id>\n  created: \u003CISO 8601 UTC>\nspec:\n  event_type: session.standup\n  timestamp: \u003CISO 8601 UTC>\n  actor: \u003CACTOR-id or agent name>\n  summary: \"Standup — \u003CYYYY-MM-DD>\"\n  details:\n    session_date: \"\u003CYYYY-MM-DD>\"\n    done:\n      - \"\u003Ccompleted item 1>\"\n      - \"\u003Ccompleted item 2>\"\n    doing:\n      - \"\u003Cin-progress item>\"\n    next:\n      - \"\u003Cnext item>\"\n    blockers: []\n---\n```\n\nSave to `context\u002Flogs\u002FLOG-\u003Cid>-standup-\u003Cdate>.md`.\n\n### Sourcing the content\n\nBefore writing, query:\n1. `workitem-management` — filter for `state: done` (completed today) and\n   `state: in_progress` (currently doing)\n2. Recent `session.handover` or `session.standup` entries — for what the\n   previous session left as \"next\"\n3. Git log — `git log --oneline --since=\"24 hours ago\"` for a mechanical\n   account of commits since the last standup\n4. GitHub, when inside a git repository with a GitHub remote and an\n   authenticated `gh` CLI:\n\n   ```\n   gh issue list --state open --limit 20 \\\n     --json number,title,labels,assignees,updatedAt,url\n   gh pr list --state open --limit 20 \\\n     --json number,title,isDraft,reviewDecision,headRefName,updatedAt,url\n   ```\n\nCross-check: if a WorkItem is marked `done` but no commit references it,\nnote it — might be a missing commit or a premature state transition.\nIf GitHub cannot be checked, note that briefly and continue. When it can\nbe checked, include PRs waiting on review and issues that create blockers\nor immediate next work; do not dump every open item into the standup.\n\n### Trigger phrases\n\nThe agent should write a standup when it hears:\n- \"write a standup\" \u002F \"standup update\"\n- \"what did I do today\" \u002F \"summarize today's work\"\n- \"write a status update for the team\"\n- \"daily update\"\n- \"end of day summary\"\n\nThis skill also provides the `\u002Fpk-status` and `\u002Fpk-standup` commands for\ndirect invocation — see `commands\u002Fpk-status.md` and\n`commands\u002Fpk-standup.md`.\n\n## Gotchas\n\n- **Writing done in present tense.** \"Working on BACK-042\" belongs in\n  doing, not done. Done means the work is finished. \"Completed BACK-042\n  auth refactor and merged to main\" is done.\n- **One-liner entries with no specifics.** \"Worked on auth\" is not a\n  standup item — it gives the team nothing. Reference the WorkItem ID,\n  the PR number, or the specific outcome: \"Merged auth refactor (BACK-042,\n  PR #88); all tests green.\"\n- **Leaving blockers vague.** \"Blocked on review\" tells the team nothing\n  actionable. Name the reviewer, the PR, and how long it has been waiting:\n  \"PR #88 waiting on Alice — submitted 2026-04-07, no response yet.\"\n- **Conflating doing and next.** Doing is what is actively in progress\n  right now. Next is what comes after. The distinction matters: doing items\n  might finish today; next items haven't started.\n- **Writing a standup without querying WorkItem state.** Memory-based\n  standups miss items and include outdated ones. Always check the actual\n  WorkItem state before writing.\n- **Missing GitHub blockers.** In GitHub-backed repositories, PR review\n  state and open issues can be the real blocker even when local worktree\n  state looks clean. Check `gh` when available and cite issue\u002FPR numbers.\n- **Writing a standup for a period longer than one session without flagging\n  it.** If the last standup was three days ago, the \"done\" list is actually\n  three days of work. Flag this in the summary line so the team knows the\n  cadence was missed.\n- **Including personal context in the team standup.** Blockers like\n  \"dentist appointment\" or \"waiting to hear back about contract\" belong in\n  a `session.handover`, not a standup. Standups are project-facing records.\n\n## Full reference\n\n### Standup vs. session handover\n\n| | standup-context | session-handover |\n|---|---|---|\n| **When** | Regular cadence (daily or per session) | Before shutdown \u002F container restart |\n| **Audience** | The team \u002F project record | The next session (same person or agent) |\n| **Focus** | Accountability — what was done | Continuity — what to pick up next |\n| **LogEntry type** | `session.standup` | `session.handover` |\n\n### Reading recent standups\n\nTo reconstruct what has happened since the last session:\n\n```\nquery_events(event_type=\"session.standup\", since=\"\u003Cdate>\", order=\"asc\")\n```\n\n`status-briefing` uses this query to populate its \"what happened\" section\nwhen no recent `session.handover` exists.\n\n### Output format for sharing\n\nWhen the user wants to copy a standup to Slack or email, format it as:\n\n```\n**Yesterday \u002F last session:**\n- \u003Cdone item 1>\n- \u003Cdone item 2>\n\n**Today:**\n- \u003Cdoing item>\n- \u003Cnext item>\n\n**Blockers:**\n- \u003Cblocker> (or: none)\n```\n","# Standup Context\n\n## Intro\n\nA standup update is a brief, structured record of session progress — written\nfor the team record and for any downstream skill (like `status-briefing`)\nthat reconstructs what happened. It lives in `context\u002Flogs\u002F` as a\n`session.standup` LogEntry. It is NOT a flat `context\u002FSTANDUPS.md` file.\n\n## Overview\n\n### The four fields\n\nEvery standup has exactly four fields:\n\n- **done** — what was completed since the last standup. Past tense, specific.\n  \"Merged BACK-042 auth refactor\" not \"worked on auth.\"\n- **doing** — what is currently in progress. These are the items that\n  will appear in the next standup's \"done\" if work continues.\n- **next** — what comes immediately after the current work. One or two items.\n  Gives the team visibility on direction.\n- **blockers** — anything preventing progress. Empty list if none.\n  Be specific: \"waiting for Alice to review PR #88\" not \"blocked on review.\"\n\n### Writing the LogEntry\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: LogEntry\nmetadata:\n  id: LOG-\u003Cnext-id>\n  created: \u003CISO 8601 UTC>\nspec:\n  event_type: session.standup\n  timestamp: \u003CISO 8601 UTC>\n  actor: \u003CACTOR-id or agent name>\n  summary: \"Standup — \u003CYYYY-MM-DD>\"\n  details:\n    session_date: \"\u003CYYYY-MM-DD>\"\n    done:\n      - \"\u003Ccompleted item 1>\"\n      - \"\u003Ccompleted item 2>\"\n    doing:\n      - \"\u003Cin-progress item>\"\n    next:\n      - \"\u003Cnext item>\"\n    blockers: []\n---\n```\n\nSave to `context\u002Flogs\u002FLOG-\u003Cid>-standup-\u003Cdate>.md`.\n\n### Sourcing the content\n\nBefore writing, query:\n1. `workitem-management` — filter for `state: done` (completed today) and\n   `state: in_progress` (currently doing)\n2. Recent `session.handover` or `session.standup` entries — for what the\n   previous session left as \"next\"\n3. Git log — `git log --oneline --since=\"24 hours ago\"` for a mechanical\n   account of commits since the last standup\n4. GitHub, when inside a git repository with a GitHub remote and an\n   authenticated `gh` CLI:\n\n   ```\n   gh issue list --state open --limit 20 \\\n     --json number,title,labels,assignees,updatedAt,url\n   gh pr list --state open --limit 20 \\\n     --json number,title,isDraft,reviewDecision,headRefName,updatedAt,url\n   ```\n\nCross-check: if a WorkItem is marked `done` but no commit references it,\nnote it — might be a missing commit or a premature state transition.\nIf GitHub cannot be checked, note that briefly and continue. When it can\nbe checked, include PRs waiting on review and issues that create blockers\nor immediate next work; do not dump every open item into the standup.\n\n### Trigger phrases\n\nThe agent should write a standup when it hears:\n- \"write a standup\" \u002F \"standup update\"\n- \"what did I do today\" \u002F \"summarize today's work\"\n- \"write a status update for the team\"\n- \"daily update\"\n- \"end of day summary\"\n\nThis skill also provides the `\u002Fpk-status` and `\u002Fpk-standup` commands for\ndirect invocation — see `commands\u002Fpk-status.md` and\n`commands\u002Fpk-standup.md`.\n\n## Gotchas\n\n- **Writing done in present tense.** \"Working on BACK-042\" belongs in\n  doing, not done. Done means the work is finished. \"Completed BACK-042\n  auth refactor and merged to main\" is done.\n- **One-liner entries with no specifics.** \"Worked on auth\" is not a\n  standup item — it gives the team nothing. Reference the WorkItem ID,\n  the PR number, or the specific outcome: \"Merged auth refactor (BACK-042,\n  PR #88); all tests green.\"\n- **Leaving blockers vague.** \"Blocked on review\" tells the team nothing\n  actionable. Name the reviewer, the PR, and how long it has been waiting:\n  \"PR #88 waiting on Alice — submitted 2026-04-07, no response yet.\"\n- **Conflating doing and next.** Doing is what is actively in progress\n  right now. Next is what comes after. The distinction matters: doing items\n  might finish today; next items haven't started.\n- **Writing a standup without querying WorkItem state.** Memory-based\n  standups miss items and include outdated ones. Always check the actual\n  WorkItem state before writing.\n- **Missing GitHub blockers.** In GitHub-backed repositories, PR review\n  state and open issues can be the real blocker even when local worktree\n  state looks clean. Check `gh` when available and cite issue\u002FPR numbers.\n- **Writing a standup for a period longer than one session without flagging\n  it.** If the last standup was three days ago, the \"done\" list is actually\n  three days of work. Flag this in the summary line so the team knows the\n  cadence was missed.\n- **Including personal context in the team standup.** Blockers like\n  \"dentist appointment\" or \"waiting to hear back about contract\" belong in\n  a `session.handover`, not a standup. Standups are project-facing records.\n\n## Full reference\n\n### Standup vs. session handover\n\n| | standup-context | session-handover |\n|---|---|---|\n| **When** | Regular cadence (daily or per session) | Before shutdown \u002F container restart |\n| **Audience** | The team \u002F project record | The next session (same person or agent) |\n| **Focus** | Accountability — what was done | Continuity — what to pick up next |\n| **LogEntry type** | `session.standup` | `session.handover` |\n\n### Reading recent standups\n\nTo reconstruct what has happened since the last session:\n\n```\nquery_events(event_type=\"session.standup\", since=\"\u003Cdate>\", order=\"asc\")\n```\n\n`status-briefing` uses this query to populate its \"what happened\" section\nwhen no recent `session.handover` exists.\n\n### Output format for sharing\n\nWhen the user wants to copy a standup to Slack or email, format it as:\n\n```\n**Yesterday \u002F last session:**\n- \u003Cdone item 1>\n- \u003Cdone item 2>\n\n**Today:**\n- \u003Cdoing item>\n- \u003Cnext item>\n\n**Blockers:**\n- \u003Cblocker> (or: none)\n```\n",{"name":5,"metadata":44,"description":67},{"processkit":45},{"id":46,"uses":47,"layer":54,"created":55,"version":56,"category":57,"commands":58,"apiVersion":66},"SKILL-standup-context",[48,51],{"skill":49,"purpose":50},"event-log","Write the session.standup LogEntry with the structured details schema.",{"skill":52,"purpose":53},"workitem-management","Query completed and in-progress WorkItems to populate done\u002Fdoing accurately.",2,1775606400000,"1.0.0","processkit",[59,63],{"args":60,"name":61,"description":62},"","pk-standup","Generate a standup update (done \u002F doing \u002F next \u002F blockers)",{"args":60,"name":64,"description":65},"pk-status","Generate a status update: current progress, blockers, and recommended next steps","processkit.projectious.work\u002Fv2","Writes a structured standup update as a session.standup LogEntry — capturing\nwhat was done, what is in progress, what comes next, and any blockers. Use\nwhen the user says \"write a standup\", \"standup update\", \"what did I do today\",\n\"write a status update for the team\", or at the end of a session on projects\nthat run daily standups.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add projectious-work\u002Fprocesskit --skill standup-context",{"tool":81,"command":82},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill standup-context",{"tool":84,"command":85},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill standup-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002FSKILL.md",true,[89,95],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"commands\u002Fpk-standup.md","REFERENCE","参考文档",363,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002Fcommands\u002Fpk-standup.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"commands\u002Fpk-status.md",416,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002Fcommands\u002Fpk-status.md",[100,107,114,120,146,166],{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":106},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":106},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":106},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":39},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[132,133,134,135,136,137,33,138,139,140,36,141,122,142,143,144,145],"management","skill management","ontology","v1","create","as","transition","get","manage","alpha","list","package","skill package","manifests",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":39},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[152],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[154,155,132,156,157,158,159,160,161,162,163,164,33,139,140,141,165],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":39},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[173,132,174,175,136,176,177,178,33,139,179,180,36,181,141,182,183,30,184,22],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","facts"]