>

Create the Visual Interface for audio plugins. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.

Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017/745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.

Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.

Creates comprehensive technical documentation from existing

>

Provides overview of architecture documentation state.

bmad-planner

This skill should be used when creating or organizing working files in the .claude/ directory. It enforces consistent structure, naming conventions, and required cross-references for plans, architecture docs, examples, research, and analysis files.

Research topics thoroughly and write comprehensive, well-structured content including articles, documentation, blog posts, and technical writing with proper citations and sources. Use when writing blog posts, creating technical articles, researching topics, gathering sources, writing documentation, creating educational content, or producing research-backed content.

Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.

Archive outdated design documentation. Use when design docs are no longer relevant, have been superseded, or document deprecated features.

Comprehensive health audit for design documentation. Use when performing thorough quality checks, preparing for releases, or ensuring documentation compliance.

Manage design documentation system configuration. Use when initializing the system, adding modules, or updating quality standards.

Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.

Co-author design docs and propose section-by-section requirement edits

Create architecture documentation and ADRs from PRD requirements

>-

Sync design docs with codebase state. Use when verifying documentation accuracy, after code changes, or when last-synced is stale.

>

Sync user documentation with design doc changes. Use when design docs

Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content

Summarize long documents with key points and abstracts. Use when creating executive summaries or condensing content.

fdd-feature-design

'Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.'

Game Design Document creation and structure. Use when no GDD exists in the project, starting a new game project, major feature requires design documentation, GDD needs updating due to changes, or preparing for prototype or production.

**Monitor open GitHub issues, match them to design docs, identify closable issues, and keep the issue tracker synchronized with actual development progress.**

infra-architect

Expert guide for documenting infrastructure including architecture diagrams, runbooks, system documentation, and operational procedures. Use when creating technical documentation for systems and deployments.

Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.

Document generator that produces polished markdown for any technical document - tickets, PR descriptions, spikes, plans, reports, architecture decisions, RFCs, and proposals. Use directly when the user asks to write, draft, or summarize a document or plan, or as the writing engine called by other skills (e.g. write-tickets for ticket markdown, dev-workflow-write-pr for PR body content).

docs-architect workflow skill. Use this skill when the user needs Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

docs-architect workflow skill. Use this skill when the user needs Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

This public intake copy packages `packages/skills-catalog/skills/(creation)/create-technical-design-doc` from `https://github.com/tech-leads-club/agent-skills` into the native Omni Skills editorial sh

Game planning and production agent. GDD structuring, game balance math, narrative design, economy design, systems design, player psychology, and production management. Does not write code.

>

Document system architecture and technical design decisions for effective team communication and ...

>

>

>

Execute from requirement analysis to design document creation

Execute from requirement analysis to frontend design document creation

Create frontend work plan from design document and obtain plan approval

Create work plan from design document and obtain plan approval

Summarize academic papers with structured extraction of key elements

| Condition | Required Documents | Creation Order |

>

Support agents currently spend a median of 8 minutes composing the first reply to each ticket. Much of that time is spent searching the internal knowledge base (KB) of ~500 Zendesk articles, copying r

Transforms technical documents into rigorous learning journeys with collegiate-level mastery requirements. Uses Bloom's taxonomy progression, 80%+ mastery thresholds, and multi-level verification before advancing. Treats learning as a high school to college graduation progression. Use when user wants deep understanding, not surface familiarity.