boil-the-ocean

Ensures code changes are fully implemented, tested, and documented.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/xinye1/xl-skills --skill boil-the-ocean-xinye1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boil-the-ocean
Source: https://github.com/xinye1/xl-skills/tree/main/skills/boil-the-ocean
Command: npx skills add https://github.com/xinye1/xl-skills --skill boil-the-ocean-xinye1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure mode of stopping short on implementation tasks, ensuring that work is fully finished, tested, and documented rather than left as a collection of workarounds or dangling TODOs.

Core Features & Use Cases

  • Implementation Standard: Enforces a high bar for finished work where the deliverable is a fully verified artifact, not just a plan or a gesture.
  • Loose-end Resolution: Mandates that minor related tasks surfaced during implementation are completed immediately to avoid future context-switching costs.
  • Use Case: When fixing a bug, this skill ensures you not only apply the fix but also write the necessary regression test and update relevant documentation, rather than leaving a comment about the limitation.

Quick Start

Apply the boil the ocean standard to ensure this feature implementation is fully verified and complete.

Frequently Asked Questions about boil-the-ocean

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

FAQPage Schema
How do I ensure full implementation completeness for new feature development?

Implementation completeness mandates full verification, testing, and documentation for all code changes, preventing incomplete workarounds or dangling TODOs. This guarantees end-to-end functionality and eliminates deferred work.

What is the best way to handle loose ends and minor tasks surfaced during refactoring?

Handling loose ends during refactoring requires completing minor related tasks immediately to avoid future context-switching costs. This approach ensures technical debt is eliminated rather than left as deferred work or comments about limitations.

Why does my bug fix process leave technical debt and how to stop it?

Bug fix processes leave technical debt when stopping short of full implementation. To stop this, apply standards ensuring you not only apply the fix but also write regression tests and update relevant documentation.

Does total implementation completeness require regression testing for bug fixes?

Yes, total implementation completeness requires regression testing for bug fixes. It enforces a high bar for finished work where the deliverable is a fully verified artifact, satisfying requirements for end-to-end functionality and regression testing.

When do I need strict quality assurance standards for refactoring tasks?

You need strict quality assurance standards for refactoring tasks when completeness is critical to long-term maintainability. This ensures the deliverable is a fully verified artifact rather than just a plan, eliminating technical debt.