panacea-component-sprint

Coordinate four-phase UI improvement sprints for PANaCEa components.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill panacea-component-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: panacea-component-sprint
Source: https://github.com/aaronjullger-lgtm/PANaCEa/tree/main/.claude/skills/panacea-component-sprint
Command: npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill panacea-component-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates end-to-end UI improvement sprints for PANaCEa components to help a lone developer deliver reliable, ship-ready UI updates for the platform.

Core Features & Use Cases

  • Four-phase improvement workflow (Explore → Plan → Implement → Verify) that surfaces findings, plans, and verifications for any PANaCEa UI subsystem, including the clinical library, toolkit, calculators, interpreters, dashboard widgets, drill components, and reference views.
  • Structured collaboration model for auditing, fixing, and polishing UI components across the codebase, with reusable templates and checks to ensure consistency and safety.
  • On-demand reusability: trigger for additional improvement cycles and rapid iteration when requirements change or issues are discovered.

Quick Start

Start by selecting a PANaCEa UI subsystem (e.g., calculators) and initiate the four-phase sprint to explore, plan, implement, and verify improvements.

Frequently Asked Questions about panacea-component-sprint

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

FAQPage Schema
How do I coordinate end-to-end UI improvements for a complex codebase?

Coordinate UI improvements using a four-phase workflow: Explore, Plan, Implement, and Verify. This approach audits, fixes, and polishes UI modules across development cycles, ensuring reliable, ship-ready changes with structured findings and rigorous verification checks.

What is a phased workflow for auditing and fixing UI components?

A phased workflow improves UI components by exploring the codebase to surface findings, planning actionable changes, implementing fixes, and verifying outcomes with rigorous checks to ensure safety and consistency.

How do I start a UI improvement sprint for specific subsystems like calculators or dashboard widgets?

Start by selecting a target UI subsystem, such as calculators or dashboard widgets, and initiate the four-phase sprint. The workflow guides you through exploring, planning, implementing, and verifying updates specifically for that module.

Can I reuse an improvement workflow across multiple UI subsystems?

Yes, the workflow supports on-demand reusability across various UI subsystems. Trigger additional improvement cycles and rapidly iterate whenever requirements change or new issues are discovered across different modules.

How do I verify UI changes are ship-ready during a development cycle?

Verify changes are ship-ready by applying the final verification phase, which performs rigorous checks on implemented updates. This ensures structured findings and actionable plans translate into safe, reliable outcomes.