follow-up-tasks

Categorize and link follow-up tasks to their parent task.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/Pixoraft/YuvaLab --skill follow-up-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: follow-up-tasks
Source: https://github.com/Pixoraft/YuvaLab/tree/main/.local/skills/follow-up-tasks
Command: npx skills add https://github.com/Pixoraft/YuvaLab --skill follow-up-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams surface and organize follow-up work after completing a task, ensuring related work isn't forgotten or misprioritized.

Core Features & Use Cases

  • Systematically categorize follow-up ideas into incomplete scope, next steps, tech debt, and test gaps.
  • Generate concise, non-technical titles suitable for stakeholders, and attach them to the parent task for traceability.
  • Use the proposeFollowUpTasks flow to submit up to three high-impact items in a single action, preserving task hierarchy and context.

Quick Start

Call proposeFollowUpTasks to submit up to three high-impact follow-up tasks linked to the current task.

Frequently Asked Questions about follow-up-tasks

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

FAQPage Schema
How do I capture follow-up tasks after completing a project milestone?

Follow-up tasks are captured by categorizing incomplete scope, desired next steps, technical debt, and test gaps, then linking them to the parent task for traceability. This ensures related work is surfaced and organized rather than forgotten.

What is the best way to link technical debt and test gaps to a parent task?

Linking technical debt and test gaps to a parent task uses a centralized flow that associates follow-up work with the original task hierarchy. It generates concise, stakeholder-friendly titles and descriptions to preserve context.

Can I submit multiple follow-up task proposals in a single action?

You can submit up to three high-impact follow-up task proposals in a single action. This workflow generates ready-to-submit items with concise titles and descriptions, maintaining the task hierarchy and linking them to the parent task.

How do I organize incomplete project scope into actionable next steps?

Organizing incomplete project scope involves systematically categorizing follow-up ideas into incomplete scope, next steps, tech debt, and test gaps. This creates ready-to-submit task proposals that are properly associated with the parent task for tracking.

Does task hierarchy get preserved when proposing follow-up work?

Task hierarchy is preserved when proposing follow-up work through a centralized flow. The generated follow-up tasks are properly associated with the parent task, ensuring context is maintained and the work is tracked through completion.

How do I generate stakeholder-friendly titles for follow-up tasks?

Generating stakeholder-friendly titles for follow-up tasks involves summarizing incomplete scope, technical debt, and test gaps into concise, non-technical descriptions. These titles are attached to the parent task to ensure traceability and clear communication.