Generate Product Requirements Document via multi-agent workflow. Use for significant features, new systems, or complex changes that warrant formal specification. NOT for bug fixes, small features, or quick iterations. Triggers on "create PRD", "write requirements", "spec this out", "define the project".
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Orchestrate the multi-agent workflow for comprehensive PRD creation.
When working on Arbitrum projects, use @arbitrum-best-practices for domain-specific patterns.
USE /prd for:
DON'T USE /prd for:
/research instead)If unsure, ask: "Would I regret not having written requirements for this?" If no, skip the PRD.
research → requirements → specs → design
(1) (2) (3) (4)
This produces an Implementation Design Document that defines WHAT to build and HOW.
/context-prep → Project Orientation (run first!)
research → Domain Research (researcher)
requirements → Requirements Discovery (product-manager)
specs → Technical Specifications (product-manager)
design → Implementation Design (architect)
[skip execute] → Implementation is separate
qa → PRD Validation (qa)
polish → Terminology & Glossary (code-quality-engineer)
docs → Final Polish (docs)
IMPORTANT: Run /context-prep first to orient to the project.
subagent_type: researcher
subagent_type: product-manager
subagent_type: product-manager
subagent_type: architect
subagent_type: qa
subagent_type: code-quality-engineer
subagent_type: docs
All agents write to: PRD-[project-name]-[YYYY-MM-DD].md
Final PRD includes:
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Arbitrum L2 development best practices. Use when implementing bridges, Orbit chains, SDK integrations, or debugging cross-chain transactions. Triggers on Arbitrum, L2, rollup, bridge, retryable, Orbit, Nitro, or cross-chain contexts.
日本語の概要は準備中です。原文の説明を表示しています。
Create or improve lightweight, brand-consistent SVG concept diagrams for the Arbitrum docs, using the official Google Drive infographic asset kit as the palette/style source. Use when asked to "make a diagram more efficient", replace a bloated haw-*.svg (draw.io PNG-in-SVG exports), replace an ASCII / box-drawing diagram in an MDX page with a real image, author a new concept diagram for content/docs/how-arbitrum-works or similar, or build a diagram from the Arbitrum brand assets. Hand-authored lean vector SVG — not Mermaid, not a full Excalidraw/draw.io pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to rebrand, restyle, re-pace, resize, or re-render an existing explainer video, when a video's labels are baked-in raster pixels that cannot be edited, or when building a new animated explainer for the Arbitrum docs from a prompt or a doc section.
日本語の概要は準備中です。原文の説明を表示しています。
Foundry's cast CLI for Ethereum interactions. Use when querying blockchain data, calling contracts, sending transactions, encoding/decoding data, or debugging on-chain issues. Triggers on "cast", "get balance", "call contract", "decode calldata", "check tx", "get block".
日本語の概要は準備中です。原文の説明を表示しています。
Run full documentation quality audit, covering sidebar orphans, unused-file review, MDX structure, internal links, glossary references, contract addresses, variables, formatting, frontmatter, tests, and types. Triggers on "audit docs", "check docs quality", "find problems", "content audit".
日本語の概要は準備中です。原文の説明を表示しています。
LLM Utility: Generate minimal project context map before starting any workflow. ALWAYS run this first at session start, before /prd, before /implement, or after context loss. Triggers on 'context prep', 'orient me', 'start', 'new session'.
日本語の概要は準備中です。原文の説明を表示しています。