Loading...
Loading...
Found 31 Skills
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.
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).
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
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
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.
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Convert the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
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.
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
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.
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
Initialize a PRD (Product Requirements Document) for structured ralph-loop execution