issue-start

Automate ticket work initiation with symptom, root cause, and fix alignment.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-start-mikersays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-start
Source: https://github.com/mikersays/mikersays-plugins/tree/main/plugins/issues/skills/issue-start
Command: npx skills add https://github.com/mikersays/mikersays-plugins --skill issue-start-mikersays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the issue of misaligned implementations by ensuring that the root cause and proposed solution are agreed upon before starting work on a ticket.

Core Features & Use Cases

  • Alignment Before Implementation: Ensures all parties are aligned on the ticket's problem, proposed fix, and scope before starting work.
  • Branch Creation: Automatically creates a branch for the ticket, adhering to the project's branch naming convention.
  • INDEX.md Updates: Updates the ticket status and INDEX.md to reflect the ticket's progress to 'In progress'.
  • Companion Skill Handoff: Flags the existence of companion skills for tasks like UI bug reproduction, access verification, or project reference cards.
  • Quick Start: To begin work on ticket '0016', use the command '/issue-start 0016'.

Quick Start

To start working on ticket '0016', say: /issue-start 0016

Frequently Asked Questions about issue-start

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

FAQPage Schema
How do I ensure team alignment on a root cause hypothesis before starting ticket implementation?

To ensure alignment before implementation, you need a workflow that captures the symptom, root cause hypothesis, and proposed fix for agreement. This Skill automates that process by prompting confirmation on these details before any development work begins.

What is the best way to automate ticket file updates and branch creation in a project workflow?

Automating ticket file updates and branch creation requires a tool that reads ticket details and applies project naming conventions. This Skill automatically updates INDEX.md status to 'In progress' and generates a branch upon user alignment.

How does ticket management alignment prevent scope creep during software engineering projects?

Ticket management alignment prevents scope creep by locking in the agreed scope and proposed fix before coding starts. This Skill enforces a strict alignment checkpoint, ensuring all parties understand the root cause before implementation.

Can I use this Skill to flag companion skills for UI bug reproduction and access verification?

Yes, you can use this Skill to flag companion skills for tasks like UI bug reproduction and access verification. It automatically identifies and prompts the existence of relevant companion skills during the ticket start process.

Do I need a specific ticketing system to start working on a ticket with this workflow?

You do not need a specific external ticketing system, but your project requires ticket files and an INDEX.md. The workflow uses local ticket identifiers, such as starting ticket '0016' with the command '/issue-start 0016'.