follow-up-planner

Name: follow-up-planner
Author: Xuxchloris

17stars2forks

How to install follow-up-planner?

xuxchloris/export_skills/follow-up-planner

$npx -y skills add Xuxchloris/export_skills --skill follow-up-planner

Installs into the current project.

Summary

Use when a trade agent needs outreach follow-up timing, next-touch planning, reminder schedules, buyer reply follow-up, quotation follow-up, sample follow-up, or prospect status updates

Files · 1

View on GitHub

SKILL.md

1	# Follow-Up Planner
2
3	## Overview
4
5	Create a practical follow-up schedule from prospect priority and reply status. The core rule is to generate reviewable tasks, not automatic sends.
6
7	## When to Use
8
9	Use this skill after an outreach draft, buyer reply classification, quotation draft, sample discussion, or meeting request when the user needs the next-touch plan.
10
11	Use `reply-classification` first when an inbound reply has not been classified.
12
13	## Inputs
14
15	- Prospect priority from `prospect-scoring`
16	- Last contact date and channel
17	- Reply classification, if available
18	- Quotation, catalog, sample, or meeting status
19	- Tone rules from `TONE.yaml`
20
21	## Outputs
22
23	```json
24	{
25	"prospect_status": "",
26	"last_contact_date": "",
27	"tasks": [
28	{
29	"due_date": "",
30	"task_type": "",
31	"reason": "",
32	"draft_requested": false,
33	"human_review_required": true
34	}
35	],
36	"pause_reason": "",
37	"review_notes": []
38	}
39	```
40
41	## Procedure
42
43	1. Read the prospect priority, last contact date, and latest reply classification.
44	2. Pause planning when the prospect status does not call for another touch.
45	3. For an unanswered A or B prospect, suggest a light sequence such as D+3, D+7, and D+14 from the first outreach date.
46	4. For a quotation, catalog, sample, or meeting discussion, plan the next touch from the latest buyer-facing action.
47	5. Keep each task specific: due date, task type, reason, and whether an email draft is needed.
48	6. Send email draft requests to `email-crafting`.
49	7. Keep every task as a human-reviewed reminder.
50
51	## Verification
52
53	- Due dates are derived from the latest relevant contact.
54	- Task reasons match prospect status and buyer signals.
55	- Paused prospects receive no new follow-up task.
56	- The plan does not send messages automatically.
57	- Every generated task requires human review.
58
59	## Common Mistakes
60
61	\| Mistake \| Fix \|
62	\| --- \| --- \|
63	\| Scheduling from an old contact date \| Use the latest relevant action \|
64	\| Giving every prospect the same cadence \| Consider priority and reply type \|
65	\| Creating vague reminders \| Include due date, reason, and task type \|
66	\| Treating a task as an automatic send \| Keep it as a human-reviewed reminder \|

People who liked this also viewed

6 picks

Type

follow-up-planner

17stars2forks

View on GitHub

How to install follow-up-planner?

xuxchloris/export_skills/follow-up-planner

$npx -y skills add Xuxchloris/export_skills --skill follow-up-planner

Installs into the current project.

Summary

Use when a trade agent needs outreach follow-up timing, next-touch planning, reminder schedules, buyer reply follow-up, quotation follow-up, sample follow-up, or prospect status updates

Files · 1

View on GitHub

SKILL.md

1	# Follow-Up Planner
2
3	## Overview
4
5	Create a practical follow-up schedule from prospect priority and reply status. The core rule is to generate reviewable tasks, not automatic sends.
6
7	## When to Use
8
9	Use this skill after an outreach draft, buyer reply classification, quotation draft, sample discussion, or meeting request when the user needs the next-touch plan.
10
11	Use `reply-classification` first when an inbound reply has not been classified.
12
13	## Inputs
14
15	- Prospect priority from `prospect-scoring`
16	- Last contact date and channel
17	- Reply classification, if available
18	- Quotation, catalog, sample, or meeting status
19	- Tone rules from `TONE.yaml`
20
21	## Outputs
22
23	```json
24	{
25	"prospect_status": "",
26	"last_contact_date": "",
27	"tasks": [
28	{
29	"due_date": "",
30	"task_type": "",
31	"reason": "",
32	"draft_requested": false,
33	"human_review_required": true
34	}
35	],
36	"pause_reason": "",
37	"review_notes": []
38	}
39	```
40
41	## Procedure
42
43	1. Read the prospect priority, last contact date, and latest reply classification.
44	2. Pause planning when the prospect status does not call for another touch.
45	3. For an unanswered A or B prospect, suggest a light sequence such as D+3, D+7, and D+14 from the first outreach date.
46	4. For a quotation, catalog, sample, or meeting discussion, plan the next touch from the latest buyer-facing action.
47	5. Keep each task specific: due date, task type, reason, and whether an email draft is needed.
48	6. Send email draft requests to `email-crafting`.
49	7. Keep every task as a human-reviewed reminder.
50
51	## Verification
52
53	- Due dates are derived from the latest relevant contact.
54	- Task reasons match prospect status and buyer signals.
55	- Paused prospects receive no new follow-up task.
56	- The plan does not send messages automatically.
57	- Every generated task requires human review.
58
59	## Common Mistakes
60
61	\| Mistake \| Fix \|
62	\| --- \| --- \|
63	\| Scheduling from an old contact date \| Use the latest relevant action \|
64	\| Giving every prospect the same cadence \| Consider priority and reply type \|
65	\| Creating vague reminders \| Include due date, reason, and task type \|
66	\| Treating a task as an automatic send \| Keep it as a human-reviewed reminder \|

People who liked this also viewed

6 picks

Type