skills.rest
4tie
4tieCOMMUNITY
Explore all skills by this author →
GitHub

follow-up-tasks

Identify follow-up tasks with titles, descriptions, and categories for software projects.

Updated Jun 20, 2026
Search Tags:#software engineering#technical debt#backlog#task planning#test gaps#follow-up tasks
One-click install
npx skills add https://github.com/4tie/fortiesr --skill follow-up-tasks-4tie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: follow-up-tasks
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/follow-up-tasks
Command: npx skills add https://github.com/4tie/fortiesr --skill follow-up-tasks-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finish work responsibly by spotting the most valuable follow-up tasks that should happen after the current task is done.

Core Features & Use Cases

  • Scope Control: Distinguish what was intentionally deferred from what should be planned next.
  • Next-Step Planning: Suggest user-facing improvements, refinements, and future enhancements that extend the current work.
  • Quality Checks: Surface technical debt and test gaps that would otherwise be missed during delivery.
  • Use Case: After completing a feature, use this Skill to identify a small set of high-impact follow-ups with clear titles and descriptions for the project backlog.

Quick Start

Ask the skill to review your current work and suggest up to three high-impact follow-up tasks with clear titles, descriptions, and categories.

Frequently Asked Questions about follow-up-tasks

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

FAQPage Schema
How do I identify follow-up tasks for technical debt and test gaps after finishing a feature?▼

To identify follow-up tasks, analyze your completed software delivery workflow for deferred scope and missing tests. This process surfaces technical debt and test gaps, generating actionable backlog items with relevant file paths and category labels for routing.

What is the best way to plan next-step feature opportunities from a completed project?▼

The best way to plan next-step feature opportunities is to evaluate the current project for upcoming refinements and user-facing enhancements. This distinguishes intentionally deferred work from valuable next tasks to extend the software effectively.

How do I distinguish intentionally deferred scope from tasks that should be planned next?▼

Distinguishing deferred scope from planned tasks requires evaluating your software delivery workflow against project goals. This scope control process separates intentionally delayed work from high-impact follow-up tasks needed for the backlog.

Can I generate actionable backlog items with file paths for missing tests in software engineering?▼

Yes, you can generate actionable backlog items for missing tests by reviewing your software engineering delivery workflow. This surfaces quality check tasks with clear descriptions, relevant file paths, and category labels supporting downstream task routing.

Does this approach to task planning support downstream routing for technical debt?▼

Yes, this task planning approach supports downstream routing for technical debt by applying category labels to each follow-up task. This ensures technical debt and test gaps are properly categorized for your project backlog management workflow.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-workflows.review

Review completed implementation against spec.md and update tasks.md statuses.

Community
Advanced
AugustEmnaAugustEmna

follow-up-tasks

Convert current work into categorized follow-up tasks via proposeFollowUpTasks.

Community
Intermediate
Tonybleything76Tonybleything76

Tech Debt Tracker

Scan codebases to identify, prioritize, and track technical debt.

Community
Advanced
carson-sweetcarson-sweet
6

product-parking-lot

Manage deferred product work in a file-based backlog system.

Community
Advanced