Loading...
Loading...
Found 42 Skills
Review and modernize Agent OS product documentation to ensure quantifiable value propositions and workspace-hub standards compliance.
Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.
Transform vague ideas into implementation-ready specifications through structured interviewing. Use when user describes a new feature/product idea, has a problem to solve, or needs to document requirements. Produces intent.md (technical spec for code agents) and overview.md (human-friendly summary).
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Creates user-facing release notes that communicate new features, improvements, and fixes in clear, benefit-focused language. Use when shipping updates to communicate changes to users, customers, or stakeholders.
Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohes
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects.
Analyzes raw requirements into visual specs and generates artifacts. Invoke when user runs /vspec:new for analysis or /vspec:verify for models and prototypes.
사용자의 업무 문제, 아이디어와 제공된 자료를 구현 가능한 제품 정의로 구체화한다. 아이디어가 없거나 일부 맥락만 있거나 명확한 아이디어가 있어도 사용자·업무·UX 정보의 부족을 단계적으로 확인한다. “무엇을 만들지 정리해줘”, “아이디어를 구체화해줘”, “요구사항 문서를 만들어줘”, “PRD를 만들어줘”처럼 구현 전에 사용자·문제·범위·완료 조건과 경험 방향을 정하는 요청에 사용한다. 제품 정의와 UX 방향이 이미 충분히 확정되어 코드 변경만 요청한 경우에는 사용하지 않는다.