# Socialseal Follow Up Planning

> Use this skill when the user asks to turn a SocialSeal meeting, report, recommendation set, or review into actions; assign owners/due dates; schedule the next refresh; or prepare the next-cycle agenda. Produce an operational follow-up plan with dependencies, acceptance criteria, open questions, and measurement checkpoints.

- Skill: `opensealai/socialseal-follow-up-planning` (Agent Skill)
- Install (CLI): `npx skillmds@latest add opensealai/socialseal-follow-up-planning`
- Raw SKILL.md: https://api.skillmd.com/api/skills/opensealai/socialseal-follow-up-planning/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: MIT
- Author: OpenSealAI (https://skillmd.com/u/opensealai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/opensealai/socialseal-follow-up-planning

---


# SocialSeal Follow-Up Planning

## Overview

Follow-up planning prevents SocialSeal work from ending as a report. It turns decisions into content actions, tracking actions, and measurement checkpoints.

## Inputs

- meeting notes, readout, or recommendations
- owner list or responsible teams
- next review date or reporting cadence
- data refresh requirements
- open questions and deferred decisions

## Workflow

1. **Extract decisions.** Separate confirmed decisions from suggestions and open questions.
2. **Create action types.** Content brief, concept, asset capture, tracking update, export refresh, analysis, stakeholder decision.
3. **Assign one owner.** Each action has one directly responsible owner.
4. **Add due date and dependency.** Include data refresh timing before analysis deadlines.
5. **Define acceptance.** What makes the action done?
6. **Schedule measurement.** Which export or tracking group will confirm progress next cycle?
7. **Write the follow-up summary.** Short enough to send after a meeting.

## Output

- action plan with owner/due date/status
- next data refresh schedule
- next review agenda
- open-question log
- measurement checkpoints

## Do / Don't

Do:

- distinguish content actions from tracking/data actions
- assign one owner per action
- schedule data refresh before analysis work
- keep deferred decisions visible

Don't:

- create ownerless actions
- turn follow-up into posting operations
- schedule review before data will exist
- lose the link between recommendations and next measurement

## Troubleshooting

- If there are too many actions, rank by impact and due date.
- If ownership is unclear, mark as “needs owner” and do not pretend it is assigned.
- If the next review lacks a measurement source, add a tracking/export action first.

## Verification Checklist

- [ ] Every action has type, owner, due date, and done definition.
- [ ] Data refresh is scheduled before the next analysis/readout.
- [ ] Open questions are recorded.
- [ ] Next review agenda is clear.
- [ ] Measurement checkpoints map back to recommendations.