develop

Fetch the next ready-to-develop ticket and run the full development pipeline.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill develop-yves-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/yves-s/just-ship/tree/main/skills/develop
Command: npx skills add https://github.com/yves-s/just-ship --skill develop-yves-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual ticket triage and development steps require repeated human intervention, slowing delivery and introducing errors.

Core Features & Use Cases

  • Automated ticket selection: Retrieves the next ready-to-develop ticket from the board or Supabase.
  • End-to-end pipeline: Creates a feature branch, runs build checks, code review, QA, documentation updates, and opens a pull request.
  • Integration flexibility: Works with Board API, legacy Supabase MCP, or standalone mode, handling various project configurations.

Quick Start

Run the /develop command to automatically fetch the next ready ticket and launch the full development workflow.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I automate fetching the next ready ticket and generating a pull request?

Automate ticket triage by running a command that retrieves the next ready-to-develop ticket, creates a worktree, runs build checks, performs code review, and opens a pull request autonomously.

What is an autonomous development workflow for ticket implementation?

An autonomous development workflow retrieves a ready ticket, creates a worktree, runs build checks, executes code review and QA, updates documentation, and generates a pull request without manual intervention.

Do I need board API credentials to automate ticket implementation?

Yes, you need board API credentials to automate ticket implementation, though the workflow also supports legacy Supabase MCP or standalone mode depending on your project configuration.

How does the automated code review process work within the pipeline?

The automated code review process works by executing review checks immediately after build checks pass, ensuring code quality before the pipeline proceeds to QA and pull request generation.

Can I use git worktree creation for isolated ticket development?

Yes, you can use git worktree creation for isolated ticket development, as the pipeline explicitly coordinates worktree creation to manage feature branches for the implemented ticket.

What are the limitations of standalone mode for automated ticket development?

In standalone mode, automated ticket development operates without board API or Supabase MCP integration, meaning ticket selection must be handled differently than the default ready-to-develop retrieval.