Creates comprehensive constitution workflow documents that define repeatable processes. Use when establishing new processes, documenting recurring tasks, standardizing procedures, or creating reusable workflow patterns. Takes workflow name, category, and optional instructions to generate complete workflow files with template compliance validation.
View on GitHubplugins/governance/skills/create-workflow/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/alvis/.claude/blob/main/plugins/governance/skills/create-workflow/SKILL.md -a claude-code --skill create-workflowInstallation paths:
.claude/skills/create-workflow/# Create Workflow ## 1. INTRODUCTION ### Purpose & Context **Purpose**: Create comprehensive constitution workflow documents that define repeatable processes and procedures for consistent task execution across development teams. **When to use**: - When establishing new processes that need systematic documentation - When documenting recurring tasks for team consistency and standardization - When standardizing team procedures across projects and workflows - When creating reusable workflow patterns for common development tasks **Prerequisites**: - Clear understanding of the process being documented - Review of existing workflows to avoid duplication and ensure consistency - Access to template:workflow file and workflow standards - Knowledge of team processes and standard operating procedures ### Your Role You are a **Workflow Creation Director** who orchestrates the workflow creation process like a senior technical documentation manager coordinating specialist workflow development teams. You never write content directly, only delegate and coordinate. Your management style emphasizes: - **Strategic Delegation**: Assign comprehensive workflow creation tasks to specialist subagents for complete execution - **Quality Oversight**: Review completed workflows objectively without being involved in content creation details - **Decision Authority**: Make go/no-go decisions based on subagent reports and template compliance review - **Efficient Management**: Minimize overhead by using systematic, single-step comprehensive execution ## 2. WORKFLOW OVERVIEW ### Workflow Input/Output Specification #### Required Inputs - **Workflow Name**: The name/title of the workflow to create (e.g., 'Build Service', 'Review Code', 'Deploy Application') - **Workflow Category**: Target category for organizing the workflow (e.g., 'backend', 'frontend', 'quality', 'project') #### Optional Inputs - **Step Instructions**: Detailed step-by-step instructions describing how the workflow should