[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPPK47P6WWQEC2M1WXSFAR":3,"skill-same:01M6NPPK47P6WWQEC2M1WXSFAR":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6NPPK47P6WWQEC2M1WXSFAR","postmortem-writing",null,"Blameless postmortem writing — timeline, root cause analysis, corrective actions. Use when writing an incident postmortem, conducting a post-incident review, building a postmortem template, or coaching a team toward blameless culture.","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\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fpostmortem-writing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"writing","postmortem writing","postmortem","root","post","coaching","incident","culture","devops","use","work","template","team","analysis","timeline","post-incident","incident postmortem","actions","root cause analysis","review","2026-11-10 10:12:30",false,"---\nname: postmortem-writing\ndescription: |\n  Blameless postmortem writing — timeline, root cause analysis, corrective actions. Use when writing an incident postmortem, conducting a post-incident review, building a postmortem template, or coaching a team toward blameless culture.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-postmortem-writing\n    version: \"1.1.0\"\n    created: 2026-04-06T00:00:00Z\n    category: devops\n    layer: 3\n---\n\n# Postmortem Writing\n\n## Intro\n\nA good postmortem is a learning artifact, not a punishment. It tells\nthe story of an incident factually, traces the root cause to a\nsystemic gap (not a person), and produces a small number of owned,\ntime-bound corrective actions.\n\n## Overview\n\n### Standard structure\n\nEvery postmortem should include, in order: title and metadata,\nsummary, impact, timeline, root cause analysis, contributing\nfactors, what went well, corrective actions, and lessons learned.\nThe order matters — facts first, analysis second, actions last.\n\n### Writing the timeline\n\nUse UTC timestamps. Format each line as\n`HH:MM UTC — Event description (who\u002Fwhat)`. Include first alert,\nescalation points, key diagnostic steps, mitigations applied, and\nfull resolution. Separate detection time (first signal) from response\ntime (first human action) and call out delays explicitly. The\ntimeline is factual, not interpretive — analysis goes in the root\ncause section.\n\n### Root cause analysis with 5 Whys\n\nStart with the observable failure and ask \"why?\" iteratively. Stop\nwhen you reach a systemic or process issue, not a human mistake. If\nthe chain branches, document all branches. Example:\n\n- Why did the site go down? The database ran out of connections.\n- Why? A query held connections open for 30+ seconds.\n- Why? It was doing a full table scan on a 50M row table.\n- Why no index? The migration that added the column did not include\n  one.\n- Why was that not caught? There is no review step for migration\n  performance impact.\n\nThe root cause is \"no migration performance review\", not \"Alice\nwrote a slow migration.\"\n\n### Corrective actions\n\nEach action must be specific, owned, and have a due date. Categorize\nas **prevent** (stop it from happening), **detect** (catch it\nfaster), or **mitigate** (reduce impact). Format:\n`[P\u002FD\u002FM] Action — @owner — due YYYY-MM-DD`. Cap at 5–8 actions; more\nmeans none get done. Aim for at least one action per category. Track\ncompletion in the team's issue tracker, not just the document.\n\n### Blameless culture\n\nFocus on systems and processes, not individuals. Use passive voice\nfor human errors (\"the config was deployed without review\", not\n\"Alice deployed without review\"). Ask \"what about our system made\nthis mistake easy to make?\" Assume everyone acted with the best\ninformation available at the time. If anyone feels blamed, the\npostmortem has failed regardless of wording.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Action item bloat.** Twenty action items with no owners mean none get done. Cap at 5–8 actions, assign a named owner and a due date to each, and track them in the team's issue tracker rather than only in the document.\n- **Stopping the 5 Whys at the symptom level.** \"The query was slow\" is a symptom, not a root cause. Keep asking why until you reach a systemic gap: \"no migration performance review step existed.\" The root cause must be something the team can change.\n- **Blame disguised as systems language.** \"The team should have noticed\" is still blame. Rewrite as \"no automated check existed for this pattern.\" If the postmortem names individuals in the cause chain rather than systemic gaps, the culture will drift away from blamelessness.\n- **Postmortem written but never referenced.** A document filed and forgotten produces no learning. Link every corrective action to a tracked ticket; schedule a follow-up review at 30 days to check completion.\n- **Scheduling the review too late.** Memories of the incident fade rapidly. Schedule the review within 3–5 business days. Waiting for a \"convenient time\" usually means the review happens weeks later, if at all.\n- **Author and facilitator being the same person.** The author is defensive about the incident they were in; the facilitator needs to be neutral. Separate the roles even on small teams.\n- **All actions in one category.** A postmortem that produces only \"Prevent\" actions has no \"Detect\" or \"Mitigate\" items, which means the next similar incident will still take too long to detect and contain. Aim for at least one action per category.\n\n## Full reference\n\n### Facilitation tips\n\n- Schedule the review within 3–5 business days of the incident;\n  memories fade fast.\n- Invite all responders plus 1–2 people who were not involved for\n  fresh perspective.\n- Time-box to 60 minutes: 10 min timeline walk-through, 20 min root\n  cause, 20 min actions, 10 min wrap-up.\n- The facilitator should not be the author — separating the roles\n  reduces defensiveness.\n- Start by reading the timeline aloud as a group to establish a\n  shared factual baseline.\n- End with: \"What is the single most important thing we should\n  change?\"\n\n### Template\n\n```markdown\n# Postmortem: [Incident Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV-1 \u002F SEV-2 \u002F SEV-3\n**Duration:** HH:MM (from detection to resolution)\n**Author:** [Name]\n**Reviewers:** [Names]\n\n## Summary\n[2-3 sentences: what happened, impact, resolution]\n\n## Impact\n- Users affected: [number or percentage]\n- Duration of user impact: [time]\n- Revenue impact: [estimate if applicable]\n- SLA budget consumed: [percentage]\n\n## Timeline (UTC)\n- HH:MM — [First signal \u002F alert fired]\n- HH:MM — [Escalation \u002F response began]\n- HH:MM — [Key diagnostic finding]\n- HH:MM — [Mitigation applied]\n- HH:MM — [Full resolution confirmed]\n\n## Root Cause Analysis\n### 5 Whys\n1. Why? ...\n2. Why? ...\n3. Why? ...\n4. Why? ...\n5. Why? ...\n\n## Contributing Factors\n- [Factor that made it worse or delayed resolution]\n\n## What Went Well\n- [Thing that worked during response]\n\n## Corrective Actions\n| Type | Action | Owner | Due Date | Status |\n|------|--------|-------|----------|--------|\n| Prevent | [Action] | @name | YYYY-MM-DD | Open |\n| Detect | [Action] | @name | YYYY-MM-DD | Open |\n| Mitigate | [Action] | @name | YYYY-MM-DD | Open |\n\n## Lessons Learned\n- [Key takeaway]\n```\n\n### Common failure modes\n\n- **Action item bloat.** Twenty actions, none done. Cut to the top\n  five and defer the rest with explicit justification.\n- **Symptom-level root cause.** Stopping at \"the query was slow\"\n  instead of asking why the slow query reached production.\n- **Blame disguised as systems language.** \"The team should have\n  noticed\" is still blame. Rewrite as \"no automated check existed\n  for X.\"\n- **Postmortem as archive.** A document that is written, filed, and\n  never referenced. Link corrective actions out to tickets and\n  schedule a follow-up review.\n","# Postmortem Writing\n\n## Intro\n\nA good postmortem is a learning artifact, not a punishment. It tells\nthe story of an incident factually, traces the root cause to a\nsystemic gap (not a person), and produces a small number of owned,\ntime-bound corrective actions.\n\n## Overview\n\n### Standard structure\n\nEvery postmortem should include, in order: title and metadata,\nsummary, impact, timeline, root cause analysis, contributing\nfactors, what went well, corrective actions, and lessons learned.\nThe order matters — facts first, analysis second, actions last.\n\n### Writing the timeline\n\nUse UTC timestamps. Format each line as\n`HH:MM UTC — Event description (who\u002Fwhat)`. Include first alert,\nescalation points, key diagnostic steps, mitigations applied, and\nfull resolution. Separate detection time (first signal) from response\ntime (first human action) and call out delays explicitly. The\ntimeline is factual, not interpretive — analysis goes in the root\ncause section.\n\n### Root cause analysis with 5 Whys\n\nStart with the observable failure and ask \"why?\" iteratively. Stop\nwhen you reach a systemic or process issue, not a human mistake. If\nthe chain branches, document all branches. Example:\n\n- Why did the site go down? The database ran out of connections.\n- Why? A query held connections open for 30+ seconds.\n- Why? It was doing a full table scan on a 50M row table.\n- Why no index? The migration that added the column did not include\n  one.\n- Why was that not caught? There is no review step for migration\n  performance impact.\n\nThe root cause is \"no migration performance review\", not \"Alice\nwrote a slow migration.\"\n\n### Corrective actions\n\nEach action must be specific, owned, and have a due date. Categorize\nas **prevent** (stop it from happening), **detect** (catch it\nfaster), or **mitigate** (reduce impact). Format:\n`[P\u002FD\u002FM] Action — @owner — due YYYY-MM-DD`. Cap at 5–8 actions; more\nmeans none get done. Aim for at least one action per category. Track\ncompletion in the team's issue tracker, not just the document.\n\n### Blameless culture\n\nFocus on systems and processes, not individuals. Use passive voice\nfor human errors (\"the config was deployed without review\", not\n\"Alice deployed without review\"). Ask \"what about our system made\nthis mistake easy to make?\" Assume everyone acted with the best\ninformation available at the time. If anyone feels blamed, the\npostmortem has failed regardless of wording.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Action item bloat.** Twenty action items with no owners mean none get done. Cap at 5–8 actions, assign a named owner and a due date to each, and track them in the team's issue tracker rather than only in the document.\n- **Stopping the 5 Whys at the symptom level.** \"The query was slow\" is a symptom, not a root cause. Keep asking why until you reach a systemic gap: \"no migration performance review step existed.\" The root cause must be something the team can change.\n- **Blame disguised as systems language.** \"The team should have noticed\" is still blame. Rewrite as \"no automated check existed for this pattern.\" If the postmortem names individuals in the cause chain rather than systemic gaps, the culture will drift away from blamelessness.\n- **Postmortem written but never referenced.** A document filed and forgotten produces no learning. Link every corrective action to a tracked ticket; schedule a follow-up review at 30 days to check completion.\n- **Scheduling the review too late.** Memories of the incident fade rapidly. Schedule the review within 3–5 business days. Waiting for a \"convenient time\" usually means the review happens weeks later, if at all.\n- **Author and facilitator being the same person.** The author is defensive about the incident they were in; the facilitator needs to be neutral. Separate the roles even on small teams.\n- **All actions in one category.** A postmortem that produces only \"Prevent\" actions has no \"Detect\" or \"Mitigate\" items, which means the next similar incident will still take too long to detect and contain. Aim for at least one action per category.\n\n## Full reference\n\n### Facilitation tips\n\n- Schedule the review within 3–5 business days of the incident;\n  memories fade fast.\n- Invite all responders plus 1–2 people who were not involved for\n  fresh perspective.\n- Time-box to 60 minutes: 10 min timeline walk-through, 20 min root\n  cause, 20 min actions, 10 min wrap-up.\n- The facilitator should not be the author — separating the roles\n  reduces defensiveness.\n- Start by reading the timeline aloud as a group to establish a\n  shared factual baseline.\n- End with: \"What is the single most important thing we should\n  change?\"\n\n### Template\n\n```markdown\n# Postmortem: [Incident Title]\n\n**Date:** YYYY-MM-DD\n**Severity:** SEV-1 \u002F SEV-2 \u002F SEV-3\n**Duration:** HH:MM (from detection to resolution)\n**Author:** [Name]\n**Reviewers:** [Names]\n\n## Summary\n[2-3 sentences: what happened, impact, resolution]\n\n## Impact\n- Users affected: [number or percentage]\n- Duration of user impact: [time]\n- Revenue impact: [estimate if applicable]\n- SLA budget consumed: [percentage]\n\n## Timeline (UTC)\n- HH:MM — [First signal \u002F alert fired]\n- HH:MM — [Escalation \u002F response began]\n- HH:MM — [Key diagnostic finding]\n- HH:MM — [Mitigation applied]\n- HH:MM — [Full resolution confirmed]\n\n## Root Cause Analysis\n### 5 Whys\n1. Why? ...\n2. Why? ...\n3. Why? ...\n4. Why? ...\n5. Why? ...\n\n## Contributing Factors\n- [Factor that made it worse or delayed resolution]\n\n## What Went Well\n- [Thing that worked during response]\n\n## Corrective Actions\n| Type | Action | Owner | Due Date | Status |\n|------|--------|-------|----------|--------|\n| Prevent | [Action] | @name | YYYY-MM-DD | Open |\n| Detect | [Action] | @name | YYYY-MM-DD | Open |\n| Mitigate | [Action] | @name | YYYY-MM-DD | Open |\n\n## Lessons Learned\n- [Key takeaway]\n```\n\n### Common failure modes\n\n- **Action item bloat.** Twenty actions, none done. Cut to the top\n  five and defer the rest with explicit justification.\n- **Symptom-level root cause.** Stopping at \"the query was slow\"\n  instead of asking why the slow query reached production.\n- **Blame disguised as systems language.** \"The team should have\n  noticed\" is still blame. Rewrite as \"no automated check existed\n  for X.\"\n- **Postmortem as archive.** A document that is written, filed, and\n  never referenced. Link corrective actions out to tickets and\n  schedule a follow-up review.\n",{"name":5,"metadata":54,"description":61},{"processkit":55},{"id":56,"layer":57,"created":58,"version":59,"category":37,"apiVersion":60},"SKILL-postmortem-writing",3,1775433600000,"1.1.0","processkit.projectious.work\u002Fv2","Blameless postmortem writing — timeline, root cause analysis, corrective actions. Use when writing an incident postmortem, conducting a post-incident review, building a postmortem template, or coaching a team toward blameless culture.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fdevops\u002Fpostmortem-writing","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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add projectious-work\u002Fprocesskit --skill postmortem-writing",{"tool":75,"command":76},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill postmortem-writing",{"tool":78,"command":79},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill postmortem-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fpostmortem-writing\u002FSKILL.md",true,[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":14,"sourceHtmlUrl":87},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fpostmortem-writing\u002Fscripts\u002F.gitkeep",[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":118,"publishedAt":49},"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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[119,120,121,122,123,124,39,125,126,127,128,129,111,130,131,132,133],"management","skill management","ontology","v1","create","as","transition","get","manage","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":49},"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":21,"taxonomyTypeDesc":22},[142,143,119,144,145,146,147,148,149,150,151,152,39,126,127,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":49},"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,119,162,163,123,164,165,166,39,126,167,168,128,169,129,170,171,172,173,174],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]