From maintainx-pack
Execute MaintainX primary workflow: Work Order lifecycle management. Use when creating, updating, and managing work orders through their full lifecycle, from creation to completion with all status transitions. Trigger with phrases like "maintainx work order", "create work order", "work order lifecycle", "maintenance task", "manage work orders".
How this skill is triggered — by the user, by Claude, or both
Slash command
/maintainx-pack:maintainx-core-workflow-aThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Master the complete work order lifecycle in MaintainX - from creation through completion. Work orders are the core unit of maintenance operations.
Master the complete work order lifecycle in MaintainX - from creation through completion. Work orders are the core unit of maintenance operations.
maintainx-install-auth setupFollow these high-level steps to implement maintainx-core-workflow-a:
For full implementation details, load: Read(plugins/saas-packs/maintainx-pack/skills/maintainx-core-workflow-a/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| 400 Bad Request | Missing title | Ensure title field is provided |
| 404 Not Found | Invalid asset/location ID | Verify IDs exist in system |
| 403 Forbidden | Insufficient permissions | Check user role and plan tier |
| Invalid transition | Wrong status flow | Follow valid transition paths |
For asset and location management, see maintainx-core-workflow-b.
Basic usage: Apply maintainx core workflow a to a standard project setup with default configuration options.
Advanced scenario: Customize maintainx core workflow a for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin maintainx-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