[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X53P2YCVGFMQDM8REGDG00":3,"skill-same:01M6X53P2YCVGFMQDM8REGDG00":88},{"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":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6X53P2YCVGFMQDM8REGDG00","schedule-management",null,"Manage Schedule entities — time-based triggers and recurring cadences (daily standup, weekly review, monthly retro). Use when defining a recurring cadence — daily\u002Fweekly\u002Fmonthly — that triggers a process or reminder.","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.8.0\u002Fcontext\u002Fskills\u002Fschedule-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"schedule management","schedule","management","time","when","weekly","v1","reminder","event","keep","cadence","triggers","review","manage","log","daily","use","recurring","daily standup","standup","2026-11-10 10:12:30",false,"---\nname: schedule-management\ndescription: |\n  Manage Schedule entities — time-based triggers and recurring cadences (daily standup, weekly review, monthly retro). Use when defining a recurring cadence — daily\u002Fweekly\u002Fmonthly — that triggers a process or reminder.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv1\n    id: SKILL-schedule-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: process\n    layer: 3\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n    provides:\n      primitives: [Schedule]\n      templates: [schedule]\n---\n\n# Schedule Management\n\n## Intro\n\nA Schedule is a time-based trigger describing when a process should run or\na reminder should fire — daily standups, weekly retros, monthly ops reviews,\nquarterly planning.\n\n## Overview\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: Schedule\nmetadata:\n  id: SCHED-daily-standup\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: daily-standup\n  description: \"Daily async standup at 09:00 local time.\"\n  cadence: daily\n  cron: \"0 9 * * 1-5\"\n  timezone: Europe\u002FBerlin\n  triggers:\n    - process: standup\n  active: true\n---\n```\n\n### Workflow\n\n1. Pick `SCHED-\u003Cname>`.\n2. Set a human `cadence` (`daily`\u002F`weekly`\u002F`monthly`\u002F`quarterly`\u002F`adhoc`\u002F`custom`).\n3. For machine-readable scheduling, set `cron` + `timezone`.\n4. Link what it `triggers` — a process name, a reminder text, etc.\n5. Use Bindings to scope a schedule to a specific team or project.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Schedule without timezone.** \"Daily at 9am\" is meaningless\n  across DST boundaries and timezone-distributed teams. Always\n  specify the timezone explicitly (`UTC`, `Europe\u002FBerlin`, etc.).\n  Schedules without timezone drift twice a year.\n- **Recurring schedule without an end date or `until`.** Some\n  schedules genuinely run forever; others should end with the\n  project, the quarter, or the team member's tenure. Make the\n  termination condition explicit, even if it's \"indefinite\" — the\n  decision to make it indefinite is itself a decision worth\n  recording.\n- **Forgetting to handle missed runs.** What happens if the\n  schedule fires but the action fails? Does it retry? Skip? Page\n  oncall? A Schedule without a missed-run policy silently\n  accumulates errors.\n- **Schedule fires without an action target.** A Schedule must\n  point at a Process, WorkItem template, or other actionable\n  artifact. \"Trigger something at 9am\" with no target is a\n  reminder, not a Schedule.\n- **Confusing schedule definition vs schedule execution.** The\n  Schedule entity defines WHEN something fires; the actual fire\n  events should be LogEntries (`schedule.fired`). Don't put\n  execution history in the Schedule entity itself.\n- **Hand-rolled cron expressions instead of using the schema.**\n  Cron strings are infamous for off-by-one errors (every 5\n  minutes vs every minute past the 5th). Use the schema's\n  structured fields (interval, days, hours) when possible;\n  reserve cron strings for cases the schema can't express.\n- **Schedule that overlaps with another.** \"Daily standup at 9am\"\n  and \"weekly review at 9am Monday\" both fire at 9am Monday. Be\n  explicit about precedence — does one preempt the other, do\n  both run, or does the agent skip one?\n\n## Full reference\n\n### Fields\n\n| Field       | Type         | Notes                                              |\n|-------------|--------------|----------------------------------------------------|\n| `name`      | string       | Kebab-case identifier                              |\n| `description` | string     | Human-readable                                     |\n| `cadence`   | enum         | `daily`\u002F`weekly`\u002F`monthly`\u002F`quarterly`\u002F`adhoc`\u002F`custom` |\n| `cron`      | string       | Standard cron expression                           |\n| `timezone`  | string       | IANA timezone name                                 |\n| `triggers`  | list[object] | What fires: processes, reminders, events           |\n| `active`    | bool         | `false` = suspended                                |\n| `last_run`  | datetime     | Advisory — set by whoever runs the schedule        |\n| `next_run`  | datetime     | Advisory                                           |\n\n### Execution\n\nprocesskit does NOT execute schedules. It describes them. An external\nrunner (GitHub Actions, cron, a human, an agent on a loop) reads the\nSchedule and fires the trigger at the right time. The `triggers` field is\nthe contract between the Schedule definition and whoever runs it.\n\n### Scoped schedules\n\nA daily standup runs in one scope, not globally. Use a Binding:\n\n```yaml\nkind: Binding\nspec:\n  type: schedule-scope\n  subject: SCHED-daily-standup\n  target: SCOPE-project-x\n```\n\nThen the runner fetches all schedules bound to the scope it's acting on.\n","# Schedule Management\n\n## Intro\n\nA Schedule is a time-based trigger describing when a process should run or\na reminder should fire — daily standups, weekly retros, monthly ops reviews,\nquarterly planning.\n\n## Overview\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: Schedule\nmetadata:\n  id: SCHED-daily-standup\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: daily-standup\n  description: \"Daily async standup at 09:00 local time.\"\n  cadence: daily\n  cron: \"0 9 * * 1-5\"\n  timezone: Europe\u002FBerlin\n  triggers:\n    - process: standup\n  active: true\n---\n```\n\n### Workflow\n\n1. Pick `SCHED-\u003Cname>`.\n2. Set a human `cadence` (`daily`\u002F`weekly`\u002F`monthly`\u002F`quarterly`\u002F`adhoc`\u002F`custom`).\n3. For machine-readable scheduling, set `cron` + `timezone`.\n4. Link what it `triggers` — a process name, a reminder text, etc.\n5. Use Bindings to scope a schedule to a specific team or project.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Schedule without timezone.** \"Daily at 9am\" is meaningless\n  across DST boundaries and timezone-distributed teams. Always\n  specify the timezone explicitly (`UTC`, `Europe\u002FBerlin`, etc.).\n  Schedules without timezone drift twice a year.\n- **Recurring schedule without an end date or `until`.** Some\n  schedules genuinely run forever; others should end with the\n  project, the quarter, or the team member's tenure. Make the\n  termination condition explicit, even if it's \"indefinite\" — the\n  decision to make it indefinite is itself a decision worth\n  recording.\n- **Forgetting to handle missed runs.** What happens if the\n  schedule fires but the action fails? Does it retry? Skip? Page\n  oncall? A Schedule without a missed-run policy silently\n  accumulates errors.\n- **Schedule fires without an action target.** A Schedule must\n  point at a Process, WorkItem template, or other actionable\n  artifact. \"Trigger something at 9am\" with no target is a\n  reminder, not a Schedule.\n- **Confusing schedule definition vs schedule execution.** The\n  Schedule entity defines WHEN something fires; the actual fire\n  events should be LogEntries (`schedule.fired`). Don't put\n  execution history in the Schedule entity itself.\n- **Hand-rolled cron expressions instead of using the schema.**\n  Cron strings are infamous for off-by-one errors (every 5\n  minutes vs every minute past the 5th). Use the schema's\n  structured fields (interval, days, hours) when possible;\n  reserve cron strings for cases the schema can't express.\n- **Schedule that overlaps with another.** \"Daily standup at 9am\"\n  and \"weekly review at 9am Monday\" both fire at 9am Monday. Be\n  explicit about precedence — does one preempt the other, do\n  both run, or does the agent skip one?\n\n## Full reference\n\n### Fields\n\n| Field       | Type         | Notes                                              |\n|-------------|--------------|----------------------------------------------------|\n| `name`      | string       | Kebab-case identifier                              |\n| `description` | string     | Human-readable                                     |\n| `cadence`   | enum         | `daily`\u002F`weekly`\u002F`monthly`\u002F`quarterly`\u002F`adhoc`\u002F`custom` |\n| `cron`      | string       | Standard cron expression                           |\n| `timezone`  | string       | IANA timezone name                                 |\n| `triggers`  | list[object] | What fires: processes, reminders, events           |\n| `active`    | bool         | `false` = suspended                                |\n| `last_run`  | datetime     | Advisory — set by whoever runs the schedule        |\n| `next_run`  | datetime     | Advisory                                           |\n\n### Execution\n\nprocesskit does NOT execute schedules. It describes them. An external\nrunner (GitHub Actions, cron, a human, an agent on a loop) reads the\nSchedule and fires the trigger at the right time. The `triggers` field is\nthe contract between the Schedule definition and whoever runs it.\n\n### Scoped schedules\n\nA daily standup runs in one scope, not globally. Use a Binding:\n\n```yaml\nkind: Binding\nspec:\n  type: schedule-scope\n  subject: SCHED-daily-standup\n  target: SCOPE-project-x\n```\n\nThen the runner fetches all schedules bound to the scope it's acting on.\n",{"name":5,"metadata":44,"description":60},{"processkit":45},{"id":46,"uses":47,"layer":51,"created":52,"version":53,"category":54,"provides":55,"apiVersion":59},"SKILL-schedule-management",[48],{"skill":49,"purpose":50},"event-log","Log events to keep the audit trail accurate after every write.",3,1775433600000,"1.0.0","process",{"templates":56,"primitives":57},[20],[58],"Schedule","processkit.projectious.work\u002Fv1","Manage Schedule entities — time-based triggers and recurring cadences (daily standup, weekly review, monthly retro). Use when defining a recurring cadence — daily\u002Fweekly\u002Fmonthly — that triggers a process or reminder.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.8.0\u002Fcontext\u002Fskills\u002Fschedule-management","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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add projectious-work\u002Fprocesskit --skill schedule-management",{"tool":74,"command":75},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill schedule-management",{"tool":77,"command":78},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill schedule-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.8.0\u002Fcontext\u002Fskills\u002Fschedule-management\u002FSKILL.md",true,[82],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fschedule.yaml","ASSET","资产文件",352,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.8.0\u002Fcontext\u002Fskills\u002Fschedule-management\u002Fassets\u002Fschedule.yaml",[89,96,103,109,134,154],{"skillNo":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":95},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":95},"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":104,"name":105,"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":106,"categories":107,"keywords":108,"publishedAt":95},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[21,121,122,25,123,124,125,126,127,32,128,129,111,130,131,132,133],"skill management","ontology","create","as","work","transition","get","update","alpha","list","package","skill package","manifests",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"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",[140],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[142,143,21,144,145,146,147,148,149,150,151,152,125,127,32,129,153],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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",[],[161,21,162,163,123,164,165,166,125,127,167,27,128,168,129,169,170,171,172,33],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","query","facts"]