feature-implementation-workflow

Organize full-stack feature development into five phase-driven steps.

1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/CatOfJupit3r/ultimate-starter --skill feature-implementation-workflow-catofjupit3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implementation-workflow
Source: https://github.com/CatOfJupit3r/ultimate-starter/tree/main/.github/skills/feature-implementation-workflow
Command: npx skills add https://github.com/CatOfJupit3r/ultimate-starter --skill feature-implementation-workflow-catofjupit3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow breaks down complex feature development into defined phases, reducing miscommunication and rework by aligning backend, contracts, and frontend work early.

Core Features & Use Cases

  • Phase-based guidance for end-to-end feature delivery across five stages: foundation, backend, frontend queries, frontend components, and testing.
  • Encourages contract-first development, type-safety checks, and progressive integration to ensure alignment between server and client teams.
  • Useful for teams starting new features, coordinating cross-cutting work, and standardizing handoffs from design to production.

Quick Start

Choose a phase to begin and follow the guided prompts to execute the workflow.

Frequently Asked Questions about feature-implementation-workflow

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

FAQPage Schema
What is contract-first full-stack feature development?

Contract-first full-stack feature development defines type-safe contracts before implementation to align server and client teams. This phase-driven approach reduces miscommunication and rework by coordinating foundation, backend, frontend, and testing stages.

How do I coordinate full-stack feature development across backend and frontend?

Coordinate full-stack feature development by organizing tasks into five progressive phases: foundation, backend, frontend queries, frontend components, and testing. This workflow links contracts, services, routers, and UI components to ensure progressive delivery.

What's the best way to reduce rework when integrating frontend and backend work?

To reduce rework when integrating frontend and backend work, use a phase-based workflow with contract-first design. Aligning server and client teams early through type-safe contracts prevents miscommunication and standardizes handoffs from design to production.

Does this phase-based workflow apply to existing features or only new feature development?

This phase-based workflow applies when starting a new feature or integrating backend and frontend work. It enforces phase-specific checks like check-types, lint, prettier, and tests to ensure type-safe contracts and progressive delivery across the stack.

How do I enforce type-safe checks across full-stack feature phases?

You enforce type-safe checks across full-stack feature phases by applying phase-specific checks at each stage. The workflow integrates check-types, lint, prettier, and tests within its five phases to link contracts, services, routers, and UI components progressively.