ship-feature

Implement end-to-end features across API, backend, frontend, and integration layers with validation.

2|Updated Apr 3, 2026

Search Tags:#architecture #documentation #validation #implementation #end-to-end #feature

Ready to run

npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill ship-feature-kscius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship-feature
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/ship-feature
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill ship-feature-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses the need for building and delivering features end-to-end, spanning frontend, backend, and integration layers, with built-in validation and documentation.

Core Features & Use Cases

End-to-end feature implementation across all affected layers, aligned with project rules and architecture.
Thorough validation, including linting, typechecking, tests, builds, and necessary migrations.
Documentation updates and knowledge transfer to ensure maintainability and onboarding.
Use Case: when a product requires a new capability from design through deployment and monitoring.

Quick Start

Inspect the repository and architecture, implement the feature end-to-end, validate thoroughly, and update docs to ship the feature.

Frequently Asked Questions about ship-feature

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

FAQPage Schema

How do I implement a feature end-to-end across API, backend, and frontend layers?▼

End-to-end feature implementation coordinates reconnaissance, planning, cross-layer coding, and verification across API, backend, frontend, and integration tasks to build and deliver the feature. It validates linting, types, and builds throughout the process.

What is the best way to ensure new feature code passes linting, type checks, and tests?▼

Validating feature delivery requires running linting, type checks, tests, and builds at every implementation step. This approach catches integration errors early and ensures the codebase meets project rules and architecture requirements before shipping.

How do I handle database migrations and documentation updates when adding a new feature?▼

Feature delivery includes executing necessary database migrations and updating documentation alongside code changes. This ensures maintainability, supports onboarding, and provides traceable results across the entire stack.

Can I use an automated workflow for cross-layer implementation and robust error handling?▼

Yes, automated feature delivery applies cross-layer implementation with robust error handling. It coordinates changes across frontend, backend, and integration layers while validating at each step to ensure traceable and reliable results.

Does end-to-end feature delivery work for existing codebases with established architecture?▼

End-to-end feature implementation inspects the existing repository and architecture before coding. It aligns new capabilities with established project rules, applying changes across all affected layers while meeting validation requirements.