task

Automate ad-hoc task lifecycle stages within the GSE-One workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill task-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/task
Command: npx skills add https://github.com/tjisousa/gensem --skill task-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ad-hoc tasks often fall outside the defined lifecycle, causing backlogs to stagnate and sprint budgets to overflow. This Skill automates the end-to-end lifecycle for ad-hoc work within GSE-One, including analysis, backlog entry, sprint validation, git setup, and finalization, while enforcing governance and guardrails.

Core Features & Use Cases

  • Automates analysis, artefact_type inference, and complexity estimation for ad-hoc tasks.
  • Creates backlog entries, validates sprint budgets, and configures git branches/worktrees for execution.
  • Supports spike handling, scope reconciliation, and finalization to ensure governance and traceability.

Quick Start

Describe an ad-hoc task to be added to the current sprint backlog.

Frequently Asked Questions about task

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

FAQPage Schema
How do I automate ad-hoc task lifecycle management within a sprint workflow?

Automating ad-hoc task lifecycle management involves analyzing tasks, inferring artefact types, estimating complexity, and validating sprint budgets. This Skill handles end-to-end execution by enforcing guardrails from backlog creation through git setup to finalization.

What is artefact_type inference and how does it work for backlog creation?

Artefact_type inference automatically determines the classification of an ad-hoc task during analysis. It supports backlog creation by categorizing work items accurately before they enter the sprint workflow.

How do I configure git branches and worktrees for ad-hoc sprint tasks?

Configuring git branches and worktrees for ad-hoc tasks is handled automatically during execution. The Skill sets up the required git infrastructure after validating sprint budgets, ensuring proper version control structure before development.

Can I validate sprint budgets before adding ad-hoc tasks to the backlog?

Yes, sprint budget validation is enforced before finalizing ad-hoc tasks. The Skill checks capacity constraints during backlog entry to prevent budget overflows and reconcile scope against existing sprint commitments.

How does spike handling work for ad-hoc tasks in a sprint?

Spike handling for ad-hoc tasks follows specific rules enforced during analysis and scope reconciliation. The Skill ensures spikes are properly categorized and governed, maintaining traceability throughout the sprint lifecycle.

When should I use scope reconciliation for ad-hoc task finalization?

Scope reconciliation should be used during ad-hoc task finalization to ensure governance and traceability. It prevents backlogs from stagnating by verifying completed work aligns with sprint budgets before closure.