Skill UI

This mode simulates a P9 Tech Lead role, specializing in strategic project management and complex task orchestration. It does not write code itself, but focuses on generating detailed, structured Task Prompts (six elements) and managing the entire workflow delivery from multiple specialized agents (P8 teams). Ideal for coordinating large, complex projects requiring strategic decomposition and coordination of three or more parallel agents.

This skill acts as a technical translator, helping Product Managers understand complex systems, codebases, APIs, and technical concepts. It goes beyond simply explaining technology by connecting technical details to real-world product implications (the 'so what'). It structures findings into summaries, workings, product impacts, and crucial questions for engineering, ensuring all insights are immediately actionable for product decisions.

This skill synthesizes a comprehensive Product Requirements Document (PRD) from the current conversation context and understanding of the codebase. It guides the user through structuring the problem statement, defining detailed user stories, outlining implementation decisions, and suggesting test strategies. The final PRD is formatted and submitted directly as a GitHub issue, ensuring a structured handover from discussion to development specification.

This skill transforms vague or high-level project ideas into eight comprehensive, interconnected planning documents (PRD, TechSpec, Design, Schema, etc.). It establishes a definitive, persistent source of truth for the project's scope, architecture, and design guidelines before a single line of code is written. Ideal for initiating brand-new software projects to prevent scope creep and planning gaps.

A comprehensive, step-by-step checklist designed for authors preparing manuscripts for submission to Manufacturing & Service Operations Management (M&SOM). It covers crucial elements including double-anonymous anonymization, strict formatting rules (32-page cap, structured abstract), proper departmental routing, and data/code disclosure requirements, ensuring readiness for the scholarOne portal submission.

This command acts as a crucial product gate, forcing a deep, strategic review before any code is written. Instead of simply fulfilling the request, it guides users through three structured roles: Scope Expansion (finding the 10x vision), Hold Scope (stress-testing assumptions and failure modes), or Scope Reduction (defining the true MVP). It ensures that the developed solution solves the user's real job-to-be-done, not just the explicit feature request.