task-enrich

Enrich task descriptions with What, Where, How, Why, and Verify elements.

9|Updated Aug 20, 2018
One-click install
npx skills add https://github.com/berlysia/dotfiles --skill task-enrich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-enrich
Source: https://github.com/berlysia/dotfiles/tree/main/.skills/task-enrich
Command: npx skills add https://github.com/berlysia/dotfiles --skill task-enrich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task descriptions often lack explicit self-contained context, causing misinterpretation during handoffs or cross-team work. This Skill verifies and enriches each task description so it can be executed without relying on prior conversations or shared context.

Core Features & Use Cases

  • Validates that each task description includes What, Where, How, Why, and Verify elements.
  • Enriches descriptions by adding missing context and concrete execution instructions.
  • Supports task-wide handoffs, QA reviews, and cross-functional collaboration by producing independent task narratives.

Quick Start

Run the task-enrich workflow after task creation to validate and expand each description so it is self-contained.

Frequently Asked Questions about task-enrich

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

FAQPage Schema
How do I make task descriptions self-contained for autonomous handoffs?

To make task descriptions self-contained for handoffs, you need to enrich each task with explicit context. This involves validating that every description includes What, Where, How, Why, and Verify elements so it can be executed without relying on prior conversations.

What elements should a task description include for cross-team execution?

A task description for cross-team execution should include What, Where, How, Why, and Verify elements. Defining these elements ensures independent execution by providing concrete instructions and explicit context without needing shared knowledge.

How do I enrich task descriptions to prevent misinterpretation during QA reviews?

You can enrich task descriptions to prevent QA misinterpretation by adding missing context and concrete execution instructions. This process updates descriptions to enforce self-contained narratives, ensuring quality assurance reviews have independent execution criteria.

Does task enrichment work for any task list used for independent execution?

Yes, task enrichment works for any task list used for handoffs, QA, or collaboration where independent execution is required. It assesses and enriches each task description regardless of the specific project to ensure independent execution without external context.

What is the best way to validate task context before a cross-functional handoff?

The best way to validate task context before a cross-functional handoff is to verify the inclusion of What, Where, How, Why, and Verify elements. This validation produces a completion checklist and updates descriptions to remove reliance on shared context.