ring:writing-prds
Writing a Product Requirements Document that defines WHAT and WHY: problem, user personas, As/I-want/So-that stories, success metrics, and explicit scope, then dispatching UX validation. Gate 1 of ring:using-pm-team; stays technology-free (no architecture, frameworks, or schemas). Use when starting a new feature or asked to plan, design, or produce requirements. Skip when a validated PRD exists, for pure technical changes, or bug fixes.
What this skill does
# PRD Creation — Business Before Technical
## When to use
- Starting new product or major feature
- User asks to "plan", "design", or "architect"
- About to write code without documented requirements
- Asked to create PRD or requirements document
## Skip when
- PRD already exists and validated → proceed to Gate 2
- Pure technical task without business impact → TRD directly
- Bug fix → systematic-debugging
## Sequence
**Runs before:** ring:mapping-feature-relationships, ring:writing-trds
The PRD defines WHAT we're building and WHY it matters to users and business. It never answers HOW we'll build it (that's TRD) or WHERE components will live.
## Mandatory Workflow
| Phase | Activities |
|-------|------------|
| **0. Load Research** | Check `docs/pre-dev/{feature}/research.md`; reference codebase patterns and findings with `file:line` notation |
| **1. Problem Discovery** | Define problem without solution bias; identify specific users; quantify pain with metrics/evidence |
| **2. Business Requirements** | Executive summary (3 sentences); user personas; user stories (As/I want/So that); success metrics (measurable); scope boundaries (in/out) |
| **3. Gate 1 Validation** | Problem articulated; impact quantified; users identified; features address problem; metrics measurable; scope explicit |
| **4. UX Validation** | Dispatch `product-designer` to validate PRD against user needs and create `ux-criteria.md` |
## Include in PRD
- Problem definition and user pain points
- User personas (demographics, goals, frustrations)
- User stories with acceptance criteria
- Feature requirements (WHAT not HOW)
- Success metrics (adoption, satisfaction, KPIs)
- Scope boundaries (in/out explicitly)
- Go-to-market considerations
## Never Include in PRD
- Architecture diagrams or component design
- Technology choices (languages, frameworks, databases)
- Implementation approaches or algorithms
- Database schemas or API specifications
- Code examples or package dependencies
- Infrastructure needs or deployment strategies
**Separation rules:**
- Technology name → Dependency Map
- "How to build" → TRD
- Implementation detail → Tasks/Subtasks
- System behavior → TRD
## Security Requirements Discovery (Business Level)
| Business Question | If Yes → Document |
|-------------------|-------------------|
| Feature handles user-specific data? | "Users can only access their own [data type]" |
| Different user roles with different permissions? | "Admins can [X], regular users can [Y]" |
| Need to identify who performed an action? | "Audit trail required for [action type]" |
| Integrates with other internal services? | "Service must authenticate to [service name]" |
| Regulatory requirements? | "Must comply with [regulation] for [data type]" |
Include: "Only authenticated users can access", "Users can only view/edit their own records", "Admin approval required for [action]"
Exclude: JWT tokens, Access Manager integration, OAuth2 flow — these go in TRD.
## Operational Dashboard Discovery (Business Level)
During PRD creation for features involving data that accumulates over time (transactions, events, operations), ask:
AskUserQuestion: "Will an operator or business manager need a consolidated view of this feature's data to make decisions?"
- "Yes — Business dashboard needed"
- "No — Infrastructure/backend only"
- "Not sure — Needs discussion"
**If "Yes":** Document in PRD under "Dashboard Requirements": consumer persona, decisions supported, key metrics, refresh cadence.
## Gate 1 Validation Checklist
| Category | Requirements |
|----------|--------------|
| **Problem Clarity** | Problem stated without solution; specific user identified; pain quantified |
| **Requirements** | User stories follow As/I want/So that; acceptance criteria testable; all PRD features address problem |
| **Metrics** | Success metrics measurable; baseline + target defined; timeframe specified |
| **Scope** | In-scope features explicit; out-of-scope stated; boundaries clear |
| **Technology-Free** | Zero technology names; zero implementation details; zero framework mentions |
**Gate Result:** ✅ PASS → Feature Map or TRD | ❌ FAIL (re-work technical content or missing requirements)
## Output
**File:** `docs/pre-dev/{feature}/prd.md`
After Gate 1 passes: dispatch `ring:product-designer` to validate UX and create `docs/pre-dev/{feature}/ux-criteria.md`.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.