home / skills / a5c-ai / babysitter / fda-510k-submission-generator

This skill automates FDA 510(k) submission preparation by generating predicate comparisons, equivalence arguments, and policy-compliant device documentation

npx playbooks add skill a5c-ai/babysitter --skill fda-510k-submission-generator

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.0 KB
---
name: fda-510k-submission-generator
description: Automated 510(k) premarket notification preparation for generating submission packages, predicate device comparisons, and substantial equivalence arguments
allowed-tools:
  - Read
  - Write
  - Glob
  - Grep
  - Edit
  - Bash
metadata:
  specialization: biomedical-engineering
  domain: science
  category: Regulatory Compliance
  skill-id: BME-SK-001
---

# FDA 510(k) Submission Generator Skill

## Purpose

The FDA 510(k) Submission Generator Skill automates the preparation of 510(k) premarket notifications for medical devices. It streamlines the creation of submission packages, predicate device comparisons, and substantial equivalence arguments to support regulatory clearance.

## Capabilities

- Predicate device database search and comparison
- Substantial equivalence argument drafting
- Device description template generation
- Performance data tabulation
- eCopy package structure validation
- FDA eSTAR form population assistance
- Indications for use statement generation
- Biocompatibility summary generation
- Software documentation compilation (if applicable)
- Performance testing summary tables
- Labeling content review assistance

## Usage Guidelines

### When to Use
- Preparing FDA 510(k) premarket notification submissions
- Identifying and comparing predicate devices
- Documenting substantial equivalence arguments
- Compiling regulatory submission packages

### Prerequisites
- Device design documentation completed
- Performance testing data available
- Predicate device research conducted
- Biocompatibility data compiled

### Best Practices
- Verify predicate device selection with regulatory team
- Ensure all performance data supports substantial equivalence
- Cross-reference with current FDA guidance documents
- Validate submission format against FDA requirements

## Process Integration

This skill integrates with the following processes:
- 510(k) Premarket Submission Preparation
- EU MDR Technical Documentation
- Post-Market Surveillance System Implementation
- Design Control Process Implementation

## Dependencies

- FDA GUDID API
- FDA 510(k) Database
- eSTAR templates
- CDRH guidance documents
- Product code database

## Configuration

```yaml
fda-510k-submission-generator:
  submission-types:
    - traditional
    - abbreviated
    - special
  device-classes:
    - Class I
    - Class II
  output-formats:
    - eCopy
    - eSTAR
  sections:
    - cover-letter
    - device-description
    - substantial-equivalence
    - performance-data
    - labeling
```

## Output Artifacts

- Complete 510(k) submission package
- Predicate device comparison tables
- Substantial equivalence arguments
- Device description documents
- Performance data summaries
- Labeling drafts
- eCopy file structure

## Quality Criteria

- Submission follows current FDA format requirements
- Predicate device selection is well-justified
- Substantial equivalence arguments are comprehensive
- All required sections are complete and accurate
- Performance data supports claimed equivalence
- Documentation suitable for FDA review

Overview

This skill automates preparation of FDA 510(k) premarket notification packages to accelerate regulatory submission readiness. It generates predicate device comparisons, drafts substantial equivalence arguments, and produces structured output like eCopy and eSTAR-friendly artifacts. The focus is on consistent, review-ready documents that align with FDA formatting and common guidance.

How this skill works

The skill ingests device design details, performance test results, labeling, and predicate research to populate section templates and comparison tables. It performs predicate device matching against public databases, drafts substantial equivalence rationale, and validates eCopy package structure and eSTAR form fields. Outputs include device descriptions, performance summaries, labeling drafts, and exportable submission bundles.

When to use it

  • When preparing a 510(k) premarket notification (traditional, abbreviated, or special).
  • During predicate device research and comparison to establish potential predicates.
  • To draft and iterate substantial equivalence arguments backed by performance data.
  • When assembling eCopy or eSTAR-ready submission packages.
  • To standardize documentation for regulatory review or internal submission checklists.

Best practices

  • Confirm predicate device choices with your regulatory or legal team before finalizing comparisons.
  • Provide complete performance and biocompatibility data; drafts rely on source data accuracy.
  • Cross-check generated content against the latest FDA CDRH guidance and product-specific guidance documents.
  • Use structured inputs (templates, test tables) to reduce manual cleanup and improve traceability.
  • Validate final package with an internal regulatory review and a submission checklist before e-filing.

Example use cases

  • Generate a complete 510(k) package from device specs and test reports for a Class II surgical instrument.
  • Create predicate device comparison tables and scoring to support device selection and strategy sessions.
  • Draft substantial equivalence sections and indications for use statements for iterative review with regulatory affairs.
  • Produce eCopy folder structure and pre-fill eSTAR fields to speed electronic submission preparation.
  • Compile software documentation and performance summary tables for a medical device with embedded software.

FAQ

Does this skill file to the FDA automatically?

No. It generates submission-ready artifacts and validates formats but does not perform electronic filing. Final review and submission must be done by your team.

What inputs are required to produce a complete package?

Essential inputs include device description, performance test data, biocompatibility results, labeling drafts, and predicate device research. More complete inputs produce higher-quality drafts.