kickoff

Fetches ticket context and routes feature work through spec, scope, and blueprint planning.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill kickoff-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kickoff
Source: https://github.com/sandsower/beislid/tree/main/skills/kickoff
Command: npx skills add https://github.com/sandsower/beislid --skill kickoff-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting work on a ticket often means manually gathering ticket details, exploring the codebase, and deciding how to plan the implementation. This Skill turns a checked-out feature branch into an approved implementation plan by orchestrating ticket fetching, codebase exploration, readiness routing, scope classification, and blueprint design before any code is written. ## Core Features & Use Cases - Ticket-to-plan pipeline: Fetches the ticket from a configured tracker (MCP, CLI, file, or paste), explores the codebase, and produces an approved design handed off to implementation. - Readiness and scope routing: Routes vague tickets through spec refinement, classifies work as atomic, single PR, multi-slice, or project, and sends large work to break-spec with human approval gates. - Config-driven workflow: Reads ticket sources, branch patterns, lifecycle actions, and policy rules from the repo-local .beislid/workflow.md, with lazy capability probing and checkpoint artifacts for context handoff. - Use Case: After checking out a feature branch for a Jira ticket, run kickoff to fetch the ticket, explore relevant code, get an approved blueprint, and post an implementation-plan comment back to the ticket. ## Quick Start Ask the agent to kick off work on the ticket for the current feature branch and produce an approved implementation plan.

Frequently Asked Questions about kickoff

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

FAQPage Schema
How do I start work on a ticket with an AI coding agent?▼

Check out the feature branch, then run kickoff. It extracts the ticket ID from the branch name, fetches the ticket body from your configured tracker, explores the codebase, and produces an approved implementation plan before any code is written.

How does kickoff decide between spec, blueprint, and break-spec?▼

Kickoff routes vague requirements to spec for refinement, classifies clear work with a scope classifier, and sends multi-slice or project-scale work to break-spec. Atomic or single-PR work goes directly to blueprint for implementation design.

What ticket trackers does kickoff support?▼

Kickoff supports MCP tools, CLI commands, local files, and manual paste as ticket sources, all configured in .beislid/workflow.md. If fetching fails, it falls back to a strict manual paste of the ticket title, body, and acceptance criteria.

What happens if .beislid/workflow.md is missing?▼

Kickoff hard-fails and stops, instructing you to run /setup to create the config or restore it. It will not continue without a valid workflow.md whose first line is the beislid-workflow v1 marker.

When should I not use kickoff?▼

Do not use kickoff for creating PRs, handling review or QA feedback, or handing off completed work. Use ready-for-review or review-response for those stages of the lifecycle.