follow-up-tasks

Generate structured follow-up tasks linked to parent project tasks.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/KartikSharma4448/aegiscare --skill follow-up-tasks-kartiksharma4448
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: follow-up-tasks
Source: https://github.com/KartikSharma4448/aegiscare/tree/main/frontend/.local/skills/follow-up-tasks
Command: npx skills add https://github.com/KartikSharma4448/aegiscare --skill follow-up-tasks-kartiksharma4448

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This task management helper helps teams identify and formalize the follow-up work needed to complete a task, ensuring nothing is overlooked before closure.

Core Features & Use Cases

  • Structured follow-ups: Create clearly defined tasks categorized as incomplete_scope, next_steps, tech_debt, or test_gaps to extend work without duplicating effort.
  • Quality guidance: Ensure every follow-up title is understandable to non-technical stakeholders, with guidance on wording and impact.
  • Linked delivery: Each proposed follow-up is linked to the parent task to maintain a coherent task hierarchy and traceability.

Quick Start

Propose up to 3 high-impact follow-up tasks linked to the current task with titles, descriptions, and a category.

Frequently Asked Questions about follow-up-tasks

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

FAQPage Schema
How do I generate follow-up tasks before closing a project task?

To generate follow-up tasks, the helper proposes up to three high-impact items linked to the parent task, each requiring a title, a category like tech_debt or test_gaps, and a concise description to extend work before closure.

What is structured follow-up task management for project workflows?

Structured follow-up task management is the process of formalizing remaining project work into categorized items like incomplete_scope or next_steps, ensuring nothing is overlooked before a task is marked complete.

Can I use this for software development, documentation, and research projects?

Yes, you can use this for software development, documentation, and research projects. It applies to any project task where related tasks exist beyond the initial deliverable and need to be linked to the parent task.

What categories can I assign to follow-up tasks?

You can assign follow-up tasks to four allowed category slugs: incomplete_scope, next_steps, tech_debt, or test_gaps. Each category helps classify the nature of the remaining work.

What's the best way to write follow-up task titles for non-technical stakeholders?

The best way to write follow-up titles for non-technical stakeholders is to follow the built-in quality guidance, ensuring every title is understandable by emphasizing clear wording and impact.

How does linking follow-up tasks to a parent task work?

Linking follow-up tasks maintains a coherent task hierarchy and traceability by connecting each proposed item directly to the parent task, ensuring extended work is tracked within the project workflow.