start-work

Validate GitHub issue relevance and update status to In progress.

6|Updated Oct 7, 2025
One-click install
npx skills add https://github.com/rjroy/vibe-garden --skill start-work-rjroy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-work
Source: https://github.com/rjroy/vibe-garden/tree/main/compass-rose/skills/start-work
Command: npx skills add https://github.com/rjroy/vibe-garden --skill start-work-rjroy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams initiate work on a GitHub Project item by validating relevance, loading full issue context, and applying XL/L escalation prompts to ensure proper planning and accurate status tracking.

Core Features & Use Cases

  • Accepts an issue number, a URL, or the keyword "next" to recommend the highest-priority ready item.
  • Loads issue details and linked context via the compass-rose gh-api-scripts, validates relevance, and updates the item status to "In progress" as work begins.
  • Enforces XL/L escalation prompts: XL items trigger formal specification prompts; L items may prompt based on preferences; S/M items proceed directly to status update.
  • Reads and displays the full issue description for context and supports subsequent codebase exploration to identify affected files.

Quick Start

Examples:

  • /compass-rose:start-work 156
  • /compass-rose:start-work https://github.com/org/repo/issues/156
  • /compass-rose:start-work next

Frequently Asked Questions about start-work

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

FAQPage Schema
How do I start work on a GitHub project issue and load its full context?

To start work on a GitHub project issue, you can provide a specific issue number or URL to validate relevance, load full context, and automatically update the item status to In progress.

How do I automatically select the next ready item from a GitHub project?

You can automatically select the next ready GitHub project item by using the keyword "next," which recommends and loads the highest-priority ready item for implementation.

What happens when I start work on an XL or L size GitHub issue?

Starting work on an XL GitHub issue triggers formal specification escalation prompts, while L items may prompt based on preferences; S and M items proceed directly to a status update.

Do I need the compass-rose gh-api-scripts to load GitHub issue details?

Yes, loading GitHub issue details and linked context relies on the compass-rose gh-api-scripts skill to execute the necessary API calls and read the full issue body.

Can I use a GitHub issue URL to kick off project work and update its status?

Yes, you can pass a direct GitHub issue URL to validate the item, load its full context, apply any required escalation prompts, and update the status to In progress.

What is the best way to enforce size-based escalation prompts for GitHub project management?

The best way to enforce escalation prompts is to trigger size checks when starting work; XL items require formal specification prompts, while L items conditionally prompt before proceeding.