skills.rest
Honigbart
HonigbartCOMMUNITY
Explore all skills by this author →
GitHub

follow-up

Track durable follow-ups from active and archived plans in a central registry.

1|Updated Apr 6, 2026
Search Tags:#workflow#planning#registry#follow-ups#artifact-tracking#plan-management
One-click install
npx skills add https://github.com/Honigbart/honeyflow --skill follow-up-honigbart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: follow-up
Source: https://github.com/Honigbart/honeyflow/tree/main/follow-up
Command: npx skills add https://github.com/Honigbart/honeyflow --skill follow-up-honigbart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manage durable follow-on artifacts generated from active and archived final plans by maintaining a single source of truth in the .ai/follow_ups.md registry. This enables teams to surface open work, start new plans, and close items without rescanning every archived plan.

Core Features & Use Cases

  • Registry-driven tracking: Uses .ai/follow_ups.md as the authoritative working registry.
  • Plan-to-follow-up surface: Aggregates follow-ons from .ai/plans/*/final_plan.md and .ai/archive/*/final_plan.md into actionable items.
  • Workflow stages: Move items through Open, Started, Done, Superseded, and Dropped, with provenance preserved.
  • Create and link: Start a follow-up as a new quick-plan or brainstorm, linking it to a plan when needed.

Quick Start

Start by listing open follow-ups and selecting one to act on

Frequently Asked Questions about follow-up

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

FAQPage Schema
How do I track durable follow-ups from archived plans without rescanning everything?▼

Use a central registry in .ai/follow_ups.md to track durable follow-ups from archived plans, aggregating items from final_plan.md files without rescanning every archive to find unresolved work.

What is the best way to manage workflow stages for plan follow-ups?▼

Manage workflow stages by moving follow-up items through Open, Started, Done, Superseded, and Dropped sections within the registry, ensuring provenance and plan linkage are preserved across transitions.

How do I turn an unresolved follow-up into a new plan?▼

Create a new quick-plan or brainstorm directly from an open follow-up item in the registry, linking the new plan to the original source to maintain provenance and traceability.

Can I track follow-on artifacts from both active and archived final plans?▼

Yes, follow-on artifacts are aggregated from both .ai/plans/*/final_plan.md and .ai/archive/*/final_plan.md files into the central registry to provide a unified view of actionable items.

Do I need a registry to maintain provenance for plan follow-ups?▼

Yes, the .ai/follow_ups.md registry enforces provenance by deriving stable IDs from plan sources and preserving plan linkage when follow-ups transition between Open, Started, Done, Superseded, or Dropped states.

Related Skills

Explore More Product & Management Skills→
HonigbartHonigbart
1

autopilot

Automate end-to-end plan execution and review across all phases.

Community
Advanced
Spectra29115Spectra29115

follow-up-tasks

Categorize and propose follow-up tasks linked to the original task.

Community
Intermediate
HonigbartHonigbart
1

quick-critique

Critique final_plan.md files with Codex CLI and write critique reports.

Community
Intermediate
maxculen86maxculen86

skill-registry

Scan SKILL.md files and persist a deduplicated registry to .atl/skill-registry.md.

Community
Intermediate