ocean-buddy

Enforce exact scope and evidence-backed decisions in project workflows.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill ocean-buddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocean-buddy
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/ocean-buddy
Command: npx skills add https://github.com/Ocean326/Agents --skill ocean-buddy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ocean-buddy provides an evidence-shaped operating lens built from local rules to enforce exact scope, stage-ordered processes, and durable artifacts. It helps ensure projects stay within defined boundaries, with traceable decisions and verifiable outputs.

Core Features & Use Cases

  • Exact scope enforcement: converts vague asks into bounded, verifiable deliverables.
  • Evidence-before-expansion: prioritizes smallest, well-supported changes.
  • Local-first execution: relies on local files, histories, and references to reduce dependency on memory.
  • Fixed phase order: prescribes a clear, step-by-step workflow with a single bounded next action.
  • Durable outputs: emphasizes artifacts that can be picked up by others without replaying chat history.
  • Governance and boundary checks: supports review and approval boundaries for safe collaboration.

Quick Start

Use ocean-buddy to transform a vague request into a bounded, evidence-backed action plan.

Frequently Asked Questions about ocean-buddy

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

FAQPage Schema
How do I enforce exact scope and evidence-backed decisions in project planning?

Evidence-backed decisions require exact scope enforcement through fixed phase order and local-first execution. This approach converts vague asks into bounded deliverables using explicit frontmatter, references, and boundaries for verifiable project outputs.

What is local-first execution for durable project artifacts?

Local-first execution for durable project artifacts relies on local files, histories, and references to reduce memory dependency. It produces reproducible outputs that others can pick up without replaying chat history.

How do I convert a vague request into a bounded, evidence-backed action plan?

Convert a vague request into a bounded action plan by applying evidence-before-expansion principles. This prioritizes smallest well-supported changes and prescribes a step-by-step workflow with a single bounded next action.

Does phase-order governance work for review and approval boundaries?

Phase-order governance supports review and approval boundaries for safe collaboration. It prescribes stage-ordered actions, ensuring traceable decisions and verifiable outputs within defined project boundaries.

When should I not use an evidence-first bounded lens for project workflows?

Avoid using an evidence-first bounded lens for tasks requiring open-ended exploration without defined boundaries or durable artifacts. It enforces exact scope and fixed phase order, which constrains unstructured adaptive workflows.