What problem does it solve? When completing a development task, related work often gets noticed but forgotten — deferred scope, tech debt, missing tests, and logical next steps. This Skill ensures that work is captured as structured, actionable follow-up tasks linked to the current task before it is marked complete. ## Core Features & Use Cases - Categorized Follow-Ups: Classifies proposed work into incomplete_scope, next_steps, tech_debt, or test_gaps for clear prioritization. - Non-Technical Titles: Guides rewriting task titles so non-technical stakeholders understand the impact, not the implementation. - Task Hierarchy Linking: Uses the proposeFollowUpTasks callback to automatically link follow-ups to the current task as parent, and markFollowUpTaskObsolete to retire stale proposals. - Use Case: After building a recipe page with hardcoded data, propose a follow-up like "Save recipes permanently so they aren't lost on refresh" with file paths and done-criteria so another agent can pick it up independently. ## Quick Start Before marking your current task complete, propose up to three follow-up tasks with categories and detailed descriptions using the proposeFollowUpTasks callback.
