Loading...
Loading...
Found 2,894 Skills
Release preparation workflow - security audit → E2E tests → review → changelog → docs
Validation agent that validates plan tech choices against current best practices
Turn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: "ideation", "brainstorm", "new idea", "explore an idea", "I want to build", "what if we", "let's think about", "propose approaches", "evaluate this idea", "idea document", "アイデア出し", "案出し", "ブレスト", "アイデアを整理", "検討したい".
Persistent decision log that creates a read-write feedback loop: read previous decisions before starting work, respect or supersede them, and write new Y-statement records as you go. Activates during any task involving architectural, structural, or design decisions - choosing libraries, designing schemas, creating modules, making tradeoffs, selecting patterns. Also activates when DECISIONS.md already exists in the project. Do NOT activate for trivial changes like typos, renames, or formatting.
Create a new track with specification and phased implementation plan
Convert USDM/EARS requirements documents from Markdown to professionally formatted Word (.docx) files for client submission. Generates cover pages, table of contents, headers/footers, and styled requirement hierarchies. Leverages the docx skill for Word file generation. Use when: "export requirements to Word", "requirements to docx", "USDM to Word", "convert requirements document", "要件書をWord出力", "要件定義書のdocx変換", "Word形式で要件書を作成", "要件定義書をWordに変換".
Synthesize multiple inputs into a concise one-page executive summary (under 500 words). Use when a PM needs help with one-pager.
Paste in a DM or email thread where partnership terms were discussed and receive a clean bulleted summary of all agreed terms formatted to send back to the creator for confirmation. This skill should be used when summarizing a creator conversation into agreed terms, extracting deal points from a DM thread, turning an email negotiation into a confirmation message, documenting what was agreed with an influencer, cleaning up a messy negotiation thread into clear terms, converting informal creator discussions into a written agreement summary, pulling terms from a back-and-forth DM exchange, creating a confirmation recap from a creator call or chat, formalizing a verbal deal with a creator, or drafting a terms confirmation message to send after a negotiation. For writing the initial outreach messages, see creator-outreach-sequence-generator. For negotiation strategy and counter-offer language, see creator-negotiation-assistant.
Chapter 1 (개발대상 및 필요성) 작성 가이드 - 템플릿, 요구사항, 웹검색 전략 통합
Update PRD based on design decisions and strategic changes made during conversations
Systematic codebase investigation to extract architectural patterns and implementation details from an existing project, with findings persisted for long-term reuse. Use when the user wants to explore an open-source or existing codebase to understand how it works and inform the development of a new project. Triggers include: "explore this codebase", "investigate this repo", "how does X implement Y", "I want to build X, study how Y does it", "deep dive into this project", "understand how this works".
Guides creation of comprehensive Product Requirement Documents (PRDs) for software projects through structured questioning and validation, then generates implementation task lists in JSON format. Use when users want to document a software idea, create specifications for development, plan a new application feature/bug, or break down requirements into actionable tasks. Transforms ideas into implementation-ready documents with verifiable pass criteria.