[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAG877B4ESXDG2TA63352R":3,"skill-same:01M7AAG877B4ESXDG2TA63352R":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AAG877B4ESXDG2TA63352R","prd",null,"Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.","eyeriis\u002Fomarchy-config-backup","eyeriis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F228332809?v=4","01M7AAFPGTGFWJ7H9FE6MFHBTD","hassan mothanna assad","01M7AAFPHZ8S6NJ2E5Z25MEDNA",0,"MIT","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.agents\u002Fskills\u002Fprd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prd\ndescription: 'Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.'\nlicense: MIT\n---\n\n# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n","# Product Requirements Document (PRD)\n\n## Overview\n\nDesign comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.\n\n## When to Use\n\nUse this skill when:\n\n- Starting a new product or feature development cycle\n- Translating a vague idea into a concrete technical specification\n- Defining requirements for AI-powered features\n- Stakeholders need a unified \"source of truth\" for project scope\n- User asks to \"write a PRD\", \"document requirements\", or \"plan a feature\"\n\n---\n\n## Operational Workflow\n\n### Phase 1: Discovery (The Interview)\n\nBefore writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context.\n\n**Ask about:**\n\n- **The Core Problem**: Why are we building this now?\n- **Success Metrics**: How do we know it worked?\n- **Constraints**: Budget, tech stack, or deadline?\n\n### Phase 2: Analysis & Scoping\n\nSynthesize the user's input. Identify dependencies and hidden complexities.\n\n- Map out the **User Flow**.\n- Define **Non-Goals** to protect the timeline.\n\n### Phase 3: Technical Drafting\n\nGenerate the document using the **Strict PRD Schema** below.\n\n---\n\n## PRD Quality Standards\n\n### Requirements Quality\n\nUse concrete, measurable criteria. Avoid \"fast\", \"easy\", or \"intuitive\".\n\n```diff\n# Vague (BAD)\n- The search should be fast and return relevant results.\n- The UI must look modern and be easy to use.\n\n# Concrete (GOOD)\n+ The search must return results within 200ms for a 10k record dataset.\n+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.\n+ The UI must follow the 'Vercel\u002FNext.js' design system and achieve 100% Lighthouse Accessibility score.\n```\n\n---\n\n## Strict PRD Schema\n\nYou **MUST** follow this exact structure for the output:\n\n### 1. Executive Summary\n\n- **Problem Statement**: 1-2 sentences on the pain point.\n- **Proposed Solution**: 1-2 sentences on the fix.\n- **Success Criteria**: 3-5 measurable KPIs.\n\n### 2. User Experience & Functionality\n\n- **User Personas**: Who is this for?\n- **User Stories**: `As a [user], I want to [action] so that [benefit].`\n- **Acceptance Criteria**: Bulleted list of \"Done\" definitions for each story.\n- **Non-Goals**: What are we NOT building?\n\n### 3. AI System Requirements (If Applicable)\n\n- **Tool Requirements**: What tools and APIs are needed?\n- **Evaluation Strategy**: How to measure output quality and accuracy.\n\n### 4. Technical Specifications\n\n- **Architecture Overview**: Data flow and component interaction.\n- **Integration Points**: APIs, DBs, and Auth.\n- **Security & Privacy**: Data handling and compliance.\n\n### 5. Risks & Roadmap\n\n- **Phased Rollout**: MVP -> v1.1 -> v2.0.\n- **Technical Risks**: Latency, cost, or dependency failures.\n\n---\n\n## Implementation Guidelines\n\n### DO (Always)\n\n- **Define Testing**: For AI systems, specify how to test and validate output quality.\n- **Iterate**: Present a draft and ask for feedback on specific sections.\n\n### DON'T (Avoid)\n\n- **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first.\n- **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`.\n\n---\n\n## Example: Intelligent Search System\n\n### 1. Executive Summary\n\n**Problem**: Users struggle to find specific documentation snippets in massive repositories.\n**Solution**: An intelligent search system that provides direct answers with source citations.\n**Success**:\n\n- Reduce search time by 50%.\n- Citation accuracy >= 95%.\n\n### 2. User Stories\n\n- **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords.\n- **AC**:\n  - Supports multi-turn clarification.\n  - Returns code blocks with \"Copy\" button.\n\n### 3. AI System Architecture\n\n- **Tools Required**: `codesearch`, `grep`, `webfetch`.\n\n### 4. Evaluation\n\n- **Benchmark**: Test with 50 common developer questions.\n- **Pass Rate**: 90% must match expected citations.\n",{"name":5,"license":15,"description":7},"main","398ba43331c8281d35ba28b511b3ebb1ec00b10e","home\u002F.agents\u002Fskills\u002Fprd","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup","https:\u002F\u002Fgithub.com\u002Feyeriis","all repos are private atm.","2026-08-08 06:57:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add eyeriis\u002Fomarchy-config-backup --skill prd",{"tool":37,"command":38},"bunx","bunx skills add eyeriis\u002Fomarchy-config-backup --skill prd",{"tool":40,"command":41},"pnpm","pnpm dlx skills add eyeriis\u002Fomarchy-config-backup --skill prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.agents\u002Fskills\u002Fprd\u002FSKILL.md",true,[],[46,55,62],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":51,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7AAGW7GNX6DCNDS68BQZFY0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.codex\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.codex\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AAGC0CYJ1851AD7EYHV98P","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.agents\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":50,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AAG17CS0MGE5WF9SX08WVV","frontend-design","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.agents\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feyeriis\u002Fomarchy-config-backup\u002Fblob\u002Fmain\u002Fhome\u002F.agents\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[]]