Loading...
Loading...
Found 268 Skills
Autonomous mobile dev subagent that implements a single user story from a PRD for Expo / React Native apps. Use when you need parallel, independent mobile implementation tasks — screens, native components, data fetching, navigation. Designed to run alongside other ralph-mobile instances. Receives a specific task ID and PRD path. Returns a structured completion signal. Does NOT commit or modify the PRD — those are handled by the documenter. Loads expo, building-native-ui, vercel-react-native-skills, native-data-fetching, and expo-dev-client skills automatically.
Creates PRDs and plans features.
Bootstrap a Memory Bank for a new or existing repository, then route into PRD-driven or brownfield workflows.
Convert PRDs to prd.json format for the Ralph autonomous agent system. Use when you have an existing PRD and need to convert it to Ralph's JSON format. Triggers on: convert this prd, turn this into ralph format, create prd.json from this, ralph json.
Use when the user says "/plan-review", "plan review", or "PRD review" and provides a plan file path that needs critical review and iterative refinement with Codex.
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs 4 specialized PM agents in parallel to produce a comprehensive PRD before PDCA Plan phase. Integrates pm-skills frameworks (MIT). Use proactively when user wants product analysis before development, needs a PRD, or asks for PM-level planning. Triggers: /pdca pm, pm analysis, product discovery, PRD, pm team, PM 분석, 제품 기획, 제품 발견, PM팀, PRD 작성, PM分析, プロダクト分析, 产品分析, 产品发现, análisis PM, descubrimiento de producto, analyse PM, découverte produit, PM-Analyse, Produktentdeckung, analisi PM, scoperta prodotto Do NOT use for: implementation, code review, existing PDCA phases (plan/design/do/check).
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
Use when making architecture decisions, evaluating build-vs-buy, planning tech stack, prioritizing tech debt, writing PRDs, or needing strategic technical leadership
Product requirements → living doc Requirements section + quality gate + domain glossary. Stateful: detects existing sections and resumes where needed. Triggers: 'define this,' 'write a PRD,' 'define requirements,' 'spec this out,' post-explore. Not for: scoping (explore), UX (design), technical design (architect).
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
Implement one prd.json task per iteration using tracer-bullet + compound mindset. Triggers on: ratatouille:.
Enrich a Phase Sepc/PRD with Quality Requirements (Q-nnn) and Acceptance Criteria (AC-nnnn). Use when user wants to add QA perspective, define test criteria, identify non-functional requirements, add verification steps, or prepare a Phase PRD for test planning.