[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F37X2JZCB23EX34PQYPAWJ":3,"skill-same:01M7F37X2JZCB23EX34PQYPAWJ":47},{"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":46},"01M7F37X2JZCB23EX34PQYPAWJ","product-capability",null,"Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.","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-技能与代理开发\u002Fproduct-capability\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: product-capability\ndescription: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.\norigin: ECC\n---\n\n# Product Capability\n\nThis skill turns product intent into explicit engineering constraints.\n\nUse it when the gap is not \"what should we build?\" but \"what exactly must be true before implementation starts?\"\n\n## When to Use\n\n- A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit\n- A feature crosses multiple services, repos, or teams and needs a capability contract before coding\n- Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy\n- Senior engineers keep restating the same hidden assumptions during review\n- You need a reusable artifact that can survive across harnesses and sessions\n\n## Canonical Artifact\n\nIf the repo has a durable product-context file such as `PRODUCT.md`, `docs\u002Fproduct\u002F`, or a program-spec directory, update it there.\n\nIf no capability manifest exists yet, create one using the template at:\n\n- `docs\u002Fexamples\u002Fproduct-capability-template.md`\n\nThe goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable.\n\n## Non-Negotiable Rules\n\n- Do not invent product truth. Mark unresolved questions explicitly.\n- Separate user-visible promises from implementation details.\n- Call out what is fixed policy, what is architecture preference, and what is still open.\n- If the request conflicts with existing repo constraints, say so clearly instead of smoothing it over.\n- Prefer one reusable capability artifact over scattered ad hoc notes.\n\n## Inputs\n\nRead only what is needed:\n\n1. Product intent\n   - issue, discussion, PRD, roadmap note, founder message\n2. Current architecture\n   - relevant repo docs, contracts, schemas, routes, existing workflows\n3. Existing capability context\n   - `PRODUCT.md`, design docs, RFCs, migration notes, operating-model docs\n4. Delivery constraints\n   - auth, billing, compliance, rollout, backwards compatibility, performance, review policy\n\n## Core Workflow\n\n### 1. Restate the capability\n\nCompress the ask into one precise statement:\n\n- who the user or operator is\n- what new capability exists after this ships\n- what outcome changes because of it\n\nIf this statement is weak, the implementation will drift.\n\n### 2. Resolve capability constraints\n\nExtract the constraints that must hold before implementation:\n\n- business rules\n- scope boundaries\n- invariants\n- trust boundaries\n- data ownership\n- lifecycle transitions\n- rollout \u002F migration requirements\n- failure and recovery expectations\n\nThese are the things that often live only in senior-engineer memory.\n\n### 3. Define the implementation-facing contract\n\nProduce an SRS-style capability plan with:\n\n- capability summary\n- explicit non-goals\n- actors and surfaces\n- required states and transitions\n- interfaces \u002F inputs \u002F outputs\n- data model implications\n- security \u002F billing \u002F policy constraints\n- observability and operator requirements\n- open questions blocking implementation\n\n### 4. Translate into execution\n\nEnd with the exact handoff:\n\n- ready for direct implementation\n- needs architecture review first\n- needs product clarification first\n\nIf useful, point to the next ECC-native lane:\n\n- `project-flow-ops`\n- `workspace-surface-audit`\n- `api-connector-builder`\n- `dashboard-builder`\n- `tdd-workflow`\n- `verification-loop`\n\n## Output Format\n\nReturn the result in this order:\n\n```text\nCAPABILITY\n- one-paragraph restatement\n\nCONSTRAINTS\n- fixed rules, invariants, and boundaries\n\nIMPLEMENTATION CONTRACT\n- actors\n- surfaces\n- states and transitions\n- interface\u002Fdata implications\n\nNON-GOALS\n- what this lane explicitly does not own\n\nOPEN QUESTIONS\n- blockers or product decisions still required\n\nHANDOFF\n- what should happen next and which ECC lane should take it\n```\n\n## Good Outcomes\n\n- Product intent is now concrete enough to implement without rediscovering hidden constraints mid-PR.\n- Engineering review has a durable artifact instead of relying on memory or Slack context.\n- The resulting plan is reusable across Claude Code, Codex, Cursor, OpenCode, and ECC 2.0 planning surfaces.\n","# Product Capability\n\nThis skill turns product intent into explicit engineering constraints.\n\nUse it when the gap is not \"what should we build?\" but \"what exactly must be true before implementation starts?\"\n\n## When to Use\n\n- A PRD, roadmap item, discussion, or founder note exists, but the implementation constraints are still implicit\n- A feature crosses multiple services, repos, or teams and needs a capability contract before coding\n- Product intent is clear, but architecture, data, lifecycle, or policy implications are still fuzzy\n- Senior engineers keep restating the same hidden assumptions during review\n- You need a reusable artifact that can survive across harnesses and sessions\n\n## Canonical Artifact\n\nIf the repo has a durable product-context file such as `PRODUCT.md`, `docs\u002Fproduct\u002F`, or a program-spec directory, update it there.\n\nIf no capability manifest exists yet, create one using the template at:\n\n- `docs\u002Fexamples\u002Fproduct-capability-template.md`\n\nThe goal is not to create another planning stack. The goal is to make hidden capability constraints durable and reusable.\n\n## Non-Negotiable Rules\n\n- Do not invent product truth. Mark unresolved questions explicitly.\n- Separate user-visible promises from implementation details.\n- Call out what is fixed policy, what is architecture preference, and what is still open.\n- If the request conflicts with existing repo constraints, say so clearly instead of smoothing it over.\n- Prefer one reusable capability artifact over scattered ad hoc notes.\n\n## Inputs\n\nRead only what is needed:\n\n1. Product intent\n   - issue, discussion, PRD, roadmap note, founder message\n2. Current architecture\n   - relevant repo docs, contracts, schemas, routes, existing workflows\n3. Existing capability context\n   - `PRODUCT.md`, design docs, RFCs, migration notes, operating-model docs\n4. Delivery constraints\n   - auth, billing, compliance, rollout, backwards compatibility, performance, review policy\n\n## Core Workflow\n\n### 1. Restate the capability\n\nCompress the ask into one precise statement:\n\n- who the user or operator is\n- what new capability exists after this ships\n- what outcome changes because of it\n\nIf this statement is weak, the implementation will drift.\n\n### 2. Resolve capability constraints\n\nExtract the constraints that must hold before implementation:\n\n- business rules\n- scope boundaries\n- invariants\n- trust boundaries\n- data ownership\n- lifecycle transitions\n- rollout \u002F migration requirements\n- failure and recovery expectations\n\nThese are the things that often live only in senior-engineer memory.\n\n### 3. Define the implementation-facing contract\n\nProduce an SRS-style capability plan with:\n\n- capability summary\n- explicit non-goals\n- actors and surfaces\n- required states and transitions\n- interfaces \u002F inputs \u002F outputs\n- data model implications\n- security \u002F billing \u002F policy constraints\n- observability and operator requirements\n- open questions blocking implementation\n\n### 4. Translate into execution\n\nEnd with the exact handoff:\n\n- ready for direct implementation\n- needs architecture review first\n- needs product clarification first\n\nIf useful, point to the next ECC-native lane:\n\n- `project-flow-ops`\n- `workspace-surface-audit`\n- `api-connector-builder`\n- `dashboard-builder`\n- `tdd-workflow`\n- `verification-loop`\n\n## Output Format\n\nReturn the result in this order:\n\n```text\nCAPABILITY\n- one-paragraph restatement\n\nCONSTRAINTS\n- fixed rules, invariants, and boundaries\n\nIMPLEMENTATION CONTRACT\n- actors\n- surfaces\n- states and transitions\n- interface\u002Fdata implications\n\nNON-GOALS\n- what this lane explicitly does not own\n\nOPEN QUESTIONS\n- blockers or product decisions still required\n\nHANDOFF\n- what should happen next and which ECC lane should take it\n```\n\n## Good Outcomes\n\n- Product intent is now concrete enough to implement without rediscovering hidden constraints mid-PR.\n- Engineering review has a durable artifact instead of relying on memory or Slack context.\n- The resulting plan is reusable across Claude Code, Codex, Cursor, OpenCode, and ECC 2.0 planning surfaces.\n",{"name":5,"origin":24,"description":7},"ECC","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fproduct-capability",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":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill product-capability",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill product-capability",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill product-capability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fproduct-capability\u002FSKILL.md",true,[],[48,55,60,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":50,"nameZh":6,"description":51,"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},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]