[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QMK08RV5A49R7J8V0HMVHT":3,"skill-same:01M6QMK08RV5A49R7J8V0HMVHT":102},{"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":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":79,"commitSha":80,"skillDirectory":81,"forksCount":14,"repositoryHtmlUrl":82,"repositoryHomepageUrl":83,"ownerHtmlUrl":84,"ownerBlogUrl":85,"ownerDescription":86,"updatedAt":87,"install":88,"resources":101},"01M6QMK08RV5A49R7J8V0HMVHT","product-skills",null,"Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing\u002Flanding (from-scratch pages), and engineering\u002Fagent-harness (the generic loop engine this orchestrator plugs into).","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproduct-skills\u002FSKILL.md",[18,23,26,31,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":35,"categoryName":36,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"product","product skills","project-management","cadence","close","summarizer","teardown","project","digest","tracker","router","design","prioritize","plan","loop","how","team","run","analytics","experiments","2026-11-10 10:12:30",false,"---\nname: \"product-skills\"\ndescription: \"Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing\u002Flanding (from-scratch pages), and engineering\u002Fagent-harness (the generic loop engine this orchestrator plugs into).\"\ncontext: fork\nversion: 2.11.1\nauthor: Alireza Rezvani\nlicense: MIT\ntags: [product, product-management, orchestrator, discovery, ux, analytics, agent-harness]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# Product Team — Domain Orchestrator & Discovery Loop\n\nThis orchestrator does two jobs. **Routing:** fork context, classify a product inquiry\nwith `scripts\u002Fproduct_goal_router.py` across all 16 product-team lanes (12 bundled + 4\nstandalone plugins), run exactly one, return a digest. **Looping:** run product work as\nbounded agentic loops with machine-checkable gates — the continuous-discovery loop\n(weekly cadence scored by `discovery_cadence_tracker.py`, tree structure enforced by\n`ost_linter.py`) and goal-scale runs through the repo-wide agent-harness.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"Prioritize features \u002F RICE \u002F PRD\" | `product-manager-toolkit` |\n| \"OKRs, strategy cascade\" | `product-strategist` |\n| \"Personas, usability, research synthesis\" | `ux-researcher-designer` |\n| \"Design tokens, WCAG contrast\" | `ui-design-system` |\n| \"Competitor matrix, teardown\" | `competitive-teardown` |\n| \"Retention, cohorts, funnels, KPIs\" | `product-analytics` |\n| \"A\u002FB test, sample size, hypothesis\" | `experiment-designer` |\n| \"Discovery, assumptions, opportunity trees\" | `product-discovery` |\n| \"Roadmap comms, release notes, changelog\" | `roadmap-communicator` |\n| \"Spec → runnable repo\" | `spec-to-repo` |\n| \"Landing page (Next.js\u002FTailwind)\" | `landing-page-generator` |\n| \"SaaS boilerplate\" | `saas-scaffolder` |\n| \"User stories, sprint capacity\" | `agile-product-owner` (standalone) |\n| \"Apple HIG audit\" | `apple-hig-expert` (standalone) |\n| \"PRD from an existing codebase\" | `code-to-prd` (standalone) |\n| \"Summarize papers\u002Farticles\" | `research-summarizer` (standalone) |\n\n## Routing logic (deterministic)\n\n```bash\npython3 scripts\u002Fproduct_goal_router.py --text \"\u003Cthe goal>\" --output json\n```\n\nExit 0 → `route_to` names the skill (with `skill_path`, including the standalone\nplugins): load its SKILL.md and follow its workflow. Exit 2 → ask ONE clarifying question\nnaming the listed candidates, with a recommended answer. Exit 3 → no signal: ask the user\nto restate the goal with the deliverable named. Never guess silently; never silently\nchain — digest first, confirm, then chain.\n\n## The discovery loop (the domain's recurring agentic loop)\n\nModern discovery is a weekly habit, not a project phase (Torres). Run it as a bounded\nloop with two machine gates:\n\n1. **Observe** — maintain `discovery_log.json` (interviews, assumption tests; shape in\n   `assets\u002Fsample_discovery_log.json`) and score the cadence:\n   ```bash\n   python3 scripts\u002Fdiscovery_cadence_tracker.py --input discovery_log.json\n   ```\n   Refuses on \u003C 2 interviews (exit 5) — there is no cadence to measure yet. Output:\n   health 0–100, verdict HEALTHY\u002FAT-RISK\u002FDORMANT, named gaps, and `next_loop_action`.\n2. **Choose** — the tracker's `next_loop_action` IS the choice: book the touchpoint,\n   re-anchor the guide on the outcome, or test the top untested assumption (route to\n   `product-discovery`'s assumption_mapper for prioritization).\n3. **Act** — run the interview \u002F assumption test with the routed sub-skill's tools.\n4. **Verify** — keep the tree structurally sound before it may drive a roadmap:\n   ```bash\n   python3 scripts\u002Fost_linter.py --input ost.json    # exit 2 = NEEDS-REWORK, fix before citing the tree\n   ```\n   Rules: one measurable outcome root (O1), opportunities are needs not features (O2),\n   targeted opportunities compare ≥ 2 solutions (O3), every solution has an assumption\n   test (O4), no orphan solutions (O5 — the feature-factory tell).\n5. **Record \u002F Repeat-or-stop** — update the log, keep the weekly streak alive. Stop\n   states: HEALTHY + validated assumption → graduate to `experiment-designer` (build the\n   A\u002FB gate) or `product-manager-toolkit` (PRD); DORMANT for 4+ weeks → escalate to the\n   product lead by name — do not quietly let discovery die.\n\nFor build-scale goals (\"turn this validated spec into a repo and verify it\"), compile\nthrough the repo-wide harness instead:\n\n```bash\npython3 engineering\u002Fagent-harness\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fgoal_compiler.py \\\n  --goal \"\u003Cgoal>\" --manifest engineering\u002Fagent-harness\u002Fskills\u002Fagent-harness\u002Fassets\u002Fharnesses\u002Fproduct-team.json \\\n  --out .agent-harness\u002Fplan.json\n```\n\nThe domain's three strongest close-out gates plug in as task verifications:\n`..\u002Fspec-to-repo\u002Fscripts\u002Fvalidate_project.py` (exit 0), `code-to-prd`'s golden\n`expected_outputs\u002F`, and `research-summarizer`'s citation-count check.\n\n## Hard rules\n\n1. **Evidence before conviction**: no roadmap item cites the OST unless `ost_linter.py`\n   exits 0; no insight is asserted from a single participant (anecdote, not insight).\n2. **Outcome-first**: every loop hangs from one measurable outcome — the linter's O1 rule\n   is the intake gate.\n3. **Experiments are gated by math**: sample size from\n   `..\u002Fexperiment-designer\u002Fscripts\u002Fsample_size_calculator.py`, never gut feel; report the\n   MDE with the verdict.\n4. **Prioritization shows its framework**: RICE for steady-state, WSJF\u002Fcost-of-delay when\n   time sensitivity dominates, opportunity scoring for underserved needs — name which and\n   why (see [references\u002Fproduct_operating_model.md](references\u002Fproduct_operating_model.md)).\n5. **AI features ship with evals**: a golden set + rubric is the PRD's quality contract\n   for probabilistic features\n   ([references\u002Fai_product_evals.md](references\u002Fai_product_evals.md)).\n6. **Never modify a gate you are judged by**; exhausted budgets escalate to a named human,\n   never report as success.\n\n## Forcing-question library (grill-with-docs pattern)\n\nOne per turn, recommended answer, canon citation. Never run a sub-skill or start a loop\nuntil the lane-defining decision is locked:\n\n- **DISCOVERY lane**: \"What is the single outcome this discovery serves, stated with a\n  number? Recommended: write it as the OST root first — opportunities without an outcome\n  are a feature factory. Canon: Torres, *Continuous Discovery Habits*; opportunity\n  solution trees (producttalk.org).\"\n- **PRIORITIZE lane**: \"Does time sensitivity change this ranking — would delaying any\n  item a quarter erode its value? Recommended: if yes, run WSJF\u002Fcost-of-delay alongside\n  RICE and compare ranks; flag items whose rank flips on a one-step estimate change.\n  Canon: Reinertsen, *Principles of Product Development Flow*; SAFe WSJF false-precision\n  critique.\"\n- **EXPERIMENT lane**: \"What baseline rate and MDE justify this test's runtime?\n  Recommended: compute n first; if you can't reach it in 4 weeks, test a bigger lever.\n  Canon: statistical power analysis (experiment-designer).\"\n- **ANALYTICS lane**: \"Is your North Star a leading indicator of value exchange, or\n  revenue\u002Fvanity? Recommended: leading value metric with an input tree. Canon: Amplitude,\n  *The North Star Playbook*.\"\n- **STRATEGY lane**: \"Are these OKRs outcomes or shipping lists? Recommended: outcomes —\n  output OKRs are the #1 operating-model failure. Canon: Cagan, *Transformed* (SVPG,\n  2024).\"\n- **BUILD lanes (spec-to-repo \u002F saas-scaffolder)**: \"Which validated assumption says this\n  should be built at all? Recommended: link the OST test that survived; building is the\n  most expensive way to test an idea. Canon: Torres; Bland, *Testing Business Ideas*.\"\n\n## Assumptions\n\n1. The user owns (or advises the owner of) the product decision.\n2. Discovery data lives in the workspace as JSON logs — the loop is file-backed and\n   resumable; every tool ships `--sample` so the shape is visible first.\n3. The four standalone plugins are installed alongside the bundle (the router still\n   routes to them by path if not).\n\n## Non-goals\n\n- Not the delivery loop — sprint\u002Fflow\u002FJira work routes to `project-management`.\n- Not the generic loop engine — that is `engineering\u002Fagent-harness`; this orchestrator is\n  the product-domain adapter (router + discovery gates).\n- Not campaign marketing — `marketing\u002Flanding` builds from-scratch marketing pages;\n  `landing-page-generator` here scaffolds product Next.js\u002FTSX pages.\n\n## Output artifacts\n\n| Mode | Artifact |\n|---|---|\n| Route | Sub-skill's own artifact + ≤ 200-word digest with one canon-cited challenge |\n| Discovery loop | `discovery_log.json` + cadence report + linted `ost.json` |\n| Harness run | `.agent-harness\u002Fplan.json` + `state.json` + close handoff |\n\n## Anti-patterns (do not)\n\n- ❌ Run all 16 lanes \"to be thorough\" — route to one, digest, chain on confirmation\n- ❌ Cite an OST that fails the linter, or promote a single-participant anecdote to insight\n- ❌ Ship an AI feature whose PRD has no eval (golden set + rubric)\n- ❌ Let the discovery streak die silently — DORMANT escalates by name\n- ❌ Treat RICE as the only prioritization lens when deadlines dominate\n\n## References\n\n- [references\u002Fcontinuous_discovery_canon.md](references\u002Fcontinuous_discovery_canon.md) —\n  Torres, OST, assumption testing, JTBD switch interviews, story mapping\n- [references\u002Fproduct_operating_model.md](references\u002Fproduct_operating_model.md) — Cagan\n  *Transformed*, North Star framework, PLG benchmarks, WSJF\u002FODI vs RICE\n- [references\u002Fai_product_evals.md](references\u002Fai_product_evals.md) — evals-as-PRD, model\n  cards, evaluator-optimizer loops\n- Loop engine: `engineering\u002Fagent-harness` · Loop vocabulary: `loop-library`\n","# Product Team — Domain Orchestrator & Discovery Loop\n\nThis orchestrator does two jobs. **Routing:** fork context, classify a product inquiry\nwith `scripts\u002Fproduct_goal_router.py` across all 16 product-team lanes (12 bundled + 4\nstandalone plugins), run exactly one, return a digest. **Looping:** run product work as\nbounded agentic loops with machine-checkable gates — the continuous-discovery loop\n(weekly cadence scored by `discovery_cadence_tracker.py`, tree structure enforced by\n`ost_linter.py`) and goal-scale runs through the repo-wide agent-harness.\n\n## When to invoke\n\n| Symptom | Sub-skill |\n|---|---|\n| \"Prioritize features \u002F RICE \u002F PRD\" | `product-manager-toolkit` |\n| \"OKRs, strategy cascade\" | `product-strategist` |\n| \"Personas, usability, research synthesis\" | `ux-researcher-designer` |\n| \"Design tokens, WCAG contrast\" | `ui-design-system` |\n| \"Competitor matrix, teardown\" | `competitive-teardown` |\n| \"Retention, cohorts, funnels, KPIs\" | `product-analytics` |\n| \"A\u002FB test, sample size, hypothesis\" | `experiment-designer` |\n| \"Discovery, assumptions, opportunity trees\" | `product-discovery` |\n| \"Roadmap comms, release notes, changelog\" | `roadmap-communicator` |\n| \"Spec → runnable repo\" | `spec-to-repo` |\n| \"Landing page (Next.js\u002FTailwind)\" | `landing-page-generator` |\n| \"SaaS boilerplate\" | `saas-scaffolder` |\n| \"User stories, sprint capacity\" | `agile-product-owner` (standalone) |\n| \"Apple HIG audit\" | `apple-hig-expert` (standalone) |\n| \"PRD from an existing codebase\" | `code-to-prd` (standalone) |\n| \"Summarize papers\u002Farticles\" | `research-summarizer` (standalone) |\n\n## Routing logic (deterministic)\n\n```bash\npython3 scripts\u002Fproduct_goal_router.py --text \"\u003Cthe goal>\" --output json\n```\n\nExit 0 → `route_to` names the skill (with `skill_path`, including the standalone\nplugins): load its SKILL.md and follow its workflow. Exit 2 → ask ONE clarifying question\nnaming the listed candidates, with a recommended answer. Exit 3 → no signal: ask the user\nto restate the goal with the deliverable named. Never guess silently; never silently\nchain — digest first, confirm, then chain.\n\n## The discovery loop (the domain's recurring agentic loop)\n\nModern discovery is a weekly habit, not a project phase (Torres). Run it as a bounded\nloop with two machine gates:\n\n1. **Observe** — maintain `discovery_log.json` (interviews, assumption tests; shape in\n   `assets\u002Fsample_discovery_log.json`) and score the cadence:\n   ```bash\n   python3 scripts\u002Fdiscovery_cadence_tracker.py --input discovery_log.json\n   ```\n   Refuses on \u003C 2 interviews (exit 5) — there is no cadence to measure yet. Output:\n   health 0–100, verdict HEALTHY\u002FAT-RISK\u002FDORMANT, named gaps, and `next_loop_action`.\n2. **Choose** — the tracker's `next_loop_action` IS the choice: book the touchpoint,\n   re-anchor the guide on the outcome, or test the top untested assumption (route to\n   `product-discovery`'s assumption_mapper for prioritization).\n3. **Act** — run the interview \u002F assumption test with the routed sub-skill's tools.\n4. **Verify** — keep the tree structurally sound before it may drive a roadmap:\n   ```bash\n   python3 scripts\u002Fost_linter.py --input ost.json    # exit 2 = NEEDS-REWORK, fix before citing the tree\n   ```\n   Rules: one measurable outcome root (O1), opportunities are needs not features (O2),\n   targeted opportunities compare ≥ 2 solutions (O3), every solution has an assumption\n   test (O4), no orphan solutions (O5 — the feature-factory tell).\n5. **Record \u002F Repeat-or-stop** — update the log, keep the weekly streak alive. Stop\n   states: HEALTHY + validated assumption → graduate to `experiment-designer` (build the\n   A\u002FB gate) or `product-manager-toolkit` (PRD); DORMANT for 4+ weeks → escalate to the\n   product lead by name — do not quietly let discovery die.\n\nFor build-scale goals (\"turn this validated spec into a repo and verify it\"), compile\nthrough the repo-wide harness instead:\n\n```bash\npython3 engineering\u002Fagent-harness\u002Fskills\u002Fagent-harness\u002Fscripts\u002Fgoal_compiler.py \\\n  --goal \"\u003Cgoal>\" --manifest engineering\u002Fagent-harness\u002Fskills\u002Fagent-harness\u002Fassets\u002Fharnesses\u002Fproduct-team.json \\\n  --out .agent-harness\u002Fplan.json\n```\n\nThe domain's three strongest close-out gates plug in as task verifications:\n`..\u002Fspec-to-repo\u002Fscripts\u002Fvalidate_project.py` (exit 0), `code-to-prd`'s golden\n`expected_outputs\u002F`, and `research-summarizer`'s citation-count check.\n\n## Hard rules\n\n1. **Evidence before conviction**: no roadmap item cites the OST unless `ost_linter.py`\n   exits 0; no insight is asserted from a single participant (anecdote, not insight).\n2. **Outcome-first**: every loop hangs from one measurable outcome — the linter's O1 rule\n   is the intake gate.\n3. **Experiments are gated by math**: sample size from\n   `..\u002Fexperiment-designer\u002Fscripts\u002Fsample_size_calculator.py`, never gut feel; report the\n   MDE with the verdict.\n4. **Prioritization shows its framework**: RICE for steady-state, WSJF\u002Fcost-of-delay when\n   time sensitivity dominates, opportunity scoring for underserved needs — name which and\n   why (see [references\u002Fproduct_operating_model.md](references\u002Fproduct_operating_model.md)).\n5. **AI features ship with evals**: a golden set + rubric is the PRD's quality contract\n   for probabilistic features\n   ([references\u002Fai_product_evals.md](references\u002Fai_product_evals.md)).\n6. **Never modify a gate you are judged by**; exhausted budgets escalate to a named human,\n   never report as success.\n\n## Forcing-question library (grill-with-docs pattern)\n\nOne per turn, recommended answer, canon citation. Never run a sub-skill or start a loop\nuntil the lane-defining decision is locked:\n\n- **DISCOVERY lane**: \"What is the single outcome this discovery serves, stated with a\n  number? Recommended: write it as the OST root first — opportunities without an outcome\n  are a feature factory. Canon: Torres, *Continuous Discovery Habits*; opportunity\n  solution trees (producttalk.org).\"\n- **PRIORITIZE lane**: \"Does time sensitivity change this ranking — would delaying any\n  item a quarter erode its value? Recommended: if yes, run WSJF\u002Fcost-of-delay alongside\n  RICE and compare ranks; flag items whose rank flips on a one-step estimate change.\n  Canon: Reinertsen, *Principles of Product Development Flow*; SAFe WSJF false-precision\n  critique.\"\n- **EXPERIMENT lane**: \"What baseline rate and MDE justify this test's runtime?\n  Recommended: compute n first; if you can't reach it in 4 weeks, test a bigger lever.\n  Canon: statistical power analysis (experiment-designer).\"\n- **ANALYTICS lane**: \"Is your North Star a leading indicator of value exchange, or\n  revenue\u002Fvanity? Recommended: leading value metric with an input tree. Canon: Amplitude,\n  *The North Star Playbook*.\"\n- **STRATEGY lane**: \"Are these OKRs outcomes or shipping lists? Recommended: outcomes —\n  output OKRs are the #1 operating-model failure. Canon: Cagan, *Transformed* (SVPG,\n  2024).\"\n- **BUILD lanes (spec-to-repo \u002F saas-scaffolder)**: \"Which validated assumption says this\n  should be built at all? Recommended: link the OST test that survived; building is the\n  most expensive way to test an idea. Canon: Torres; Bland, *Testing Business Ideas*.\"\n\n## Assumptions\n\n1. The user owns (or advises the owner of) the product decision.\n2. Discovery data lives in the workspace as JSON logs — the loop is file-backed and\n   resumable; every tool ships `--sample` so the shape is visible first.\n3. The four standalone plugins are installed alongside the bundle (the router still\n   routes to them by path if not).\n\n## Non-goals\n\n- Not the delivery loop — sprint\u002Fflow\u002FJira work routes to `project-management`.\n- Not the generic loop engine — that is `engineering\u002Fagent-harness`; this orchestrator is\n  the product-domain adapter (router + discovery gates).\n- Not campaign marketing — `marketing\u002Flanding` builds from-scratch marketing pages;\n  `landing-page-generator` here scaffolds product Next.js\u002FTSX pages.\n\n## Output artifacts\n\n| Mode | Artifact |\n|---|---|\n| Route | Sub-skill's own artifact + ≤ 200-word digest with one canon-cited challenge |\n| Discovery loop | `discovery_log.json` + cadence report + linted `ost.json` |\n| Harness run | `.agent-harness\u002Fplan.json` + `state.json` + close handoff |\n\n## Anti-patterns (do not)\n\n- ❌ Run all 16 lanes \"to be thorough\" — route to one, digest, chain on confirmation\n- ❌ Cite an OST that fails the linter, or promote a single-participant anecdote to insight\n- ❌ Ship an AI feature whose PRD has no eval (golden set + rubric)\n- ❌ Let the discovery streak die silently — DORMANT escalates by name\n- ❌ Treat RICE as the only prioritization lens when deadlines dominate\n\n## References\n\n- [references\u002Fcontinuous_discovery_canon.md](references\u002Fcontinuous_discovery_canon.md) —\n  Torres, OST, assumption testing, JTBD switch interviews, story mapping\n- [references\u002Fproduct_operating_model.md](references\u002Fproduct_operating_model.md) — Cagan\n  *Transformed*, North Star framework, PLG benchmarks, WSJF\u002FODI vs RICE\n- [references\u002Fai_product_evals.md](references\u002Fai_product_evals.md) — evals-as-PRD, model\n  cards, evaluator-optimizer loops\n- Loop engine: `engineering\u002Fagent-harness` · Loop vocabulary: `loop-library`\n",{"name":5,"tags":63,"author":69,"context":70,"license":15,"version":71,"description":7,"compatible_tools":72},[38,64,65,66,67,56,68],"product-management","orchestrator","discovery","ux","agent-harness","Alireza Rezvani","fork","2.11.1",[73,74,75,76,77,78],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fproduct-skills","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":89,"prompt":99,"zipAvailable":100},[90,93,96],{"tool":91,"command":92},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill product-skills",{"tool":94,"command":95},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill product-skills",{"tool":97,"command":98},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill product-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproduct-skills\u002FSKILL.md",true,[],[103,133,157,182,205,227],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":112,"publishedAt":58},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[109],{"categoryNo":110,"categoryName":111,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":58},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[140,141,142,143,117,144,145,51,146,147,148,149,150,151,152,153,154,155,156,129],"twitter","x twitter growth","growth","research","content","engineering","web search","competitors","analyze","engine","write","strategy","use","platform","grow","posting","competitive",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":58},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[163],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[165,150,166,167,168,169,170,171,152,172,173,79,174,175,176,177,178,179,180,181],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":58},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[189,190,191,192,193,55,194,195,196,152,197,124,198,199,42,200,201,202,203,204],"wrap up","up","wrap","gemini","deployment","file","hardening","closeout","stop","upgrade","founder","companion","you","tables","directions","phase",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":58},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[211],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[213,214,215,49,216,167,55,217,218,219,52,220,150,221,123,222,223,224,225,226],"workflow","workflow builder","builder","workflows","code","orchestrate","pipeline","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":233,"publishedAt":58},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[234,235,236,237,238,239,240,241,54,52,242,40,243,244,245,45,125,246,41,204],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","projects","scanner","conversation","back","sprint"]