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

spellbook-onboarding-delivery-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Onboarding and role-based work often ends with scattered outputs, unverified assumptions, and unclear next steps. This Skill structures the final delivery review so every handoff includes the result, supporting evidence, known risks, and one executable next action. ## Core Features & Use Cases - Structured Handoff Format: Enforces a fixed output contract of result first, evidence second, risk third, and next action last. - Delivery-Risk Review: Runs a risk review for the role before sign-off and resolves or escalates blockers. - Use Case: When completing an onboarding task in the 入职引导 pack, use this Skill to assemble the role's output, attach validation evidence, document assumptions, and close with a single actionable next step for the operator. ## Quick Start Load the delivery-review skill and produce a final handoff for the current onboarding task with result, evidence, risks, and one next action.

Frequently Asked Questions about spellbook-onboarding-delivery-review

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

FAQPage Schema
How do I structure a delivery review handoff for a role-based task?▼

Lead with the recommendation or completed artifact, then attach evidence and known assumptions, run a delivery-risk review for the role, resolve or hand off blockers, and end with one executable next action.

What is the output contract for a delivery review workflow?▼

The output contract is fixed: result first, evidence second, risk third, and next action last. This ordering ensures operators see the decision before the supporting detail.

When should I use a delivery review workflow instead of a chat response?▼

Use it when operating the onboarding pack and a concrete artifact, evidence gate, or formal handoff is required. It is not intended for generic conversational replies.

Can this delivery review workflow run in Claude Code, Codex, or OpenClaw?▼

Yes, the workflow is designed to be reusable across Claude Code, Codex, Gemini, Hermes, and OpenClaw, so the same role capability is not tied to one-off chat prompts.

What are the limitations of a delivery review workflow?▼

It only formalizes the final review and handoff stage; it does not generate the underlying role output or validation evidence itself. Those inputs must exist before the review can be assembled.

Related Skills

Explore More Product & Management Skills→
withpiperwithpiper
6

define

Generate a project-definition.md from a validated concept brief.

Official
Advanced
HonigbartHonigbart
1

autopilot

Automate end-to-end plan execution and review across all phases.

Community
Advanced
Elmanuel1Elmanuel1

grill-me

Validates design assumptions via structured decision-tree interviews and a Dependency Ledger.

Community
Advanced
TitoPrauseeTitoPrausee

inter-agent-gitlab-message-queue

Coordinate asynchronous AI agent messages through GitLab issues.

Community
Intermediate