Purpose

The workflow skill conducts a workflow for one project. It reads where the run stands, runs the first unapproved phase's skills, and stops at the phase boundary to ask whether to approve and continue. It works for the fourteen domain workflows and the five cross-domain ones. The Workflows page explains the workflow files, gates, artifacts and run log in full.

Usage

Example:

/workflow launch-product checkout-v2

Run the same command to resume, even in a new conversation: the conductor picks up at the first phase you have not approved. With no project name it asks for one; with an unknown workflow name it lists the available workflows.

Cross-Domain Workflows

Launch a Product

Full product launch from market research through go-to-market.

Research → Branding → Design → Development → Accessibility → Marketing

launch-product, 25 phases covering all major domains. Use for new products, major features, or MVPs.

Build a Feature

Structured feature development from research through shipping.

Research → Development → Accessibility → Coaching → Ship

build-feature, 9 phases. Use for individual features, bug fixes with research, or technical spikes.

Rebrand

Complete rebranding from research through rollout.

Research → Branding → Coaching → Marketing

rebrand, 12 phases. Use for full rebrands, brand refreshes, or brand extension into new markets.

New Team

Build and launch a new team with leadership and processes.

Leadership → Project Management → Development

new-team, 10 phases. Use when forming a new team, onboarding a new manager, or restructuring.

Compliance Audit

Comprehensive compliance check across legal, accessibility, and brand.

Legal → Accessibility → Branding → Coaching

compliance-audit, 13 phases. Use for pre-launch compliance, annual audits, or regulatory preparation.

Progress Tracking

A phase counts as complete only when you approved it, which the conductor records as a phase-approved line in .singularskills/log.jsonl. An artifact on disk without that line is offered for approval again rather than skipped. Use /singular-status for an overview of every project.

Workflow Files

Workflows are YAML files in the pack's workflows/ folder. Each lists phases with a title, an artifact, the artifacts it requires and its member skills. The workflow skill also carries a copy of every file in its own references/workflows/ folder, so it works wherever the skills were installed. It reads workflows/<workflow>.yml next to the skills/ folder first, and falls back to that copy.

Workflow Conductor