From guidewire-pack
Data handling best practices for Guidewire InsuranceSuite including entity management, data migration, batch operations, and data governance. Trigger with phrases like "guidewire data", "entity management", "data migration", "batch processing", "data governance guidewire". Use when working with guidewire data handling.
How this skill is triggered — by the user, by Claude, or both
Slash command
/guidewire-pack:guidewire-data-handlingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Best practices for data handling in Guidewire InsuranceSuite including entity management, CRUD operations, data migration, batch processing, and data governance.
Best practices for data handling in Guidewire InsuranceSuite including entity management, CRUD operations, data migration, batch processing, and data governance.
// Gosu entity management patterns
Implement data handling best practices.
For detailed implementation code and configurations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Issue | Solution |
|---|---|
| Configuration error | Check settings |
For role-based access control, see guidewire-enterprise-rbac.
Basic usage: Apply guidewire data handling to a standard project setup with default configuration options.
Advanced scenario: Customize guidewire data handling for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin guidewire-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026