opl-stagecraft-stage-designer

Design OPL Stagecraft stage configurations with explicit authority boundaries and handoff evidence requirements.

8|5|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-stagecraft-stage-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opl-stagecraft-stage-designer
Source: https://github.com/gaofeng21cn/one-person-lab/tree/main/plugins/opl-foundation-skills/skills/opl-stagecraft-stage-designer
Command: npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-stagecraft-stage-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common issue of misaligned OPL stage designs that blur the line between auditable Stagecraft contract boundaries and open-ended AI execution strategy, which leads to unclear authority, missing required evidence, and broken stage handoffs for complex knowledge work projects.

Core Features & Use Cases

  • Boundary-Aligned Stage Design: Separates stable Stagecraft contract rules (allowed surfaces, receipt lower bounds) from flexible AI execution strategy (prompt shaping, rubric, capability use rules) to avoid authority oversteps.
  • Complete Stage Configuration: Generates stage goal framing, decomposition logic, route-back reasoning, handoff packet structures, and capability use policies tailored to the stage's specific workflow.
  • Use Case: For teams building OPL agents for medical research, grant writing, or patent delivery, use this Skill to create stage designs that ensure all required evidence is collected, executors stay within their allowed surfaces, and handoffs to domain owners include all necessary context.

Quick Start

Use the opl-stagecraft-stage-designer skill to create a full stage design for the literature review stage of a medical research paper project, including the stage descriptor, prompt outline, and handoff lower bound.

Frequently Asked Questions about opl-stagecraft-stage-designer

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

FAQPage Schema
How do I separate AI execution strategy from contract rules in OPL stage design?

OPL stage design separates stable Stagecraft contract rules, like allowed surfaces and receipt lower bounds, from flexible AI execution strategy, such as prompt shaping and capability use policies, to prevent authority oversteps and ensure clear boundaries.

What is a handoff lower bound in knowledge work workflows?

A handoff lower bound defines the minimum required evidence and context that executors must collect and pass to domain owners during stage transitions in complex knowledge work workflows like research paper development or patent package assembly.

How do I create a stage configuration for a literature review in a medical research project?

To create a stage configuration, generate the stage goal framing, decomposition logic, prompt outline, capability use policies, and handoff packet structures tailored to the literature review's specific workflow and authority boundaries.

Can I use this approach for grant proposal drafting and patent package assembly?

Yes, this boundary-aligned stage design approach supports complex knowledge work workflows including grant proposal drafting and patent package assembly by ensuring required evidence is collected and executors stay within allowed surfaces.

Why does my OPL stage design have missing required evidence and broken stage handoffs?

Broken stage handoffs and missing evidence occur when OPL stage designs blur the boundary between auditable Stagecraft contract rules and open-ended AI execution strategy, leading to unclear authority and incomplete handoff packets.