ops-engineer-scope-contract

Converts ambiguous requests into bounded role contracts with outcomes, non-goals, and validation criteria.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill ops-engineer-scope-contract-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-engineer-scope-contract
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/ops-engineer/skills/pack-maturity/scope-contract
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill ops-engineer-scope-contract-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous task requests in operations work lead to scope creep, unclear deliverables, and unverifiable results. This Skill turns a vague request into a bounded role contract that defines outcomes, non-goals, required inputs, risks, and validation methods before work begins. ## Core Features & Use Cases - Scope Definition: Restates the user outcome in one sentence and lists role-owned scope plus explicit non-goals. - Input and Artifact Contract: Names required and unavailable inputs, then defines the deliverable artifact and its validation method. - Decision Gate: Returns a stop, go, iterate, or escalate decision with a fixed output order of result, evidence, risk, and next action. - Use Case: When an operations engineer receives a vague request like "check the servers," use this Skill to produce a contract specifying what will be inspected, what is out of scope, what access is needed, and how success will be verified. ## Quick Start Ask the agent to load the scope-contract workflow and turn my current operations request into a bounded contract with outcomes, non-goals, inputs, and a go or no-go decision.

Frequently Asked Questions about ops-engineer-scope-contract

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

FAQPage Schema
How do I turn a vague task request into a clear scope contract?▼

Restate the desired outcome in one sentence, list the scope you own plus explicit non-goals, name required and unavailable inputs, then define the deliverable and its validation method. Finish with a stop, go, iterate, or escalate decision.

What should a scope contract for operations work include?▼

A scope contract should include a one-sentence outcome, role-owned scope, explicit non-goals, required and missing inputs, the expected artifact, a validation method, and a final decision. Output order is result first, evidence second, risk third, next action last.

When should I use a scope contract workflow instead of answering directly?▼

Use it when a task requires a concrete artifact, an evidence gate, or a formal handoff, especially in operations engineering contexts. Do not use it for generic chat responses or simple informational questions.

What are the limitations of a scope contract workflow?▼

It adds upfront structure that may be unnecessary for trivial or purely conversational requests. It also depends on the requester providing enough context to name inputs and validation criteria, otherwise the contract must flag unavailable inputs.