Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
日本語の概要は準備中です。原文の説明を表示しています。
8,321 件 ・ 関連度順
概要と使いどころ
Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.
日本語の概要は準備中です。原文の説明を表示しています。
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update product briefs through guided or autonomous discovery. Use when the user requests to create or update a Product Brief.
日本語の概要は準備中です。原文の説明を表示しています。
Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"
日本語の概要は準備中です。原文の説明を表示しています。
System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.
日本語の概要は準備中です。原文の説明を表示しています。
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
日本語の概要は準備中です。原文の説明を表示しています。
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"
日本語の概要は準備中です。原文の説明を表示しています。
Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"
日本語の概要は準備中です。原文の説明を表示しています。
Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
日本語の概要は準備中です。原文の説明を表示しています。
Build React animations with Motion (Framer Motion) - gestures (drag, hover, tap), scroll effects, spring physics, layout animations, SVG. Bundle: 2.3 KB (mini) to 34 KB (full). Use when: drag-and-drop, scroll animations, modals, carousels, parallax. Troubleshoot: AnimatePresence exit, list performance, Tailwind conflicts, Next.js "use client".
日本語の概要は準備中です。原文の説明を表示しています。
Map existing materials into a first knowledge record, or investigate a subject's history in depth. Use whenever the user asks to map, survey, go through, reconstruct or investigate what already exists - folders of documents, decision records, meeting notes, emails, exports, code - or wants a starting record built from existing materials, even when the word 'record' is never said: consult this before listing or reading the files yourself, because a map has an agreed scope, a protocol and a report. Also, once, at a suitable moment, to offer the starting choices where a workspace has no record and the work is clearly ongoing - never on a greeting. Learning while working needs no map. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
kpopper Hub: optional experimental application for exploring the project record. Use when the user explicitly requests kpopper Hub or its record page, its graph, layout or verification, or has a standing preference for this application. Do not render automatically after mapping or recording. Install the HTML runtime before use. Not for ordinary HTML documents or a text answer from the record. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when you need to create isolated git worktree for parallel development.
日本語の概要は準備中です。原文の説明を表示しています。
[Workflow] Use when you need to run /workflow-review-changes repeatedly in an outer convergence loop until a complete whole-workflow run applies zero fixes — recursive re-review of a fixed scope (branch-diff + current changes) until a clean no-op pass.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when you need to generate a detailed, AI-analyzed release document from git history over a time range or custom prompt.
日本語の概要は準備中です。原文の説明を表示しています。
[Process] Use when you need to end the active workflow and clear state.
日本語の概要は準備中です。原文の説明を表示しています。
[Testing] Use when you need individual page/component testing with Python Playwright scripts.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when you need to review recent changes and wrap up the work.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when reviewing UI/frontend changes for long-content overflow, responsive multi-screen layout (flex-wrap / row-to-column on small devices), flex-vs-fixed sizing, z-index discipline, SCSS/BEM styling quality, and async UI states & feedback (loading indicator, error surface, empty state).
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.
日本語の概要は準備中です。原文の説明を表示しています。
[Codex] Use when you need to run the full Codex mirror sync + verify pipeline (migrate → hooks → context → verify) standalone, no npm/package JSON needed.
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.
日本語の概要は準備中です。原文の説明を表示しています。