Skip to content
cccskills
FreePublished on GitHub

prd

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".

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252 stars(GitHub 252 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

PRD Generation

Orchestrate the multi-agent workflow for comprehensive PRD creation.

When working on Arbitrum projects, use @arbitrum-best-practices for domain-specific patterns.

When to Use This Workflow

USE /prd for:

  • New features with multiple components
  • System redesigns or major refactors
  • External-facing APIs or SDK features
  • Cross-team initiatives requiring alignment
  • Features with security/compliance implications
  • Complex implementations with multiple integration points

DON'T USE /prd for:

  • Bug fixes (just fix them)
  • Simple features with clear, limited scope
  • Internal tooling tweaks
  • Quick iterations on existing features
  • Exploratory spikes (use /research instead)

If unsure, ask: "Would I regret not having written requirements for this?" If no, skip the PRD.

Core Flow

research → requirements → specs → design
   (1)         (2)         (3)      (4)

This produces an Implementation Design Document that defines WHAT to build and HOW.

Full Workflow

/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.

Phase Details

Research

subagent_type: researcher

  • Analyze 3-5 similar solutions
  • Document anti-patterns and failure lessons
  • Identify domain-specific considerations

Requirements

subagent_type: product-manager

  • Iterative questioning (2-4 questions per round)
  • Extract functional requirements (FR-001, FR-002...)
  • Extract non-functional requirements (NFR-001, NFR-002...)
  • Define constraints, assumptions, out-of-scope

Specs

subagent_type: product-manager

  • Transform requirements into precise specifications
  • Define data models with types and constraints
  • Document API contracts (inputs, outputs, errors)
  • Write testable acceptance criteria

Design

subagent_type: architect

  • System design and component breakdown
  • Technology stack with justification
  • File paths and integration points
  • Security and scalability approach

QA

subagent_type: qa

  • Hostile falsification of complete PRD
  • Edge case generation
  • Traceability check (requirement → spec → design)
  • Risk assessment

Polish

subagent_type: code-quality-engineer

  • Terminology consistency audit
  • Glossary creation
  • Clarity improvements throughout

Docs

subagent_type: docs

  • Document structure review
  • Executive summary
  • Final formatting

Shared Document

All agents write to: PRD-[project-name]-[YYYY-MM-DD].md

Output

Final PRD includes:

  • Executive Summary
  • Domain Research
  • Requirements Specification
  • Technical Specifications
  • Implementation Design
  • Validation Report
  • Glossary
  • Unresolved Questions (even if "None")

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

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.

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

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.

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

cast

Free

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".

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

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".

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

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'.

The English summary is being prepared. Showing the original description.

OffchainLabs/arbitrum-docs252Updated Oct 24, 2026

See all skills by OffchainLabs

Report a problem with this skill