specification▌

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Generates formal, AI-optimized specifications for GitHub Actions workflows to standardize documentation and enable maintenance. \n \n Produces structured markdown specifications with execution flow diagrams, job dependency matrices, and requirement tables designed for token efficiency \n Covers functional, security, and performance requirements alongside input/output contracts, error handling strategies, and quality gates \n Includes sections for monitoring, compliance, edge cases, and change ma

Generate structured, AI-optimized specification documents with standardized templates and machine-readable formatting. \n \n Creates specification files in /spec/ directory following naming convention spec-[purpose]-[type].md with YAML front matter for metadata \n Enforces structured markdown with 11 standard sections covering purpose, requirements, interfaces, acceptance criteria, and validation \n Includes explicit guidelines for unambiguous language, acronym definitions, and self-contained do

Create comprehensive technical specifications that define system requirements, architecture, implementation details, and acceptance criteria for software projects.

Complete reference for writing, validating, and interpreting OpenAPI Specification 2.0 (Swagger) documents. \n \n Covers all core schema elements: Swagger Object root, Info/Contact/License metadata, Paths, Operations, Parameters (path, query, header, body, formData), Responses, and Schemas with composition and polymorphism support \n Includes security definitions for Basic auth, API Key, and OAuth2 flows (implicit, password, application, accessCode) with scope and requirement objects \n Provides

Agent-oriented reference for the OpenAPI Specification 3.2.0. Use when editing, generating, or validating OpenAPI descriptions (OAD).

Create GitHub issues from specification files using the feature_request.yml template. \n \n Analyzes specification files to extract requirements and automatically generates issue titles and descriptions \n Searches existing issues to prevent duplicates before creating new ones \n Supports both creating new issues and updating existing ones via the GitHub API \n Applies feature and enhancement labels automatically based on specification content \n

Automated GitHub pull request creation from specification templates with draft-to-review workflow. \n \n Reads pull request template from .github/pull_request_template.md and extracts requirements to populate PR body and title \n Checks for existing pull requests on the target branch before creation to prevent duplicates \n Progresses pull requests from draft status to ready for review, then auto-assigns to the creator \n Analyzes PR diffs to ensure specification changes are properly documented

Transform customer insights into clear, detailed specifications that engineering can build from. Master user story writing, define acceptance criteria, and manage scope ruthlessly.

Update specification files for AI-ready consumption based on new requirements or code changes. \n \n Modifies existing specification documents in /spec/ directory using structured markdown with YAML front matter \n Ensures specifications are precise, unambiguous, and machine-readable through established formatting standards (headings, lists, tables, code blocks) \n Covers 11 core sections: purpose, definitions, requirements, interfaces, acceptance criteria, testing strategy, rationale, dependenc