imedicalxc-doctor-extend-engineer

Orchestrate a 10-step workflow for integrating third-party systems with the HIS doctor station.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-extend-engineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: imedicalxc-doctor-extend-engineer
Source: https://github.com/SkylerCook/imedical.agents/tree/main/plugins/imedicalxc-doctor-extend-engineer/skills/imedicalxc-doctor-extend-engineer
Command: npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-extend-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires superpowers:brainstorming, superpowers:writing-plans, superpowers:subagent-driven-development, superpowers:finishing-a-development-branch, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the entire 10-step workflow for integrating third-party systems with the HIS doctor station, from requirement brainstorming to CI/CD delivery, saving time and reducing errors in complex integrations.

Core Features & Use Cases

  • End-to-End Workflow Orchestration: Manages the complete 10-step process for third-party system integration, including requirement analysis, design, implementation, testing, and delivery.
  • Domain-Specific Skills Integration: Dynamically loads and integrates domain-specific skills for architecture, scope analysis, planning, implementation, and delivery.
  • Use Case: For a project integrating a new diagnostic system with the HIS doctor station, this Skill guides the engineer through each step, ensuring compliance with architectural principles and domain-specific requirements.

Quick Start

Use the imedicalxc-doctor-extend-engineer skill to initiate the integration workflow for a new third-party diagnostic system.

Frequently Asked Questions about imedicalxc-doctor-extend-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to orchestrate end-to-end HIS doctor station third-party system integration?▼

HIS doctor station integration is managed through a 10-step workflow covering requirement analysis, design, implementation, testing, and CI/CD delivery. This structured orchestration dynamically loads domain-specific skills to ensure compliance with architectural principles and reduce integration errors.

How do I plan CI/CD delivery for a new diagnostic system connecting to an HIS?▼

You plan CI/CD delivery for a diagnostic system by following a workflow that spans from initial requirement brainstorming to final delivery. The process dynamically integrates domain-specific skills for scope analysis, architecture planning, and implementation to streamline delivery.

Can I use this workflow for third-party integration scope analysis and architecture design?▼

Yes, you can use this workflow for third-party integration scope analysis and architecture design. The 10-step process dynamically loads domain-specific skills specifically to handle architectural principles and comprehensive scope analysis.

Does the integration workflow support requirement brainstorming before implementation?▼

Yes, the integration workflow supports requirement brainstorming before implementation. It initiates a structured 10-step process starting with requirement analysis and brainstorming, guiding engineers through design, implementation, and testing before final CI/CD delivery.

What domain knowledge is needed for HIS doctor station third-party integrations?▼

You need a comprehensive understanding of the HIS domain and third-party system integration processes. This includes knowledge of CI/CD, workflow orchestration, system integration, and architectural principles to successfully navigate the 10-step delivery workflow.