playbooks

home / skills / krosebrook / source-of-truth-monorepo / workflow

workflow skill

/plugins/installed/superpowers-developing-for-claude-code/examples/full-featured-plugin/skills/workflow

This skill guides users through a multi-step workflow demonstration, showcasing structured planning, execution, and verification for plugin developers.

npx playbooks add skill krosebrook/source-of-truth-monorepo --skill workflow

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

Files (1)
SKILL.md
1.4 KB
---
name: example-workflow
description: Use when demonstrating plugin workflow features - shows how skills can guide multi-step processes
---

# Example Workflow Skill

## Overview

This skill demonstrates how to create a workflow-based skill that guides Claude through a multi-step process. It serves as a reference implementation for plugin developers.

## When to Use

This is an example skill for learning purposes. In a real plugin, you would:
- Use when specific conditions match the skill's domain
- Provide clear triggering criteria
- Guide through complex multi-step workflows

## Example Workflow

When invoked, this skill would guide through these steps:

1. **Gather requirements** - Ask clarifying questions
2. **Plan approach** - Create a structured plan using TodoWrite
3. **Execute systematically** - Follow the plan step-by-step
4. **Verify results** - Confirm the outcome matches requirements

## Integration with Other Components

This skill demonstrates how skills can:
- Reference bundled documentation in `references/`
- Call executable scripts in `scripts/`
- Use MCP server tools provided by the plugin
- Trigger or respond to plugin hooks

## For Plugin Developers

Key points this example demonstrates:
- Clear YAML frontmatter with name and description
- Structured workflow with numbered steps
- Integration points with other plugin components
- Documentation of when/how to use the skill

Overview

This skill demonstrates a workflow-based skill that guides a multi-step process and shows how skills can coordinate actions across a plugin. It serves as a compact reference implementation for building guided, repeatable workflows in TypeScript-based plugins. The skill focuses on clear triggers, step sequencing, and integration points with other components.

How this skill works

When invoked, the skill prompts for requirements, builds a structured plan, executes the plan step-by-step, and verifies results against the original requirements. It can call bundled scripts, reference local documentation, and interact with plugin hooks or MCP server tools to perform automated actions. Each step includes checkpoints and clarifying questions to keep the process deterministic and traceable.

When to use it

  • Demonstrating or testing multi-step plugin workflows
  • Teaching developers how to structure guided processes
  • When you need a reproducible, documented approach to complex tasks
  • As a template for integrating scripts, docs, and plugin hooks
  • When clear triggering criteria and step sequencing are required

Best practices

  • Define explicit triggering criteria so the skill activates only in relevant contexts
  • Keep each workflow step atomic and verifiable with clear success conditions
  • Ask clarifying questions early to reduce rework during execution
  • Log actions and decisions to enable traceability and debugging
  • Use bundled references and scripts for deterministic behavior and easier testing

Example use cases

  • Collect requirements for a feature request, produce a task plan, and run validation scripts
  • Walk a user through a multi-step deployment checklist that calls automation scripts
  • Demonstrate plugin capabilities to new developers using a predictable, documented flow
  • Automate testing sequences that require human confirmation at key checkpoints
  • Serve as a starting template when implementing new workflow-style skills

FAQ

Is this skill intended for production use?

No. This skill is an example and reference implementation. Use it as a template and adapt steps, validation, and integrations before production use.

How does the skill integrate with scripts and docs?

The skill references bundled documentation for guidance and can invoke executable scripts or MCP tools exposed by the plugin. Structure integrations so actions are idempotent and logged.