universal-dev-standards

Plugin universal-dev-standards from marketplace asia-ostrich in AsiaOstrich/universal-dev-standards. Commands read from the repo's manifest — 5 days ago.

Skills (57)

• ac-coverage

  [UDS] Analyze AC-to-test traceability and generate requirement-level coverage reports. Use when: auditing which acceptance criteria have tests, building a traceability matrix from a SPEC file, finding uncovered AC before release. Not for: code-level line/branch/function coverage — use /coverage; wri

• adr

  [UDS] Create, manage, and track Architecture Decision Records (ADR). Use when: architecture decisions, technology choices, design trade-offs, pattern selection. Not for: decisions that do not change architecture — record them in the spec or commit; ideas not yet formed enough to decide — use /brains

• ai-collaboration-standards

  Prevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Not for: authoring the AI instruction files themselves — use /ai-instruction-stan

• ai-friendly-architecture

  Design AI-friendly architecture with explicit patterns, layered documentation, and semantic boundaries. Use when: structuring projects for AI collaboration, optimizing codebase for AI analysis, setting up AI context. Not for: writing the instruction files — use /ai-instruction-standards; language-co

• ai-instruction-standards

  Create and maintain AI instruction files (CLAUDE.md, AGENTS.md, .cursor/rules/, etc.) with proper structure. Use when: creating AI instruction files, separating universal vs project-specific rules, configuring AI tools. Not for: shaping the codebase so AI can navigate it — use /ai-friendly-architect

• api-design

  Guide API design following REST, GraphQL, and gRPC best practices. Use when: designing APIs, reviewing endpoints, API versioning decisions. Not for: verifying a running API against its consumers — use /contract-test; schema design behind the API — use /database. Keywords: API, REST, GraphQL, gRPC, e

• atdd

  [UDS] Reference for Acceptance Test-Driven Development: INVEST criteria, Gherkin AC format, and Three Amigos structure. Use when: defining acceptance criteria with a product owner, running a specification workshop, checking a user story against INVEST. Not for: executing the ATDD lifecycle or enforc

• audit

  [UDS] Diagnose UDS installation health and submit structured feedback upstream. Use when: .standards/ looks broken or out of sync, verifying manifest integrity, reporting friction with an existing UDS standard. Not for: auditing your own application code quality — use /metrics or /code-review; depen

• bdd

  [UDS] Reference for Behavior-Driven Development: Gherkin Given-When-Then format and Three Amigos structure. Use when: writing or reviewing .feature scenarios, choosing ubiquitous language, running a discovery conversation about behaviour. Not for: executing the BDD lifecycle or RED/GREEN automation

• brainstorm

  [UDS] Structured multi-persona brainstorming with a scored quality gate, run before a spec exists. Use when: an idea is still vague, exploring alternatives before committing to a direction, needing diversity rather than the first plausible answer. Not for: planning work whose direction is already de

• changelog

  [UDS] Generate and maintain CHANGELOG.md entries in Keep a Changelog format. Use when: writing changelog entries from commit history, filling the Unreleased section, categorising changes as Added/Changed/Fixed. Not for: choosing the next version number or running the release — use /release; writing

• checkin

  [UDS] Reference for pre-commit quality gates: gate definitions, checklist items, and never-commit rules. Use when: deciding what must pass before a commit, auditing which quality gates a project enforces, checking readiness to check in. Not for: executing the gate sequence or aborting a commit — tha

• ci-cd

  Guide CI/CD pipeline design, configuration, and optimization. Use when: setting up pipelines, optimizing build times, configuring deployment stages. Not for: deploying without a CI/CD platform — use /deploy; version bumps and promotion — use /release. Keywords: CI/CD, pipeline, GitHub Actions, deplo

• code-review

  [UDS] Reference for systematic code review: eight review categories and BLOCKING/IMPORTANT/SUGGESTION comment prefixes. Use when: reviewing a pull request or diff, deciding how to phrase and prioritise review comments, agreeing review scope with a team. Not for: executing a gated review workflow — t

• commit

  [UDS] Generate commit messages that follow Conventional Commits, including the bilingual format. Use when: writing a commit message for staged changes, choosing a type and scope, producing a bilingual English and 中文 subject and body. Not for: deciding whether the change is ready to commit — use /che

• comprehend

  [UDS] Turn one hard-to-follow AI output into easier forms: controlled text, a Mermaid diagram, a single-file HTML explainer. All forms come from one shared outline, so the form changes and the facts do not. Use when: an AI explanation, spec or code walk-through is too dense to judge, a non-specialis

• contract-test

  [UDS] Guide contract testing strategy for APIs and microservices. Use when: API contracts, microservices, consumer-driven testing, provider verification. Not for: designing the API surface in the first place — use /api-design; user-visible flows through a UI — use /e2e. Keywords: contract test, Pact

• database

  Guide database design, migration, and query optimization. Use when: schema design, migration planning, query optimization, index strategy. Not for: application code migration or framework upgrades — use /migrate; the API contract over the data — use /api-design. Keywords: database, schema, migration

• deploy

  Guide reliable deployments without CI/CD platforms (GitHub Actions / GitLab CI). Use when: deploying to VPS, air-gapped servers, or environments without CI/CD infrastructure. Not for: pipelines on GitHub Actions or GitLab CI — use /ci-cd; version bumps and release promotion — use /release. Keywords:

• methodology

  [UDS] Select and track the active development methodology (SDD, BDD, TDD) for a project. Use when: deciding which methodology a project should follow, switching methodology, checking which phase the current methodology is in. Not for: finding which command to run at a given development stage — use /

• dev-workflow

  [UDS] Map the current software development phase to the right UDS commands and skills. Use when: unsure which UDS command fits the task at hand, onboarding to UDS, walking a feature from planning through release. Not for: choosing or switching a methodology — use /methodology; doing the actual work

• docs-generator
• documentation-guide
• durable-execution-assistant
• e2e-assistant
• error-code-guide
• git-workflow-guide
• incident-response-assistant
• journey-test-assistant
• knowledge-graph
• logging-guide
• metrics-dashboard-assistant
• migration-assistant
• observability-assistant
• open-work-assistant
• orchestrate
• plan
• pr-automation-assistant
• project-discovery
• project-structure-guide
• push
• refactoring-assistant
• release-standards
• requirement-assistant
• retrospective-assistant
• reverse-engineer
• runbook-assistant
• security-assistant
• security-scan-assistant
• skill-builder
• slo-assistant
• spec-derivation
• spec-driven-dev
• sweep
• tdd-assistant
• test-coverage-assistant
• testing-guide

Slash commands (53)

• /universal-dev-standards:COMMAND-FAMILY-OVERVIEW
• /universal-dev-standards:README
• /universal-dev-standards:ac-coverage

  [UDS] Generate AC-to-test traceability matrix and coverage report

• /universal-dev-standards:api-design

  [UDS] Guide API design following REST, GraphQL and gRPC best practices

• /universal-dev-standards:atdd

  [UDS] Guide through Acceptance Test-Driven Development workflow

• /universal-dev-standards:audit

  [UDS] UDS health check and feedback system, diagnose installation integrity and detect development patterns

• /universal-dev-standards:bdd

  [UDS] Guide through Behavior-Driven Development workflow

• /universal-dev-standards:brainstorm

  [UDS] Structured AI-assisted brainstorming before spec creation

• /universal-dev-standards:changelog

  [UDS] Generate and maintain CHANGELOG.md entries

• /universal-dev-standards:check

  [UDS] Verify standards adoption status

• /universal-dev-standards:checkin

  [UDS] Pre-commit quality gates verification

• /universal-dev-standards:ci-cd

  [UDS] Guide CI/CD pipeline design, configuration and optimization

• /universal-dev-standards:code-review

  [UDS] Perform systematic code review with checklist

• /universal-dev-standards:commit

  [UDS] Generate commit messages following Conventional Commits standard

• /universal-dev-standards:config

  [UDS] Configure project development standards

• /universal-dev-standards:coverage

  [UDS] Analyze test coverage and provide recommendations

• /universal-dev-standards:database

  [UDS] Guide database design, migration planning and query optimization

• /universal-dev-standards:derive-all

  [UDS] Derive all test structures (BDD, TDD, ATDD) from SDD specification

• /universal-dev-standards:derive-atdd

  [UDS] Derive ATDD acceptance tests from SDD specification

• /universal-dev-standards:derive-bdd

  [UDS] Derive BDD Gherkin scenarios from SDD specification

• /universal-dev-standards:derive-tdd

  [UDS] Derive TDD test skeletons from SDD specification

• /universal-dev-standards:derive

  [UDS] Derive BDD scenarios, TDD skeletons, or ATDD tables from specifications.

• /universal-dev-standards:dev-workflow

  [UDS] Guide for mapping software development phases to UDS commands and features

• /universal-dev-standards:discover

  [UDS] Assess project health, architecture, and risks before adding features

• /universal-dev-standards:docgen

  [UDS] Generate usage documentation from project sources

• /universal-dev-standards:docs

  [UDS] Manage, guide, and generate documentation.

• /universal-dev-standards:durable

  [UDS] Guide workflow failure recovery with checkpoints, retries and rollback strategies

• /universal-dev-standards:e2e

  [UDS] Generate E2E test skeletons from BDD scenarios with framework detection

• /universal-dev-standards:guide

  [UDS] Access Universal Development Standards guides and references.

• /universal-dev-standards:incident

  [UDS] Guide incident response, root cause analysis and post-mortem documentation

• /universal-dev-standards:init

  [UDS] Initialize development standards in current project

• /universal-dev-standards:journey-test

  [UDS] Generate coherent user journey test plans (TESTPLAN) and E2E skeletons from a project description.

• /universal-dev-standards:methodology

  [UDS] Manage development methodology workflow

• /universal-dev-standards:metrics

  [UDS] Track development metrics, code quality indicators and project health

• /universal-dev-standards:migrate

  [UDS] Guide code migration, framework upgrades and technology modernization

• /universal-dev-standards:observability

  [UDS] Guide observability setup, metrics design, alerting, and maturity assessment

• /universal-dev-standards:pr

  [UDS] Guide Pull Request creation, review automation and merge strategies

• /universal-dev-standards:refactor

  [UDS] Guide refactoring decisions and strategy selection

• /universal-dev-standards:release

  [UDS] Manage release process and changelogs.

• /universal-dev-standards:requirement

  [UDS] Write user stories and requirements following INVEST criteria

• /universal-dev-standards:reverse-bdd

  [UDS] Transform SDD acceptance criteria to BDD scenarios

• /universal-dev-standards:reverse-sdd

  [UDS] Reverse engineer code into SDD specification document

• /universal-dev-standards:reverse-tdd

  [UDS] Analyze BDD-TDD coverage gaps

• /universal-dev-standards:reverse

  [UDS] Reverse engineer code to Specs, BDD, or TDD coverage.

• /universal-dev-standards:runbook

  [UDS] Guide runbook creation, maintenance, drills, and coverage reporting

• /universal-dev-standards:scan

  [UDS] Guide automated security scanning, dependency auditing and secret detection

• /universal-dev-standards:sdd-retro

  [UDS] Create retroactive specs for untracked feat/fix commits

• /universal-dev-standards:sdd

  [UDS] Create or review specification documents for Spec-Driven Development

• /universal-dev-standards:security

  [UDS] Guide security review and vulnerability assessment following OWASP standards

• /universal-dev-standards:skill-builder

  [UDS] Identify repeated processes and build Skills with the right development depth.

• /universal-dev-standards:slo

  [UDS] Guide SLI selection, SLO setting, and Error Budget management

• /universal-dev-standards:tdd

  [UDS] Guide through Test-Driven Development workflow

• /universal-dev-standards:update

  [UDS] Update development standards to latest version

Subagents (6)

• README
• code-architect

  Software architecture specialist for system design and technical planning. Use when: designing systems, planning architecture, evaluating patterns, creating technical proposals. Keywords: architecture, system design, design patterns, technical design, API design, database modeling, 架構, 系統設計, 技術設計. -

• doc-writer

  Documentation specialist for technical writing, API docs, and user guides. Use when: writing documentation, creating READMEs, API documentation, user guides, changelogs. Keywords: documentation, README, API docs, user guide, technical writing, changelog, 文件, 說明文件. - technical-writing - api-documenta

• reviewer

  Code review specialist for quality assessment, security analysis, and best practices enforcement. Use when: reviewing pull requests, checking code quality, security audit, pre-merge review. Keywords: code review, PR review, quality check, security audit, pull request, 程式碼審查, PR 審查. - code-review - s

• spec-analyst

  Specification analysis specialist for requirement extraction and spec generation. Use when: analyzing requirements, extracting specs from code, creating specifications, requirement clarification. Keywords: specification, requirements, analysis, spec extraction, user stories, 規格分析, 需求, 規格. - requirem

• test-specialist

  Testing strategy specialist for test design, coverage analysis, and quality assurance. Use when: designing tests, analyzing coverage, implementing TDD/BDD, writing test plans. Keywords: testing, TDD, BDD, unit test, integration test, coverage, test strategy, 測試, 單元測試, 整合測試. - test-strategy - tdd - b

Similar plugins