outcome-bounded-work

Separate required outcomes, evidence, and constraints from replaceable implementation choices.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/srinitude/skills --skill outcome-bounded-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: outcome-bounded-work
Source: https://github.com/srinitude/skills/tree/main/skills/outcome-bounded-work
Command: npx skills add https://github.com/srinitude/skills --skill outcome-bounded-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you distinguish what must be achieved from how it should be done, so you can keep requirements, proof, boundaries, and optional implementation paths clear.

Core Features & Use Cases

  • Contract shaping: Turn mixed instructions into an inspectable outcome contract with outcome, proof, boundaries, forbidden outcomes, mandatory methods, candidate paths, adaptation rules, and unknowns.
  • Artifact audit: Review policies, prompts, or specs without mutating the source, while assigning stable source IDs and preserving requirement strength.
  • Conversation control: Handle live requests by proposing the smallest useful contract early, preserving user intent, and asking at most one focused question when needed.
  • Safety and scope preservation: Keep privacy, authority, reversibility, and explicit user-required methods fixed while allowing only replaceable routes to change.
  • Use case: A user asks for a fast account setup flow, but also suggests a specific UI and backend; this Skill separates the target result and safety constraints from the optional design route.

Quick Start

Ask the skill to turn your request or policy into a clear outcome contract with accepted requirements, candidate paths, and proof criteria.

Frequently Asked Questions about outcome-bounded-work

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

FAQPage Schema
How do I separate required outcomes from implementation choices in a specification?

To separate required outcomes from implementation choices, you need to distinguish fixed goals and safety boundaries from replaceable methods. This process shapes mixed instructions into an inspectable contract, preserving proof obligations while identifying candidate paths and unresolved distinctions.

What is contract shaping for mixed instructions and prompts?

Contract shaping is the process of turning mixed instructions into an inspectable outcome contract. It isolates outcomes, proof, boundaries, and forbidden outcomes from mandatory methods and candidate paths, ensuring safety and scope preservation without mutating the original source.

How do I audit a policy or prompt without changing the original source?

Auditing a policy without changing the source involves reviewing the text while assigning stable source IDs and preserving requirement strength. This artifact audit separates fixed safety boundaries and proof obligations from optional implementation routes.

Can I use requirement classification to handle live conversation requests?

Requirement classification handles live conversation requests by proposing the smallest useful contract early. It preserves user intent and asks at most one focused question when needed, separating the target result and safety constraints from optional design routes.

What is the best way to identify candidate paths in a project plan?

The best way to identify candidate paths is by applying scope control to separate target outcomes from implementation choices. This preserves exact methods, safety boundaries, and proof obligations while highlighting unresolved distinctions and replaceable routes within the plan.