skills.rest
gaofeng21cn
gaofeng21cnCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

opl-workspace-handoff-writer

Generate five OPL handoff packet types with strict truth adherence.

8|5|Updated Apr 2, 2026
Search Tags:#handoff-writing#knowledge-work#owner-routing#artifact-references#route-back#opl-workspace#workspace-briefing
One-click install
npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-workspace-handoff-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opl-workspace-handoff-writer
Source: https://github.com/gaofeng21cn/one-person-lab/tree/main/plugins/opl-foundation-skills/skills/opl-workspace-handoff-writer
Command: npx skills add https://github.com/gaofeng21cn/one-person-lab --skill opl-workspace-handoff-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OPL workspace handoffs frequently lose critical locator, path, artifact reference, and owner route information during cross-session or cross-team transfers, leading to broken references, duplicated work, and delayed project progress as teams waste time re-tracing authoritative sources.

Core Features & Use Cases

  • Five Handoff Packet Types: Supports creation of workspace briefings, source-artifact handoffs, missing-input route-backs, owner route packets, and review-only packets for all OPL workflow stages.
  • Strict Truth Adherence: Never invents, mutates, or relocates source or artifact references, always relying on authoritative Workspace or program-owned surfaces as the single source of truth.
  • Automated Missing Input Detection: Identifies gaps such as absent references, ambiguous paths, stale sources, or mismatched owners, and generates structured route-back packets instead of guessing to avoid propagating incorrect information.
  • Use Case: When handing off a multi-session research project workspace to a new team member, use this skill to package all valid source refs, artifact units, and current owner routes into a clear, actionable packet so they can pick up work immediately without re-verifying source authority.

Quick Start

Use the opl-workspace-handoff-writer skill to generate a complete handoff packet for the active OPL workspace, including all valid source refs, artifact units, and current owner routes.

Frequently Asked Questions about opl-workspace-handoff-writer

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

FAQPage Schema
What is an OPL workspace handoff packet and when do I need one?▼

An OPL workspace handoff packet is a structured document that preserves locator, path, artifact reference, and owner route information during cross-session or cross-team transfers. You need one when transferring knowledge work to prevent broken references and duplicated work.

How do I document missing inputs for an OPL workspace route-back?▼

To document missing inputs for an OPL workspace route-back, identify gaps such as absent references, ambiguous paths, or mismatched owners, then generate a structured route-back packet. This avoids guessing and prevents propagating incorrect information during the handoff.

What's the best way to write an OPL handoff packet without losing artifact references?▼

The best way to write an OPL handoff packet without losing artifact references is to enforce strict adherence to authoritative Workspace and program-owned reference surfaces. Never invent, mutate, or relocate source references, always relying on them as the single source of truth.

Can I create different types of handoff packets for various OPL workflow stages?▼

Yes, you can create five handoff packet types for OPL workflows: workspace briefings, source-artifact handoffs, missing-input route-backs, owner route packets, and review-only packets. Each type addresses specific cross-session or cross-team transfer requirements.

Why do OPL workspace handoffs fail when transferring projects between team members?▼

OPL workspace handoffs fail because critical locator, path, artifact reference, and owner route information is frequently lost during transfers. This leads to broken references, duplicated work, and delayed progress as teams waste time re-tracing authoritative sources.

Does the OPL handoff writer work for multi-session research project transfers?▼

Yes, the OPL handoff writer works for multi-session research project transfers by packaging all valid source refs, artifact units, and current owner routes into a clear, actionable packet so new team members can pick up work immediately without re-verifying source authority.

Related Skills

Explore More Education & Research Skills→
gaofeng21cngaofeng21cn
8

opl-workspace-source-readiness-auditor

Audit OPL Workspace source material and classify consumption-blocking gaps.

Community
Intermediate
danielbaustindanielbaustin
4

architecture-fitness-function-author

Convert architecture findings into fitness-function candidates with validation commands.

Community
Intermediate
gaofeng21cngaofeng21cn
8

opl-atlas-capability-router

Resolve ambiguous OPL Atlas catalog references and generate refs-only route packets.

Community
Intermediate
FabienDehopreFabienDehopre

handoff

Create structured handoff documents that transfer conversation context between AI agents.

Community
Basic