[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71RF1V3H8N219AMSBDD19VV":3,"skill-same:01M71RF1V3H8N219AMSBDD19VV":90},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71RF1V3H8N219AMSBDD19VV","autospec-grow-define",null,"Use when the user wants \u002Fautospec-grow-define to run the planning half of the autospec-growth pipeline for a product opted into `.autospec\u002Fgrowth.yml` — sync\u002Fmeasure current metrics, fan out the 6-lens growth researcher roster (technical-seo, keyword-gap, content-opportunity, community, directory, backlink), adversarially verify + ROI\u002Fseverity-rank candidates through the deterministic pipeline, then decompose survivors into linked GitHub issues (growth:artifact \u002F growth:outbound). Stops after decomposition and hands off to \u002Fautospec-grow-run for autonomous drain.","berlinguyinca\u002Fautospec","berlinguyinca","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16364?v=4","01M71R7C0SWBG05FNHQE4XQ7Y3","Gert Wohlgemuth","01M71R7C1VY5K3Q715RNDDBVGQ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"autospec","define","autospec grow define","grow","github issues","sync","directory","run","decomposition","product","artifact","outbound","when","opportunity","autonomous","technical-seo","issues","pipeline","lens","community","2026-11-10 13:02:02",false,"---\nname: autospec-grow-define\ndescription: Use when the user wants \u002Fautospec-grow-define to run the planning half of the autospec-growth pipeline for a product opted into `.autospec\u002Fgrowth.yml` — sync\u002Fmeasure current metrics, fan out the 6-lens growth researcher roster (technical-seo, keyword-gap, content-opportunity, community, directory, backlink), adversarially verify + ROI\u002Fseverity-rank candidates through the deterministic pipeline, then decompose survivors into linked GitHub issues (growth:artifact \u002F growth:outbound). Stops after decomposition and hands off to \u002Fautospec-grow-run for autonomous drain.\n---\n\n# autospec-grow-define workflow (harness-neutral)\n\nRun the planning half of the autospec-growth pipeline for a product\u002Fsite opted\ninto `.autospec\u002Fgrowth.yml`: **measure → lens research → adversarial-verify +\nrank pipeline → decompose into linked GitHub issues.** Stop after decomposition;\nthe implementation half is handed off to `\u002Fautospec-grow-run`.\n\nManage your own context — never exceed 60%. Delegate to subagents whenever your harness supports it; do not run lens research, adversarial verification, or decomposition directly in the main conversation when a subagent can do it.\n\n\u003C!-- autospec-block:startup-self-update SKILL_NAME=autospec-grow-define -->\n\n## Self-update mode\n\nIf the invocation argument matches the regex `^\\s*update\\s*$` (case-insensitive, whitespace-padded), this skill enters self-update mode and does not run the normal pipeline:\n\n1. **Detect harness** by checking which install path exists for this skill:\n   - Claude Code: `~\u002F.claude\u002Fskills\u002Fautospec-grow-define\u002FSKILL.md`\n   - OpenCode:    `~\u002F.config\u002Fopencode\u002Fagent\u002Fautospec-grow-define.md`\n   - Codex CLI:   `~\u002F.codex\u002Fprompts\u002Fautospec-grow-define.md`\n2. **Re-install the full autospec suite from `main`** by piping the canonical installer:\n   ```bash\n   curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fberlinguyinca\u002Fautospec\u002Fmain\u002Fbootstrap.sh | bash -s -- --skill all --harness all --update\n   ```\n   Run this one-liner once; it refreshes all autospec skills across all harnesses.\n3. **Show the diff** between the prior installed file(s) and the freshly fetched copy (e.g. `diff \u003C(cat \u003Cprior>) \u003C(curl -fsSL ...SKILL.md)` or the equivalent recorded by the installer).\n4. **Stop.** Do not enter Phase G0 \u002F any pipeline phase. Print the upgrade summary and return to the user.\n\nIf no install path is detected, print `Self-update: no installed copy of autospec-grow-define found; run install.sh first.` and exit.\n\n## Required capabilities & harness adapter\n\nThis workflow assumes five capabilities. Map each one to your harness's actual tool. If a capability is missing, use the listed fallback.\n\n| Capability                  | Claude Code                          | OpenCode                                 | Codex CLI                                | Fallback if missing                                |\n|-----------------------------|--------------------------------------|------------------------------------------|------------------------------------------|----------------------------------------------------|\n| Read-only codebase research | `Agent` (subagent_type=Explore)      | `task` agent in read-only mode           | `apply_patch` read-only \u002F shell `grep`   | Do the search in-thread with `rg`\u002F`grep`           |\n| Foreground delegation       | `Agent` (subagent_type=general-purpose) | nested `task` agent, await output     | spawn nested CLI session                 | Do the work in-thread (more context cost)          |\n| Background delegation       | `Agent` with `run_in_background: true` | detached `task` agent                  | nohup'd CLI session writing to a logfile | Run the monitor in a separate terminal\u002Ftmux pane   |\n| Ask the user a question     | `AskUserQuestion`                    | inline prompt                            | inline prompt                            | Ask in the response and wait for the next turn     |\n| Subagent model tier         | Tier A: `opus` + `ultrathink`; Tier B: `sonnet` + medium thinking | Tier A: top `task` model + high reasoning; Tier B: smaller-tier `task` + medium reasoning | Tier A: top GPT + `reasoning_effort=high`; Tier B: current spark\u002Fcost-optimized Codex + `reasoning_effort=medium` | Honor the per-phase tier mapping in AGENTS.md; retry the same subagent UP on unavailability |\n\u003C!-- autospec-block:harness-adapter-core -->\n\n**Persistent project notes**: write durable preferences to **`AGENTS.md`** in the repo root — recognized by Claude Code, OpenCode, and Codex. Per AGENTS.md, subagent dispatches use a **two-tier policy**: Tier A (top model + extended thinking) for research\u002Fverify\u002Fdecompose work; Tier B (cheaper model + medium thinking) for mechanical steps. The orchestrator keeps the user's invoked model. Fall back UP the tier on quota\u002Fcapacity or other unavailability by retrying the same subagent with the stronger tier while preserving parent context.\n\n## Harness detection (run once at skill start, before Phase G0)\n\nDetect your harness by checking available tools before any phase:\n\n1. **Claude Code** — the `Agent` tool with a `subagent_type` parameter is available.\n   - `TIER_A` = `opus` + `ultrathink`  (the alias, which resolves to the current Claude Opus generation)\n   - `TIER_B` = `sonnet`               (the alias, which resolves to the current Claude Sonnet generation)\n\n2. **OpenCode** — a `task` tool with model\u002Ftier configuration is available (no `subagent_type`).\n   - `TIER_A` = top-tier task model + high reasoning\n   - `TIER_B` = smaller-tier task model + medium reasoning\n\n3. **Codex CLI** — neither `Agent` nor a configurable `task` tool is available; `apply_patch` is the primary edit tool.\n   - `TIER_A` = current top GPT model + `reasoning_effort=high`\n   - `TIER_B` = the spark \u002F cost-optimized variant of the configured model when one exists, else the configured model + `reasoning_effort=medium`\n\n**Fallback rule:** If `TIER_B` is not available in your harness (model unknown, quota\u002Fcapacity failure, authorization failure, or tool call returns an error for that model), silently retry the same subagent dispatch with `TIER_A`. Preserve the parent context on retry; for Codex native subagents, fork\u002Finherit the current conversation context and use the latest top GPT model instead of moving the work into the main session. Never ask the user.\n\nHold `TIER_A` and `TIER_B` for the entire skill run. Every \"Tier A\" and \"Tier B\" reference below resolves to these harness-specific values.\n\n**Model tier — what runs where:**\n\n| Phase | Model tier | Why |\n|---|---|---|\n| G1 Lens research (each of the 6 lenses) | `TIER_A` | Judgment-heavy: reading real metrics\u002Fsite\u002Fcrawl signals and proposing candidates with defensible ROI\u002Fseverity\u002Fconfidence scores. |\n| G2 Adversarial verify (per candidate) | `TIER_A` | Must actively try to refute a claim, not rubber-stamp it — cheap models default to agreeing. |\n| G3 Decompose (delegated to `autospec-define` Phase 3) | `TIER_A` | Inherits `autospec-define`'s own spec-work tier. |\n| Config read\u002Fvalidate, JSONL plumbing, `growth-measure.sh`\u002F`grow-define-pipeline.sh`\u002F`grow-define-file-issues.sh` invocations | `TIER_B` (or no subagent at all — deterministic scripts) | Mechanical: parsing, validating, and shelling out to deterministic scripts. |\n\n## Configuration\n\n`\u002Fautospec-grow-define` is **opt-in per repo**, mirroring `autospec-fab`'s\n`.autospec\u002Ffab.yml` gate. Before any phase:\n\n1. Check for `.autospec\u002Fgrowth.yml`. If absent, print:\n   `\"No .autospec\u002Fgrowth.yml found — this repo is not opted into autospec-growth. See skills\u002Fautospec-grow-define\u002FREADME.md to configure a product\u002Fsite and try again.\"`\n   and **exit** (inert; do not create the file, do not proceed to any phase).\n2. Render the YAML as JSON (e.g. `yq -o=json . .autospec\u002Fgrowth.yml`) and validate it:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fvalidate-growth-config.sh\" \u003Cconfig.json>\n   ```\n   If validation fails (non-zero exit), print the validator's stderr reason and **exit** — do not proceed with a partially-valid config.\n3. Hold the validated `\u003Cconfig.json>` path for the rest of the run — Phase G0 uses it to locate metric sources, G1 uses `channels`\u002F`targets`, G2 passes it to `grow-define-pipeline.sh`, G3 uses `approval.control_repo` and `channels` for labeling.\n\n## Relevant memory injection (run-start, once)\n\nBefore executing the main pipeline phases, call the injector to surface relevant saved lessons:\n\n```bash\nbash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Finject-relevant-memory.sh\" \\\n  --context \"autospec-grow-define growth lens research adversarial verify decompose\" \\\n  --top-k 5\n```\n\nPrepend the output block (if non-empty) to your working context. This surfaces lessons like the growth-ethics blocklist immutability rule and prior lint\u002Fdecomposition pitfalls before they recur.\n\n## Phase G0 — Measure (optional)\n\nSync current metrics before research so lens candidates cite real deltas\ninstead of guesses. This phase is best-effort — a fresh repo with no metrics\nhistory still proceeds.\n\n1. Read `measurement` from `\u003Cconfig.json>` (GSC property, analytics\n   provider\u002Ftoken_env, github_repo, rank_source). If the config points at\n   local raw metric files (or fixture files under a configured path) that\n   exist on disk, normalize each one:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrowth-measure.sh\" --normalize \u003Cprovider> \u003Craw.json>\n   ```\n2. If no config-pointed or fixture metric files exist, skip normalization and\n   proceed with an **empty measurement envelope** (`{\"provider\":null,\"metrics\":{},\"ts\":\u003Cnow>}`)\n   — G1 lenses fall back to structural\u002Fon-site evidence (crawl, GSC query\n   list if available, repo signals) rather than measured deltas.\n3. **Live provider API calls (GSC, Plausible\u002FGA4, SERP, backlink APIs) are\n   out of scope for this skill — that wiring lands in Plan 4.** This phase\n   only normalizes metric payloads already on disk or supplied as fixtures.\n\nHold the normalized envelope(s) (or the empty envelope) for G1 lens dispatches.\n\n## Phase G1 — Lens research (delegate, one Tier-A subagent per lens)\n\n> **Model tier:** `TIER_A` (research) — top model with extended thinking; resolved at startup.\n\nDispatch the full **Lens roster** below in parallel — one foreground Tier-A\nsubagent per lens, each bounded to a fresh context (config summary + G0\nmeasurement envelope + that lens's evidence sources only; do not fork the full\nparent conversation). Each lens subagent researches, then returns a JSON array\nof candidate objects matching the Plan 2 candidate schema\n(`skills\u002Fautospec-shared\u002Fschemas\u002Fgrowth-candidate.schema.json`):\n\n```json\n{\n  \"lens\": \"\u003Cone of the 6 lens tokens>\",\n  \"channel\": \"technical_seo|content|outreach|directories\",\n  \"kind\": \"artifact|outbound\",\n  \"title\": \"\u003Chuman-readable candidate title>\",\n  \"norm_title\": \"\u003Cnormalized dedup key>\",\n  \"rationale\": \"\u003Cwhy this candidate, grounded in evidence>\",\n  \"evidence\": [\"\u003Ccitation 1>\", \"\u003Ccitation 2>\"],\n  \"roi\": 1,\n  \"severity\": 1,\n  \"effort\": \"small|medium|large\",\n  \"confidence\": 0.0\n}\n```\n\n**Budget per lens.** Before dispatching, compute each lens's fan-out budget\n(how many candidates to ask for \u002F how much crawl-depth or query-breadth to\nspend) by reading the ledger-derived weight for that lens:\n\n```bash\nbash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrowth-source-weights.sh\"\n```\n\nThis prints a JSON object keyed by the 6 lens tokens with a smoothed weight in\n`[0,1]`. Scale each lens's candidate budget (e.g. `round(base_budget *\nweight[lens] * 2)`, floor 1) so lenses that have historically produced\nmerged\u002Fpublished\u002Fshipped candidates get more research budget this cycle, and\nlenses that mostly get refuted get less — without ever starving a lens to\nzero.\n\nAppend every candidate object returned by every lens (one JSON object per\nline) to a single candidates file, e.g. `\u002Ftmp\u002Fgrow-define-candidates.jsonl`.\nThis file is the G2 pipeline's first input.\n\n## Lens roster\n\nDispatch exactly these 6 lenses, each a Tier-A subagent, each returning\ncandidate JSON per the schema above:\n\n1. **`technical-seo`** — Technical-SEO auditor. Crawl the site (via\n   `autospec-playwright` \u002F Claude-in-Chrome if available, else static analysis\n   of `site.repo_path`): Core Web Vitals signals, meta tags, canonical\u002Fhreflang,\n   structured data (schema.org), sitemap\u002Frobots.txt, broken links, index\n   coverage. Candidates are `kind: artifact`, `channel: technical_seo`.\n\n2. **`keyword-gap`** — Keyword-gap researcher. Use the G0 GSC measurement\n   envelope (queries ranking position 5–20 are quick wins) plus\n   `targets.keyword_seeds` from config to find competitor keyword gaps.\n   Candidates are typically `kind: artifact`, `channel: content` (new\u002Fupdated\n   pages targeting the gap).\n\n3. **`content-opportunity`** — Content-opportunity researcher. Identify topic\n   clusters, \"vs\"\u002Fcomparison pages, and tutorial\u002Fdocs gaps relative to\n   `product.competitors` and `product.value_props`. Candidates are `kind:\n   artifact`, `channel: content`.\n\n4. **`community`** — Community researcher. From `targets.communities` in\n   config, propose genuinely on-topic posts for subreddits, HN, forums,\n   Discords, and awesome-lists — each candidate's `rationale` MUST cite the\n   venue's recorded `self_promo_rule` and `cadence_cap_per_week`. Candidates\n   are `kind: outbound`, `channel: outreach`.\n\n5. **`directory`** — Directory\u002Flisting researcher. From\n   `targets.directories`, propose legitimate directory\u002Flisting submissions\n   (Product Hunt, AlternativeTo, awesome-list PRs) the product genuinely\n   qualifies for. Candidates are `kind: outbound`, `channel: directories`\n   (an awesome-list PR that lands directly in the target repo may instead be\n   `kind: artifact` if it's a self-mergeable PR against a repo the product\n   owns).\n\n6. **`backlink`** — Backlink\u002Fpartnership researcher. Identify guest-post\n   targets and integration partners from `product.competitors`,\n   `product.personas`, and any backlink data in the G0 envelope. Candidates\n   are `kind: outbound`, `channel: outreach`.\n\nEvery lens candidate MUST set `norm_title` to a stable, whitespace\u002Fcase\n-normalized dedup key (the same on-topic idea proposed twice, even with\ndifferent phrasing, should normalize to the same key) — this is what\n`grow-define-pipeline.sh`'s dedup step matches against the ledger.\n\n## Phase G2 — Pipeline (delegate verify, then deterministic rank)\n\n> **Model tier:** `TIER_A` (verify) — top model with extended thinking; resolved at startup.\n\n1. **Adversarial verify (delegate, one Tier-A subagent per candidate, or\n   batched per lens if your harness supports structured batch output).** For\n   each candidate in the G1 candidates JSONL, dispatch a Tier-A subagent\n   prompted to **actively try to refute** the candidate — check the cited\n   evidence, re-derive the claim from source data where possible, and look\n   for reasons it's stale, already shipped, ethically blocked, or\n   unsupported. The subagent must default to `real:false` on any genuine\n   doubt (fail-closed, matching the pattern used by `autospec-explore`'s\n   verify stage). Collect one verdict object per candidate:\n   ```json\n   {\"norm_title\": \"\u003Ccandidate norm_title>\", \"real\": true, \"reason\": \"\u003C1-line justification>\"}\n   ```\n   Append every verdict (one JSON object per line) to a verdicts file, e.g.\n   `\u002Ftmp\u002Fgrow-define-verdicts.jsonl`.\n\n2. **Deterministic pipeline.** Run the shared G2 script against the\n   candidates, verdicts, and the validated config:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrow-define-pipeline.sh\" \\\n     \u002Ftmp\u002Fgrow-define-candidates.jsonl \u002Ftmp\u002Fgrow-define-verdicts.jsonl \u003Cconfig.json>\n   ```\n   This deterministically validates each candidate against the schema, dedups\n   against `.autospec\u002Fgrowth\u002Fledger.jsonl` (both previously-shipped and\n   previously-rejected items, so refused candidates don't reappear every\n   cycle), drops any candidate with no matching verdict or a `real:false`\n   verdict, ROI\u002Fseverity-ranks the survivors, and slices to\n   `grow.max_issues_per_cycle` (default 8). It prints the ranked top-N\n   candidates (one JSON object per line) to stdout — capture this as the\n   ranked output for Phase G3.\n\nIf the ranked output is empty, print `\"Phase G2: no candidates survived\nverification\u002Franking this cycle.\"` and skip Phase G3.\n\n## Phase G3 — Decompose\n\nSplit the ranked output from Phase G2 by `kind`.\n\n**Routing (explicit):**\n\n- **`kind: outbound`, and any `kind: artifact` candidate that is a simple,\n  single-issue artifact** (one file or one small self-contained change, no\n  natural multi-issue split) → file directly with the shared script:\n  ```bash\n  bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrow-define-file-issues.sh\" \\\n    \u003Cranked.jsonl> \u003Cconfig.json>\n  ```\n  This creates one GitHub issue per ranked candidate with the correct\n  `growth:artifact`\u002F`growth:outbound` + `growth:\u003Cchannel>` labels, appends a\n  `pending` ledger line per created issue, and prints the created issue\n  numbers.\n\n- **`kind: artifact` candidates that warrant decomposition into multiple\n  linked issues** (e.g. a comparison-page campaign spanning several pages, or\n  a technical-SEO fix touching more than ~3 files\u002Flogical units) → do **not**\n  file directly. Instead delegate to `autospec-define`'s Phase 3 decomposition\n  (same sizing caps, lint loop, and `## Model fit` classification it already\n  runs) to create the umbrella + linked children, then add the\n  `growth:artifact` label and the appropriate `growth:\u003Cchannel>` label to\n  every created issue (`gh issue edit \u003CN> --add-label\n  \"growth:artifact,growth:\u003Cchannel>\" --repo {repo}`).\n\nBoth paths append the resulting issues to the growth ledger (directly via\n`grow-define-file-issues.sh`, or via an explicit\n`growth-ledger.sh --append` call after the `autospec-define` Phase 3 path\ncreates its issues) so future G2 dedup passes see them.\n\n## Stop\n\nPrint a run summary and hand off — do not launch `\u002Fautospec-grow-run`\nautomatically:\n\n```\nPhase G3 complete on {repo}.\n- measured: \u003Cprovider(s) normalized, or \"none (empty envelope)\">\n- lens candidates: \u003Ctotal across all 6 lenses>\n- verified real: \u003Ccount> \u002F refuted: \u003Ccount>\n- filed: \u003CN> issues (\u003CA> growth:artifact, \u003CB> growth:outbound)\n- ledger: \u003Cpath to .autospec\u002Fgrowth\u002Fledger.jsonl>\n\nRun \u002Fautospec-grow-run to drain the growth backlog now, or let your external\nconductor (\u002Fautospec-grow) pick it up.\n```\n","# autospec-grow-define workflow (harness-neutral)\n\nRun the planning half of the autospec-growth pipeline for a product\u002Fsite opted\ninto `.autospec\u002Fgrowth.yml`: **measure → lens research → adversarial-verify +\nrank pipeline → decompose into linked GitHub issues.** Stop after decomposition;\nthe implementation half is handed off to `\u002Fautospec-grow-run`.\n\nManage your own context — never exceed 60%. Delegate to subagents whenever your harness supports it; do not run lens research, adversarial verification, or decomposition directly in the main conversation when a subagent can do it.\n\n\u003C!-- autospec-block:startup-self-update SKILL_NAME=autospec-grow-define -->\n\n## Self-update mode\n\nIf the invocation argument matches the regex `^\\s*update\\s*$` (case-insensitive, whitespace-padded), this skill enters self-update mode and does not run the normal pipeline:\n\n1. **Detect harness** by checking which install path exists for this skill:\n   - Claude Code: `~\u002F.claude\u002Fskills\u002Fautospec-grow-define\u002FSKILL.md`\n   - OpenCode:    `~\u002F.config\u002Fopencode\u002Fagent\u002Fautospec-grow-define.md`\n   - Codex CLI:   `~\u002F.codex\u002Fprompts\u002Fautospec-grow-define.md`\n2. **Re-install the full autospec suite from `main`** by piping the canonical installer:\n   ```bash\n   curl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fberlinguyinca\u002Fautospec\u002Fmain\u002Fbootstrap.sh | bash -s -- --skill all --harness all --update\n   ```\n   Run this one-liner once; it refreshes all autospec skills across all harnesses.\n3. **Show the diff** between the prior installed file(s) and the freshly fetched copy (e.g. `diff \u003C(cat \u003Cprior>) \u003C(curl -fsSL ...SKILL.md)` or the equivalent recorded by the installer).\n4. **Stop.** Do not enter Phase G0 \u002F any pipeline phase. Print the upgrade summary and return to the user.\n\nIf no install path is detected, print `Self-update: no installed copy of autospec-grow-define found; run install.sh first.` and exit.\n\n## Required capabilities & harness adapter\n\nThis workflow assumes five capabilities. Map each one to your harness's actual tool. If a capability is missing, use the listed fallback.\n\n| Capability                  | Claude Code                          | OpenCode                                 | Codex CLI                                | Fallback if missing                                |\n|-----------------------------|--------------------------------------|------------------------------------------|------------------------------------------|----------------------------------------------------|\n| Read-only codebase research | `Agent` (subagent_type=Explore)      | `task` agent in read-only mode           | `apply_patch` read-only \u002F shell `grep`   | Do the search in-thread with `rg`\u002F`grep`           |\n| Foreground delegation       | `Agent` (subagent_type=general-purpose) | nested `task` agent, await output     | spawn nested CLI session                 | Do the work in-thread (more context cost)          |\n| Background delegation       | `Agent` with `run_in_background: true` | detached `task` agent                  | nohup'd CLI session writing to a logfile | Run the monitor in a separate terminal\u002Ftmux pane   |\n| Ask the user a question     | `AskUserQuestion`                    | inline prompt                            | inline prompt                            | Ask in the response and wait for the next turn     |\n| Subagent model tier         | Tier A: `opus` + `ultrathink`; Tier B: `sonnet` + medium thinking | Tier A: top `task` model + high reasoning; Tier B: smaller-tier `task` + medium reasoning | Tier A: top GPT + `reasoning_effort=high`; Tier B: current spark\u002Fcost-optimized Codex + `reasoning_effort=medium` | Honor the per-phase tier mapping in AGENTS.md; retry the same subagent UP on unavailability |\n\u003C!-- autospec-block:harness-adapter-core -->\n\n**Persistent project notes**: write durable preferences to **`AGENTS.md`** in the repo root — recognized by Claude Code, OpenCode, and Codex. Per AGENTS.md, subagent dispatches use a **two-tier policy**: Tier A (top model + extended thinking) for research\u002Fverify\u002Fdecompose work; Tier B (cheaper model + medium thinking) for mechanical steps. The orchestrator keeps the user's invoked model. Fall back UP the tier on quota\u002Fcapacity or other unavailability by retrying the same subagent with the stronger tier while preserving parent context.\n\n## Harness detection (run once at skill start, before Phase G0)\n\nDetect your harness by checking available tools before any phase:\n\n1. **Claude Code** — the `Agent` tool with a `subagent_type` parameter is available.\n   - `TIER_A` = `opus` + `ultrathink`  (the alias, which resolves to the current Claude Opus generation)\n   - `TIER_B` = `sonnet`               (the alias, which resolves to the current Claude Sonnet generation)\n\n2. **OpenCode** — a `task` tool with model\u002Ftier configuration is available (no `subagent_type`).\n   - `TIER_A` = top-tier task model + high reasoning\n   - `TIER_B` = smaller-tier task model + medium reasoning\n\n3. **Codex CLI** — neither `Agent` nor a configurable `task` tool is available; `apply_patch` is the primary edit tool.\n   - `TIER_A` = current top GPT model + `reasoning_effort=high`\n   - `TIER_B` = the spark \u002F cost-optimized variant of the configured model when one exists, else the configured model + `reasoning_effort=medium`\n\n**Fallback rule:** If `TIER_B` is not available in your harness (model unknown, quota\u002Fcapacity failure, authorization failure, or tool call returns an error for that model), silently retry the same subagent dispatch with `TIER_A`. Preserve the parent context on retry; for Codex native subagents, fork\u002Finherit the current conversation context and use the latest top GPT model instead of moving the work into the main session. Never ask the user.\n\nHold `TIER_A` and `TIER_B` for the entire skill run. Every \"Tier A\" and \"Tier B\" reference below resolves to these harness-specific values.\n\n**Model tier — what runs where:**\n\n| Phase | Model tier | Why |\n|---|---|---|\n| G1 Lens research (each of the 6 lenses) | `TIER_A` | Judgment-heavy: reading real metrics\u002Fsite\u002Fcrawl signals and proposing candidates with defensible ROI\u002Fseverity\u002Fconfidence scores. |\n| G2 Adversarial verify (per candidate) | `TIER_A` | Must actively try to refute a claim, not rubber-stamp it — cheap models default to agreeing. |\n| G3 Decompose (delegated to `autospec-define` Phase 3) | `TIER_A` | Inherits `autospec-define`'s own spec-work tier. |\n| Config read\u002Fvalidate, JSONL plumbing, `growth-measure.sh`\u002F`grow-define-pipeline.sh`\u002F`grow-define-file-issues.sh` invocations | `TIER_B` (or no subagent at all — deterministic scripts) | Mechanical: parsing, validating, and shelling out to deterministic scripts. |\n\n## Configuration\n\n`\u002Fautospec-grow-define` is **opt-in per repo**, mirroring `autospec-fab`'s\n`.autospec\u002Ffab.yml` gate. Before any phase:\n\n1. Check for `.autospec\u002Fgrowth.yml`. If absent, print:\n   `\"No .autospec\u002Fgrowth.yml found — this repo is not opted into autospec-growth. See skills\u002Fautospec-grow-define\u002FREADME.md to configure a product\u002Fsite and try again.\"`\n   and **exit** (inert; do not create the file, do not proceed to any phase).\n2. Render the YAML as JSON (e.g. `yq -o=json . .autospec\u002Fgrowth.yml`) and validate it:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fvalidate-growth-config.sh\" \u003Cconfig.json>\n   ```\n   If validation fails (non-zero exit), print the validator's stderr reason and **exit** — do not proceed with a partially-valid config.\n3. Hold the validated `\u003Cconfig.json>` path for the rest of the run — Phase G0 uses it to locate metric sources, G1 uses `channels`\u002F`targets`, G2 passes it to `grow-define-pipeline.sh`, G3 uses `approval.control_repo` and `channels` for labeling.\n\n## Relevant memory injection (run-start, once)\n\nBefore executing the main pipeline phases, call the injector to surface relevant saved lessons:\n\n```bash\nbash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Finject-relevant-memory.sh\" \\\n  --context \"autospec-grow-define growth lens research adversarial verify decompose\" \\\n  --top-k 5\n```\n\nPrepend the output block (if non-empty) to your working context. This surfaces lessons like the growth-ethics blocklist immutability rule and prior lint\u002Fdecomposition pitfalls before they recur.\n\n## Phase G0 — Measure (optional)\n\nSync current metrics before research so lens candidates cite real deltas\ninstead of guesses. This phase is best-effort — a fresh repo with no metrics\nhistory still proceeds.\n\n1. Read `measurement` from `\u003Cconfig.json>` (GSC property, analytics\n   provider\u002Ftoken_env, github_repo, rank_source). If the config points at\n   local raw metric files (or fixture files under a configured path) that\n   exist on disk, normalize each one:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrowth-measure.sh\" --normalize \u003Cprovider> \u003Craw.json>\n   ```\n2. If no config-pointed or fixture metric files exist, skip normalization and\n   proceed with an **empty measurement envelope** (`{\"provider\":null,\"metrics\":{},\"ts\":\u003Cnow>}`)\n   — G1 lenses fall back to structural\u002Fon-site evidence (crawl, GSC query\n   list if available, repo signals) rather than measured deltas.\n3. **Live provider API calls (GSC, Plausible\u002FGA4, SERP, backlink APIs) are\n   out of scope for this skill — that wiring lands in Plan 4.** This phase\n   only normalizes metric payloads already on disk or supplied as fixtures.\n\nHold the normalized envelope(s) (or the empty envelope) for G1 lens dispatches.\n\n## Phase G1 — Lens research (delegate, one Tier-A subagent per lens)\n\n> **Model tier:** `TIER_A` (research) — top model with extended thinking; resolved at startup.\n\nDispatch the full **Lens roster** below in parallel — one foreground Tier-A\nsubagent per lens, each bounded to a fresh context (config summary + G0\nmeasurement envelope + that lens's evidence sources only; do not fork the full\nparent conversation). Each lens subagent researches, then returns a JSON array\nof candidate objects matching the Plan 2 candidate schema\n(`skills\u002Fautospec-shared\u002Fschemas\u002Fgrowth-candidate.schema.json`):\n\n```json\n{\n  \"lens\": \"\u003Cone of the 6 lens tokens>\",\n  \"channel\": \"technical_seo|content|outreach|directories\",\n  \"kind\": \"artifact|outbound\",\n  \"title\": \"\u003Chuman-readable candidate title>\",\n  \"norm_title\": \"\u003Cnormalized dedup key>\",\n  \"rationale\": \"\u003Cwhy this candidate, grounded in evidence>\",\n  \"evidence\": [\"\u003Ccitation 1>\", \"\u003Ccitation 2>\"],\n  \"roi\": 1,\n  \"severity\": 1,\n  \"effort\": \"small|medium|large\",\n  \"confidence\": 0.0\n}\n```\n\n**Budget per lens.** Before dispatching, compute each lens's fan-out budget\n(how many candidates to ask for \u002F how much crawl-depth or query-breadth to\nspend) by reading the ledger-derived weight for that lens:\n\n```bash\nbash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrowth-source-weights.sh\"\n```\n\nThis prints a JSON object keyed by the 6 lens tokens with a smoothed weight in\n`[0,1]`. Scale each lens's candidate budget (e.g. `round(base_budget *\nweight[lens] * 2)`, floor 1) so lenses that have historically produced\nmerged\u002Fpublished\u002Fshipped candidates get more research budget this cycle, and\nlenses that mostly get refuted get less — without ever starving a lens to\nzero.\n\nAppend every candidate object returned by every lens (one JSON object per\nline) to a single candidates file, e.g. `\u002Ftmp\u002Fgrow-define-candidates.jsonl`.\nThis file is the G2 pipeline's first input.\n\n## Lens roster\n\nDispatch exactly these 6 lenses, each a Tier-A subagent, each returning\ncandidate JSON per the schema above:\n\n1. **`technical-seo`** — Technical-SEO auditor. Crawl the site (via\n   `autospec-playwright` \u002F Claude-in-Chrome if available, else static analysis\n   of `site.repo_path`): Core Web Vitals signals, meta tags, canonical\u002Fhreflang,\n   structured data (schema.org), sitemap\u002Frobots.txt, broken links, index\n   coverage. Candidates are `kind: artifact`, `channel: technical_seo`.\n\n2. **`keyword-gap`** — Keyword-gap researcher. Use the G0 GSC measurement\n   envelope (queries ranking position 5–20 are quick wins) plus\n   `targets.keyword_seeds` from config to find competitor keyword gaps.\n   Candidates are typically `kind: artifact`, `channel: content` (new\u002Fupdated\n   pages targeting the gap).\n\n3. **`content-opportunity`** — Content-opportunity researcher. Identify topic\n   clusters, \"vs\"\u002Fcomparison pages, and tutorial\u002Fdocs gaps relative to\n   `product.competitors` and `product.value_props`. Candidates are `kind:\n   artifact`, `channel: content`.\n\n4. **`community`** — Community researcher. From `targets.communities` in\n   config, propose genuinely on-topic posts for subreddits, HN, forums,\n   Discords, and awesome-lists — each candidate's `rationale` MUST cite the\n   venue's recorded `self_promo_rule` and `cadence_cap_per_week`. Candidates\n   are `kind: outbound`, `channel: outreach`.\n\n5. **`directory`** — Directory\u002Flisting researcher. From\n   `targets.directories`, propose legitimate directory\u002Flisting submissions\n   (Product Hunt, AlternativeTo, awesome-list PRs) the product genuinely\n   qualifies for. Candidates are `kind: outbound`, `channel: directories`\n   (an awesome-list PR that lands directly in the target repo may instead be\n   `kind: artifact` if it's a self-mergeable PR against a repo the product\n   owns).\n\n6. **`backlink`** — Backlink\u002Fpartnership researcher. Identify guest-post\n   targets and integration partners from `product.competitors`,\n   `product.personas`, and any backlink data in the G0 envelope. Candidates\n   are `kind: outbound`, `channel: outreach`.\n\nEvery lens candidate MUST set `norm_title` to a stable, whitespace\u002Fcase\n-normalized dedup key (the same on-topic idea proposed twice, even with\ndifferent phrasing, should normalize to the same key) — this is what\n`grow-define-pipeline.sh`'s dedup step matches against the ledger.\n\n## Phase G2 — Pipeline (delegate verify, then deterministic rank)\n\n> **Model tier:** `TIER_A` (verify) — top model with extended thinking; resolved at startup.\n\n1. **Adversarial verify (delegate, one Tier-A subagent per candidate, or\n   batched per lens if your harness supports structured batch output).** For\n   each candidate in the G1 candidates JSONL, dispatch a Tier-A subagent\n   prompted to **actively try to refute** the candidate — check the cited\n   evidence, re-derive the claim from source data where possible, and look\n   for reasons it's stale, already shipped, ethically blocked, or\n   unsupported. The subagent must default to `real:false` on any genuine\n   doubt (fail-closed, matching the pattern used by `autospec-explore`'s\n   verify stage). Collect one verdict object per candidate:\n   ```json\n   {\"norm_title\": \"\u003Ccandidate norm_title>\", \"real\": true, \"reason\": \"\u003C1-line justification>\"}\n   ```\n   Append every verdict (one JSON object per line) to a verdicts file, e.g.\n   `\u002Ftmp\u002Fgrow-define-verdicts.jsonl`.\n\n2. **Deterministic pipeline.** Run the shared G2 script against the\n   candidates, verdicts, and the validated config:\n   ```bash\n   bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrow-define-pipeline.sh\" \\\n     \u002Ftmp\u002Fgrow-define-candidates.jsonl \u002Ftmp\u002Fgrow-define-verdicts.jsonl \u003Cconfig.json>\n   ```\n   This deterministically validates each candidate against the schema, dedups\n   against `.autospec\u002Fgrowth\u002Fledger.jsonl` (both previously-shipped and\n   previously-rejected items, so refused candidates don't reappear every\n   cycle), drops any candidate with no matching verdict or a `real:false`\n   verdict, ROI\u002Fseverity-ranks the survivors, and slices to\n   `grow.max_issues_per_cycle` (default 8). It prints the ranked top-N\n   candidates (one JSON object per line) to stdout — capture this as the\n   ranked output for Phase G3.\n\nIf the ranked output is empty, print `\"Phase G2: no candidates survived\nverification\u002Franking this cycle.\"` and skip Phase G3.\n\n## Phase G3 — Decompose\n\nSplit the ranked output from Phase G2 by `kind`.\n\n**Routing (explicit):**\n\n- **`kind: outbound`, and any `kind: artifact` candidate that is a simple,\n  single-issue artifact** (one file or one small self-contained change, no\n  natural multi-issue split) → file directly with the shared script:\n  ```bash\n  bash \"${AUTOSPEC_SCRIPTS_DIR:-$HOME\u002F.autospec\u002Fscripts}\u002Fgrow-define-file-issues.sh\" \\\n    \u003Cranked.jsonl> \u003Cconfig.json>\n  ```\n  This creates one GitHub issue per ranked candidate with the correct\n  `growth:artifact`\u002F`growth:outbound` + `growth:\u003Cchannel>` labels, appends a\n  `pending` ledger line per created issue, and prints the created issue\n  numbers.\n\n- **`kind: artifact` candidates that warrant decomposition into multiple\n  linked issues** (e.g. a comparison-page campaign spanning several pages, or\n  a technical-SEO fix touching more than ~3 files\u002Flogical units) → do **not**\n  file directly. Instead delegate to `autospec-define`'s Phase 3 decomposition\n  (same sizing caps, lint loop, and `## Model fit` classification it already\n  runs) to create the umbrella + linked children, then add the\n  `growth:artifact` label and the appropriate `growth:\u003Cchannel>` label to\n  every created issue (`gh issue edit \u003CN> --add-label\n  \"growth:artifact,growth:\u003Cchannel>\" --repo {repo}`).\n\nBoth paths append the resulting issues to the growth ledger (directly via\n`grow-define-file-issues.sh`, or via an explicit\n`growth-ledger.sh --append` call after the `autospec-define` Phase 3 path\ncreates its issues) so future G2 dedup passes see them.\n\n## Stop\n\nPrint a run summary and hand off — do not launch `\u002Fautospec-grow-run`\nautomatically:\n\n```\nPhase G3 complete on {repo}.\n- measured: \u003Cprovider(s) normalized, or \"none (empty envelope)\">\n- lens candidates: \u003Ctotal across all 6 lenses>\n- verified real: \u003Ccount> \u002F refuted: \u003Ccount>\n- filed: \u003CN> issues (\u003CA> growth:artifact, \u003CB> growth:outbound)\n- ledger: \u003Cpath to .autospec\u002Fgrowth\u002Fledger.jsonl>\n\nRun \u002Fautospec-grow-run to drain the growth backlog now, or let your external\nconductor (\u002Fautospec-grow) pick it up.\n```\n",{"name":5,"description":7},"main","9e7f04357ff46ab731d4f56a4ac5ca5449c13bb0","skills\u002Fautospec-grow-define",1,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec","https:\u002F\u002Fgithub.com\u002Fberlinguyinca","Love to lead, code, cook and contribute to open source and believe that you can learn anything you set your mind too.\r\n","2026-11-11 07:09:35",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add berlinguyinca\u002Fautospec --skill autospec-grow-define",{"tool":58,"command":59},"bunx","bunx skills add berlinguyinca\u002Fautospec --skill autospec-grow-define",{"tool":61,"command":62},"pnpm","pnpm dlx skills add berlinguyinca\u002Fautospec --skill autospec-grow-define","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002FSKILL.md",true,[66,72,78,82,86],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"codex\u002Fprompt.md","REFERENCE","参考文档",17930,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002Fcodex\u002Fprompt.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"install.sh","SCRIPT","脚本",13129,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002Finstall.sh",{"path":79,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":80,"sourceHtmlUrl":81},"opencode\u002Fagent.md",18564,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002Fopencode\u002Fagent.md",{"path":83,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":84,"sourceHtmlUrl":85},"README.md",4677,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002FREADME.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"uninstall.sh",3945,"https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-grow-define\u002Funinstall.sh",[91,104,113,122,146,170],{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":101,"publishedAt":39},"01M71RJHYMKPTC9AAPXWQ6F4RT","trio-pass-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-trio-pass\u002FSKILL.md",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[102,103],"trio","trio pass skill",{"skillNo":105,"name":106,"nameZh":6,"description":6,"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":110,"publishedAt":39},"01M71RJFBQ1KAF9XM3T3Y4VMSK","duo-pass-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-duo-pass\u002FSKILL.md",[109],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[111,112],"duo pass skill","duo",{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":39},"01M71RJDT1TB3P9TRWR6A534FB","duo-divergence-skill","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flockstep-duo-divergence\u002FSKILL.md",[118],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[120,112,121],"duo divergence skill","divergence",{"skillNo":123,"name":19,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":39},"01M71RJAC4NNEQSYBDSY3NZS73","Use when the user wants to ship a feature end-to-end across multiple commits — bootstraps repo if missing, brainstorms a design spec, decomposes into linked GitHub issues, or splits an existing spec into issues, then runs an autonomous implementation loop with auto-merge.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000015","视觉设计",[19,131,132,35,133,33,134,135,31,136,137,138,139,140,23,141,142,143,144,145],"ship a feature","end","design","auto","loop","across","design spec","merge","ship","implementation loop","feature","commits","repo","missing","use",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":39},"01M71RJ4F9HT8PT26CKNM9XE1M","autospec-upgrade","Use when the user wants to upgrade an Angular, Next.js, or React project to the latest official versions safely — by locking observable behavior before touching versions, upgrading one major at a time with official codemods, and gating completion on mutation score rather than coverage theater.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-upgrade\u002FSKILL.md",[],[153,19,154,155,156,157,158,159,160,31,161,162,163,164,145,165,166,167,168,169],"autospec upgrade","upgrade","mutation","coverage","official","project","time","gating","angular","react","next","at","Next.js","one","with","behavior","latest",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":181,"publishedAt":39},"01M71RJ28FJ4PM6DXHB7T5CF8H","autospec-ui-audit","Use when a React Router application needs a deterministic whole-site route inventory before UI, UX, navigation, or evidence auditing begins.","https:\u002F\u002Fgithub.com\u002Fberlinguyinca\u002Fautospec\u002Fblob\u002Fmain\u002Fskills\u002Fautospec-ui-audit\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":179,"taxonomyTypeDesc":180},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[182,19,183,184,185,145,186,187,188,189,190,191,192,193,194,162,195,31,196],"ui audit","audit","autospec ui audit","ui","inventory","evidence","deterministic","route","ux","site","react router","navigation","application","needs","router"]