durable
Skill4 starsChanged 28 days agoMITView on GitHub
[UDS] Guide fault-tolerant workflow design with checkpoints, retry policies, and rollback plans. Use when: a long-running workflow keeps failing partway, designing checkpoint granularity, choosing a retry or backoff strategy. Not for: responding to a production incident already in progress — use /incident; deployment rollback mechanics — use /deploy. Keywords: durable execution, checkpoint, retry, backoff, idempotency, rollback, 持久執行, 檢查點, 重試策略.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026
- gplanchat/durable-skilltheir own version, first seen Oct 1, 2026
Other versions2 projects use a version of this.
Word for word · 1
- AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 1
- gplanchat/durable-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 99
After /durable completes, the AI assistant should suggest:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Durable Execution Assistant | 持久執行助手
Guide fault-tolerant workflow design with automatic recovery, checkpoints, and retry strategies.
引導容錯工作流程設計，包含自動恢復、檢查點與重試策略。
Usage | 使用方式
| Command | Purpose | 用途 |
/durable | Start interactive failure recovery guide | 啟動互動式故障恢復引導 |
/durable --checkpoint | Design checkpoint strategy | 設計檢查點策略 |
/durable --retry | Configure retry policies | 配置重試策略 |
/durable --rollback | Plan rollback procedures | 規劃回滾程序 |
/durable <workflow> | Analyze specific workflow for durability | 分析特定工作流的持久性 |
Core Concepts | 核心概念
| Concept | Definition | 定義 |
| Checkpoint | Save execution state at known-good points | 在已知正確的位置儲存執行狀態 |
| Retry | Automatically re-attempt failed operations | 自動重新嘗試失敗的操作 |
| Rollback | Revert to last known-good state on failure | 失敗時回復到上一個已知正確狀態 |
| Idempotency | Operations produce same result on re-execution | 操作重新執行時產生相同結果 |
| Circuit Breaker | Stop retries when failure rate exceeds threshold | 失敗率超過閾值時停止重試 |
Failure Recovery Decision Tree | 故障恢復決策樹
Failure detected
├── Is it transient? (network, timeout)
│ ├── Yes → Retry with backoff
│ └── No → Is state corrupted?
│ ├── Yes → Rollback to checkpoint
│ └── No → Is it a logic error?
│ ├── Yes → Stop, report, fix code
│ └── No → Escalate with diagnosticsRetry Strategy Guide | 重試策略指南
| Strategy | When to Use | Config | 使用時機 |
| Immediate | Rare glitches, fast ops | max 2 retries | 罕見故障、快速操作 |
| Exponential Backoff | Network/API calls | base 1s, max 30s | 網路/API 呼叫 |
| Circuit Breaker | Downstream service issues | threshold 50%, window 60s | 下游服務問題 |
| Dead Letter | Unrecoverable after retries | max 5 retries then queue | 重試後仍不可恢復 |
Checkpoint Granularity | 檢查點粒度
| Granularity | Use Case | 使用場景 |
| Per-step | Long pipelines (> 5 steps) | 長管線（> 5 步驟） |
| Per-batch | Bulk data processing | 批量資料處理 |
| Per-phase | Multi-phase workflows | 多階段工作流程 |
| Start/End | Short, atomic operations | 短暫的原子操作 |
Workflow | 工作流程
- DETECT - Identify failure type and scope
- DIAGNOSE - Determine root cause category
- RECOVER - Apply appropriate recovery strategy
- VERIFY - Confirm system state is consistent
- RESUME - Continue from last checkpoint
- 偵測 - 識別故障類型與範圍
- 診斷 - 判定根本原因類別
- 恢復 - 套用適當的恢復策略
- 驗證 - 確認系統狀態一致
- 繼續 - 從上一個檢查點繼續
Usage Examples | 使用範例
User: /durable deploy-pipeline
AI: Analyzing deploy-pipeline for durability...
Steps: build → test → deploy → verify
Risk: deploy step has no rollback strategy.
Recommendation: Add checkpoint after test,
configure rollback for deploy using blue-green strategy.Next Steps Guidance | 下一步引導
After /durable completes, the AI assistant should suggest:
持久性分析完成。建議下一步 / Durability analysis complete. Suggested next steps:
- 執行
/methodology選擇適合的開發方法論 ⭐ Recommended / 推薦 — Choose suitable methodology- 執行
/commit提交持久化設計變更 — Commit durability design changes
Version History | 版本歷史
| Version | Date | Changes | 變更 |
| 1.0.0 | 2026-03-24 | Initial release | 初始版本 |
AI Agent Behavior | AI 代理行為
完整的 AI 行為定義請參閱對應的命令文件：
/durableFor complete AI agent behavior definition, see the corresponding command file:
/durable
License | 授權
CC BY 4.0
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.