FREESKILL v1.0UPDATED 2026-08
Single-Threaded Owner
This skill defines one accountable owner, mission, decision rights, boundaries, interfaces, measures, and review cadence for a program. It produces a Single Threaded Owner Charter from supplied evidence without inventing missing detail.
A title does not create ownership. A single-threaded owner needs a defined mission, decision rights, boundaries, interfaces, measures, and a review cadence that makes accountability observable.
Write the charter around the outcome the owner controls. Reserve decisions that sit elsewhere, name the dependencies, and give every interface a handoff rule instead of relying on goodwill.
One owner works only when the decision rights are equally clear.
SIGNALS YOU NEED THIS
Naming an owner without authority.
Making the owner responsible for every task.
Overlapping charters.
Frame the work
HYPOTHETICAL INPUT Write an STO charter for the intake quality program. Mission: reduce preventable rework. Proposed owner: Program Lead. The owner may change intake fields and review cadence. Finance policy and staffing remain reserved decisions. Dependencies: Data Operations and Support. Review monthly through December.
Build the evidence ledger
FACT LEDGER - Supplied facts: retained as supplied - Inference: labeled - Missing evidence: [Needed]
Draft the artifact
WORKING ARTIFACT - Artifact: Single Threaded Owner Charter - Owner: [Needed if not supplied] - Decision boundary: explicit
Audit and hand off
REVIEW STATUS - Unsupported claims: removed - Open actions: owner and date required - Human decisions: reserved
single-threaded-owner/
|-- SKILL.md
|-- meta.yaml
|-- LICENSE.md
|-- assets/
| |-- single-threaded-owner-charter-template.md
|-- references/
|-- owner-charter-standard.md"Write the single threaded owner charter for this program."
ClaudeChatGPTCursorGemini