[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BTE2PQJN7HTX52WTPQGZ24":3,"skill-same:01M7BTE2PQJN7HTX52WTPQGZ24":56},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7BTE2PQJN7HTX52WTPQGZ24","which-skill",null,"Ask which skill or flow fits your situation. A router over the skills in this repo.","rodolfochicone\u002Fskills","rodolfochicone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12111481?v=4","01M7BTCM1TKSMKXWZKVK8XP06H","Rodolfo Chicone","01M7BTCM2C047E93J84NCKTP1T",0,"MIT","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwhich-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: which-skill\ndescription: Ask which skill or flow fits your situation. A router over the skills in this repo.\ndisable-model-invocation: true\n---\n\n# Which Skill\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-docs`** — sharpen the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No working directory? Use `\u002Fgrill-me` — see Standalone. Both run the same `\u002Fgrill` primitive; `grill-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandover`** in both directions (a prototype lives in its own directory, which is exactly what `\u002Fhandover` is for — see Phase boundaries):\n   - **`\u002Fhandover`** out, then open a fresh session against that file,\n   - **`\u002Fspike`** to answer the question with throwaway code,\n   - **`\u002Fhandover`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fwrite-spec`** (turn the thread into a spec), then **`\u002Fsplit-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`\u002Fbuild-it`** per ticket, **`\u002Fclear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.\n   - **No** → **`\u002Fbuild-it`** right here, in the same context window.\n\n   Either way, **`\u002Fbuild-it`** builds each issue by driving **`\u002Ftest-first`** internally — one red-green slice at a time — then closes out by running **`\u002Freview-diff`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`\u002Ftest-first`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Freview-diff`** on its own whenever you want to review a branch or PR against a fixed point.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fsplit-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fbuild-it` then starts fresh, working from the ticket.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fsplit-tickets`, don't push on degraded — `\u002Fcompact` at the nearest phase boundary and carry on (see Phase boundaries).\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Fintake`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fbuild-it`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fsplit-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fbug-hunt`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`\u002Fimprove-architecture`** when the real finding is that there's no good seam to lock the bug down.\n\n- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`\u002Froadmap`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Where **`\u002Fgrill-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't — and it's slower and denser, so save it for exactly that, never a well-scoped feature.\n\n  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`\u002Fwrite-spec`**, which collapses the map's linked decisions into a buildable plan, then `\u002Fsplit-tickets` and `\u002Fbuild-it` as usual. Looping the map straight into `\u002Fbuild-it` skips that collapse and throws the linked detail away — go straight to `\u002Fbuild-it` only when the effort turned out genuinely small.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-docs`. It's the survey that finds the candidates; **`\u002Fmodule-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-model`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-docs` drives to keep `CONTEXT.md` a clean glossary.\n- **`\u002Fmodule-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftest-first` and `\u002Fimprove-architecture` both speak it.\n\n## Phase boundaries\n\nA **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:\n\n- **Continue** — stay put. Costs nothing, loses nothing.\n- **`\u002Fclear`** — empty the window, when nothing here matters to what's next.\n- **`\u002Fhandover`** — write a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.\n- **Subagent** — send a tightly-scoped task to its own window and get a report back.\n- **`\u002Fcompact`** — compress this context and seed a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.\n\nRead [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree — the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrill-me`** — the same relentless interview as `\u002Fgrill-docs`, but **stateless**: it saves nothing locally and builds no `CONTEXT.md`. Reach for it when you are **not working in a working directory** — sharpening a plan, a design, a piece of writing, anything with no repo under it. If you are in a working directory, use `\u002Fgrill-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.\n- **`\u002Fgrill`** — the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `\u002Fgrill-me` and `\u002Fgrill-docs` are the two named ways in, and `\u002Fintake`, `\u002Froadmap` and `\u002Fimprove-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.\n- **`\u002Ffix-merge`** — work an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finish the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.\n- **`\u002Fspike`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype\u002F\u003Cname>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fdeep-research`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-docs` — research feeds the thinking, it doesn't replace it.\n- **`\u002Fquestionnaire`** — when the thing blocking you isn't in your head or the codebase but in **someone else's**, this writes them a questionnaire to fill in. It's the inverse of `\u002Fgrill-me`: instead of interviewing you about the subject, it interviews you about the **send** — who it's going to, what you need back — and aims the questions at the gap. What comes back is material for `\u002Fgrill-docs` or `\u002Fwrite-spec`.\n- **`\u002Fmake-wizard`** — for the steps only a **human** can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into `.env` and GitHub secrets — so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop.\n- **`\u002Fwait-what`** — the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `CONTEXT.md` vocabulary. It works after the fact; `\u002Fgrill-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.\n- **`\u002Ftutor`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fagent-docs`** — reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.\n\n## Precondition\n\n**`\u002Fsetup-repo`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n","# Which Skill\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-docs`** — sharpen the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `CONTEXT.md` and ADRs. (No working directory? Use `\u002Fgrill-me` — see Standalone. Both run the same `\u002Fgrill` primitive; `grill-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)\n2. **Branch — can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandover`** in both directions (a prototype lives in its own directory, which is exactly what `\u002Fhandover` is for — see Phase boundaries):\n   - **`\u002Fhandover`** out, then open a fresh session against that file,\n   - **`\u002Fspike`** to answer the question with throwaway code,\n   - **`\u002Fhandover`** back what you learned, and reference it from the original idea thread.\n3. **Branch — is this a multi-session build?**\n   - **Yes** → **`\u002Fwrite-spec`** (turn the thread into a spec), then **`\u002Fsplit-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off **`\u002Fbuild-it`** per ticket, **`\u002Fclear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.\n   - **No** → **`\u002Fbuild-it`** right here, in the same context window.\n\n   Either way, **`\u002Fbuild-it`** builds each issue by driving **`\u002Ftest-first`** internally — one red-green slice at a time — then closes out by running **`\u002Freview-diff`**, a two-axis review (Standards + Spec) of the diff, before committing. Reach for **`\u002Ftest-first`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Freview-diff`** on its own whenever you want to review a branch or PR against a fixed point.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** — don't compact or clear until after `\u002Fsplit-tickets` — so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fbuild-it` then starts fresh, working from the ticket.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fsplit-tickets`, don't push on degraded — `\u002Fcompact` at the nearest phase boundary and carry on (see Phase boundaries).\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Fintake`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fbuild-it`** later picks up.\n\n  Triage is only for issues **you didn't create** — bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fsplit-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fbug-hunt`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** — one command that already goes red on *this* bug — then fixes with a regression test. Its post-mortem hands off to **`\u002Fimprove-architecture`** when the real finding is that there's no good seam to lock the bug down.\n\n- **A huge, foggy effort — a greenfield project or a huge feature build, too big for one session** → **`\u002Froadmap`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time — producing **decisions, not deliverables** — until the fog is pushed back and the way is clear. Where **`\u002Fgrill-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't — and it's slower and denser, so save it for exactly that, never a well-scoped feature.\n\n  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`\u002Fwrite-spec`**, which collapses the map's linked decisions into a buildable plan, then `\u002Fsplit-tickets` and `\u002Fbuild-it` as usual. Looping the map straight into `\u002Fbuild-it` skips that collapse and throws the linked detail away — go straight to `\u002Fbuild-it` only when the effort turned out genuinely small.\n\n## Codebase health\n\nNot feature work — upkeep.\n\n- **`\u002Fimprove-architecture`** — run whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-docs`. It's the survey that finds the candidates; **`\u002Fmodule-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills — each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-model`** — sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-docs` drives to keep `CONTEXT.md` a clean glossary.\n- **`\u002Fmodule-design`** — the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftest-first` and `\u002Fimprove-architecture` both speak it.\n\n## Phase boundaries\n\nA **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:\n\n- **Continue** — stay put. Costs nothing, loses nothing.\n- **`\u002Fclear`** — empty the window, when nothing here matters to what's next.\n- **`\u002Fhandover`** — write a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.\n- **Subagent** — send a tightly-scoped task to its own window and get a report back.\n- **`\u002Fcompact`** — compress this context and seed a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.\n\nRead [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree — the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrill-me`** — the same relentless interview as `\u002Fgrill-docs`, but **stateless**: it saves nothing locally and builds no `CONTEXT.md`. Reach for it when you are **not working in a working directory** — sharpening a plan, a design, a piece of writing, anything with no repo under it. If you are in a working directory, use `\u002Fgrill-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.\n- **`\u002Fgrill`** — the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `\u002Fgrill-me` and `\u002Fgrill-docs` are the two named ways in, and `\u002Fintake`, `\u002Froadmap` and `\u002Fimprove-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.\n- **`\u002Ffix-merge`** — work an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finish the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.\n- **`\u002Fspike`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype\u002F\u003Cname>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fdeep-research`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-docs` — research feeds the thinking, it doesn't replace it.\n- **`\u002Fquestionnaire`** — when the thing blocking you isn't in your head or the codebase but in **someone else's**, this writes them a questionnaire to fill in. It's the inverse of `\u002Fgrill-me`: instead of interviewing you about the subject, it interviews you about the **send** — who it's going to, what you need back — and aims the questions at the gap. What comes back is material for `\u002Fgrill-docs` or `\u002Fwrite-spec`.\n- **`\u002Fmake-wizard`** — for the steps only a **human** can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into `.env` and GitHub secrets — so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop.\n- **`\u002Fwait-what`** — the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `CONTEXT.md` vocabulary. It works after the fact; `\u002Fgrill-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.\n- **`\u002Ftutor`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fagent-docs`** — reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.\n\n## Precondition\n\n**`\u002Fsetup-repo`** — run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","8be5fe21ddbaa32ab309942d81eecd22a1ca5d4d","skills\u002Fengineering\u002Fwhich-skill","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills","https:\u002F\u002Fgithub.com\u002Frodolfochicone","https:\u002F\u002Frodolfochicone.dev","I build local-first tools for AI agents and developers. Creator of RC an agent plugin that takes ideas to shipped code inside Claude Code, Codex, Grok etc...","2026-08-30 21:36:39",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add rodolfochicone\u002Fskills --skill which-skill",{"tool":39,"command":40},"bunx","bunx skills add rodolfochicone\u002Fskills --skill which-skill",{"tool":42,"command":43},"pnpm","pnpm dlx skills add rodolfochicone\u002Fskills --skill which-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwhich-skill\u002FSKILL.md",[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",140,"https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwhich-skill\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"PHASE-BOUNDARIES.md",4280,"https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwhich-skill\u002FPHASE-BOUNDARIES.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7BTEQ0KQ7YG0WTFGY45QJ4B","wait-what","Stop. That last message did not land — re-pitch it.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7BTEN7YY8Q6GAACHFPCXNFG","tutor","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Ftutor\u002FSKILL.md",[],[],{"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},"01M7BTEK7WHPJ9NGJKC3D1870Z","questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fquestionnaire\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},"01M7BTEHSNG14EFYRA434FZ3SY","handover","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fhandover\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},"01M7BTEFS1TZV0507GAVSWEBY5","grill","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrill\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},"01M7BTED8EVDRCA89P4C43WXN2","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Frodolfochicone\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrill-me\u002FSKILL.md",[],[]]