roster-workflow-build

Generate CWR workflow files from completed Roster plan JSON.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-workflow-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster-workflow-build
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-workflow-build
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-workflow-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating CWR workflow files from validated project plans is time-consuming and prone to template mismatch errors that break pipeline execution. This Skill automates the entire generation process to ensure workflows are accurate and aligned with the correct mode template every time.

Core Features & Use Cases

  • Template-Accurate Generation: Copies mode-specific template steps verbatim to preserve curated prompts and eliminate manual editing errors.
  • Built-In Privacy Gate: Presents three clear output options (commit to git, local-only, or execution-only temporary) before writing any files, giving users full control over workflow storage and versioning.
  • Use Case: After a Roster plan is marked COMPLETED, this Skill instantly generates the matching CWR workflow file so the pipeline can dispatch execution without manual setup, cutting down workflow creation time from minutes to seconds.

Quick Start

Use the roster-workflow-build skill to generate a CWR workflow file from your completed project plan for the current task.

Frequently Asked Questions about roster-workflow-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a CWR workflow file from a completed plan?

To generate a CWR workflow file from a completed plan, the system matches the plan's execution mode to a pre-defined template and translates the validated plan JSON into a compliant workflow file.

What is the process for translating a validated plan JSON into a CWR workflow?

Translating a validated plan JSON into a CWR workflow involves matching the plan's execution mode to the correct template, applying a synchronous privacy gate, and writing valid JSON output compatible with CWR runtime dispatch.

Can I use roster-workflow-build to create workflows for express, fast, and full pipeline modes?

Yes, you can use this workflow generation process for express, fast, and full pipeline modes, as it matches the plan's specific execution mode to the corresponding pre-defined template to ensure compliance.

How does the privacy gate work before writing pipeline workflow files?

The privacy gate enforces a synchronous checkpoint before file writes, presenting three output options: committing to git, keeping files local-only, or using an execution-only temporary state.

Why does template matching matter for CWR workflow generation?

Template matching matters for CWR workflow generation because it preserves curated template step definitions verbatim, eliminating manual editing errors and ensuring accurate pipeline execution.

What are the requirements for automating CWR workflow generation from Roster plans?

Automating CWR workflow generation requires a Roster plan marked COMPLETED in JSON format and the absence of an existing corresponding workflow file for the current pipeline task.