Skills Guide

Workflow Orchestration

VerifiedSafe

Orchestrate the standard delivery flow from brief through draft PR using skills and thin role wrappers.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/28/2026
Claude Code
#workflow#orchestration#tdd#code-review#pull-request

Recommended for

Backend developerClaude CodeCode reviewTest generationFrontend developerFullstack developer

Automated summary

Orchestrates a repository delivery flow from brief through draft PR by chaining the brief, spec, tdd, code, review, and draft-pr stage skills.

Strengths

  • Keeps stages clearly separated and routes work to each stage skill instead of duplicating its guidance
  • Checks for existing artifacts in docs/briefs, docs/specs, and docs/qa/reports before asking the user to recreate them
  • Requires a full verification pass before opening or updating a PR, with a sensible exemption for docs-only changes
  • Summarizes after every stage what was produced, which paths changed, and what blockers remain

Limitations

  • Assumes the brief, spec, tdd, code, review, and draft-pr skills plus their owning subagents are already installed
  • Artifact paths are hardcoded (docs/briefs, docs/specs, docs/qa/reports), which may not fit repositories with other conventions
  • Covers only this phase: it deliberately creates no workflow state or JSON checkpoint files
When to use it

Use it when a feature should move through the full brief, spec, tdd, code, review, and draft PR cycle in a disciplined way.

When not to use it

Avoid it for a quick bug fix or a trivial edit where running every stage would be unnecessary overhead.

Security analysis

Safe
Quality score72/100

The skill is a pure orchestration entry point: it asks the user which stage range to run, checks for existing artifact paths under docs/, and delegates to other named skills. It declares no tools, runs no shell commands, touches no secrets or network endpoints, and includes no obfuscated or destructive instructions. The only mild consideration is that it ultimately routes into downstream skills that may perform git/PR operations, but that risk lives in those skills, not here.

No concerns found

How this analysis is made

Examples

Full feature flow
Run the full workflow for a feature called team-invites, from brief through draft PR.
Resume mid-flow
Resume the workflow for checkout-retry starting at the tdd stage; the spec already exists in docs/specs.
Partial range
Run the workflow for rate limiting, but only the spec -> code stages.

name: workflow description: Orchestrate the repo workflow from brief through draft PR using skills and thin role wrappers.

Workflow

Objective

Coordinate the standard delivery flow:

brief -> spec -> tdd -> code -> review -> draft-pr

This is a skill entry point, not a command wrapper. Keep the orchestration light and route work into the stage skills instead of duplicating their guidance here.

Instructions

  1. Ask for the feature or change name and which stage range to run (full, partial like spec -> code, or resume from an existing artifact).
  2. Check which stage artifacts already exist before asking the user to recreate them:
    • docs/briefs/
    • docs/specs/
    • docs/qa/reports/
  3. For each selected stage, invoke the matching skill (brief, spec, tdd, code, review, draft-pr). Each skill self-routes via its own Invocation preface: brief, spec, tdd, code, and test run inline in the current chat under the appropriate persona, while review, draft-pr, and pr-description default to delegating to their owning subagent.
  4. After each stage, summarize:
    • what was produced
    • which paths changed or were created
    • open decisions or blockers
    • the next recommended skill
  5. Keep context compact. Prefer referencing existing artifact paths over restating full document contents.
  6. Do not create workflow state files or command-era JSON checkpoint files in Phase 1.

PR validation (before draft-pr)

  • Prefer targeted checks while iterating; do not rerun full verification on every tiny commit by default.
  • Before opening or updating a PR: run a full verification pass from the repo root. Include builds when the change touches app/runtime code, config, dependencies, or anything that could affect shipped output.
  • Docs-only edits (markdown with no runtime effect): a full build is not required; still run linting when the diff touches linted paths.
  • On follow-up pushes to an open PR, rerun checks when the changeset meaningfully affects verified code.

Stage Outputs

  • brief -> docs/briefs/{feature}.md
  • spec -> docs/specs/{feature}.md
  • tdd -> failing or newly added unit tests
  • code -> implementation and verification results
  • review -> docs/qa/reports/{date}-{branch-or-pr}.md
  • draft-pr -> branch, commit, and draft PR output

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/workflow-orchestration-ms47vpor/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/workflow-orchestration-ms47vpor' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/workflow-orchestration-ms47vpor/download' --output '.skill-downloads/workflow-orchestration-ms47vpor/SKILL.md.part' && mv '.skill-downloads/workflow-orchestration-ms47vpor/SKILL.md.part' '.skill-downloads/workflow-orchestration-ms47vpor/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/workflow-orchestration-ms47vpor/SKILL.md' && test -s '.skill-downloads/workflow-orchestration-ms47vpor/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/workflow' && cp -R '.skill-downloads/workflow-orchestration-ms47vpor' '.claude/skills/workflow'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/workflow-orchestration-ms47vpor'

openskills read 'workflow-orchestration-ms47vpor'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/workflow-orchestration-ms47vpor/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot