Loading...
Loading...
Found 19 Skills
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Product requirements and planning specialist. Creates PRDs and tech specs with functional/non-functional requirements, prioritizes features using MoSCoW/RICE frameworks, breaks down epics into user stories, and ensures requirements are testable and traceable. Use for PRD creation, requirements definition, feature prioritization, tech specs, epics, user stories, and acceptance criteria.
Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user stories, modeling business processes, or translating business needs to technical specs.
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
Generate structured product and technical documents through guided discovery. 8 document types: PRD, Brief, Issue, Task, User Story, RFC, ADR, TDD. Use when: defining products, reporting bugs, planning sprints, writing stories, proposing changes, recording decisions, designing systems. Triggers on "create PRD", "create issue", "report bug", "feature request", "create task", "create user story", "create RFC", "create ADR", "create TDD", "create document", "write doc".
Use when an HR workshop student kicks off the workshop, uploads a filled brainstorm worksheet (any filename), pastes or attaches an idea document, describes an internal tool, or wants to go from a rough idea to PRD, build slice (今日切片), HTML prototype, a running local app, and local run. This is the generic student entry for every group. Do not require a Group 6 / Group 4 wrapper.
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
Product requirements → living doc Requirements section + quality gate + domain glossary. Stateful: detects existing sections and resumes where needed. Triggers: 'define this,' 'write a PRD,' 'define requirements,' 'spec this out,' post-explore. Not for: scoping (explore), UX (design), technical design (architect).
Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
Create detailed feature specifications with user stories, acceptance criteria, and edge cases. Use when starting a new feature or initializing a new project.