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.