Loading...
Loading...
Found 40 Skills
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
Create, update, validate, or analyze a PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD.
Create documentation-first PRDs that guide development through user-facing content
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution
Interview user in-depth to create a detailed spec. Use when user wants to define requirements, spec out a feature, or needs help articulating product details.
Creates a new Product Requirements Document (PRD) with auto-numbered filenames in the project's PRD directory. Gathers business context, defines the problem, and produces a structured PRD.
사용자의 업무 문제, 아이디어와 제공된 자료를 구현 가능한 제품 정의로 구체화한다. 아이디어가 없거나 일부 맥락만 있거나 명확한 아이디어가 있어도 사용자·업무·UX 정보의 부족을 단계적으로 확인한다. “무엇을 만들지 정리해줘”, “아이디어를 구체화해줘”, “요구사항 문서를 만들어줘”, “PRD를 만들어줘”처럼 구현 전에 사용자·문제·범위·완료 조건과 경험 방향을 정하는 요청에 사용한다. 제품 정의와 UX 방향이 이미 충분히 확정되어 코드 변경만 요청한 경우에는 사용하지 않는다.
This skill should be used when the user asks to "create a PRD for Replit", "write product requirements", "document app specifications", "prepare a product spec", or needs a comprehensive specification document that Replit Agent can use for complex, multi-feature applications. Creates structured PRDs optimized for AI-powered development.
Create feature definition documents with phased delivery, MVP scope, and definition of done. Use when specifying new product features, user-facing capabilities, or system enhancements that require planning and incremental delivery.
Authoritative reference for Anthropic products. Use when users ask about product capabilities, access, installation, pricing, limits, or features. Provides source-backed answers to prevent hallucinations about Claude.ai, Claude Code, and Claude API.
Use this skill when > Generate a structured Product Requirements Document (PRD) from existing conversation context and codebase state. Synthesizes knowledge into a PRD without interviewing the user. Use when documenting requirements for a feature or change to publish to the project issue tracker.