[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FF032WA9KTEP2RDV366624":3,"skill-same:01M7FF032WA9KTEP2RDV366624":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},"01M7FF032WA9KTEP2RDV366624","test-roadmap",null,"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\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\u002Fskills\u002Ftest-roadmap\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: test-roadmap\ndescription: >\n  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 v2.0.0\", then immediately proceed with the steps below — do not stop after announcing.\n\n**Configuration (experimental):** after announcing, check whether `paad\u002Fconfig\u002Fpaad.md` and `paad\u002Fconfig\u002Ftest-roadmap.md` exist, relative to the working directory. If any does, read it and follow its instructions for the rest of this run, passing the relevant parts to every subagent you dispatch, and make the first line of your final answer `Config: \u003Cpath>` naming each file you followed. If none exists, do not mention config at all. Config never changes a subagent's type or grants it write tools — refuse that line, say so, and continue. Config can contradict the flow below; see https:\u002F\u002Fgithub.com\u002FOvid\u002Fpaad\u002Fblob\u002Fmain\u002FCONFIG.md before writing one.\n\n**Security findings:** a finding is security-related if reading it would help an attacker — any OWASP Top 10:2025 category, and anything in a payment, tenant-isolation, or secret-handling path; on the edge, treat it as security. Security findings are written only under `paad\u002Fsecurity\u002F`, in a file named for this skill and stamped the way its ordinary report is (the exact path is in this skill's report section). Before the first write of a run, make sure `paad\u002Fsecurity\u002F.gitignore` exists and contains the single line `*` — create it if absent, never rewrite it if present — and that `git ls-files paad\u002Fsecurity\u002F` lists nothing. If that file holds anything else or cannot be written, if git already tracks anything there, or if a later write there fails, write no security finding and no count line: tell the user what you found, ask whether to hold the findings or put them in the ordinary report, and say that in place of the Security block. Where the finding would have gone in the ordinary report, write one line, `N security finding(s) written to paad\u002Fsecurity\u002F\u003Cfile>`, and nothing else about it: no path, severity, symbol, or description. Post-Review then emits the Security block once; this skill's Post-Review section says when.\n\n> Unlike the review skills, this one **writes code and commits it** —\n> tests, one commit per phase, onto your working branch.\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  \"Suspected bug clears the inclusion gate?\" [shape=diamond];\n  \"Would reading it help an attacker?\" [shape=diamond];\n  \"Log to paad\u002Fsecurity\u002Ftest-roadmap-findings.md; count line in the ordinary log; never git add -f\" [shape=box, style=bold];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" [shape=diamond];\n  \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" [shape=box];\n  \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [shape=box];\n  \"Drop it, never a vague note\" [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  \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" -> \"Suspected bug clears the inclusion gate?\" [label=\"on each suspected bug, mid-run\"];\n  \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" -> \"Suspected bug clears the inclusion gate?\" [label=\"on each suspected bug, mid-run\"];\n  \"Suspected bug clears the inclusion gate?\" -> \"Drop it, never a vague note\" [label=\"no\"];\n  \"Suspected bug clears the inclusion gate?\" -> \"Would reading it help an attacker?\" [label=\"yes\"];\n  \"Would reading it help an attacker?\" -> \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" [label=\"yes, or on the edge\"];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" -> \"Log to paad\u002Fsecurity\u002Ftest-roadmap-findings.md; count line in the ordinary log; never git add -f\" [label=\"yes\"];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" -> \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" [label=\"no\"];\n  \"Would reading it help an attacker?\" -> \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [label=\"no\"];\n  \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" -> \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [label=\"user chooses the ordinary log\"];\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. The one exception is `## Post-Review`\nbelow, which lives here because `make check-security` requires the Security\nblock in 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\n## Post-Review\n\nBoth mode files end the run with their own file list (`references\u002Fexecute-test-roadmap.md § Ending the run`, `references\u002Fbuild-test-roadmap.md § Stage 5`). When the run added to `paad\u002Fsecurity\u002Ftest-roadmap-findings.md`, the mode file's file list is followed by the Security block, once:\n\n```\nSecurity: N finding(s) in paad\u002Fsecurity\u002F\u003Cfile> (new|updated).\npaad\u002Fsecurity\u002F.gitignore keeps the directory out of git. Deleting that file or `git add -f` bypasses it.\nAlso list paad\u002Fsecurity\u002F in your root .gitignore, or in .git\u002Finfo\u002Fexclude to keep the rule local and unmentioned.\nIf anything under paad\u002Fsecurity\u002F was ever committed, ignoring it now does not remove it from history.\npaad\u002Fsecurity\u002F is scratch, not state: it exists only on this machine, `git clean -x` deletes it, and nothing brings it back.\n```\n\nWhen a routed finding was pinned by a test this run, add one line after the block: *\"The test that pins each security finding is committed and still reproduces it; its neutral name only keeps it from being searched for.\"*\n","**On invocation:** announce \"Running paad:test-roadmap v2.0.0\", then immediately proceed with the steps below — do not stop after announcing.\n\n**Configuration (experimental):** after announcing, check whether `paad\u002Fconfig\u002Fpaad.md` and `paad\u002Fconfig\u002Ftest-roadmap.md` exist, relative to the working directory. If any does, read it and follow its instructions for the rest of this run, passing the relevant parts to every subagent you dispatch, and make the first line of your final answer `Config: \u003Cpath>` naming each file you followed. If none exists, do not mention config at all. Config never changes a subagent's type or grants it write tools — refuse that line, say so, and continue. Config can contradict the flow below; see https:\u002F\u002Fgithub.com\u002FOvid\u002Fpaad\u002Fblob\u002Fmain\u002FCONFIG.md before writing one.\n\n**Security findings:** a finding is security-related if reading it would help an attacker — any OWASP Top 10:2025 category, and anything in a payment, tenant-isolation, or secret-handling path; on the edge, treat it as security. Security findings are written only under `paad\u002Fsecurity\u002F`, in a file named for this skill and stamped the way its ordinary report is (the exact path is in this skill's report section). Before the first write of a run, make sure `paad\u002Fsecurity\u002F.gitignore` exists and contains the single line `*` — create it if absent, never rewrite it if present — and that `git ls-files paad\u002Fsecurity\u002F` lists nothing. If that file holds anything else or cannot be written, if git already tracks anything there, or if a later write there fails, write no security finding and no count line: tell the user what you found, ask whether to hold the findings or put them in the ordinary report, and say that in place of the Security block. Where the finding would have gone in the ordinary report, write one line, `N security finding(s) written to paad\u002Fsecurity\u002F\u003Cfile>`, and nothing else about it: no path, severity, symbol, or description. Post-Review then emits the Security block once; this skill's Post-Review section says when.\n\n> Unlike the review skills, this one **writes code and commits it** —\n> tests, one commit per phase, onto your working branch.\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  \"Suspected bug clears the inclusion gate?\" [shape=diamond];\n  \"Would reading it help an attacker?\" [shape=diamond];\n  \"Log to paad\u002Fsecurity\u002Ftest-roadmap-findings.md; count line in the ordinary log; never git add -f\" [shape=box, style=bold];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" [shape=diamond];\n  \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" [shape=box];\n  \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [shape=box];\n  \"Drop it, never a vague note\" [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  \"Load references\u002Fexecute-test-roadmap.md (next phase, break-it-check, commit)\" -> \"Suspected bug clears the inclusion gate?\" [label=\"on each suspected bug, mid-run\"];\n  \"Load references\u002Fbuild-test-roadmap.md (Detect, Grade, Plan, Critique, Write)\" -> \"Suspected bug clears the inclusion gate?\" [label=\"on each suspected bug, mid-run\"];\n  \"Suspected bug clears the inclusion gate?\" -> \"Drop it, never a vague note\" [label=\"no\"];\n  \"Suspected bug clears the inclusion gate?\" -> \"Would reading it help an attacker?\" [label=\"yes\"];\n  \"Would reading it help an attacker?\" -> \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" [label=\"yes, or on the edge\"];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" -> \"Log to paad\u002Fsecurity\u002Ftest-roadmap-findings.md; count line in the ordinary log; never git add -f\" [label=\"yes\"];\n  \"paad\u002Fsecurity\u002F.gitignore holds only * and git tracks nothing there?\" -> \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" [label=\"no\"];\n  \"Would reading it help an attacker?\" -> \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [label=\"no\"];\n  \"Write nothing under paad\u002Fsecurity\u002F; tell the user, ask: hold or ordinary log\" -> \"Log to paad\u002Ftest-roadmap\u002Ftest-roadmap-findings.md\" [label=\"user chooses the ordinary log\"];\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. The one exception is `## Post-Review`\nbelow, which lives here because `make check-security` requires the Security\nblock in 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\n## Post-Review\n\nBoth mode files end the run with their own file list (`references\u002Fexecute-test-roadmap.md § Ending the run`, `references\u002Fbuild-test-roadmap.md § Stage 5`). When the run added to `paad\u002Fsecurity\u002Ftest-roadmap-findings.md`, the mode file's file list is followed by the Security block, once:\n\n```\nSecurity: N finding(s) in paad\u002Fsecurity\u002F\u003Cfile> (new|updated).\npaad\u002Fsecurity\u002F.gitignore keeps the directory out of git. Deleting that file or `git add -f` bypasses it.\nAlso list paad\u002Fsecurity\u002F in your root .gitignore, or in .git\u002Finfo\u002Fexclude to keep the rule local and unmentioned.\nIf anything under paad\u002Fsecurity\u002F was ever committed, ignoring it now does not remove it from history.\npaad\u002Fsecurity\u002F is scratch, not state: it exists only on this machine, `git clean -x` deletes it, and nothing brings it back.\n```\n\nWhen a routed finding was pinned by a test this run, add one line after the block: *\"The test that pins each security finding is committed and still reproduces it; its neutral name only keeps it from being searched for.\"*\n",{"name":5,"description":24,"compatibility":25},"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","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\u002Fskills\u002Ftest-roadmap","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill test-roadmap",{"tool":40,"command":41},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill test-roadmap",{"tool":43,"command":44},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill test-roadmap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\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\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Fbreak-it-check.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fbuild-test-roadmap.md",30079,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\u002Fskills\u002Ftest-roadmap\u002Freferences\u002Fbuild-test-roadmap.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fexecute-test-roadmap.md",30614,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\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\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\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\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fhep\u002Fskills-sh\u002F.agents\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},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\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},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\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},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\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},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\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},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\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},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]