task

Automates governance-driven ad-hoc task creation and tracking in GSE-One sprint workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executive teams and developers often need to run tasks outside the standard lifecycle while preserving governance, traceability, and alignment with sprint plans. This Skill provides a controlled ad-hoc task workflow that integrates with backlog, sprint budgets, and git history to ensure accountability and repeatability.

Core Features & Use Cases

  • Ad-hoc invocation: Trigger /gse:task to create a governed ad-hoc task within the current sprint.
  • Backlog & sprint alignment: Automatically generate backlog entries and track artefact typing and traces.
  • Budget, risk & scope gates: Validate complexity, apply budget constraints, and perform scope reconciliation before finalization.
  • Use Case: A developer needs a quick hotfix or exploratory analysis outside the standard flow, while staying within governance.

Quick Start

Invoke /gse:task to start a new ad-hoc task under the current sprint governance.

Frequently Asked Questions about task

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

FAQPage Schema
How do I create an ad-hoc task without breaking sprint governance?

To create an ad-hoc task without breaking sprint governance, invoke the task command to generate a backlog entry with explicit artefact typing, complexity estimation, and scope reconciliation within the current sprint budget.

What is governance-driven ad-hoc task tracking in a sprint workflow?

Governance-driven ad-hoc task tracking is the process of logging out-of-band work into a sprint-backed workflow, ensuring traceability through artefact typing, backlog integration, and budget validation for accountability.

How do I handle a hotfix that falls outside the standard development lifecycle?

To handle a hotfix outside the standard lifecycle, use an ad-hoc task workflow that integrates with git history and sprint budgets, applying complexity estimation and finalization steps to maintain traceability.

Does ad-hoc task creation apply complexity estimation and scope reconciliation?

Yes, ad-hoc task creation applies complexity estimation and scope reconciliation by validating task complexity, applying budget constraints, and ensuring finalization steps align with the current sprint backlog.

Can I perform exploratory analysis while staying aligned with sprint budgets?

You can perform exploratory analysis while staying aligned with sprint budgets by triggering a governed ad-hoc task, which automatically logs the work as a backlog entry and validates it against sprint budget constraints.

What are the limitations of using ad-hoc tasks for backlog management?

Ad-hoc tasks for backlog management require explicit artefact typing and finalization steps per the spec, meaning work cannot bypass governance gates, complexity estimation, or scope reconciliation before completion.