Results for “spec-generation”

Regenerates a specific code layer (schemas, services, routes, hooks, ui) or all layers, then runs the corresponding validation checks.

Generate a complete, production-ready application from an OpenAPI specification using the active framework's conventions and best practices.

Scaffold, test, document, and debug REST and GraphQL APIs from the command line, including curl testing, OpenAPI spec generation, mocking, and troubleshooting.

Analyze existing code files to generate a project-specific coding standards document, with options for templates, README insertion, and inconsistency detection.

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Design Open Graph and social sharing images with platform-specific specs, text placement, and branding guidelines. Generate images via HTML-to-image or AI, and configure OG meta tags for Facebook, Twitter, LinkedIn, and more.

Create a committed per-feature spec under `docs/specs/YYYY-MM-DD-<slug>/{spec,tasks}.md` with frontmatter (status, created, owner, pr, tags). Promotes an ephemeral `.claude/plans/<name>.md` into a persistent, searchable artifact. Use when starting a feature that's larger than a one-shot PR.

Create a structured specification file for a solution component, optimized for Generative AI consumption.

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".

Spec Craft

Escribe especificaciones técnicas en formato Given/When/Then, describiendo qué debe hacer el sistema y no cómo, con escenarios de caso feliz, bordes y errores.

spec-ship

Manages spec-driven development with OpenSpec. Use when creating change proposals, planning features, implementing from specs, or archiving completed changes. Triggers on "proposal", "change", or "spec" with "create", "plan", "make", or "help".

Turn vague intent into a precise, executable spec in five phases. (gstack)

在要求写结构化的 spec、规格文档、行为规格或验收标准时使用。

Extracts specifications from existing codebases by analyzing structure, data flows, and observable behaviors to document requirements in EARS format.

Create a feature branch with sequential or timestamp numbering

CEO/founder-mode plan review. (gstack)

Use this skill when the user requests to generate, create, or imagine videos. Supports structured prompts and reference image for guided generation.

Turn vague intent into a precise, executable spec in five phases. (gstack)

Generate typed SDK bindings (Pydantic v2 models, TypeScript types) from the Bloodbank JSON Schema tree at `bloodbank/schemas/bloodbank/v1/**` (Draft 2020-12). Uses `datamodel-code-generator` and `json-schema-to-typescript` — NOT the deprecated hand-rolled Holyfields generators. Use when generating event-contract bindings for a Bloodbank consumer, importing typed CloudEvents envelopes into another project, or scaffolding a `bloodbank-contracts` SDK package. Trigger keywords — "bloodbank SDK", "bloodbank contracts", "Pydantic from bloodbank schemas", "TypeScript types for bloodbank events", "bloodbank.v1.* types", "event contract bindings", "datamodel-code-generator", "json-schema-to-typescript", "regenerate SDK", "CloudEvents bindings". Do NOT use for schema authoring (edit `bloodbank/schemas/` directly per `docs/event-naming.md` §12), runtime envelope validation (use `BLOODBANK_HOOK_VALIDATE=1`), schema-tree consistency (`mise run smoketest:schemas`), or generic JSON Schema codegen unrelated to Bloodbank.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

Gera especificações executáveis do sistema legado como contratos operacionais, em formato de pasta-por-unit com requirements.md, design.md e tasks.md. Use na fase de geração de uma análise de engenharia reversa.

ateam-spec

Generate comprehensive checklists to validate requirements quality (Unit Tests for Specs). Critically examine the spec for clarity, completeness, and consistency before implementation starts.

Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.