magebyte-power

Use when a user has received a product requirements document (PRD, feature spec, or PM-written requirements) and needs to convert it into engineering work: sprint tasks, technical feasibility review, service/team impact analysis, or implementation planning. The defining signal is an existing product artifact from a PM — not ideation or debugging existing code. Unlike brainstorming (no doc yet) or spec-driven-development (user writes their own spec), this skill's input is always an external requirements document that needs translation into executable developer tasks with real file paths. Invoke immediately without clarifying questions. Also triggers in Chinese: PM发了需求文档、PRD拆任务、技术方案评审、哪些服务受影响、工程师执行的任务清单.

The user wants to build backend code correctly and knows (or should know) that mistakes here are expensive. Use when they are implementing — not explaining — any of: payment or refund flows, wallet balance updates, idempotent MQ consumers and deduplication logic, distributed locks for concurrency or oversell prevention, dual-write database migrations, or cross-service state machine refactors. The defining signal: this is an implementation request in a domain where bugs cause financial loss, stuck orders, or production incidents. Always invoke on /cross-verified-workflow. Also invoke when users signal caution: 幂等, 资金安全, 生产事故, 严谨, or English equivalents. Skip for UI/frontend, one-time scripts, documentation, and conceptual questions.