task

Execute development tasks with branch creation, coding, and conventional commits.

294|54|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/owainlewis/blueprint --skill task-owainlewis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/owainlewis/blueprint/tree/main/skills/task
Command: npx skills add https://github.com/owainlewis/blueprint --skill task-owainlewis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of picking up, executing, and marking development tasks as complete, ensuring efficient workflow management.

Core Features & Use Cases

  • Task Execution: Handles tasks described by ticket IDs or plain text descriptions.
  • Branch Management: Creates conventionally named branches for new work.
  • Commit Automation: Stages and commits code with conventional commit messages.
  • Status Updates: Updates task status in project management tools or informs the user.
  • Use Case: A developer receives a ticket LIN-123 to implement user authentication. They use this Skill to create a branch, perform the work, commit the changes, and mark the ticket as done.

Quick Start

Use the task skill to execute ticket GH-42 and add user authentication.

Frequently Asked Questions about task

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

FAQPage Schema
How do I automate git branching and committing for a specific issue tracking ticket?

You can automate git branching and committing by providing an issue tracking ticket ID to execute the development task. The skill creates a conventionally named branch, writes the code, and stages the changes using conventional commit standards.

Can I execute a development task from a plain text description instead of a ticket ID?

Yes, you can execute a development task using a direct plain text description instead of a ticket ID. The skill manages the branching, coding, and commit processes based on the provided textual description.

How does conventional commit integration work when finalizing a development workflow?

Conventional commit integration works by automatically staging and committing code changes with standardized commit messages. This ensures your development workflow adheres to conventional commit standards upon task completion.

Does this development workflow tool update issue tracking status automatically?

Yes, the development workflow tool updates issue tracking status automatically upon completion. If direct integration is unavailable, it informs the user so the ticket status can be updated manually.

What is the best way to manage a full development workflow from ticket pickup to commit?

The best way to manage a development workflow is to pass the ticket ID to the skill, which handles task execution from branch creation through coding to the final commit. This streamlines picking up, executing, and marking development tasks as complete.