
from manifest-dev64
Orchestrates multi-party deliberation in Slack: presses for decisions, surfaces trade-offs and evidence, and posts wrap-up syntheses while the operator retains
This skill runs asynchronous, evidence-driven deliberations in Slack channels or threads. Acting as an involved orchestrator, it asks load-bearing questions first, brings supporting evidence, names trade-offs, and advances when the group reaches coherent answers. It also produces a final synthesis post for the channel.
Use when teams cannot meet synchronously and a structured decision or alignment is required in Slack: product trade-offs, design choices, incident postmortems, or cross-functional approvals. Requires an operator in Claude Code to launch and Slack MCP connectivity.
references/ folder with guidance on Slack mrkdwn and logging options (has_references=true)Designed for Claude Code-style operators that can call Slack tools and manage session-bound trust; works where the operator controls writes and the skill polls Slack for new messages.
A thin discovery wrapper that forwards arguments to the manifest-dev:figure-out skill with a --team flag. No scripts, no logic beyond delegation. The SKILL.md is just a routing instruction — minimal instructions, no error handling guidance, no output contract. Relies entirely on the parent skill for substance.
This is a passthrough/discovery wrapper skill with no scripts, no references, and no substantive instructions beyond delegating to another skill. The frontmatter is complete and well-structured, but the body adds almost no value beyond routing. Architecture is flat — no separation of concerns because there's nothing to separate. Security is clean (no executable content, no network calls, no credentials). Usefulness is moderate because team deliberation orchestration is a real use case, but this wrapper itself provides no implementation.