playbooks

home / skills / duc01226 / easyplatform / workflow-start

workflow-start skill

/.claude/skills/workflow-start

This skill activates a selected workflow from the injected catalog, initializes state, and prepares step execution to streamline automation.

npx playbooks add skill duc01226/easyplatform --skill workflow-start

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.0 KB
---
name: workflow-start
description: Activate a workflow from the injected catalog. Use when the workflow-router hook injects a catalog and a matching workflow is identified, or when the user explicitly requests a workflow activation (e.g., "start feature workflow", "activate bugfix workflow").
infer: true
allowed-tools: Skill, TodoWrite, AskUserQuestion, Read, Glob, Grep
---

# Workflow Activation

Start a workflow by ID from the workflow catalog injected by the hook system. This creates workflow state and prepares the step sequence for execution.

## When to Use

- After the workflow-router hook injects a catalog and you identify a matching workflow
- When the user explicitly asks to follow a specific workflow
- When switching from one active workflow to another

## Workflow

1. **Validate** the workflow ID against the injected catalog
2. **Confirm if needed** — If the workflow has a **Confirm first** marker, ask the user BEFORE activation
3. **Activate** — Invoke `/workflow:start <workflowId>` slash command to create workflow state via the workflow-step-tracker hook
4. **Create TodoWrite items** for ALL sequence steps immediately after activation
5. **Follow the sequence** in order, marking each step `in_progress` then `completed`

## Activation Rules

- Call this ONLY after reading the workflow catalog injected by the hook
- Use the exact workflow ID shown in the catalog (e.g., `feature`, `bugfix`, `investigation`)
- If the workflow has **Confirm first** marker, ask the user BEFORE calling this command
- If called while another workflow is active, it will auto-switch (end current, start new)

## After Activation

Your FIRST action after activation completes MUST be `TodoWrite` with items like:

    [Workflow] /step-command - Step description (status: in_progress for first, pending for rest)

Do NOT skip TodoWrite. It is a hard-blocking requirement.

## IMPORTANT Task Planning Notes (MUST FOLLOW)

- Always plan and break work into many small todo tasks
- Always add a final review todo task to verify work quality and identify fixes/enhancements

Overview

This skill activates a workflow from the catalog injected by the workflow-router hook. It validates the workflow ID, optionally asks for confirmation if the workflow is marked "Confirm first", and issues the activation command to create workflow state and prepare step sequencing. Activation also triggers creation of todo items for every step so execution can be tracked.

How this skill works

The skill reads the injected catalog and validates the requested workflow ID exactly as shown in the catalog. If the workflow has a "Confirm first" marker, it prompts the user before proceeding. It then calls the workflow start command to create workflow state and immediately generates TodoWrite items for all steps, marking the first step in_progress and the rest pending so the sequence can be followed in order.

When to use it

  • After the workflow-router hook injects a catalog and you identify a matching workflow
  • When a user explicitly asks to start or activate a named workflow (e.g., "start feature workflow")
  • When switching from one active workflow to another and you need to auto-switch
  • When you need to create tracked step-level todos before executing work

Best practices

  • Always read and validate the exact workflow ID from the injected catalog (case-sensitive match)
  • Respect the "Confirm first" marker: ask the user before activation when present
  • Immediately perform a TodoWrite for all sequence steps after activation; do not skip this
  • Break work into many small todo tasks and include a final review task for quality checks
  • If another workflow is active, expect the skill to auto-switch and close the prior workflow state

Example use cases

  • User says "activate bugfix workflow" and the skill validates the ID then prompts if confirmation is required
  • Switching from a current "investigation" workflow to a new "feature" workflow, auto-ending the old and starting the new
  • Automated process that reacts to a hook-injected catalog and starts a matching workflow when criteria are met
  • Starting a workflow and immediately generating step-level todos so a team can pick up individual steps

FAQ

What happens if I call start while another workflow is active?

The skill will auto-switch: the current workflow ends and the new workflow is started. Todo items for the new workflow are created immediately.

Can I skip creating todos after activation?

No. Creating TodoWrite items for all steps immediately after activation is mandatory and must include the first step marked in_progress.