[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WXYCS5Y67RE7XQ2EBWTQZX":3,"skill-same:01M6WXYCS5Y67RE7XQ2EBWTQZX":92},{"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":65,"commitSha":66,"skillDirectory":67,"forksCount":14,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":71,"install":72,"resources":85},"01M6WXYCS5Y67RE7XQ2EBWTQZX","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\u002Ftemplates\u002Fprocesskit\u002Fv0.11.1\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","when","workitem","at","progress","end","next","done","query","log","write","work","projects","team","update","run","generate","status","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\u002Fv1\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: standup-context-write\n        args: \"\"\n        description: \"Generate a standup update (done \u002F doing \u002F next \u002F blockers)\"\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 `morning-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\u002Fv1\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\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.\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 `\u002Fstandup-context-write` slash command for direct invocation — see `commands\u002Fstandup-context-write.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- **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`morning-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 `morning-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\u002Fv1\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\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.\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 `\u002Fstandup-context-write` slash command for direct invocation — see `commands\u002Fstandup-context-write.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- **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`morning-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":64},{"processkit":45},{"id":46,"uses":47,"layer":54,"created":55,"version":56,"category":57,"commands":58,"apiVersion":63},"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],{"args":60,"name":61,"description":62},"","standup-context-write","Generate a standup update (done \u002F doing \u002F next \u002F blockers)","processkit.projectious.work\u002Fv1","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\u002Ftemplates\u002Fprocesskit\u002Fv0.11.1\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-09 00:53:29",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add projectious-work\u002Fprocesskit --skill standup-context",{"tool":78,"command":79},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill standup-context",{"tool":81,"command":82},"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\u002Ftemplates\u002Fprocesskit\u002Fv0.11.1\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"commands\u002Fstandup-context-write.md","REFERENCE","参考文档",115,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.11.1\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fstandup-context\u002Fcommands\u002Fstandup-context-write.md",[93,119,139,158,175,193],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":104,"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",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[105,106,107,35,108,109,32,110,111,112,95,113,114,115,116,117,118],"management","skill management","create","package","alpha","list","manage","ontology","get","as","manifests","v1","skill package","transition",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"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",[125],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[105,127,128,129,130,131,109,32,132,133,111,134,135,136,113,137,138],"schema","schema management","MCP","workflows","validation","generated","rebuild","contracts","wed","deterministic","contract","mode",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"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",[],[105,146,147,107,35,148,109,32,30,149,150,29,113,151,152,153,154,155,156,157],"proposition","proposition management","index","world","record","creation","event","interface","updates","facts","claims","WSJF",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"01M6X5KMQ83QN9M6MPWZM7344F","ontology-management","Manage generated v1 ontology entities that do not require a dedicated domain server.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fontology-management\u002FSKILL.md",[],[105,112,165,107,109,166,167,132,168,30,111,169,170,113,171,172,152,173,116,174],"ontology management","lifecycle","archive","roadmap","do","domain","iteration","keep","measurement","generic",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":39},"01M6X5KCY2DN3SM21RERSFNEBT","okf-compatibility","Import, export, and validate conformant Open Knowledge Format bundles.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fokf-compatibility\u002FSKILL.md",[],[182,183,184,185,109,186,187,188,32,189,190,191,192],"okf","compatibility","okf compatibility","validate","open","knowledge","format","export","bundles","bundle","import",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":39},"01M6X5JA8S5PNGJVFW4EQY8T83","capability-management","Manage versioned Capability entities and their governed lifecycle.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcapability-management\u002FSKILL.md",[],[105,200,201,107,35,148,109,166,32,110,30,202,111,150,113,172,152,153,203,118],"capability","capability management","queries","changes"]