[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DFVXXT4K23TXHDFK57YR8T":3,"skill-same:01M7DFVXXT4K23TXHDFK57YR8T":70},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DFVXXT4K23TXHDFK57YR8T","test-roadmap",null,"EXPERIMENTAL. Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.","heynemann\u002Fomp-marketplace","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7DFBDAM3NXF540P210W3NYT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-roadmap\ndescription: >\n  EXPERIMENTAL. Analyzes a repository and any existing test suite, grades\n  existing tests for weakness, classifies mocks, emits a phased roadmap for\n  building a test suite that catches real regressions, then executes those\n  phases one at a time. Use when planning or building a test suite, assessing\n  whether existing tests are worth anything, adding tests to a legacy codebase,\n  or when the user mentions test coverage, test strategy, or weak tests. Not for\n  reviewing a branch for bugs, and not for fixing the bugs it logs.\ncompatibility: Requires git\n---\n\n**On invocation:** announce \"Running paad:test-roadmap v1.31.0\" before anything else.\n\n> **EXPERIMENTAL SKILL.** Its arguments, output paths, and behavior may\n> change or be withdrawn in any release, including patch releases. It is not\n> covered by the semver guarantees the other paad skills carry. Unlike every\n> other paad skill, this one **writes code and commits it** — tests, one commit\n> per phase, onto your working branch. Report rough edges at\n> \u003Chttps:\u002F\u002Fgithub.com\u002FOvid\u002Fpaad\u002Fissues>.\n\n# test-roadmap\n\nThis file is the router. The routing itself stays dumb on purpose: one check,\ntwo routes, nothing else. A couple of preconditions guard it first. All the\nsubstance — grading, planning, writing tests, bug injection — lives in\n`references\u002F` and loads only once routing has picked a mode.\n\n**Pre-flight and routing:**\n\n```dot\ndigraph route {\n  \"Inside a git repo?\" [shape=diamond];\n  \"STOP: needs a git checkout\" [shape=box, style=bold];\n  \"Detached HEAD?\" [shape=diamond];\n  \"origin\u002FHEAD pointer resolves?\" [shape=diamond];\n  \"Current branch == default branch?\" [shape=diamond];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" [shape=diamond];\n  \"ASK: is this your main development line?\" [shape=diamond];\n  \"OFFER: create a working branch\" [shape=box];\n  \"Developer agrees?\" [shape=diamond];\n  \"STOP: never build on the primary branch\" [shape=box, style=bold];\n  \"git switch -c \u003Cname>\" [shape=box];\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [shape=diamond];\n  \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" [shape=box];\n  \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" [shape=box];\n\n  \"Inside a git repo?\" -> \"STOP: needs a git checkout\" [label=\"no\"];\n  \"Inside a git repo?\" -> \"Detached HEAD?\" [label=\"yes\"];\n  \"Detached HEAD?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Detached HEAD?\" -> \"origin\u002FHEAD pointer resolves?\" [label=\"no\"];\n  \"origin\u002FHEAD pointer resolves?\" -> \"Current branch == default branch?\" [label=\"yes (authoritative)\"];\n  \"origin\u002FHEAD pointer resolves?\" -> \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" [label=\"no\"];\n  \"Current branch == default branch?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Current branch == default branch?\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [label=\"no\"];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" -> \"ASK: is this your main development line?\" [label=\"no\"];\n  \"ASK: is this your main development line?\" -> \"OFFER: create a working branch\" [label=\"yes \u002F unsure\"];\n  \"ASK: is this your main development line?\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [label=\"no\"];\n  \"OFFER: create a working branch\" -> \"Developer agrees?\";\n  \"Developer agrees?\" -> \"STOP: never build on the primary branch\" [label=\"no\"];\n  \"Developer agrees?\" -> \"git switch -c \u003Cname>\" [label=\"yes\"];\n  \"git switch -c \u003Cname>\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\";\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" -> \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" [label=\"yes\"];\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" -> \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" [label=\"no\"];\n}\n```\n\n## Before routing: confirm you're in a repo\n\n`compatibility: Requires git` above means this skill needs a working git\ncheckout — build mode fans out grading subagents against the tree as it\nstands, and execute mode's `break-it-check` gate runs bug injection in a\ndisposable `git worktree`. If the current directory isn't inside a git repo,\nsay so and stop before loading either mode file.\n\n## Before routing: confirm you're on a working branch\n\nThis skill commits as it goes — build mode commits the roadmap, execute mode\ncommits each phase's tests — all onto the branch you are on right now. A\nhalf-built test suite landing on the developer's main development line is exactly\nwhat this check prevents, the same spirit as running a code review on a feature\nbranch rather than on `main`. So before routing, confirm the current branch is a\n*working* branch, not the primary one.\n\nIdentify the primary branch from repo signals, in order — stop at the first that\ndecides:\n\n1. **Detached HEAD** — `git symbolic-ref -q HEAD` prints nothing. There is no\n   branch for the suite to accumulate on at all; treat it like being on the\n   primary branch and offer a working branch (below).\n2. **The repo's own default-branch pointer** — `git symbolic-ref -q --short\n   refs\u002Fremotes\u002Forigin\u002FHEAD` resolves to e.g. `origin\u002Fmain`; strip the remote\n   prefix for the default branch name. If the current branch (`git symbolic-ref\n   -q --short HEAD`) equals it, you are on the primary branch. This is the\n   authoritative signal and needs no built-in list of names.\n3. **No such pointer** (a local-only repo, or one where it was never set) — fall\n   back to the well-known primary names: `main`, `master`, `trunk`, `develop`,\n   `devel`, and the like — **examples, not a closed list**, the same stance\n   Stage 1 takes on manifests. If the current branch name matches one, treat it\n   as primary. If it matches none *and* step 2 could not confirm, **ask the\n   developer once, in plain words**, whether this is their main development line —\n   never silently proceed on a branch that might be it. Being wrong toward asking\n   costs a keystroke; being wrong toward building on the main line is the harm\n   this check exists to prevent.\n\n**When the current branch is the primary one (or HEAD is detached), do not route\nyet.** Say why in plain words — *\"I build the test suite up commit by commit, and\nyou don't want those landing on your main branch while it's half-done, so let's\nput them on a working branch\"* — then offer to make one: propose a name\n(`test-roadmap` is a fine default), and on the developer's OK run `git switch -c\n\u003Cname>` (or `git checkout -b \u003Cname>` on older git) and continue to routing. If\nthey decline, stop — never build or execute on the primary branch.\n\nThis is the skill's **one** branch: a single working branch, created at\ninvocation only when needed. It is **not** a per-phase branch — execute mode\nstill commits every phase onto whatever working branch you are on, and the suite\naccumulates there (see `references\u002Fexecute-test-roadmap.md § What execute mode\nwrites`). Both mode files assume this check has already passed and never re-run\nit; the guard lives here, once.\n\n## Route\n\n```\npaad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?  →  load references\u002Fexecute-test-roadmap.md\n                       absent  →  load references\u002Fbuild-test-roadmap.md\n```\n\nThat is the entire routing logic — one file existence check, two branches.\n`paad\u002Ftest-roadmap\u002Ftest-roadmap.md` is the roadmap this skill itself writes at the end of\nbuild mode, so its presence is exactly the signal that a previous run already\ndid Detect\u002FGrade\u002FPlan\u002FCritique\u002FWrite and there is a phased plan to execute\nagainst. Its absence means this is either the first run against this repo, or\na run after that file was deleted — either way, build it.\n\nIf it ever grows a third condition, that is a signal something has been put\nin the wrong place — take it back to `build-test-roadmap.md` or\n`execute-test-roadmap.md`, not to this file.\n\nThis router never loads `references\u002Fbreak-it-check.md`,\n`references\u002Ftest-pushback.md`, or `references\u002Ftest-theater.md` directly.\nThose three are loaded by whichever of the two mode files needs them, at the\npoint in their own protocol that needs them — not from here.\n\n## Entering build mode\n\nBefore build mode can plan anything, it needs to know what it's planning\nfor. The first thing it does — Stage 1, Detect — is identify the stack from\nmanifests and config rather than assumption (`package.json`,\n`pyproject.toml`, `go.mod`, `Cargo.toml`, `Gemfile`, and so on: examples, not\na closed table), then determine how tests are invoked and what test files\nalready exist. The skill must never hardcode a language; where it needs a\nper-ecosystem fact, it looks for the signal in the repo instead of consulting\na built-in list.\n\nThe full five-stage protocol — Detect, Grade, Plan, Critique, Write — lives\nin `references\u002Fbuild-test-roadmap.md`. Load it now if\n`paad\u002Ftest-roadmap\u002Ftest-roadmap.md` is absent.\n\n## Entering execute mode\n\nLoad `references\u002Fexecute-test-roadmap.md` now if `paad\u002Ftest-roadmap\u002Ftest-roadmap.md`\nexists. It reads that file's `## Decisions` section once, selects the next\nphase per the completion protocol, and gets on with writing tests — it does\nnot re-detect or re-ask anything build mode already settled.\n","**On invocation:** announce \"Running paad:test-roadmap v1.31.0\" before anything else.\n\n> **EXPERIMENTAL SKILL.** Its arguments, output paths, and behavior may\n> change or be withdrawn in any release, including patch releases. It is not\n> covered by the semver guarantees the other paad skills carry. Unlike every\n> other paad skill, this one **writes code and commits it** — tests, one commit\n> per phase, onto your working branch. Report rough edges at\n> \u003Chttps:\u002F\u002Fgithub.com\u002FOvid\u002Fpaad\u002Fissues>.\n\n# test-roadmap\n\nThis file is the router. The routing itself stays dumb on purpose: one check,\ntwo routes, nothing else. A couple of preconditions guard it first. All the\nsubstance — grading, planning, writing tests, bug injection — lives in\n`references\u002F` and loads only once routing has picked a mode.\n\n**Pre-flight and routing:**\n\n```dot\ndigraph route {\n  \"Inside a git repo?\" [shape=diamond];\n  \"STOP: needs a git checkout\" [shape=box, style=bold];\n  \"Detached HEAD?\" [shape=diamond];\n  \"origin\u002FHEAD pointer resolves?\" [shape=diamond];\n  \"Current branch == default branch?\" [shape=diamond];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" [shape=diamond];\n  \"ASK: is this your main development line?\" [shape=diamond];\n  \"OFFER: create a working branch\" [shape=box];\n  \"Developer agrees?\" [shape=diamond];\n  \"STOP: never build on the primary branch\" [shape=box, style=bold];\n  \"git switch -c \u003Cname>\" [shape=box];\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [shape=diamond];\n  \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" [shape=box];\n  \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" [shape=box];\n\n  \"Inside a git repo?\" -> \"STOP: needs a git checkout\" [label=\"no\"];\n  \"Inside a git repo?\" -> \"Detached HEAD?\" [label=\"yes\"];\n  \"Detached HEAD?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Detached HEAD?\" -> \"origin\u002FHEAD pointer resolves?\" [label=\"no\"];\n  \"origin\u002FHEAD pointer resolves?\" -> \"Current branch == default branch?\" [label=\"yes (authoritative)\"];\n  \"origin\u002FHEAD pointer resolves?\" -> \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" [label=\"no\"];\n  \"Current branch == default branch?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Current branch == default branch?\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [label=\"no\"];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" -> \"OFFER: create a working branch\" [label=\"yes\"];\n  \"Name matches a well-known primary (main\u002Fmaster\u002Ftrunk\u002Fdevelop\u002F...)?\" -> \"ASK: is this your main development line?\" [label=\"no\"];\n  \"ASK: is this your main development line?\" -> \"OFFER: create a working branch\" [label=\"yes \u002F unsure\"];\n  \"ASK: is this your main development line?\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" [label=\"no\"];\n  \"OFFER: create a working branch\" -> \"Developer agrees?\";\n  \"Developer agrees?\" -> \"STOP: never build on the primary branch\" [label=\"no\"];\n  \"Developer agrees?\" -> \"git switch -c \u003Cname>\" [label=\"yes\"];\n  \"git switch -c \u003Cname>\" -> \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\";\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" -> \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" [label=\"yes\"];\n  \"paad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?\" -> \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" [label=\"no\"];\n}\n```\n\n## Before routing: confirm you're in a repo\n\n`compatibility: Requires git` above means this skill needs a working git\ncheckout — build mode fans out grading subagents against the tree as it\nstands, and execute mode's `break-it-check` gate runs bug injection in a\ndisposable `git worktree`. If the current directory isn't inside a git repo,\nsay so and stop before loading either mode file.\n\n## Before routing: confirm you're on a working branch\n\nThis skill commits as it goes — build mode commits the roadmap, execute mode\ncommits each phase's tests — all onto the branch you are on right now. A\nhalf-built test suite landing on the developer's main development line is exactly\nwhat this check prevents, the same spirit as running a code review on a feature\nbranch rather than on `main`. So before routing, confirm the current branch is a\n*working* branch, not the primary one.\n\nIdentify the primary branch from repo signals, in order — stop at the first that\ndecides:\n\n1. **Detached HEAD** — `git symbolic-ref -q HEAD` prints nothing. There is no\n   branch for the suite to accumulate on at all; treat it like being on the\n   primary branch and offer a working branch (below).\n2. **The repo's own default-branch pointer** — `git symbolic-ref -q --short\n   refs\u002Fremotes\u002Forigin\u002FHEAD` resolves to e.g. `origin\u002Fmain`; strip the remote\n   prefix for the default branch name. If the current branch (`git symbolic-ref\n   -q --short HEAD`) equals it, you are on the primary branch. This is the\n   authoritative signal and needs no built-in list of names.\n3. **No such pointer** (a local-only repo, or one where it was never set) — fall\n   back to the well-known primary names: `main`, `master`, `trunk`, `develop`,\n   `devel`, and the like — **examples, not a closed list**, the same stance\n   Stage 1 takes on manifests. If the current branch name matches one, treat it\n   as primary. If it matches none *and* step 2 could not confirm, **ask the\n   developer once, in plain words**, whether this is their main development line —\n   never silently proceed on a branch that might be it. Being wrong toward asking\n   costs a keystroke; being wrong toward building on the main line is the harm\n   this check exists to prevent.\n\n**When the current branch is the primary one (or HEAD is detached), do not route\nyet.** Say why in plain words — *\"I build the test suite up commit by commit, and\nyou don't want those landing on your main branch while it's half-done, so let's\nput them on a working branch\"* — then offer to make one: propose a name\n(`test-roadmap` is a fine default), and on the developer's OK run `git switch -c\n\u003Cname>` (or `git checkout -b \u003Cname>` on older git) and continue to routing. If\nthey decline, stop — never build or execute on the primary branch.\n\nThis is the skill's **one** branch: a single working branch, created at\ninvocation only when needed. It is **not** a per-phase branch — execute mode\nstill commits every phase onto whatever working branch you are on, and the suite\naccumulates there (see `references\u002Fexecute-test-roadmap.md § What execute mode\nwrites`). Both mode files assume this check has already passed and never re-run\nit; the guard lives here, once.\n\n## Route\n\n```\npaad\u002Ftest-roadmap\u002Ftest-roadmap.md exists?  →  load references\u002Fexecute-test-roadmap.md\n                       absent  →  load references\u002Fbuild-test-roadmap.md\n```\n\nThat is the entire routing logic — one file existence check, two branches.\n`paad\u002Ftest-roadmap\u002Ftest-roadmap.md` is the roadmap this skill itself writes at the end of\nbuild mode, so its presence is exactly the signal that a previous run already\ndid Detect\u002FGrade\u002FPlan\u002FCritique\u002FWrite and there is a phased plan to execute\nagainst. Its absence means this is either the first run against this repo, or\na run after that file was deleted — either way, build it.\n\nIf it ever grows a third condition, that is a signal something has been put\nin the wrong place — take it back to `build-test-roadmap.md` or\n`execute-test-roadmap.md`, not to this file.\n\nThis router never loads `references\u002Fbreak-it-check.md`,\n`references\u002Ftest-pushback.md`, or `references\u002Ftest-theater.md` directly.\nThose three are loaded by whichever of the two mode files needs them, at the\npoint in their own protocol that needs them — not from here.\n\n## Entering build mode\n\nBefore build mode can plan anything, it needs to know what it's planning\nfor. The first thing it does — Stage 1, Detect — is identify the stack from\nmanifests and config rather than assumption (`package.json`,\n`pyproject.toml`, `go.mod`, `Cargo.toml`, `Gemfile`, and so on: examples, not\na closed table), then determine how tests are invoked and what test files\nalready exist. The skill must never hardcode a language; where it needs a\nper-ecosystem fact, it looks for the signal in the repo instead of consulting\na built-in list.\n\nThe full five-stage protocol — Detect, Grade, Plan, Critique, Write — lives\nin `references\u002Fbuild-test-roadmap.md`. Load it now if\n`paad\u002Ftest-roadmap\u002Ftest-roadmap.md` is absent.\n\n## Entering execute mode\n\nLoad `references\u002Fexecute-test-roadmap.md` now if `paad\u002Ftest-roadmap\u002Ftest-roadmap.md`\nexists. It reads that file's `## Decisions` section once, selects the next\nphase per the completion protocol, and gets on with writing tests — it does\nnot re-detect or re-ask anything build mode already settled.\n",{"name":5,"description":24,"compatibility":25},"EXPERIMENTAL. Analyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.\n","Requires git","main","2147d79c9cd764770418b462c29634bcdc710096","plugins\u002Fbase\u002Fskills\u002Ftest-roadmap","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-09-29 21:26:05",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add heynemann\u002Fomp-marketplace --skill test-roadmap",{"tool":40,"command":41},"bunx","bunx skills add heynemann\u002Fomp-marketplace --skill test-roadmap",{"tool":43,"command":44},"pnpm","pnpm dlx skills add heynemann\u002Fomp-marketplace --skill test-roadmap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002FSKILL.md",true,[48,54,58,62,66],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fbreak-it-check.md","REFERENCE","参考文档",17374,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Fbreak-it-check.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fbuild-test-roadmap.md",26326,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Fbuild-test-roadmap.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fexecute-test-roadmap.md",28769,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Fexecute-test-roadmap.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Ftest-pushback.md",12373,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Ftest-pushback.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ftest-theater.md",10395,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Ftest-theater.md",[71,78,85,92,99,106],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7DFXDYP0N6P8KR0AF7C0TDK","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7DFX9C5B0T1T0AVDCWNR5P2","write-skill","Use when creating, designing, or fixing an agent skill (SKILL.md pack) — triggers include \"write a skill\", \"make me a skill\", \"create a skill\", skill directories, and skills that fail to trigger or fire on the wrong tasks.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwrite-skill\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DFX64VSTQV0CSGYR76MPZF","write-agent","Use when creating, designing, or fixing an omp subagent (task agent) — triggers include \"write an agent\", \"make me an agent\", \"create a subagent\", agent `.md` definitions, and agents that misbehave when spawned via task.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwrite-agent\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DFX22JEY7ZN9EDESM732K5","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DFWYXR5V2CY2BPDAAS19R1","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7DFWXFFMBKV294WS66S475V","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fomp-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fbase\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[]]