spec-setup

Scan repositories to generate .workflow/specs and project-tech.json files.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-setup-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-setup
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/spec-setup
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-setup-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maestro-Flow projects require consistent, machine-readable specification files but creating them by hand is time-consuming and error-prone; spec-setup automates discovery of conventions and the tech profile to initialize those specs.

Core Features & Use Cases

  • Automated Codebase Scanning: Detects package manifests, config files, source structure, and test patterns to infer languages, frameworks, and module systems.
  • Spec Generation: Creates .workflow/specs entries for coding conventions, architecture constraints, quality rules, and learnings, and writes a consolidated .workflow/project-tech.json.
  • Validation & Reporting: Verifies preconditions, surfaces explicit error codes for missing initialization or no source files, and flags uncertain detections with warnings.
  • Use Case: Quickly bootstrap workflow governance for a repository so downstream agents and CI pipelines have a consistent spec-driven context.

Quick Start

Run the spec-setup skill to scan the repository and generate .workflow/specs and .workflow/project-tech.json.

Frequently Asked Questions about spec-setup

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

FAQPage Schema
How do I auto-generate project specs from my codebase?

Spec-setup scans your repository for package manifests, config files, source structure, and test patterns to infer languages, frameworks, and module systems, generating structured .workflow/specs files and .workflow/project-tech.json.

How do I bootstrap Maestro workflows for an existing repository?

Run spec-setup against an existing codebase to validate preconditions and auto-generate .workflow/specs entries for coding conventions, architecture constraints, quality rules, and learnings to initialize Maestro workflows.

What files do I need to initialize workflow governance in a repository?

You need a repository with source files and config files; spec-setup scans these to detect languages and frameworks, producing .workflow/specs and .workflow/project-tech.json to establish spec-driven context for CI pipelines.

Why does project setup fail when scanning a repository for conventions?

Spec-setup emits explicit error codes for missing initialization or no source files, and flags uncertain technology detections with warnings, ensuring you resolve missing preconditions before generating .workflow specifications.

Can I use spec-setup with any tech stack to create a project tech profile?

Spec-setup infers languages, frameworks, and module systems by scanning your repository's package manifests and config files, reading template defaults when available to produce a consolidated .workflow/project-tech.json.