start-task

Detect task identifiers, sync the main branch, and create a named branch with saved context.

41|15|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/foyzulkarim/skills --skill start-task-foyzulkarim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-task
Source: https://github.com/foyzulkarim/skills/tree/main/dev-pipeline/skills/start-task
Command: npx skills add https://github.com/foyzulkarim/skills --skill start-task-foyzulkarim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual setup of feature branches by detecting task identifiers, gathering context, syncing from the main branch, and persisting the information developers need before planning work.

Core Features & Use Cases

  • Task detection and confirmation: It parses Jira ticket keys, GitHub numbers, and local files in order, confirms the source with the developer, and fetches the details using the proper CLI tools before continuing.
  • Branch orchestration: It inspects the current branch, syncs the default branch, sanitizes the slug, proposes a conventional branch name, creates the branch, and pushes it with guardrails against data loss.
  • Context persistence: It writes or updates /specs/context/{identifier}.md with the task identifier, title, type, sources, notes, and timestamps so downstream skills and future sessions inherit the context. Use Case: Onboarding a Jira ticket before planning, during which the skill gathers the tracker description, confirms the type and title, and leaves a clean branch ready for /plan-feature.

Quick Start

Ask start-task to detect the ticket key, pull the latest main, and create the synced feature branch with saved context.

Frequently Asked Questions about start-task

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

FAQPage Schema
How do I create a feature branch from a Jira ticket automatically?

To create a feature branch from a Jira ticket automatically, this skill detects the ticket key, fetches tracker context via CLI, syncs the default branch, sanitizes the slug, and pushes the correctly named branch.

What is the best way to sync local context when starting a new GitHub task?

The best way to sync local context for a GitHub task is to parse the GitHub issue number, confirm the source, and persist task details, sources, and timestamps to a local context file.

How do I bootstrap an ad-hoc task branch without manual git setup?

Bootstrapping an ad-hoc task branch without manual git setup involves detecting the local task identifier, applying slug sanitization rules, proposing a conventional branch name, and creating the branch with data loss guardrails.

Does branch creation work with existing local task files?

Yes, branch creation works with existing local task files by parsing them in order alongside Jira ticket keys and GitHub numbers, confirming the source with the developer, and applying slug sanitization before branch creation.

Why do I need to persist task context before planning feature implementation?

You need to persist task context before planning feature implementation so downstream skills and future sessions inherit the task identifier, title, type, sources, notes, and timestamps automatically.

Do I need specific CLI tools installed to detect task identifiers and create branches?

Yes, you need specific CLI tools installed because the skill performs CLI availability checks before fetching tracker descriptions, confirming task types, and executing branch orchestration and push commands.