planner

Name: planner
Availability: InStock
Author: Allen

Route Notion-backed topic plans into the correct planner workflow.

Updated Aug 27, 2026

Search Tags:#workflow #routing #concurrency #notion #planner #topic-management

Ready to run

npx skills add https://github.com/AllenZhou/MIRISE --skill planner-allenzhou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/AllenZhou/MIRISE/tree/main/agents/social-media-writer
Command: npx skills add https://github.com/AllenZhou/MIRISE --skill planner-allenzhou

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates routing and governance for MIRISE social-media planning, turning Notion-backed topic plans into concrete writer workflows and ensuring consistent state across stages.

Core Features & Use Cases

Notion-driven routing: queries topic status, depth, and platforms, then dispatches to the appropriate planner workflow.
Concurrency control and gates: enforces locking, entry-step selection, and rollback paths to prevent race conditions and ensure safe transitions.
Notion as single source of truth: all state changes, topic attributes, and handoffs are anchored to Notion records, enabling traceability and auditability.
Use cases include initiating new topics, routing existing topics through planning, and coordinating pre-notes and draft handoffs across planner, write, revise, and publish workflows.

Quick Start

Route a new topic into the correct planner workflow by querying topics and invoking the prepare-dispatch path with the topic payload.

Frequently Asked Questions about planner

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

FAQPage Schema

How do I route Notion topic plans into content workflows?▼

To route Notion topic plans, this Skill queries topic status, depth, and platforms, then dispatches the payload into the correct planner workflow for deterministic end-to-end content creation.

How does concurrency control work for Notion-backed content routing?▼

Concurrency control for Notion-backed routing works by enforcing state locking, entry-step selection, and rollback paths, which prevents race conditions and ensures safe workflow transitions across platforms.

Can I use Notion as the single source of truth for multi-platform topic management?▼

Yes, you can use Notion as the single source of truth for multi-platform topic management. All state changes, topic attributes, and handoffs are anchored to Notion records for full traceability.

Do I need a Notion API client to automate topic planning and dispatch?▼

Yes, automating topic planning and dispatch requires access to the Notion API client and internal dispatch helpers to resolve entry steps, lock states, and workflow paths for accurate routing.

What is the best way to coordinate draft handoffs across writer and publish workflows?▼

The best way to coordinate draft handoffs is by using Notion-driven routing to initiate topics and manage pre-notes, ensuring consistent state across planner, write, revise, and publish workflows.

Why does my content workflow routing fail during state transitions?▼

Content workflow routing fails during state transitions when concurrency gates and locking mechanisms are bypassed, preventing the resolution of entry steps and safe rollback paths across platforms.