Skill UI

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.

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.

This skill guides the creation of comprehensive Product Requirements Documents (PRDs) following industry best practices. It ensures all critical sections are included, such as problem statements, user stories, functional/non-functional requirements, technical considerations, and success metrics. Use it when formalizing a new feature or product specification for engineers and stakeholders.

This skill transforms vague feature briefs, PRD sections, or general ideas into highly detailed, actionable user stories. It enforces industry best practices by including standard formats (As a... I want to...), behavioral acceptance criteria (Given/When/Then), edge cases, and a Definition of Done. Ideal for product managers and business analysts who need to create estimate-ready tickets for development teams.

This comprehensive template provides a structured framework for creating Product Requirements Documents (PRDs). It guides product managers and teams through defining the core problem, setting measurable success metrics (KPIs), defining feature scope, detailing user stories, integrating design notes, and planning the release rollout, ensuring all phases of product development are fully documented.