ospec-workflow

Generate repository wiki pages mapping architecture, specs, and status. Trigger: orchestrator launches sdd-document.

Shared SDD references for installed skills. Not invokable.

Read-only generalist screening contract for selective 4R review.

Read-only targeted correction validator for a bounded review lineage.

Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.

Create pull requests with branch, validation, and publication checks. Trigger: creating, opening, or preparing PRs for review.

Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.

Trigger: sdd foundation, new project, empty workspace, project from scratch. Build project foundation docs and config.

Run or continue apply for an OpenSpec change.

Run or continue apply for an OpenSpec change.

Implement SDD tasks from specs and design. Trigger: orchestrator launches apply for one or more change tasks.

Trigger: sdd baseline, brownfield baseline, seed specs, baseline.status pending or partial. Seed openspec/specs/ with baseline specs of existing behavior in resumable one-domain batches.

Reduce spec ambiguities before design. Trigger: orchestrator launches clarify after sdd-spec completes.

Create the SDD technical design and architecture approach. Trigger: orchestrator launches design for a change.

Explore SDD ideas before committing to a change. Trigger: orchestrator launches exploration or requirement clarification.

Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.

Walk users through the SDD workflow on the real codebase. Trigger: orchestrator launches onboarding for the full SDD cycle.

Create an SDD change proposal with intent, scope, and approach. Trigger: orchestrator launches proposal work for a change.

Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.

Trigger: SDD verification phase, verify change. Execute tests and prove implementation matches specs, design, and tasks.

Trigger: sdd workspace, federated, multi-repo, atlas, cross-repo impact, artifact_store.backend workspace-federated. Manage the federation atlas and surface cross-repo state.

Astro Starlight documentation framework — setup, sidebar navigation, frontmatter, built-in components, asides, theming, i18n, search

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Trigger: release notes, changelog entries, tag release. Generate homogeneous Spanish release notes based on project format.

Trigger: sdd reconcile, spec drift, reconcile domain, fold changes into spec, /sdd-reconcile. Fold already-shipped, undocumented code changes back into a baseline domain's spec as a diff-window-scoped retroactive delta.

Go (Golang) programming language — idiomatic structures, concurrency, error handling

Kotlin JetBrains Exposed ORM framework — DAO, DSL, transactions

Kotlin Ktor web framework — routing, content negotiation, serialization, plugins

Kotlin language guidelines — naming, idioms, coding standards

Kotlin testing standards — Kotest, Mockk, JUnit 5

Python development guidelines — style, patterns, virtual environments

React performance optimization — memoization, lazy loading, rendering profiling

React UI library — components, hooks, state management, patterns

React component testing — React Testing Library, Vitest, Jest

Vite frontend build tool — configuration, plugins, asset loading

Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.

Angular frontend framework — standalone components, signals, reactive forms, routing, RxJS

ASP.NET Core + C# backend — minimal APIs, dependency injection, EF Core, nullable reference types

Go testing standards — unit tests, mocks, integration tests

Java coding standards for Spring Boot and Quarkus services — naming, immutability, Optional, streams, DI