dev-pipeline

Stage, draft, and execute a conventional commit. Use this command when you want to commit changes at any point in your workflow — after writing plan docs, mid-TDD, after fixing review findings, or any ad-hoc change. Inspects git state, helps you decide what to stage, drafts a conventional commit message with type, optional task scope, and description, then executes after your confirmation.

Generate TDD-ready task specs from a feature plan. Use this skill when the user wants to create a detailed, TDD-ready task specification — either from an existing feature plan artifact or from a brief description of a simple, well-understood task — before implementation begins. This skill has a collaborative conversation with the user to understand the plan, draft a test plan, and produce task specs embedded directly in the plan document. It does NOT write implementation code, and it does NOT gather requirements (that is the plan-feature skill's job).

Plan a single feature — uncovers requirements, edge cases, and constraints before coding. Use this skill when the user wants to plan a single feature, endpoint, infrastructure piece, or any focused unit of work before implementation begins. This skill conducts a Socratic conversation to uncover requirements, edge cases, failure modes, and design decisions, then produces a feature plan artifact. It does NOT plan entire projects (that is the plan-project skill's job), and it does NOT write code or generate task specs.

Plan a new project or major epic — explores the domain and decomposes into phased features. Use this skill when the user wants to plan a new project, a major epic, or any body of work that spans multiple features. This skill conducts a structured conversation to define system boundaries, architecture direction, phase breakdown, and feature decomposition — then produces a project plan artifact. It does NOT plan individual features in depth (that is the plan-feature skill's job), and it does NOT write code or generate task specs.

Review and verify code before merge — triage-first with up to 16 checks. Use this skill when the user wants to review and verify implemented code before considering a task complete or opening a PR. This skill triages what checks are relevant, then runs only the selected checks as parallel agents and produces a combined report. It supports two modes: pipeline review (verifying task implementation against a plan) and general review (PR, branch, or staged changes). It does NOT write or fix code — it flags findings for the developer to address.

Start a new task by creating a synced feature branch. Pulls latest main, gathers task context from Jira, GitHub, or local specs, then creates and pushes a branch with the pattern {type}/{task-number}/{slug}. Use this skill only when the user explicitly asks to start a new task or create a new branch for work — do not trigger automatically.

Implement a task spec via RED-GREEN-REFACTOR, one test at a time. Use this skill when the user wants to implement a task specification using test-driven development. Supports two modes: collaborative (default, pauses at every red/green) and auto (runs through all tests autonomously). It does NOT plan features or generate task specs (those are upstream skills). Arguments: Pass 'auto' to run autonomously without pausing for confirmation. Default is collaborative mode.