Menu
Document upstream influence, provenance, wrapping relationships, and notice obligations with explicit categories and GitHub-visible records.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create a host-native `/goal` prompt for bounded ORCA plan work, especially when the user wants an agent to keep working through ready ORCA plans, delegate blocker fixes to subagents, record true blockers, and move on without stalling.
Implement planned changes with scoped edits, verification, and respect for existing project patterns.
Create bounded delegation briefs and structured executor returns for ORCA Framework workflows.
Prepare release readiness checks, release notes, rollback guidance, and handoff.
Record time, retries, and optional token, cache, and cost metrics for ORCA Framework workflows without fabricating precision.
Provide lightweight, skill-sensitive coaching without slowing down normal ORCA Framework execution.
| name | orca-attribution |
| description | Document upstream influence, provenance, wrapping relationships, and notice obligations with explicit categories and GitHub-visible records. |
A workflow for making upstream influence, integration scope, provenance, and notice obligations easy to understand.
Use when:
Do not use for generic gratitude alone. Use this when provenance and attribution clarity materially affect the repository.
UPSTREAM.md as the canonical catalog.THIRD_PARTY_NOTICES.md and NOTICE if notice handling changes.The output should name names, classify relationships clearly, and avoid both vagueness and legal theater.
Supports README, workflow, integration, licensing, and contributor-maintenance quality across the framework.