Loading...
Loading...
Found 314 Skills
Integrated Collaboration for PRD + Executable Test Cases (Development Paradigm v2 Definition Section). Input is a finalized split task/requirement; outputs 4 files: PRD-MD and Test Case-MD (fact sources for AI) + two template-based review HTMLs (for human review, strictly 1:1 with MD). Co-write and iterate with users: autonomously read code after understanding requirements before writing; story-driven + phased single-point confirmation; UI stories include ASCII wireframes + Mermaid capabilities. Triggers: organizing/writing/refining PRDs, requirement documents, user stories, acceptance criteria, test cases, test benchmarks, test plans. Not applicable to: ambiguous requirements not split into tasks (use issue-pool first), unexplored interface solutions (use design-exploration first, whose output requirement-summary.md is exactly the input for this skill), small requirements for modifying an already launched feature (use req-change-workflow), long HTML articles/retrospectives/reports for human reading (use readable-output), project-level framework plans and version roadmaps (use issue-pool), writing code or running tests (this skill only produces documents, does not implement or execute cases).
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.
Generate a design document (design proposal) from a PRD, following the style of Go's official design proposals — structured with Abstract / Background / Design / Rationale / Compatibility / Implementation sections, with a strong focus on the 'why' behind decisions and tradeoffs. Trigger keywords: to-design, prd-to-design, PRD to design document, generate design document, write design document, design doc, design proposal, design proposal, technical design document.
Generates a polished, static HTML reading view from an existing Markdown PRD or technical design. Use when a user asks to render, present, visualize, or make a PRD or design document easier for humans to read in a browser.
Implement a piece of work based on a PRD or set of issues.
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.
Use this skill any time the user wants to create, draft, or generate a written document or report. This includes: competitive analysis, market research reports, technical design docs, PRDs, project proposals, meeting summaries, white papers, business plans, literature reviews, due diligence reports, industry analysis, executive summaries, SOPs, memos, and any request where the output is a structured document. Also trigger when: user says 写个文档, 做个竞品调研, 写份报告, 产品需求文档, 技术方案, 项目提案, 行业分析, 会议纪要整理成文档. If a document or report needs to be created, use this skill.
Generate Next.js projects based on configurations and requirements, supporting the --quick fast mode to skip the PRD phase
The ultimate autonomous dev pipeline. Combines wavybaby (CoVe verification, skill discovery, MCP tooling) + GSD (roadmaps, phases, plans, discovery, state tracking) + Ralph (autonomous loop with circuit breakers). Generates a PRD, equips itself with the best tools, bootstraps a full GSD .planning/ structure, then runs Ralph to autonomously execute each plan with CoVe-verified code until the milestone is complete.
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.