[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N8785AP0XC3KSZF8DAM2K8":3,"skill-same:01M6N8785AP0XC3KSZF8DAM2K8":62},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":22,"linkOnly":23,"markdownContent":24,"markdownBody":25,"frontMatter":26,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M6N8785AP0XC3KSZF8DAM2K8","mh-cto-sdlc-hypercare",null,"Imad-Oute\u002FMicroHard","Imad-Oute","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F139675528?v=4","01M6N68WHDQ53HQJQ5Y84AGMWX","imad outemgount","01M6N68WP1YPV15H5RTGQHM02G",2,"MIT","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcto\u002Fsdlc\u002Fphase-7-launch\u002Fmh-cto-sdlc-hypercare\u002FSKILL.md",[],[18,19,20,21],"sdlc","hypercare","cto","mh cto sdlc hypercare","2026-11-10 10:12:30",false,"---\nname: mh-cto-sdlc-hypercare\ndescription: Hypercare — manages the elevated monitoring period (24-72h) immediately after launch. All defects are P1 regardless of severity. Structured monitoring cadence, rapid response posture, defect triage, and hypercare closure when stability is confirmed. Trigger phrases: \"hypercare\", \"post-launch monitoring\", \"launch monitoring\", \"day after launch\", \"post-launch\", \"launch stability\", \"hypercare period\".\nmetadata:\n  author: MicroHard\n  version: 1.0.0\n  phase: 7-launch\n  module: cto-sdlc\n---\n\n# Hypercare\n\n**Hypercare is elevated, not paranoid.** The first 24-72 hours post-launch are the highest-risk operational window because: traffic patterns are new, edge cases that testing missed are found by real users, and configuration surprises surface under real load. Elevated readiness means: shorter monitoring intervals, faster defect response, and lower severity threshold for action.\n\n**Elite character:** Hypercare ends when stability is demonstrated — not when a timer expires. A product that is crashing on Day 3 is not out of hypercare just because it is Day 3.\n\n## Step 1 — Load Go-Live Context\n\nRead `_mh-output\u002Fcto\u002Fsdlc\u002Fgo-live\u002F{latest}_go-live-log.md`.\n\nConfirm: product launched (not rolled back). If rolled back: \"Go-live was rolled back. Hypercare only applies to a live system. Resolve the rollback cause, re-run `\u002Fmh-cto-sdlc-go-live`, then begin hypercare.\"\n\nEstablish hypercare window:\n\n- **Standard:** 48 hours from T+0\n- **Extended (use if):** Any incident in first 24h, any rollback condition that was narrowly avoided, any P0 path not fully verified at gate\n\n## Step 2 — Monitoring Cadence\n\nDuring hypercare, monitor at elevated frequency:\n\n| Window         | Frequency        | Metrics to Check                                           |\n| -------------- | ---------------- | ---------------------------------------------------------- |\n| T+0 to T+4h    | Every 30 minutes | Error rate, P95 latency, active users, anomalous logs      |\n| T+4h to T+24h  | Every 2 hours    | Same + memory growth, DB connection pool, queue depth      |\n| T+24h to T+48h | Every 4 hours    | Same + performance regression check vs pre-launch baseline |\n\nFor each monitoring check, record:\n\n```\n{timestamp} — Error rate: {N}% | P95: {N}ms | Users: {N} | Anomalies: {none \u002F description}\n```\n\n## Step 3 — Defect Triage Protocol\n\nDuring hypercare, ALL defects are treated as P1 regardless of severity:\n\n- A cosmetic bug discovered during hypercare gets the same immediate triage as a data bug\n- Triage does not mean fix — it means classify, assess impact, and decide on response\n\nFor each defect found:\n\n| ID    | Description   | User Impact                | Response                                     | Status            |\n| ----- | ------------- | -------------------------- | -------------------------------------------- | ----------------- |\n| D-001 | {description} | {None \u002F Degraded \u002F Broken} | {Fix + deploy \u002F Hotfix \u002F Rollback \u002F Monitor} | {Open \u002F Resolved} |\n\n**Response options:**\n\n- **Fix + deploy:** Low-risk change, CI\u002FCD gate passes, deploy normally\n- **Hotfix:** High-impact defect, expedited review, deploy outside normal cycle\n- **Rollback:** User-impacting defect with no quick fix — rollback to previous version\n- **Monitor:** Low user impact, no immediate fix, monitor for worsening\n\n## Step 4 — Hypercare Closure Criteria\n\nHypercare closes when ALL of the following are true:\n\n- [ ] No P0\u002FP1 defects open for more than 2 hours without a resolution plan\n- [ ] Error rate has been within baseline for 12 consecutive hours\n- [ ] P95 latency has been within baseline for 12 consecutive hours\n- [ ] No new defect categories discovered in the last 24 hours\n- [ ] No open rollback risk (no defect that, if it worsens, would require rollback)\n\nIf hypercare window expires (48h) but closure criteria are not met: extend hypercare and document the reason.\n\n## Step 5 — Write Hypercare Log\n\nSave to `_mh-output\u002Fcto\u002Fsdlc\u002Fhypercare\u002F{YYYY-MM-DD}_{r###}_hypercare-log.md`:\n\n```markdown\n# Hypercare Log\n\n**Product:** {name}\n**Launch date:** {date}\n**Hypercare window:** {start} to {end}\n**Outcome:** STABLE — hypercare closed \u002F EXTENDED — reason: {reason}\n\n---\n\n## Monitoring Log\n\n{Timestamped entries from Step 2}\n\n## Defects Discovered\n\n{Table from Step 3 — or \"None\"}\n\n## Closure Assessment\n\n{Checklist from Step 4 with each item verified or flagged}\n\n## Lessons for Phase 8\n\n{Any patterns from defects or monitoring that should feed the Phase 8 retrospectives}\n```\n\n## Step 6 — Present Summary\n\n**Hypercare: {CLOSED (stable) \u002F EXTENDED}**\n\n**Duration:** {N} hours.\n\n**Defects found:** {N} — {N} resolved, {N} open with mitigation.\n\n**Stability confirmed:** Error rate and latency within baseline for {N}h.\n\n**Lessons for Phase 8:** {N} items captured.\n\n**Next step:** Run `\u002Fmh-cto-sdlc-outcome-measure` to begin Phase 8 Validation & Evolution.\n","# Hypercare\n\n**Hypercare is elevated, not paranoid.** The first 24-72 hours post-launch are the highest-risk operational window because: traffic patterns are new, edge cases that testing missed are found by real users, and configuration surprises surface under real load. Elevated readiness means: shorter monitoring intervals, faster defect response, and lower severity threshold for action.\n\n**Elite character:** Hypercare ends when stability is demonstrated — not when a timer expires. A product that is crashing on Day 3 is not out of hypercare just because it is Day 3.\n\n## Step 1 — Load Go-Live Context\n\nRead `_mh-output\u002Fcto\u002Fsdlc\u002Fgo-live\u002F{latest}_go-live-log.md`.\n\nConfirm: product launched (not rolled back). If rolled back: \"Go-live was rolled back. Hypercare only applies to a live system. Resolve the rollback cause, re-run `\u002Fmh-cto-sdlc-go-live`, then begin hypercare.\"\n\nEstablish hypercare window:\n\n- **Standard:** 48 hours from T+0\n- **Extended (use if):** Any incident in first 24h, any rollback condition that was narrowly avoided, any P0 path not fully verified at gate\n\n## Step 2 — Monitoring Cadence\n\nDuring hypercare, monitor at elevated frequency:\n\n| Window         | Frequency        | Metrics to Check                                           |\n| -------------- | ---------------- | ---------------------------------------------------------- |\n| T+0 to T+4h    | Every 30 minutes | Error rate, P95 latency, active users, anomalous logs      |\n| T+4h to T+24h  | Every 2 hours    | Same + memory growth, DB connection pool, queue depth      |\n| T+24h to T+48h | Every 4 hours    | Same + performance regression check vs pre-launch baseline |\n\nFor each monitoring check, record:\n\n```\n{timestamp} — Error rate: {N}% | P95: {N}ms | Users: {N} | Anomalies: {none \u002F description}\n```\n\n## Step 3 — Defect Triage Protocol\n\nDuring hypercare, ALL defects are treated as P1 regardless of severity:\n\n- A cosmetic bug discovered during hypercare gets the same immediate triage as a data bug\n- Triage does not mean fix — it means classify, assess impact, and decide on response\n\nFor each defect found:\n\n| ID    | Description   | User Impact                | Response                                     | Status            |\n| ----- | ------------- | -------------------------- | -------------------------------------------- | ----------------- |\n| D-001 | {description} | {None \u002F Degraded \u002F Broken} | {Fix + deploy \u002F Hotfix \u002F Rollback \u002F Monitor} | {Open \u002F Resolved} |\n\n**Response options:**\n\n- **Fix + deploy:** Low-risk change, CI\u002FCD gate passes, deploy normally\n- **Hotfix:** High-impact defect, expedited review, deploy outside normal cycle\n- **Rollback:** User-impacting defect with no quick fix — rollback to previous version\n- **Monitor:** Low user impact, no immediate fix, monitor for worsening\n\n## Step 4 — Hypercare Closure Criteria\n\nHypercare closes when ALL of the following are true:\n\n- [ ] No P0\u002FP1 defects open for more than 2 hours without a resolution plan\n- [ ] Error rate has been within baseline for 12 consecutive hours\n- [ ] P95 latency has been within baseline for 12 consecutive hours\n- [ ] No new defect categories discovered in the last 24 hours\n- [ ] No open rollback risk (no defect that, if it worsens, would require rollback)\n\nIf hypercare window expires (48h) but closure criteria are not met: extend hypercare and document the reason.\n\n## Step 5 — Write Hypercare Log\n\nSave to `_mh-output\u002Fcto\u002Fsdlc\u002Fhypercare\u002F{YYYY-MM-DD}_{r###}_hypercare-log.md`:\n\n```markdown\n# Hypercare Log\n\n**Product:** {name}\n**Launch date:** {date}\n**Hypercare window:** {start} to {end}\n**Outcome:** STABLE — hypercare closed \u002F EXTENDED — reason: {reason}\n\n---\n\n## Monitoring Log\n\n{Timestamped entries from Step 2}\n\n## Defects Discovered\n\n{Table from Step 3 — or \"None\"}\n\n## Closure Assessment\n\n{Checklist from Step 4 with each item verified or flagged}\n\n## Lessons for Phase 8\n\n{Any patterns from defects or monitoring that should feed the Phase 8 retrospectives}\n```\n\n## Step 6 — Present Summary\n\n**Hypercare: {CLOSED (stable) \u002F EXTENDED}**\n\n**Duration:** {N} hours.\n\n**Defects found:** {N} — {N} resolved, {N} open with mitigation.\n\n**Stability confirmed:** Error rate and latency within baseline for {N}h.\n\n**Lessons for Phase 8:** {N} items captured.\n\n**Next step:** Run `\u002Fmh-cto-sdlc-outcome-measure` to begin Phase 8 Validation & Evolution.\n",{},"main","2ec3bbf5ba353f3fdd2c6d842b791fd75d08a635","src\u002Fdepartments\u002Fcto\u002Fsdlc\u002Fphase-7-launch\u002Fmh-cto-sdlc-hypercare",0,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard","https:\u002F\u002Fgithub.com\u002FImad-Oute","https:\u002F\u002Fimad369.vercel.app\u002F","I'm just starting my Journey.","2026-05-13 03:02:22",{"source":7,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Imad-Oute\u002FMicroHard --skill mh-cto-sdlc-hypercare",{"tool":42,"command":43},"bunx","bunx skills add Imad-Oute\u002FMicroHard --skill mh-cto-sdlc-hypercare",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Imad-Oute\u002FMicroHard --skill mh-cto-sdlc-hypercare","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcto\u002Fsdlc\u002Fphase-7-launch\u002Fmh-cto-sdlc-hypercare\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"customize.toml","OTHER","其他",414,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcto\u002Fsdlc\u002Fphase-7-launch\u002Fmh-cto-sdlc-hypercare\u002Fcustomize.toml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"mh-skill-manifest.yaml","REFERENCE","参考文档",392,"https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fdepartments\u002Fcto\u002Fsdlc\u002Fphase-7-launch\u002Fmh-cto-sdlc-hypercare\u002Fmh-skill-manifest.yaml",[63,90,107,121,138,155],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":22},"01M6N8JYRPSHVW4Y76X5SAGRDX","mh-vo-vault-brief","Weekly vault intelligence report — health score, pipeline status, OS alignment, and top issues. Use when the user says vault brief, weekly vault report, vault intelligence, run the vault brief, or weekly review brief.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F5-report\u002Fmh-vo-vault-brief\u002FSKILL.md",[],[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89],"mh vo vault brief","brief","vault","intelligence report","top","weekly","os","pipeline","health","issues","report","run","status","review","weekly review","user","use","pipeline status","alignment","intelligence",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":22},"01M6N8JCK7E7Y19940RBB51R96","mh-vo-output-bridge","Scan _mh-output\u002F for new artifacts and create or update corresponding vault entries. Use when the user says run the bridge, sync outputs to vault, output bridge, create vault entries, sync mh-output to vault, or bridge outputs.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F4-bridge\u002Fmh-vo-output-bridge\u002FSKILL.md",[],[97,98,99,72,100,101,81,102,103,104,85,105,106,86],"bridge","output","mh vo output bridge","artifacts","update","create","sync","for","entries","scan",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":22},"01M6N8HXW3ENQ939C93R59W371","mh-vo-moc-builder","Create or update Maps of Content for vault sections and ensure every note is reachable from a MOC. Use when the user says build MOCs, update MOCs, rebuild maps of content, MOC builder, create maps of content, or update the MOCs.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-moc-builder\u002FSKILL.md",[],[114,115,104,116,117,118,119,102,86,72,120,101,85],"builder","mh vo moc builder","note","build","rebuild","maps","content",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":22},"01M6N8HHZ30706B2ZS33X3MR42","mh-vo-link-architect","Identify missing vault connections and generate precise link recommendations. Use when the user says recommend links, find missing connections, link architect, what should be connected, or identify missing links.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-link-architect\u002FSKILL.md",[],[128,129,130,85,131,132,133,134,135,86,136,72,137],"mh vo link architect","link","architect","recommend","links","missing","recommendations","connections","find","generate",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":22},"01M6N8H6FKWGTNFWS5PTPPTEN0","mh-vo-base-builder","Generate Obsidian Bases (.base files) for live database views of vault data. Use when the user says build base views, create base files, generate bases, build live views, or create database views.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F3-connect\u002Fmh-vo-base-builder\u002FSKILL.md",[],[145,146,147,114,72,148,149,150,137,102,151,85,104,152,117,153,154,86],"mh vo base builder","base builder","base","obsidian bases","data","database","obsidian","live","files","bases",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":22},"01M6N8GSRETQW3B9C843F1S1CP","mh-vo-taxonomy-enforcer","Audit vault tags and frontmatter, find drift, and apply corrections. Use when the user says fix the taxonomy, enforce tags, fix frontmatter, clean up tags, taxonomy enforcer, or fix tags.","https:\u002F\u002Fgithub.com\u002FImad-Oute\u002FMicroHard\u002Fblob\u002Fmain\u002Fsrc\u002Fmodules\u002Fvo\u002F2-route\u002Fmh-vo-taxonomy-enforcer\u002FSKILL.md",[],[162,163,164,165,166,167,168,169,170,171,86,172,85,136,72,173],"mh vo taxonomy enforcer","taxonomy","enforce","apply","frontmatter","tags","drift","clean","vault tags","up","fix","audit"]