ship

Classify engineering requests as CREATE, EVOLVE, REMOVE, or FIX and route to implementation skills.

22|3|Updated Jul 28, 2024
One-click install
npx skills add https://github.com/webdevcody/go-mailing-list --skill ship-webdevcody
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill ship-webdevcody

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ship Skill removes the decision tax of choosing the right engineering workflow and how deep to go, by classifying intent and routing to the appropriate core skill with an automatically selected depth mode.

Core Features & Use Cases

  • Intent Classification (CREATE / EVOLVE / REMOVE / FIX): Detects the user’s engineering goal and selects the matching workflow route for implementation.
  • Depth Mode Inference (fast / balanced / production): Chooses a safe execution depth based on risk and complexity signals, while respecting user-specified mode when applicable.
  • Guardrailed Execution & Reporting: Runs the routed core skill, then summarizes phases and findings without committing, pushing, or opening PRs.

Quick Start

Tell the AI your engineering goal (e.g., “ship an end-to-end unsubscribe flow with bounce tracking in this mailing list app”), and it will choose the correct workflow and run it up to code-ready state.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I orchestrate engineering workflows for building, updating, or fixing features?

Engineering workflow orchestration classifies your intent as CREATE, EVOLVE, REMOVE, or FIX, then routes the request to the appropriate core implementation skill. It automatically infers a safe execution depth based on risk and complexity signals.

What is the best way to manage risk-based execution depth for code-ready engineering changes?

Risk-based mode resolution selects an appropriate execution depth—fast, balanced, or production—based on risk and complexity signals. It respects your user-specified mode while applying interactive confirmation for production-risk pipelines.

How do I route a feature creation request to the correct engineering workflow?

Routing a feature creation request uses intent classification to detect your engineering goal. It identifies the CREATE action and selects the matching workflow route to run the implementation up to a code-ready state.

Does this engineering orchestration workflow commit code or open pull requests automatically?

Engineering orchestration stops at code-ready without committing, pushing, or opening PRs. It runs the routed core implementation skill, then summarizes phases and findings so you retain full control over version control actions.

Can I use workflow routing for fixing existing features without specifying the execution mode?

Yes, workflow routing handles fixing features by classifying the intent as FIX. If you do not specify an execution mode, it automatically infers a safe depth mode—fast, balanced, or production—based on complexity and risk signals.

What do I need to set up before routing engineering changes end-to-end?

Routing engineering changes requires YAML-defined naming and description entry to classify intent accurately. You provide your engineering goal, and the orchestration skill resolves the mode and routes to the core implementation skill.