AgiFlow

Use Doom Pi Runner to supervise shell commands, inspect durable logs, provide interactive input, and stop background runs.

Author DoomPi repository or plugin hooks. Use when creating or changing .doom/hooks.yaml, selecting hook groups from modes.yaml, writing hook commands, or adapting Claude Code hook payloads and decisions to DoomPi.

Set up and debug DoomPi agents using installed package guidance and scoped, read-only diagnostics. Diagnose missing capabilities before proposing authorized repairs.

Use Doom Pi MCP to inspect domain-scoped servers, authenticate, reload configuration, measure what server tool schemas cost in context, and troubleshoot tool availability.

Recover a failed or interrupted workflow-mcp run so it resumes from its active repair rather than starting over. Use before a recover action (workflow_run in Pi CLI, workflow_tools in server/web sessions), whenever a run shows stage error or interrupted, or…

Use DoomPi workflows. Use when discovering or launching workflows, monitoring or controlling asynchronous runs, interpreting terminal notifications, or recovering a failed run safely.

Author DoomPi workflow definitions. Use when creating or changing a *.workflow.yml graph, arranging job dependencies and host-executed steps, or deciding how a command requiring a TTY should run.

Use scaffold-mcp CLI commands for project boilerplates, feature scaffolds, template authoring, and scaffold-backed file creation. Trigger before creating new files, when adding routes/components/services/packages/apps, when listing available scaffolds, or…

Create or update reusable toolkit boilerplate templates and feature scaffolds. Trigger for explicit template-authoring requests. Do not trigger for simply generating an app or feature from an existing template.

Author project design patterns and coding rules with architect-mcp admin tools. Trigger when the user asks to change pattern or rule definitions. Do not trigger for reviewing existing code against unchanged rules.

Discover and create a new application from a scaffold-mcp boilerplate. Trigger for requests to start a new project. Do not trigger when adding a feature to an existing project.

Set up toolkit templates and project metadata in a consumer workspace. Trigger when the user asks to initialize AI Code Toolkit or scaffold cannot find templates. Do not trigger for routine editing in an already configured project.

Discover existing project themes, supported CSS classes and reusable UI components. Trigger for frontend styling or component-selection requests. Do not trigger for unrelated backend changes or executing visual previews.

Render and inspect a design-system component in a trusted project. Trigger for explicit visual component preview requests. Do not trigger for simple theme/class lookup or untrusted repositories.

Add or edit a feature in a toolkit-configured project using scaffold methods and file-specific design patterns. Trigger for feature implementation or pattern-guided edits. Do not trigger for standalone project creation, admin template authoring or review-only…

Review changes against file-specific toolkit rules. Trigger for code-review and quality-check requests. Do not trigger when the user asks to generate a project or author coding rules.

Review Agiflow Planning tasks for readiness, prioritize approved work, group related tasks into work units, and promote ready tasks to Todo. Use when grooming a backlog, organizing planned tasks, creating work units, or deciding what should be executed next.

Produce a concise read-only Agiflow status summary covering completed work, work in progress, blockers, and recommended next priorities. Use for daily standups, morning checks, stakeholder updates, or a quick project pulse.

Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.

Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.

Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.

Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.

Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses list_tasks, list_active_tasks_by_org, list_members, update_task,…

Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work <work-unit-or-task>. Uses get_work_unit,…

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack…