Skill UI

Converts product or technical specs into detailed Notion implementation plans, tasks, and progress logs so Claude code can execute requirements tracking from inception to completion.

Creates high-fidelity visuals through structured JSON prompts and a Python generator script, handling subjects, styles, references, and technical specs for characters, scenes, or products.

A comprehensive workflow designed for Product Managers and technical leads to systematically identify, prioritize, and document missing features in a software project. It guides users through project understanding, gap analysis, applying a scoring matrix for prioritization, developing detailed Minimum Viable Product (MVP) specifications, and structuring the output as actionable development issues (e.g., GitHub Issues) with dependency mapping and workload optimization.

This skill serves as a comprehensive entry point for initiating new development work. It systematically analyzes project metadata (specs, roadmaps) to determine the optimal work decomposition path (new spec, existing extension, or simple fix). By conducting deep context loading and guiding structured dialogue, it refines vague ideas into clearly defined, actionable scope boundaries. Finally, it proposes multiple concrete technical approaches, complete with trade-offs and estimates, ensuring the resulting project scope is well-defined and ready for implementation.

A comprehensive, final-gate audit guide for submitting papers to major robotics conferences like ICRA using the PaperPlaza system. It details mandatory technical specifications, including page limits (6 content + 2 refs), IEEE two-column compliance, double-anonymous rules, video attachment specs, and critical deadlines. Essential reading to prevent submission rejection or administrative disqualification.

This workflow bundle facilitates comprehensive technical documentation generation for software projects. It covers creating API documentation, architecture diagrams, README files, code comments, and user guides. The process includes planning, generating OpenAPI specs, documenting code structures, and maintaining wikis. It ensures all documentation types are up-to-date and accurate for developers and users.