create-github-action-workflow-specification

Generates implementation-agnostic specifications for existing GitHub Actions CI/CD workflows.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/jeje-it/template-projet --skill create-github-action-workflow-specification-jeje-it
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-github-action-workflow-specification
Source: https://github.com/jeje-it/template-projet/tree/main/.agents/skills/create-github-action-workflow-specification
Command: npx skills add https://github.com/jeje-it/template-projet --skill create-github-action-workflow-specification-jeje-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? GitHub Actions workflows often lack formal documentation, making them hard to maintain, review, and evolve safely. This Skill converts an existing workflow file into a structured, AI-optimized specification that captures behavior, requirements, and constraints without implementation details. ## Core Features & Use Cases - Structured Specification Template: Produces a complete spec covering workflow overview, job dependencies, requirements matrices, input/output contracts, error handling, quality gates, and compliance controls. - Mermaid Diagram Generation: Creates execution flow diagrams with sequential, parallel, and conditional patterns, including subgraphs for complex workflows with 5+ jobs. - Token-Efficient Output: Uses tables, lists, and cross-references to keep specifications dense and readable for both humans and AI systems. - Use Case: A DevOps engineer inherits an undocumented CI/CD pipeline and needs a formal spec before refactoring. Provide the workflow file and receive a versioned specification saved to /spec/spec-process-cicd-[workflow-name].md. ## Quick Start Ask the AI to create a specification for your GitHub Actions workflow by providing the workflow file path, for example: create a workflow specification for .github/workflows/ci.yml.

Frequently Asked Questions about create-github-action-workflow-specification

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

FAQPage Schema
How do I document an existing GitHub Actions workflow?▼

Provide the workflow file path and the Skill generates a formal specification covering purpose, triggers, job dependencies, inputs, outputs, and constraints. The output is saved as a Markdown file under /spec/ with a Mermaid execution flow diagram.

What should a CI/CD workflow specification include?▼

A complete spec includes a workflow overview, execution flow diagram, jobs and dependencies table, functional and security requirements, input/output contracts, error handling strategy, quality gates, monitoring metrics, and change management process.

Can I generate Mermaid diagrams for complex GitHub Actions workflows?▼

Yes, the Skill generates Mermaid flow diagrams supporting sequential, parallel, and conditional job patterns. For workflows with five or more jobs, it uses subgraphs to group phases like build and deploy for readability.

Does the specification include implementation details like tool versions?▼

No, the specification is intentionally implementation-agnostic. It focuses on what the workflow accomplishes, its requirements, and constraints rather than specific syntax, commands, or tool versions, making it durable as the workflow evolves.

Where is the generated workflow specification saved?▼

The specification is saved as a Markdown file at /spec/spec-process-cicd-[workflow-name].md, where the workflow name is derived from the analyzed file. It includes YAML frontmatter with title, version, date, owner, and tags.