okhp3-project-promotion

Assembles a promotion packet for efforts that cleared a documented graduation gate.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-project-promotion-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-project-promotion
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-project-promotion
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-project-promotion-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Exploratory efforts that pass a readiness gate still need a structured, owner-reviewable package before they can become formal projects. This Skill assembles that promotion packet with provenance, decisions, risks, and destination tradeoffs so the owner can make an informed approval decision. ## Core Features & Use Cases - Promotion Packet Drafting: Compiles scope, non-goals, evidence, decision rationale, risks, unresolved owner choices, and destination tradeoffs into one draft package. - Gate Enforcement: Requires a documented GO result from a graduation gate before proceeding, and stops or returns BLOCKED when gate evidence is missing. - Authorization Boundaries: Stops at the owner decision and never creates repositories, publishes, pushes, or moves work externally without separate authorization. - Use Case: After an exploratory prototype clears its readiness review, use this Skill to produce the draft promotion packet with artifact inventory, validation status, and the first immediately executable formal-project action for the owner to approve. ## Quick Start Use okhp3-project-promotion to prepare a promotion packet for this effort using its cleared gate result and artifact inventory.

Frequently Asked Questions about okhp3-project-promotion

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

FAQPage Schema
How do I prepare a project promotion packet after a readiness review?▼

Provide the cleared gate result, effort root, artifact inventory, provenance, decision log, and proposed destination. The Skill returns a draft packet with scope, non-goals, evidence, risks, owner choices, destination tradeoffs, and the first executable action.

What inputs are required to formalize an exploratory effort?▼

You need a documented GO result from the graduation gate, the effort root, an artifact inventory with relative paths, provenance, a decision log, and a proposed formal destination. Missing gate evidence causes the Skill to stop or return BLOCKED.

Can this Skill create a repository or publish the promotion package?▼

No. It stops at the owner decision and never creates repositories, publishes, pushes, or moves work externally. Those actions require separate authorization within the same current request.

What happens if the effort has no documented GO result?▼

The Skill stops or returns BLOCKED pending the gate, names the missing gate evidence, and does not imply promotion is approved. A GO from the graduation gate is a hard prerequisite.

When should artifact validation run in the promotion workflow?▼

Run artifact validation before calling the package ready. The Skill records scrub and validation results in the packet so the owner can confirm the evidence trail before approval.