start-task

Start backlog tasks by generating branches and task checklists.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/weselow/Telegram-support-bot --skill start-task-weselow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-task
Source: https://github.com/weselow/Telegram-support-bot/tree/main/.claude/skills/start-task
Command: npx skills add https://github.com/weselow/Telegram-support-bot --skill start-task-weselow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines kicking off work on backlog items by standardizing task intake, classification, and initial task scaffolding across projects.

Core Features & Use Cases

  • Backlog item discovery & classification: determines whether the task is a normal backlog task or a technical debt task based on its path and context.
  • Branch naming & setup: creates the appropriate feature or fix branch naming convention and prepares structure for the task.
  • Validation & governance: checks alignment with the backlog workflow standard and ensures required steps like code review are planned.

Quick Start

Start the task workflow by instructing the skill to process the backlog item at the specified path and follow the standard branch naming rules.

Frequently Asked Questions about start-task

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

FAQPage Schema
How do I standardize backlog task intake and branch creation for project management?

Standardize backlog task intake by processing items located under docs/backlog to classify tasks, generate task-specific branches, and produce a task checklist for validation and code review.

How does branch management work for technical debt versus regular backlog tasks?

Branch management handles technical debt and regular tasks by determining the task type from its path context and creating the appropriate feature or fix branch naming convention automatically.

What's the best way to enforce code review and validation steps when starting backlog work?

Enforce code review and validation by applying the backlog workflow standard during task intake, which checks alignment and ensures required steps like code review are planned before work begins.

Can I use this standardized task flow for nested subfolders within my project backlog?

Yes, the standardized task flow applies to backlog items located under docs/backlog and processes nested subfolders, classifying both regular tasks and technical debt with corresponding output destinations.

Do I need any specific dependencies to automate my project task management workflow?

No specific dependencies are required to automate your project task management workflow, as the skill operates standalone to enforce intake standards and generate task scaffolding.

Why should I standardize task scaffolding instead of manually creating branches and checklists?

Standardizing task scaffolding ensures consistent workflow governance across projects by automating branch naming, classification, and checklist generation, reducing manual errors and maintaining validation compliance.