prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Discover blockchain project management skills, compare source repositories and read the instructions for each workflow.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Creates Product Requirements Documents (PRDs) for features with user stories in Ralph-compatible format. Use when asked to create a PRD, write requirements, plan a feature, or generate user stories.
Fetch and manage work items from issue trackers. Use this skill when: - User references an issue number (#42, PROJ-123) - User asks about requirements or acceptance criteria - User needs to understand current t...
セッションコンテキストを表示。タブを離れて戻ってきた時に「何をやっていたか」「何を依頼したか」「次に何をすべきか」を思い出すために使用。
This skill shoudl be used when the user ask to "behaviors", "specification", "read implementation", "analyze component", "振る舞いを分析", "振る舞いを理解". Analyze component(module, package, class, function) b...
Log key learnings to progress.txt during PRD iteration. Use when you discover codebase patterns, encounter gotchas, make important decisions, or learn something that would help future work sessions. Triggers on...
Convert a PRD markdown file to a structured JSON task file with progress tracking. Use when converting a PRD to JSON, creating trackable tasks from a PRD, or when asked to make a PRD actionable. Triggers on: co...
Use when creating implementation plans for features or tasks. Focuses on tactical execution planning with clear tasks, dependencies, and success criteria.
Use when about to implement a plan, when plan seems incomplete or has gaps, when unsure if tasks are feasible, or when validating spec before coding
Use when starting a new feature that needs planning - runs brainstorming then creates numbered task folder in _tasks/
Analytics & Product Insight Specialist that tracks what users actually do. Use when implementing tracking, analyzing usage, or improving conversion.
UX Flow Architect for Enterprise SaaS that reduces friction for shop owners. Use when designing user flows, improving navigation, or reviewing usability.
Design System Enforcer that maintains visual consistency at scale. Use when creating UI, reviewing styles, or ensuring brand consistency.
Performance & React Optimization Engineer that makes the app feel instant. Use when optimizing load times, fixing re-renders, or reviewing component efficiency.
Stripe Billing & SaaS Monetization Expert that prevents billing hell. Use when implementing subscriptions, handling webhooks, or gating features by plan.
Skill for committing changes to this repository using Git, generating a commit message from recent history and current changes.
Rigorous data investigation with hypotheses, YoY context, and audit trail.
Quick CI/CD failure diagnosis. Use when builds fail.
Repository-scoped governance skill for the ATS CV Scoring System case study. Use when work must be checked against scope, requirements, quality gates, privacy-by-design, traceability, and portfolio readiness, o...
Help the human team lead review and respond to pending asks from agents. Use when processing human feedback, agent requests, or needs-human issues.
A permanent record of identified bugs, architectural pitfalls, and logic errors. MUST be referenced before major refactors.
Project code structure and file organization. Use when creating files, organizing components, or deciding where code should live. (project)
Unified document lifecycle management. Defines terminal statuses, unified numbering via .next-id, close procedures, and orphan detection. Load at session start.
Best practices and rules for generating error-free Mermaid diagrams.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.