infra-engineer-scope-contract

Converts ambiguous infrastructure requests into bounded role contracts with outcomes, risks, and validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous infrastructure requests often lead to scope creep, unclear ownership, and unverifiable deliverables. This Skill turns a vague task into a bounded role contract that defines outcomes, non-goals, inputs, outputs, risks, and validation criteria 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 asked to "improve our deployment pipeline" inside the infrastructure engineer pack, use this Skill to first produce a contract stating the concrete outcome, what is out of scope, which inputs are missing, and how the result will be validated. ## Quick Start Ask the agent to load the scope-contract skill and turn the current infrastructure request into a bounded contract with outcomes, non-goals, risks, and a go or escalate decision.

Frequently Asked Questions about infra-engineer-scope-contract

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

FAQPage Schema
How do I turn an ambiguous infrastructure request into a clear scope?▼

Load the scope-contract skill and follow its five-step procedure: restate the outcome in one sentence, list owned scope and non-goals, name required and missing inputs, define the artifact and validation method, then return a stop, go, iterate, or escalate decision.

What is a scope contract in infrastructure engineering work?▼

A scope contract is a bounded agreement produced before execution that defines the expected outcome, explicit non-goals, required inputs, the deliverable artifact, and how it will be validated. It prevents scope creep and unclear ownership on infrastructure tasks.

When should I use the scope-contract skill?▼

Use it when operating the infrastructure engineer pack and a task requires a concrete artifact, evidence gate, or handoff. It is not intended for generic chat responses or open-ended discussion without deliverables.

Which AI platforms support this scope contract workflow?▼

The skill is designed to run in Claude Code, Codex, Gemini, Hermes, and OpenClaw, letting infrastructure teams reuse the same role capability across platforms instead of relying on one-off chat prompts.

What output format does the scope contract produce?▼

The output follows a fixed contract: result first, evidence second, risk third, and next action last. It ends with an explicit stop, go, iterate, or escalate decision so the requester knows how to proceed.