[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7868EPFSXM8EPVFNQEYJ2XM":3,"skill-same:01M7868EPFSXM8EPVFNQEYJ2XM":48},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7868EPFSXM8EPVFNQEYJ2XM","project-to-prd",null,"Use when an existing repository needs current-state product documentation reverse-extracted into a PRD suite from repository evidence.","chenziyang110\u002Flaunchdeck","chenziyang110","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43693913?v=4","01M7863EBWK1D0P6A29YGEMAS4","Robin11","01M7863ECM1VB6RXDMHTW90D2T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-to-prd\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"project-to-prd\"\ndescription: \"Use when an existing repository needs current-state product documentation reverse-extracted into a PRD suite from repository evidence.\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fpassive-skills\u002Fproject-to-prd\u002FSKILL.md\"\n---\n\n\n# Project To PRD\n\nUse this passive skill to recognize existing-project PRD extraction work and\nroute it to `sp-prd-scan`, then `sp-prd-build`.\n\nUse `sp-specify` when the user wants to align a new or changed feature intent\nbefore planning. Use `sp-prd-scan -> sp-prd-build` when the user wants a\nprofessional current-state PRD suite reconstructed from the repository that\nalready exists. `sp-prd` is deprecated and remains compatibility-only for older\nsurfaces that have not been updated yet.\n\nThe canonical PRD lane is a heavy reconstruction workflow:\n`sp-prd-scan` runs with `execution_model: subagent-mandatory`, critical claims\nmust reach `L4 Reconstruction-Ready`, and the scan package includes contract\nartifacts such as `config-contracts.json` before `sp-prd-build` compiles exports.\n`sp-prd-build` is build-only: it must compile from the scan package instead of\nstarting a second repository scan, and it must block completion when critical\nevidence is still missing.\n\n## Required Behavior\n\n- Route existing-project reverse PRD requests to `sp-prd-scan`, then\n  `sp-prd-build`, before repository inspection.\n- Treat `sp-prd-scan -> sp-prd-build` as the depth-aware current-state\n  extraction workflow, not a flat repo summary pass.\n- Treat the canonical lane as heavy reconstruction work with\n  `subagent-mandatory` scan execution, not leader-only summarization.\n- Treat `sp-prd-build` as a build-only compilation step. It must not reread the\n  repository, and it must refuse completion when critical evidence gaps remain.\n- Treat `sp-prd` as a deprecated compatibility-only entrypoint that must route\n  into the canonical `sp-prd-scan -> sp-prd-build` flow.\n- Ground the PRD in current implementation reality: code, docs, tests, routes,\n  UI surfaces, service\u002FAPI surfaces, configuration, data models, domain terms,\n  `PROJECT-HANDBOOK.md`, and project cognition evidence when present.\n- Require capability triage before claiming the PRD suite is complete.\n- Use targeted evidence harvest for `critical` and `high` capabilities.\n- Keep `critical capabilities` visible until they are depth-aware and\n  `L4 Reconstruction-Ready` rather than merely surface-covered.\n- Preserve the distinction between Evidence, Inference, and Unknown.\n- Treat `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md` as the resumable state\n  source for the PRD run.\n- Keep the default terminal state as completed PRD exports under\n  `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n- Do not automatically hand off to `sp-plan`, `sp-tasks`, or implementation\n  planning.\n\n## Routing Signals\n\nUse `sp-prd-scan`, then `sp-prd-build` for requests like:\n\n- \"write a PRD for this existing app\"\n- \"extract product requirements from this repo\"\n- \"document what this product currently does\"\n- \"turn the current implementation into a product requirements document\"\n- \"generate UI\u002Fservice PRD docs from the codebase\"\n\nRoute to `sp-specify` instead when the user is describing a new product idea or\nfuture change that is not grounded in an existing repository surface.\n\n## Output Expectations\n\nThe active workflow should produce a current-state PRD suite, typically:\n\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprd-scan.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcapability-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fconfig-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fevidence\u002F`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fmaster\u002Fmaster-pack.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fexports\u002Fprd.md`\n\nMode-specific exports may include UI, service, flow, data, rule, or internal\nbrief views when the repository evidence supports them. Completion requires\ncapability triage, targeted evidence harvest, and depth-aware handling for\nproduct-defining capabilities.\n","# Project To PRD\n\nUse this passive skill to recognize existing-project PRD extraction work and\nroute it to `sp-prd-scan`, then `sp-prd-build`.\n\nUse `sp-specify` when the user wants to align a new or changed feature intent\nbefore planning. Use `sp-prd-scan -> sp-prd-build` when the user wants a\nprofessional current-state PRD suite reconstructed from the repository that\nalready exists. `sp-prd` is deprecated and remains compatibility-only for older\nsurfaces that have not been updated yet.\n\nThe canonical PRD lane is a heavy reconstruction workflow:\n`sp-prd-scan` runs with `execution_model: subagent-mandatory`, critical claims\nmust reach `L4 Reconstruction-Ready`, and the scan package includes contract\nartifacts such as `config-contracts.json` before `sp-prd-build` compiles exports.\n`sp-prd-build` is build-only: it must compile from the scan package instead of\nstarting a second repository scan, and it must block completion when critical\nevidence is still missing.\n\n## Required Behavior\n\n- Route existing-project reverse PRD requests to `sp-prd-scan`, then\n  `sp-prd-build`, before repository inspection.\n- Treat `sp-prd-scan -> sp-prd-build` as the depth-aware current-state\n  extraction workflow, not a flat repo summary pass.\n- Treat the canonical lane as heavy reconstruction work with\n  `subagent-mandatory` scan execution, not leader-only summarization.\n- Treat `sp-prd-build` as a build-only compilation step. It must not reread the\n  repository, and it must refuse completion when critical evidence gaps remain.\n- Treat `sp-prd` as a deprecated compatibility-only entrypoint that must route\n  into the canonical `sp-prd-scan -> sp-prd-build` flow.\n- Ground the PRD in current implementation reality: code, docs, tests, routes,\n  UI surfaces, service\u002FAPI surfaces, configuration, data models, domain terms,\n  `PROJECT-HANDBOOK.md`, and project cognition evidence when present.\n- Require capability triage before claiming the PRD suite is complete.\n- Use targeted evidence harvest for `critical` and `high` capabilities.\n- Keep `critical capabilities` visible until they are depth-aware and\n  `L4 Reconstruction-Ready` rather than merely surface-covered.\n- Preserve the distinction between Evidence, Inference, and Unknown.\n- Treat `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md` as the resumable state\n  source for the PRD run.\n- Keep the default terminal state as completed PRD exports under\n  `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002F`.\n- Do not automatically hand off to `sp-plan`, `sp-tasks`, or implementation\n  planning.\n\n## Routing Signals\n\nUse `sp-prd-scan`, then `sp-prd-build` for requests like:\n\n- \"write a PRD for this existing app\"\n- \"extract product requirements from this repo\"\n- \"document what this product currently does\"\n- \"turn the current implementation into a product requirements document\"\n- \"generate UI\u002Fservice PRD docs from the codebase\"\n\nRoute to `sp-specify` instead when the user is describing a new product idea or\nfuture change that is not grounded in an existing repository surface.\n\n## Output Expectations\n\nThe active workflow should produce a current-state PRD suite, typically:\n\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fworkflow-state.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fprd-scan.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcoverage-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fcapability-ledger.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fartifact-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fconfig-contracts.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Freconstruction-checklist.json`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fevidence\u002F`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fmaster\u002Fmaster-pack.md`\n- `.specify\u002Fprd-runs\u002F\u003Crun-id>\u002Fexports\u002Fprd.md`\n\nMode-specific exports may include UI, service, flow, data, rule, or internal\nbrief views when the repository evidence supports them. Completion requires\ncapability triage, targeted evidence harvest, and depth-aware handling for\nproduct-defining capabilities.\n",{"name":5,"metadata":24,"description":7,"compatibility":27},{"author":25,"source":26},"github-spec-kit","templates\u002Fpassive-skills\u002Fproject-to-prd\u002FSKILL.md","Requires spec-kit project structure with .specify\u002F directory","main","021f5cbe02157229460a577e9a585f2da6d78cb0",".claude\u002Fskills\u002Fproject-to-prd","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck","https:\u002F\u002Fgithub.com\u002Fchenziyang110","2026-08-07 18:10:54",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add chenziyang110\u002Flaunchdeck --skill project-to-prd",{"tool":40,"command":41},"bunx","bunx skills add chenziyang110\u002Flaunchdeck --skill project-to-prd",{"tool":43,"command":44},"pnpm","pnpm dlx skills add chenziyang110\u002Flaunchdeck --skill project-to-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fproject-to-prd\u002FSKILL.md",true,[],[49,56,62,68,75,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7875F3HQ1GF5F6BR36KY3JE","launchdeck-agent","Codex host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fcodex\u002Fskill\u002FSKILL.md",[],[],{"skillNo":57,"name":51,"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},"01M7875DV2DQR33K1NFJHKAMZP","Claude host adapter contract fixture for Launchdeck.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fagent-hosts\u002Fclaude\u002Fskill\u002FSKILL.md",[],[],{"skillNo":63,"name":51,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78759JQ7A6FQ8KDQTNYS3X9","Use this skill aggressively for local project lifecycle operations even when the user does not mention Launchdeck: start this project, run the dev server, dev, build, test, restart service, stop service, show logs, inspect ports, port is occupied, clean cache; and when the user explicitly asks to configure this local project for Launchdeck or create or generate a project-adapted `.launchdeck.yml`, including 为这个项目生成 Launchdeck 配置. Do not use for ordinary code edits, docs-only work, general explanations, API design discussion, or production deployment unless the user also asks to operate or configure a local project or service.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002Fagent\u002Finstaller-payload\u002Fskill\u002Flaunchdeck-agent\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78753ZJQ7G2CZT1W1G8WRJV","zig-testing","Use ONLY when user explicitly requests Zig test code, built-in test runner configuration,\ntest failure diagnosis, or coverage for Zig projects.\n\nTriggers: \"write test zig\", \"zig test\", \"testing.allocator\", \"zig coverage\",\n\"comptime test\", \"zig expectError\", \"zig snapshot test\", \"zig fuzz\".\n\nDo NOT activate for: general Zig coding without test context, build.zig configuration\nfor non-test targets, Zig compiler errors, or Zig build system setup.","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fzig-testing\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78750JXY4Z5D5W1EX3PQ31Z","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7874X2T83EQQFRCEY5SJJVC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fchenziyang110\u002Flaunchdeck\u002Fblob\u002Fmain\u002F.specify\u002Ftemplates\u002Fpassive-skills\u002Fverification-before-completion\u002FSKILL.md",[],[]]