Skill UI

This tool generates a comprehensive hiring rubric and technical interview scorecard for evaluating software engineers at specific levels and roles. It defines clear behavioral anchors, structured technical questions, and system design criteria, ensuring consistent, unbiased evaluation across all interviewers, and providing a full debrief agenda.

Produces a structured, scannable weekly engineering status report. This tool helps teams communicate critical progress, key metrics, decisions, blockers, and future priorities to stakeholders and management. The standardized format ensures information is easily digestible and highly professional, making status updates clear and concise.

Runs a comprehensive, systematic QA check on Figma designs to ensure they are production-ready before handing off to engineering. The checklist rigorously evaluates file hygiene, component consistency, accessibility (WCAG AA), content completeness, and overall readiness across multiple platforms (iOS/Android/Web). Use this skill when needing to validate a design’s quality and structure to prevent costly development rework.

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 planning and structuring of Figma prototypes specifically for usability testing and user research. It helps define the precise scope (in/out scope), specifies every interaction detail (trigger, elements, animations), builds comprehensive flow diagrams, and generates detailed test task scripts. It ensures the prototype is the minimum viable version needed to answer the research questions, preventing scope creep and over-engineering.

This skill generates a comprehensive, role-assigned checklist for product launches, feature releases, or major updates. It guides cross-functional teams through pre-launch readiness (Engineering, Marketing, Support), critical Go/No-Go decision points, launch day execution, and post-launch monitoring, ensuring a structured and complete deployment process.

A comprehensive skill for generating a structured Request for Comments (RFC) document. Use this to formally propose technical decisions, architectural changes, or significant system implementations. The output ensures all critical aspects are covered, including problem statements, proposed solutions, rejected alternatives, success metrics, and migration plans, facilitating rigorous technical review and decision-making.

This tool analyzes historical sprint velocity data to generate a comprehensive engineering team health report. It moves beyond simple charts by diagnosing underlying delivery patterns, identifying risks like chronic over-commitment, and assessing story point calibration. The report provides actionable recommendations for improving capacity planning and team predictability.

This skill generates a comprehensive Technology Radar document following the ThoughtWorks format. It provides a structured framework for an engineering team to evaluate and categorize all significant technologies (tools, languages, platforms, techniques) into four quadrants (Adopt, Trial, Assess, Hold). It helps establish a shared, explicit technology strategy, detailing adoption rationales, decision trails, and maintenance processes for consistent engineering choices.

This skill generates a comprehensive technical debt register for any team or service. It guides users to input critical data points (e.g., business impact, effort, tech stack) and produces a structured report that categorizes debt (Architecture, Security, Testing, etc.). The output includes a calculated priority score and a quarterly debt reduction roadmap, enabling deliberate, business-aware engineering decision-making.

A comprehensive template designed to structure complex technical specifications, ensuring a complete record of engineering decisions. It guides users to document problem statements, proposed solutions, system architecture, data models, API designs, security considerations, and rollout plans, bridging product requirements and technical implementation.

This skill scaffolds the necessary configurations for advanced engineering workflows. It guides the user through setting up the issue tracking system (GitHub, GitLab, or local markdown), defining the canonical triage label vocabulary, and establishing the domain documentation context (single or multi-context). It must be run once to initialize the repository for subsequent agent-driven development skills.