[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754MA3B8RCTG5Q818Q9XYFX":3,"skill-same:01M754MA3B8RCTG5Q818Q9XYFX":58},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M754MA3B8RCTG5Q818Q9XYFX","grill-with-docs",null,"Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.","nino-chavez\u002Fagentic-ways-of-working","nino-chavez","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12718755?v=4","01M754JW20GYYZXXN5MCEDN4ZF","Nino Chavez","01M754JW30HW4WBYC09HN1HCEX",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: grill-with-docs\ndescription: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.\n---\n\n\u003Cwhat-to-do>\n\nInterview me about the unresolved decisions in this plan until we reach a shared understanding. Map which decisions depend on others. For each question, provide your recommended answer and a short reason grounded in the project's code, terminology, or documented trade-offs.\n\nWork in short rounds:\n\n1. Resolve facts from the codebase and existing documents before asking the user. An unfinished lookup leaves its dependent decisions unready; other independent questions can still proceed.\n2. Ask ready, independent questions together in a numbered round. A question is ready when its prerequisites are settled and its wording, options, and recommendation do not depend on another open answer. Usually two or three concise questions fit; ask one when it is the only ready decision or needs focused discussion. Honor a request for one-at-a-time questions.\n3. Wait for feedback before asking dependent follow-ups. Apply each explicit answer, capture resolved terms as described below, and recompute which decisions are ready. With a partial reply, keep unanswered questions open; silence does not accept a recommendation. If the reply is ambiguous about which question it answers (for example, a bare “yes” after two different questions), clarify only that mapping instead of applying it to every recommendation. Clear answers need no numbered format; “yes to both” can settle both. Do not repeat settled questions unless new evidence changes their basis.\n4. Finish when the scoped decisions are resolved, or name the remaining dependency if progress requires missing evidence or a user decision. Batching questions does not authorize implementation or turn a proposed answer into an accepted ADR.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## Domain awareness\n\nDuring codebase exploration, also look for existing documentation:\n\n### File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Keep answers attached to the decision\n\nWhen several choices remain open, use the [review and decision capture\nreference](..\u002F..\u002Fdocs\u002Freview-decisions.md#present-only-the-decisions-that-are-ready).\nIt owns stable IDs, source versions, partial replies, and revalidation when the\nbasis changes. Use the host's question UI or the existing project review page;\nan answer sheet does not replace the project's approval mechanism. Keep resolved\nanswers in the existing plan or decision owner, rather than a second ledger.\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account' — do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nDon't couple `CONTEXT.md` to implementation details. Only include terms that are meaningful to domain experts.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n\u003C\u002Fsupporting-info>\n\nQuestion-round sequencing adapted from [Matt Pocock's grilling skill](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Fblob\u002F49dd158d1076134a641b33efb035946536778336\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md). Domain checks and inline documentation remain part of this skill.\n","\u003Cwhat-to-do>\n\nInterview me about the unresolved decisions in this plan until we reach a shared understanding. Map which decisions depend on others. For each question, provide your recommended answer and a short reason grounded in the project's code, terminology, or documented trade-offs.\n\nWork in short rounds:\n\n1. Resolve facts from the codebase and existing documents before asking the user. An unfinished lookup leaves its dependent decisions unready; other independent questions can still proceed.\n2. Ask ready, independent questions together in a numbered round. A question is ready when its prerequisites are settled and its wording, options, and recommendation do not depend on another open answer. Usually two or three concise questions fit; ask one when it is the only ready decision or needs focused discussion. Honor a request for one-at-a-time questions.\n3. Wait for feedback before asking dependent follow-ups. Apply each explicit answer, capture resolved terms as described below, and recompute which decisions are ready. With a partial reply, keep unanswered questions open; silence does not accept a recommendation. If the reply is ambiguous about which question it answers (for example, a bare “yes” after two different questions), clarify only that mapping instead of applying it to every recommendation. Clear answers need no numbered format; “yes to both” can settle both. Do not repeat settled questions unless new evidence changes their basis.\n4. Finish when the scoped decisions are resolved, or name the remaining dependency if progress requires missing evidence or a user decision. Batching questions does not authorize implementation or turn a proposed answer into an accepted ADR.\n\n\u003C\u002Fwhat-to-do>\n\n\u003Csupporting-info>\n\n## Domain awareness\n\nDuring codebase exploration, also look for existing documentation:\n\n### File structure\n\nMost repos have a single context:\n\n```\n\u002F\n├── CONTEXT.md\n├── docs\u002F\n│   └── adr\u002F\n│       ├── 0001-event-sourced-orders.md\n│       └── 0002-postgres-for-write-model.md\n└── src\u002F\n```\n\nIf a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:\n\n```\n\u002F\n├── CONTEXT-MAP.md\n├── docs\u002F\n│   └── adr\u002F                          ← system-wide decisions\n├── src\u002F\n│   ├── ordering\u002F\n│   │   ├── CONTEXT.md\n│   │   └── docs\u002Fadr\u002F                 ← context-specific decisions\n│   └── billing\u002F\n│       ├── CONTEXT.md\n│       └── docs\u002Fadr\u002F\n```\n\nCreate files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs\u002Fadr\u002F` exists, create it when the first ADR is needed.\n\n## During the session\n\n### Keep answers attached to the decision\n\nWhen several choices remain open, use the [review and decision capture\nreference](..\u002F..\u002Fdocs\u002Freview-decisions.md#present-only-the-decisions-that-are-ready).\nIt owns stable IDs, source versions, partial replies, and revalidation when the\nbasis changes. Use the host's question UI or the existing project review page;\nan answer sheet does not replace the project's approval mechanism. Keep resolved\nanswers in the existing plan or decision owner, rather than a second ledger.\n\n### Challenge against the glossary\n\nWhen the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. \"Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?\"\n\n### Sharpen fuzzy language\n\nWhen the user uses vague or overloaded terms, propose a precise canonical term. \"You're saying 'account' — do you mean the Customer or the User? Those are different things.\"\n\n### Discuss concrete scenarios\n\nWhen domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.\n\n### Cross-reference with code\n\nWhen the user states how something works, check whether the code agrees. If you find a contradiction, surface it: \"Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?\"\n\n### Update CONTEXT.md inline\n\nWhen a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](.\u002FCONTEXT-FORMAT.md).\n\nDon't couple `CONTEXT.md` to implementation details. Only include terms that are meaningful to domain experts.\n\n### Offer ADRs sparingly\n\nOnly offer to create an ADR when all three are true:\n\n1. **Hard to reverse** — the cost of changing your mind later is meaningful\n2. **Surprising without context** — a future reader will wonder \"why did they do it this way?\"\n3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons\n\nIf any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](.\u002FADR-FORMAT.md).\n\n\u003C\u002Fsupporting-info>\n\nQuestion-round sequencing adapted from [Matt Pocock's grilling skill](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Fblob\u002F49dd158d1076134a641b33efb035946536778336\u002Fskills\u002Fproductivity\u002Fgrilling\u002FSKILL.md). Domain checks and inline documentation remain part of this skill.\n",{"name":5,"description":7},"main","6ccdd47a6d908bb540b44198221fabf7a71f7bba","skills\u002Fgrill-with-docs",0,"https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working#readme","https:\u002F\u002Fgithub.com\u002Fnino-chavez","https:\u002F\u002Fninochavez.co","Enterprise Architect & AI Systems Designer | Action Sports Photographer. Building human-AI systems that scale.","2026-11-14 02:34:16",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add nino-chavez\u002Fagentic-ways-of-working --skill grill-with-docs",{"tool":40,"command":41},"bunx","bunx skills add nino-chavez\u002Fagentic-ways-of-working --skill grill-with-docs",{"tool":43,"command":44},"pnpm","pnpm dlx skills add nino-chavez\u002Fagentic-ways-of-working --skill grill-with-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"ADR-FORMAT.md","REFERENCE","参考文档",2766,"https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-with-docs\u002FADR-FORMAT.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"CONTEXT-FORMAT.md",3145,"https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fgrill-with-docs\u002FCONTEXT-FORMAT.md",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M754N3A73KPE25NE31Z2XP3M","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M754N16FXP38FVD365N0MFT4","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M754MXZNPAN5VY4VGQT37APS","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M754MT24EMZEFB3M6VKZ0KZ1","tdd","Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions \"red-green-refactor\", wants integration tests, or asks for test-first development.","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M754MMX5RP4494W44ZEN6YDX","symbol-surgery","Symbol-first refactoring discipline using the native LSP tool — locate by symbol, check blast radius before changing, edit at symbol boundaries, verify references after. Use when renaming, changing a signature, moving\u002Fextracting\u002Finlining, or deleting code that other code depends on; or whenever the question is \"where is this used and what breaks if I change it?\" Mechanical-execution complement to `deepen` (which decides what to refactor) and `simplify` (which decides what's clean).","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fsymbol-surgery\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M754MGZR49W94V1SW4GTG20G","ship","Deploy, release, or run migrations against production for a project. Use when user says \"deploy\", \"ship\", \"push to prod\", \"release\", \"run the migration\", \"apply migrations\", or asks how a project gets deployed \u002F where it lives. Reads per-project DEPLOY.md as source of truth; falls back to inference + offer to scaffold one.","https:\u002F\u002Fgithub.com\u002Fnino-chavez\u002Fagentic-ways-of-working\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[]]