[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F50M00SA00PFT9KTSG81VP":3,"skill-same:01M7F50M00SA00PFT9KTSG81VP":52},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7F50M00SA00PFT9KTSG81VP","skill-prd",null,"Write an AI-optimized PRD using multi-AI orchestration — use when scoping a new feature or product","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-prd\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: skill-prd\ndescription: \"Write an AI-optimized PRD using multi-AI orchestration — use when scoping a new feature or product\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# STOP - SKILL ALREADY LOADED\n\n**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**\n\n\n## PHASE 0: CLARIFICATION (MANDATORY)\n\nBefore writing ANY PRD content, you MUST ask the user these questions:\n\n```\nI need to understand your requirements before creating the PRD.\n\n1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)\n2. **Core Problem**: What specific pain point does this solve? Any metrics?\n3. **Success Criteria**: How will you measure if this succeeds?\n4. **Constraints**: Any technical, budget, or timeline constraints?\n5. **Existing Context**: Is this greenfield or integrating with existing systems?\n\nPlease answer these (even briefly) so I can create a more targeted PRD.\n```\n\n**WAIT for user response before proceeding to Phase 1.**\n\nIf user says \"skip\" or provides the feature description inline, extract what you can and note assumptions.\n\n\n## PHASE 1: QUICK RESEARCH (Max 2 searches)\n\nOnly search if topic is unfamiliar. Limit to 2 web searches max:\n- One for domain\u002Fmarket context\n- One for technical patterns (if needed)\n\nDo NOT over-research. 60 seconds max for this phase.\n\n\n## PHASE 2: WRITE PRD\n\nStructure:\n1. **Executive Summary** - Vision + key value prop\n2. **Problem Statement** - Quantified pain points by user segment\n3. **Goals & Metrics** - SMART goals, P0\u002FP1\u002FP2 priority, success metrics table\n4. **Non-Goals** - Explicit boundaries (what we WON'T do)\n5. **User Personas** - 2-3 specific personas with use cases\n6. **Functional Requirements** - FR-001 format with acceptance criteria\n7. **Implementation Phases** - Dependency-ordered, time-boxed\n8. **Risks & Mitigations** - Top 3-5 risks with mitigation strategies\n\n\n## PHASE 2.5: ADVERSARIAL PRD REVIEW (RECOMMENDED)\n\n**After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review.** A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.\n\nDispatch the PRD draft to a different provider (Codex, Antigravity, or Sonnet as fallback) with this prompt:\n\n> \"Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?\"\n\n**After receiving the challenge:**\n- Revise the PRD to address valid challenges\n- Note dismissed challenges in the Risks section if they have partial merit\n- Add to PRD footer: `Adversarial review: applied`\n\n**Skip with `--fast` or when user requests speed over thoroughness.** See `prd.md` command for full dispatch syntax.\n\n\n## PHASE 3: SELF-SCORE\n\nScore against 100-point framework:\n- AI-Specific Optimization: 25 pts (sequential phases, non-goals, structured format)\n- Traditional PRD Core: 25 pts (problem statement, goals, personas, specs)\n- Implementation Clarity: 30 pts (FRs with codes, NFRs, architecture, phases)\n- Completeness: 20 pts (risks, dependencies, examples, doc quality)\n\n\n## PHASE 4: SAVE\n\nWrite to user-specified filename or generate based on feature name.\n\n\n**START WITH PHASE 0 CLARIFICATION QUESTIONS NOW.**\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# STOP - SKILL ALREADY LOADED\n\n**DO NOT call Skill() again. DO NOT load any more skills. Execute directly.**\n\n\n## PHASE 0: CLARIFICATION (MANDATORY)\n\nBefore writing ANY PRD content, you MUST ask the user these questions:\n\n```\nI need to understand your requirements before creating the PRD.\n\n1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)\n2. **Core Problem**: What specific pain point does this solve? Any metrics?\n3. **Success Criteria**: How will you measure if this succeeds?\n4. **Constraints**: Any technical, budget, or timeline constraints?\n5. **Existing Context**: Is this greenfield or integrating with existing systems?\n\nPlease answer these (even briefly) so I can create a more targeted PRD.\n```\n\n**WAIT for user response before proceeding to Phase 1.**\n\nIf user says \"skip\" or provides the feature description inline, extract what you can and note assumptions.\n\n\n## PHASE 1: QUICK RESEARCH (Max 2 searches)\n\nOnly search if topic is unfamiliar. Limit to 2 web searches max:\n- One for domain\u002Fmarket context\n- One for technical patterns (if needed)\n\nDo NOT over-research. 60 seconds max for this phase.\n\n\n## PHASE 2: WRITE PRD\n\nStructure:\n1. **Executive Summary** - Vision + key value prop\n2. **Problem Statement** - Quantified pain points by user segment\n3. **Goals & Metrics** - SMART goals, P0\u002FP1\u002FP2 priority, success metrics table\n4. **Non-Goals** - Explicit boundaries (what we WON'T do)\n5. **User Personas** - 2-3 specific personas with use cases\n6. **Functional Requirements** - FR-001 format with acceptance criteria\n7. **Implementation Phases** - Dependency-ordered, time-boxed\n8. **Risks & Mitigations** - Top 3-5 risks with mitigation strategies\n\n\n## PHASE 2.5: ADVERSARIAL PRD REVIEW (RECOMMENDED)\n\n**After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review.** A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.\n\nDispatch the PRD draft to a different provider (Codex, Antigravity, or Sonnet as fallback) with this prompt:\n\n> \"Challenge this PRD. What assumptions are wrong? What user scenarios are missing? What requirements contradict each other? What will the first user complaint be? What risk does this PRD ignore?\"\n\n**After receiving the challenge:**\n- Revise the PRD to address valid challenges\n- Note dismissed challenges in the Risks section if they have partial merit\n- Add to PRD footer: `Adversarial review: applied`\n\n**Skip with `--fast` or when user requests speed over thoroughness.** See `prd.md` command for full dispatch syntax.\n\n\n## PHASE 3: SELF-SCORE\n\nScore against 100-point framework:\n- AI-Specific Optimization: 25 pts (sequential phases, non-goals, structured format)\n- Traditional PRD Core: 25 pts (problem statement, goals, personas, specs)\n- Implementation Clarity: 30 pts (FRs with codes, NFRs, architecture, phases)\n- Completeness: 20 pts (risks, dependencies, examples, doc quality)\n\n\n## PHASE 4: SAVE\n\nWrite to user-specified filename or generate based on feature name.\n\n\n**START WITH PHASE 0 CLARIFICATION QUESTIONS NOW.**\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fskill-prd",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-prd",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-prd",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-prd\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",161,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-prd\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]