Skill UI

This assistant guides users through the structured process of creating comprehensive product briefs, PRDs, and feature specifications. It ensures that all critical elements—including problem statements, user value, success metrics, scope boundaries (in/out), and dependencies—are clearly defined before development begins, enabling effective product scoping and communication.

This skill takes large plans, specifications, or Product Requirement Documents (PRDs) and systematically breaks them down into small, independently verifiable, and actionable GitHub issues. Utilizing the 'vertical slice' (tracer bullet) methodology, it ensures that each generated task cuts through all integration layers (UI, API, Schema, Tests) end-to-end. It manages dependencies, identifies required human interaction (HITL) versus autonomous implementation (AFK), and prepares a structured, executable backlog ready for immediate ticketing.

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 professional writing assistant specializes in creating clear, compelling, and highly structured documentation for Product Managers (PMs). It helps users draft, refine, and polish various deliverables—including product briefs, status updates, and executive emails—by adhering to best practices like leading with conclusions, maintaining extreme conciseness, and tailoring the tone to the specific audience (e.g., engineering team vs. executive leadership).

This skill generates a comprehensive, one-page product specification document (PRD) or feature brief. It structures critical information—including problem statements, success metrics, user stories, and scope—into a professional, actionable markdown/HTML format. Ideal for formalizing product ideas and kickstarting development planning when presented with terms like 'PRD' or 'spec'.

This skill summarizes the current conversation into a structured handoff document, ideal for passing work to a fresh AI agent or starting a new session. It avoids content duplication by referencing existing artifacts (PRDs, plans, issues, commits) using their paths or URLs, ensuring the receiving agent has a concise and actionable overview of the project's state, open decisions, and next steps.

This skill automates the transformation of high-level product specifications (PRDs) or feature specs stored in Notion into an actionable development lifecycle. It systematically parses requirements, generates structured implementation plans, breaks down complex needs into manageable, linked tasks, and facilitates continuous progress tracking, ensuring all development artifacts remain synchronized with the original spec.

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.

This skill surfaces and prioritizes hidden assumptions embedded in product briefs, PRDs, or concept descriptions. It assesses assumptions across Desirability, Feasibility, Viability, and Usability, scoring them by Confidence and Impact to create a structured, prioritized map. It is essential for product risk auditing, validating product plans, and ensuring the robustness of early-stage concepts.

This skill transforms vague feature briefs or Product Requirement Documents (PRDs) into highly structured design handoff briefs. It ensures designers have comprehensive context before starting work, including the core user goal, emotional context, critical technical constraints, necessary edge cases, and clear scope boundaries, preventing misdirection and scope creep.

Automatically generates a comprehensive, structured design brief for Figma. Users can input raw product requirements or feature requests, and the skill outputs a complete spec including goals, detailed user flows, required screens, component usage, constraints, and success criteria, ensuring designers have everything needed to start building confidently.

This skill automates a structured Product Management (PM) design review process. It assesses a Figma design against defined product requirements (PRD) and user flows, ensuring functional completeness and readiness for engineering handoff. It checks for requirements coverage, handles edge cases (empty/error/loading states), identifies functional concerns (not aesthetic), and provides a clear, actionable approval status.