spec-flow

Automate spec-to-PR workflows with GitHub flow, issue creation, and CI checks.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-flow
Source: https://github.com/OpenElementsLabs/claude-base/tree/main/claude-project-base/skills/spec-flow
Command: npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end spec-to-PR workflows by automating the lifecycle from a completed spec to a ready-to-merge GitHub Pull Request, saving time and reducing manual coordination.

Core Features & Use Cases

  • Orchestrates issue creation (if missing), feature-branch creation, and PR preparation based on a completed spec (design.md + behaviors.md).
  • Coordinates multiple reviews (spec and quality) and CI checks to ensure a clean, production-ready merge.
  • Provides a repeatable flow for teams adopting GitHub flow and Claude Code-based automation to standardize spec-to-PR processes.

Quick Start

Initiate the flow by running /spec-flow after placing a complete spec in specs and ensuring gh is authenticated.

Frequently Asked Questions about spec-flow

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

FAQPage Schema
How do I automate the spec-to-PR workflow using GitHub flow?

Automating spec-to-PR workflows involves orchestrating issue creation, feature branch management, implementation, iterative reviews, and PR creation based on completed specifications to ensure a production-ready merge.

What is needed to start automating pull request creation from specifications?

Starting automated pull request creation from specifications requires a cleaned working tree, gh CLI authentication, and a completed spec containing design.md and behaviors.md files placed in the specs directory.

How does spec-to-PR orchestration handle code reviews and CI checks?

Spec-to-PR orchestration coordinates multiple reviews, including spec and quality checks, alongside CI validation to ensure a clean, production-ready merge before the GitHub Pull Request is finalized.

Can I use this automated spec-to-PR flow for team-wide standardization?

Yes, this automated spec-to-PR flow provides a repeatable process for teams adopting GitHub flow and Claude Code-based automation to standardize their specification to ready-to-merge pull request lifecycle.

Why does spec-to-PR automation require a cleaned working tree?

Spec-to-PR automation requires a cleaned working tree to safely handle feature branch creation and implementation without conflicting uncommitted changes disrupting the orchestrated GitHub flow.

Does spec-flow support generating GitHub issues automatically?

Yes, spec-flow supports generating GitHub issues automatically by orchestrating issue creation if one is missing, linking the completed specification directly to the subsequent feature branch and pull request.