executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
repair-damageImplement regenerative recovery using triage, scaffolding, and progressive rebuild. Covers damage assessment, wound classification, emergency stabilization, scar tissue management, and resilience strengthening for systems that have sustained structural damage. Use when a system has suffered an incident needing structured recovery, when a failed transformati…
Independent GitHub snapshot · Automated classification · Original documentation governs
施再生之復用分緩急、立架、漸建之法。涵損之察、傷之分、急穩、痕管、為已受構損之系強韌。
adapt-architecture)留系於損之中乃用defend-colony)若殖受損乃用速察諸損而以重急分之。
Wound Classification:
┌──────────┬──────────────────────┬────────────────────────────────────┐
│ Class │ Severity │ Response │
├──────────┼──────────────────────┼────────────────────────────────────┤
│ Critical │ Core function lost, │ Immediate: stop bleeding, activate │
│ │ data at risk, │ backup, redirect traffic, page │
│ │ actively spreading │ on-call team │
├──────────┼──────────────────────┼────────────────────────────────────┤
│ Serious │ Important function │ Urgent: fix within hours/days, │
│ │ degraded, no spread │ workarounds acceptable short-term │
├──────────┼──────────────────────┼────────────────────────────────────┤
│ Moderate │ Non-critical function│ Scheduled: fix within sprint, │
│ │ affected, contained │ prioritize against other work │
├──────────┼──────────────────────┼────────────────────────────────────┤
│ Minor │ Cosmetic or edge │ Backlog: fix when convenient, │
│ │ case, no user impact │ may self-resolve │
└──────────┴──────────────────────┴────────────────────────────────────┘
得:諸傷之全錄依重分,附排序之修序,慮諸傷相互。
敗則:若分過久(系活衰),略詳分而專注:「最當穩之單事為何?」先修之,再返全分。
修之前止損漫。
得:系穩(非活衰)雖衰。損已抑而不漫。證已存供根因之析。
敗則:若穩敗(雖抑而損仍漫),升至全系退:啟災復、轉至備系、或優雅衰至最少行。穩過久則自為災。
立支修程之臨構。
得:修之境附診能、序之修計、痕險之察。
敗則:若立正修境過緩(系急需即時產變),直施變然以極律:一次一變,以可得之法試,若無助則退。
系統修損,每修驗後再進。
得:critical 與 serious 之傷以驗修。急補已除。系復行。
敗則:若修嘗敗或致退,退至前態而再察。若同傷數修皆敗,損或過深不能局修——考受件需全代而非修(見 dissolve-form)。
理急修時所引之變通與捷徑,強以防再。
defend-colony 之免疫記)得:痕已管(除、代、或書受)。系不獨修且勝損前韌。所學已捕為來事故。
敗則:若痕管被低排(「行矣,勿觸」),明排之。未管之痕積而終資下事故。若根因不能識,強察與復速為補之控。
assess-form — 損察與形察共法adapt-architecture — 損露構弱時或需構之化dissolve-form — 件損過深不能修;溶而重建defend-colony — 守觸修;事故後復返饋於守shift-camouflage — 表化可掩損而修進(慎)conduct-post-mortem — 構之事後析補根因之識write-incident-runbook — 修程宜捕為來事故之行手