skills.rest
MARUCIE
MARUCIECOMMUNITY
Explore all skills by this author →
GitHub

ops-engineer-delivery-review

Combines role output, risk review, and validation evidence into an operator-ready delivery handoff.

1|Updated Mar 18, 2026
Search Tags:#workflow#handoff#operations#risk review#validation evidence#delivery review#ops engineer
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill ops-engineer-delivery-review-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-engineer-delivery-review
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/ops-engineer/skills/pack-maturity/delivery-review
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill ops-engineer-delivery-review-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operations and delivery work often ends with scattered outputs, unverified assumptions, and unclear next steps. This Skill structures the final review stage so every delivery includes a concrete artifact, supporting evidence, a risk assessment, and one executable next action. ## Core Features & Use Cases - Structured Handoff: Combines role output, risk review, validation evidence, and next action into a single operator-ready delivery. - Output Contract: Enforces a fixed order of result first, evidence second, risk third, and next action last. - Use Case: After completing an ops task such as a deployment check or incident follow-up, run the delivery review to produce a final handoff document that records what was done, the evidence, remaining risks, and the exact next step for the on-call engineer. ## Quick Start Ask the agent to run the delivery review workflow for the current ops task and produce a final handoff with evidence, risks, and one next action.

Frequently Asked Questions about ops-engineer-delivery-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a delivery review for an ops task?▼

Load the delivery-review skill after completing the ops work, then follow its five-step procedure: lead with the result, attach evidence and assumptions, run the delivery-risk review, resolve or hand off blockers, and end with one executable next action.

What should an operations handoff document include?▼

An operations handoff should include the completed result or artifact first, supporting evidence and known assumptions second, a risk assessment third, and a single executable next action last. This skill enforces that exact output contract.

When should I not use the delivery review workflow?▼

Do not use it for generic chat responses or exploratory discussion. It is designed only for situations requiring a concrete artifact, an evidence gate, or a formal handoff within the ops-engineer pack.

How do I handle blockers found during delivery review?▼

The workflow's fourth step requires you to either resolve blockers directly or explicitly hand them off. Unresolved blockers must be recorded in the risk section so the receiving operator knows what remains open.

Can this workflow be used in Claude Code, Codex, or OpenClaw?▼

Yes, the skill is platform-agnostic markdown instructions and can be loaded in Claude Code, Codex, Gemini, Hermes, or OpenClaw, letting the same delivery review process be reused across agent platforms.

Related Skills

Explore More Software Engineering Skills→
SlooowllySlooowlly

Verification Before Completion

Verify task completion with fresh test command output and build logs.

Community
Basic
Covcloud-LLCCovcloud-LLC

wrap-up

Reconcile plan slices and capture project knowledge after task completion.

Official
Advanced
ringlochidringlochid

security-review-gate

Identify security risks in application code and config with evidence-backed reports.

Community
Advanced
Dokkabei97Dokkabei97
2

postmortem-writer

Generate blame-free postmortem documents with timeline, root cause analysis, and prevention measures.

Community
Basic