minimal-workflow
Use when the user asks to "summarize this incident" or "write the incident handoff" from a completed incident timeline.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- minimal-workflow
- license
- MIT
- metadata
- { "summary": "Converts a completed incident timeline into a factual handoff.", "category": "Communication" }
- description
- Use when the user asks to "summarize this incident" or "write the incident handoff" from a completed incident timeline.
03 SKILL.md 正文
Minimal Workflow
Scope
Use when a completed incident timeline needs a handoff.
Do not use for active incident diagnosis. Use diagnose when installed; otherwise establish the cause before writing the handoff.
Workflow
-
Extract the impact, recovery action, and unresolved follow-up from the timeline. Mark absent facts unknown.
Done when every statement traces to a timeline entry or is marked unknown.
-
Write one sentence for each extracted item.
Done when the handoff includes impact, recovery, and follow-up without inventing facts.
Example: Given "09:00 login errors; 09:10 rollback restored login; cause unknown", write "Login failed from 09:00 to 09:10. A rollback restored login. The cause remains unknown."
Verification
- Every factual statement matches the supplied timeline.
- Missing facts remain unknown.
04 同仓库更多 Skills
write-agent-instructions
Make the smallest evidence-backed change to persistent project instructions and test downstream behavior.
verify-work
Use when a finished, runnable artifact (a script, config, parser, prompt, or CLI, not a diff under review) must survive hostile input before shipping: the user asks to "verify this script", "find the loopholes", "test this properly against bad input", or asks "is this ready to ship" about one. Also when a shipped artifact failed on an input nobody tried, or when verification so far is a happy-path smoke test.
understand-codebase
Use when the user asks to "understand this codebase", "how does this feature work in this repo?", "trace this feature through the code", or needs onboarding, an architecture explanation, or answers about unfamiliar code. Also use for read-only code-path questions before a change.
tdd
Use when writing or changing production behavior: implementing a feature, fixing a bug whose cause is already known, or altering stored, transformed, migrated, serialized, or externally transmitted data. Also use when a user says "use TDD", "test first", or "red-green-refactor", and when code is being written before a failing test. For a failure whose cause is unknown, diagnose first.
simplify-code
Use when the user asks to "simplify this code", "remove the fluff", or "clean up this over-engineered module", or wants working code that is bloated, duplicated, over-abstracted, or dependency-heavy reduced without changing behavior.
review-session
Review an agent session for evidence-backed friction and the smallest measurable remedies.