GxpCode Global Regulatory Guidance Auto-Tracking

Problem

Regulatory and guidance updates for pharma products are scattered across agency sites. Manual monitoring can miss new, revised, or withdrawn documents, and it is hard to judge whether a file affects the company's products.
GxpCode targets regulatory tracking and turns "find documents, diff changes, fetch details, tag content, and report" into a repeatable pipeline.

How It Works

The skill uses config.yaml, sources.yaml, and history.json as state, producing intermediate JSON files and .done markers:
- Source detection: reads RSS or Web sources and extracts candidate regulatory or guidance items.
- Change comparison: uses the history store to identify new, revised, withdrawn, and similar status changes.
- Detail fetching: retrieves full text and PDF attachments into the current workspace.
- Analysis and tagging: summarizes items, assigns tags, and assesses relevance to the configured products.
- Reporting and notification: generates dated Markdown and PDF tracking reports, then updates history.

Branch capabilities include parser matching for new regulatory source URLs and a source management panel triggered by keywords to adjust sources.yaml. Execution constraints emphasize fault tolerance: a single source or item can be skipped, while only a FATAL failure stops the full pipeline.

Scope: the skill is oriented toward ongoing pharma regulatory and guidance tracking, not a full compliance audit. PDF output and tracking data paths follow workspace conventions, and first-time use requires initialization.