Loading...
Loading...
Found 407 Skills
Analyzes Figma designs and generates implementation-ready PRDs with detailed visual specifications. Use when user provides Figma link or uploads design screenshots. Requires Figma MCP server connection.
Generate a Phase Spec/PRD by extracting features from an annotated Vision PRD. Use when user wants to create quarterly phase documentation, extract requirements from vision, plan a development phase, or decompose features into R-nnnn requirements. Requires annotated Vision PRD with F-nnn tags and Coverage Index.
Use when a Lightning Web Component data need is described in ambiguous natural language — turn "get contact info" or "show account data" into a clear, PRD-ready data-requirements spec. TRIGGER when the user says "define data requirements for this LWC", "turn this PRD data section into validated object/field names", "recommend GraphQL vs UIAPI for this data need", "validate these Salesforce API names", or "spec out the LDS adapter for this component", or references LWC bundle files (`.js`, `.js-meta.xml`) whose data layer is not yet specified. DO NOT TRIGGER when the data layer is already fully specified, when authoring the actual query or adapter code from a known spec, or when implementing an LWC end-to-end (use experience-lwc-generate).
Turn a vague feature or product idea into an agreed, persisted specification through relentless structured questioning. Never assumes — every gap, ambiguity, or "probably" becomes a question to the developer, and the spec cannot be approved while open questions remain. Produces docs/specs/<NNN>-<slug>.md with acceptance criteria that /plan, /scaffold, and /tdd consume. Use when: "spec", "write a spec", "spec this out", "requirements", "PRD", "acceptance criteria", "define the feature", "user stories", "what should we build", or before planning any feature too big to describe in one sentence.
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.
Interactive project planning for PRD, architecture, and epic/story generation. Use for new projects, planning features, creating PRDs, designing architecture, breaking down work into epics and stories.
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
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.
사용자의 업무 문제, 아이디어와 제공된 자료를 구현 가능한 제품 정의로 구체화한다. 아이디어가 없거나 일부 맥락만 있거나 명확한 아이디어가 있어도 사용자·업무·UX 정보의 부족을 단계적으로 확인한다. “무엇을 만들지 정리해줘”, “아이디어를 구체화해줘”, “요구사항 문서를 만들어줘”, “PRD를 만들어줘”처럼 구현 전에 사용자·문제·범위·완료 조건과 경험 방향을 정하는 요청에 사용한다. 제품 정의와 UX 방향이 이미 충분히 확정되어 코드 변경만 요청한 경우에는 사용하지 않는다.
Write or update a single-feature PRD (`Type: feat`/`fix`/`chore`) with scope, user stories, and acceptance criteria. Triggers: plan prd, write feature spec, define acceptance criteria, update prd.
As a standard S0 pre-skill for larger page workflows like `hiui-page-workflow`, it focuses on requirement refinement for B-end back-office systems and before HiUI page generation. It transforms vague or abstract back-office/management/operation/configuration/approval workflow requirements into executable product solutions, MVP scopes, user flows, business rules, traceable page inventories, product PRDs, global generation contexts, page-level prompts, and HiUI handoff packages. It is suitable for clarifying back-office product ideas, converting rough requirements into PRDs or product solutions, breaking down work surfaces such as lists/details/editing/configuration, defining role permissions/data permissions/state machines/audit rules, and supplementing permission matrices, state transition tables, field dictionaries, exception and audit matrices, batch/import-export specifications, and legacy system transformation and release strategies when needed; it also acts as a B-end product expert to provide judgments including business value decomposition, priority suggestions, solution trade-offs, multi-tenant/version/activation models, master data and system boundaries, anti-pattern identification and risk prompts, continuously turning vague B-end requirements into implementable inputs; when requirements arise in existing projects/repositories, it is also used to perform context-aware requirement refinement combining the current repository's pages, modules, interfaces, types, and documents.
Implement one prd.json task per iteration using tracer-bullet + compound mindset. Triggers on: ratatouille:.