[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6MBY155X6HWCWF91VBY7X":3,"skill-same:01M7F6MBY155X6HWCWF91VBY7X":55},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7F6MBY155X6HWCWF91VBY7X","guildhall-review",null,"Use in a review stage to review one code head against its accepted spec and the inlined standards on two separate axes, and write a review outcome with rule-cited findings and dispositions of the previous round.","ndrwl\u002Fguildhall","ndrwl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6626220?v=4","01M7F6J064TCN62N90J027CSYB","Andrew Lee","01M7F6J06N59PMK748BS50MVJ4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-review\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: guildhall-review\ndescription: Use in a review stage to review one code head against its accepted spec and the inlined standards on two separate axes, and write a review outcome with rule-cited findings and dispositions of the previous round.\n---\n\nAdapted from `code-review` in mattpocock\u002Fskills (MIT, commit 5beb35b); see CREDITS.md.\n\n# Review\n\nA review stage judges one code head on two axes and writes one review outcome.\nNobody answers you during the stage: the inputs, the standards in the prompt and the repository are your whole brief.\nReview alone and start no sub-agents, because a workflow that wants several reviewers runs this skill in several attempts.\n\n## What you review\n\n- The head is the commit the `head` input names, and the outcome binds to it.\n- The base is the exact commit in the prompt's `Review base` field, taken from the attempt's recorded range; never substitute the current default branch.\n- If `Review base` is `unavailable`, the attempt has no recorded range: report the missing base as a blocker rather than guessing the range.\n- Read the change once with `git diff \u003Cbase>...\u003Chead>` and `git log --oneline \u003Cbase>..\u003Chead>`, and review only what it changes.\n- With a `resolution` input the round re-reviews a rebase: review that resolution diff, and carry earlier findings by the round rules below.\n- The spec is the `spec` input under `inputs\u002F`, at the digest the prompt lists; it is never missing and you never look for another.\n- The standards are the ones inlined in the prompt; for the Guildhall repository they are rules S1 to S11 of `docs\u002Freview.md` and the requirements in `docs\u002Frequirements.md`.\n- An empty diff is not a question: write `rejected` with one finding, citing S1, that says the range changes nothing.\n\n## Two axes\n\nThe axes are reviewed and reported separately, because a change can pass one and fail the other.\nNever merge them or rerank across them: give each finding an id starting `spec-` or `std-`, and suggestions an id starting `smell-`.\n\n**Spec.**\nReport what the spec asked for that is missing or partial, what looks implemented but is wrong, and behaviour it did not ask for.\nScope creep is a finding (S1).\nQuote the spec line each finding rests on in its summary.\n\n**Standards.**\nReport every place the diff breaks an inlined standard, and cite the rule id, such as `S4` or `R1.27`.\nSkip anything tooling enforces, such as formatting, vet and lint that CI runs.\nWhen the repository keeps decision records, check that each new decision in the diff has a record that meets the repository's bar for one and uses its template, and that every record it supersedes or amends is marked in the same change.\nThen match the diff against the smell baseline in `smells.md`.\nA smell is always a labelled judgement call (\"possible Feature Envy\") and a suggestion, never a blocker: a smell never makes the verdict `changes_requested`.\nA written standard overrides the baseline: where one endorses the pattern, drop the smell, and where one forbids it, as S6 and S11 forbid speculative abstractions, report a finding citing that rule instead.\n\n## Findings and suggestions\n\nThe outcome keeps blockers and suggestions in two lists.\n\n`findings` are the blockers.\nEach names its `id`, `rule`, `file` and `line`, and its summary states a concrete failure: the input or state and the wrong result.\nA finding must cite a rule; intake refuses one that does not.\n\n`suggestions` are everything with no rule behind it, and every `smell-` item.\nEach names its `id` and `summary`, and may give `file` and `line`.\nA suggestion never blocks, never holds the merge and needs no disposition in a later round.\nThe verdict, not the lists, routes the task: `changes_requested` always sends the build back, so suggestions alone go in an `approved` outcome.\n\nAn id is lowercase letters, digits and hyphens, names one problem, is used once across both lists, and keeps that name in every later round.\n\n## Summary\n\nGive the outcome a `summary`: one paragraph, with no blank line, saying your overall verdict and why.\nName the worst finding on each axis, if there is one, and say whether only suggestions remain.\n\n## Rounds\n\nWhen the inputs include `previous`, disposition every finding of that outcome before you write new ones, so the Director can see a stall.\nDisposition only previous *findings*; never disposition a suggestion.\n\n- `resolved`: this head fixes it, or you no longer hold it; never list its id again, in either `findings` or `suggestions`.\n  Downgrading a finding to a suggestion under the same id also lists it again: if the point should live on as a suggestion, give it a new id.\n- `unresolved`: it stands; list it again under the same id.\n- `disputed`: the builder argued against it without fixing it, and you find the argument plausible but still hold the finding; list it again under the same id, and give the disposition a `reason` saying what the builder argued and why the rule still applies.\n\nA disputed finding stays open.\nWith `changes_requested` the loop goes on; with `approved` it holds the merge until the Director rules on it.\n\nWith a `rulings` input, keeping a ruled finding open, `unresolved` or `disputed`, contests the Director's ruling and stops the loop for the Guildmaster, so do that only when the cited rule still plainly applies, and say why.\n\n## Verdict and result\n\n- `approved`: no finding stands that you hold as a blocker; suggestions, smells included, may remain.\n- `changes_requested`: at least one finding stands; it always sends the build back, so never use it for suggestions alone.\n- `rejected`: the change should not go on in this form, such as an empty range or work that contradicts the spec throughout; at least one finding says why.\n\nBind the outcome to the head, the spec input's digest and the standards revision the prompt gives, with reviewer `automated`.\nWrite it as `review-outcome.json`, schema `guildhall.review-outcome\u002F2`, and list it as the first output of your result file.\n\nBefore you write the result file, check the outcome as intake will:\n\n```text\nguildhall review check review-outcome.json\n```\n\nWhen there is a `previous` input, add `--previous \u003Cthe previous input's path>`, so the check also finds a previous finding with no disposition.\nFix every error it reports, and run it again until it prints `ok`.\nOnly then write the result to the draft file and submit it, as the prompt's Result template says:\n\n```text\nguildhall result submit \u003Cdraft file>\n```\n\nIt checks the whole result as intake will, the outcome's binding to this attempt included, and prints `ok` or `rejected: \u003Creason>`.\nOn `rejected`, fix what the reason names and submit again until it prints `ok`, so the review round is not lost.\nIf either command cannot be run, because permission is denied or it is not found, say so in the result summary; never skip the self-check silently.\n\nThe result's summary is one line: the findings on each axis and the worst one within each axis, never one winner across both.\n\n```json\n{\n  \"schema\": \"guildhall.review-outcome\u002F2\",\n  \"reviewer\": \"automated\",\n  \"verdict\": \"changes_requested\",\n  \"summary\": \"The --json output is still a table for two tasks (spec-json-output), and the new test has no red run (std-no-red-run), which the builder disputes; the poll race is fixed and one smell is suggested.\",\n  \"findings\": [\n    {\"id\": \"spec-json-output\", \"rule\": \"S1\", \"file\": \"internal\u002Fcli\u002Fstatus.go\", \"line\": 42,\n     \"summary\": \"Spec: \\\"status --json prints one object per task\\\"; with two tasks the head prints a table, so a script decoding the output fails.\"},\n    {\"id\": \"std-no-red-run\", \"rule\": \"S2\", \"file\": \"internal\u002Fcli\u002Fstatus_test.go\", \"line\": 18,\n     \"summary\": \"The --json test was added with the code and the description shows no red run, so nothing shows it failed before the change.\"}\n  ],\n  \"suggestions\": [\n    {\"id\": \"smell-data-clump\", \"file\": \"internal\u002Fcli\u002Fstatus.go\", \"line\": 60,\n     \"summary\": \"Possible Data Clumps: repository, task and step travel together through four functions; one small type would carry them.\"}\n  ],\n  \"dispositions\": [\n    {\"finding\": \"spec-json-output\", \"state\": \"unresolved\"},\n    {\"finding\": \"std-no-red-run\", \"state\": \"disputed\",\n     \"reason\": \"The builder says the test is obviously new; S2 still asks for the red run to be shown.\"},\n    {\"finding\": \"std-poll-race\", \"state\": \"resolved\"}\n  ],\n  \"revisions\": {\n    \"subject\": {\"code_head\": \"0123456789abcdef0123456789abcdef01234567\"},\n    \"spec_digest\": \"sha256:242df7188ef036fb7f2376eda94382b23f989a04a61db84ae59acba315fc21be\",\n    \"standards_revision\": \"standards-1\"\n  }\n}\n```\n\nThe wrong way: a reviewer dispositions `suggest-4`, a suggestion of the previous outcome, as resolved and lists it again in `suggestions`.\n\n```text\n\"suggestions\": [\n  {\"id\": \"suggest-4\", \"summary\": \"A shorter name would read better.\"}\n],\n\"dispositions\": [\n  {\"finding\": \"suggest-4\", \"state\": \"resolved\"}\n]\n```\n\nIntake refuses the outcome, and the whole review round is lost:\n\n```text\nresolved finding \"suggest-4\" is still listed in findings or suggestions\n```\n\nTo fix it, drop the disposition, since a suggestion is never dispositioned, and either keep the suggestion or remove it.\n","Adapted from `code-review` in mattpocock\u002Fskills (MIT, commit 5beb35b); see CREDITS.md.\n\n# Review\n\nA review stage judges one code head on two axes and writes one review outcome.\nNobody answers you during the stage: the inputs, the standards in the prompt and the repository are your whole brief.\nReview alone and start no sub-agents, because a workflow that wants several reviewers runs this skill in several attempts.\n\n## What you review\n\n- The head is the commit the `head` input names, and the outcome binds to it.\n- The base is the exact commit in the prompt's `Review base` field, taken from the attempt's recorded range; never substitute the current default branch.\n- If `Review base` is `unavailable`, the attempt has no recorded range: report the missing base as a blocker rather than guessing the range.\n- Read the change once with `git diff \u003Cbase>...\u003Chead>` and `git log --oneline \u003Cbase>..\u003Chead>`, and review only what it changes.\n- With a `resolution` input the round re-reviews a rebase: review that resolution diff, and carry earlier findings by the round rules below.\n- The spec is the `spec` input under `inputs\u002F`, at the digest the prompt lists; it is never missing and you never look for another.\n- The standards are the ones inlined in the prompt; for the Guildhall repository they are rules S1 to S11 of `docs\u002Freview.md` and the requirements in `docs\u002Frequirements.md`.\n- An empty diff is not a question: write `rejected` with one finding, citing S1, that says the range changes nothing.\n\n## Two axes\n\nThe axes are reviewed and reported separately, because a change can pass one and fail the other.\nNever merge them or rerank across them: give each finding an id starting `spec-` or `std-`, and suggestions an id starting `smell-`.\n\n**Spec.**\nReport what the spec asked for that is missing or partial, what looks implemented but is wrong, and behaviour it did not ask for.\nScope creep is a finding (S1).\nQuote the spec line each finding rests on in its summary.\n\n**Standards.**\nReport every place the diff breaks an inlined standard, and cite the rule id, such as `S4` or `R1.27`.\nSkip anything tooling enforces, such as formatting, vet and lint that CI runs.\nWhen the repository keeps decision records, check that each new decision in the diff has a record that meets the repository's bar for one and uses its template, and that every record it supersedes or amends is marked in the same change.\nThen match the diff against the smell baseline in `smells.md`.\nA smell is always a labelled judgement call (\"possible Feature Envy\") and a suggestion, never a blocker: a smell never makes the verdict `changes_requested`.\nA written standard overrides the baseline: where one endorses the pattern, drop the smell, and where one forbids it, as S6 and S11 forbid speculative abstractions, report a finding citing that rule instead.\n\n## Findings and suggestions\n\nThe outcome keeps blockers and suggestions in two lists.\n\n`findings` are the blockers.\nEach names its `id`, `rule`, `file` and `line`, and its summary states a concrete failure: the input or state and the wrong result.\nA finding must cite a rule; intake refuses one that does not.\n\n`suggestions` are everything with no rule behind it, and every `smell-` item.\nEach names its `id` and `summary`, and may give `file` and `line`.\nA suggestion never blocks, never holds the merge and needs no disposition in a later round.\nThe verdict, not the lists, routes the task: `changes_requested` always sends the build back, so suggestions alone go in an `approved` outcome.\n\nAn id is lowercase letters, digits and hyphens, names one problem, is used once across both lists, and keeps that name in every later round.\n\n## Summary\n\nGive the outcome a `summary`: one paragraph, with no blank line, saying your overall verdict and why.\nName the worst finding on each axis, if there is one, and say whether only suggestions remain.\n\n## Rounds\n\nWhen the inputs include `previous`, disposition every finding of that outcome before you write new ones, so the Director can see a stall.\nDisposition only previous *findings*; never disposition a suggestion.\n\n- `resolved`: this head fixes it, or you no longer hold it; never list its id again, in either `findings` or `suggestions`.\n  Downgrading a finding to a suggestion under the same id also lists it again: if the point should live on as a suggestion, give it a new id.\n- `unresolved`: it stands; list it again under the same id.\n- `disputed`: the builder argued against it without fixing it, and you find the argument plausible but still hold the finding; list it again under the same id, and give the disposition a `reason` saying what the builder argued and why the rule still applies.\n\nA disputed finding stays open.\nWith `changes_requested` the loop goes on; with `approved` it holds the merge until the Director rules on it.\n\nWith a `rulings` input, keeping a ruled finding open, `unresolved` or `disputed`, contests the Director's ruling and stops the loop for the Guildmaster, so do that only when the cited rule still plainly applies, and say why.\n\n## Verdict and result\n\n- `approved`: no finding stands that you hold as a blocker; suggestions, smells included, may remain.\n- `changes_requested`: at least one finding stands; it always sends the build back, so never use it for suggestions alone.\n- `rejected`: the change should not go on in this form, such as an empty range or work that contradicts the spec throughout; at least one finding says why.\n\nBind the outcome to the head, the spec input's digest and the standards revision the prompt gives, with reviewer `automated`.\nWrite it as `review-outcome.json`, schema `guildhall.review-outcome\u002F2`, and list it as the first output of your result file.\n\nBefore you write the result file, check the outcome as intake will:\n\n```text\nguildhall review check review-outcome.json\n```\n\nWhen there is a `previous` input, add `--previous \u003Cthe previous input's path>`, so the check also finds a previous finding with no disposition.\nFix every error it reports, and run it again until it prints `ok`.\nOnly then write the result to the draft file and submit it, as the prompt's Result template says:\n\n```text\nguildhall result submit \u003Cdraft file>\n```\n\nIt checks the whole result as intake will, the outcome's binding to this attempt included, and prints `ok` or `rejected: \u003Creason>`.\nOn `rejected`, fix what the reason names and submit again until it prints `ok`, so the review round is not lost.\nIf either command cannot be run, because permission is denied or it is not found, say so in the result summary; never skip the self-check silently.\n\nThe result's summary is one line: the findings on each axis and the worst one within each axis, never one winner across both.\n\n```json\n{\n  \"schema\": \"guildhall.review-outcome\u002F2\",\n  \"reviewer\": \"automated\",\n  \"verdict\": \"changes_requested\",\n  \"summary\": \"The --json output is still a table for two tasks (spec-json-output), and the new test has no red run (std-no-red-run), which the builder disputes; the poll race is fixed and one smell is suggested.\",\n  \"findings\": [\n    {\"id\": \"spec-json-output\", \"rule\": \"S1\", \"file\": \"internal\u002Fcli\u002Fstatus.go\", \"line\": 42,\n     \"summary\": \"Spec: \\\"status --json prints one object per task\\\"; with two tasks the head prints a table, so a script decoding the output fails.\"},\n    {\"id\": \"std-no-red-run\", \"rule\": \"S2\", \"file\": \"internal\u002Fcli\u002Fstatus_test.go\", \"line\": 18,\n     \"summary\": \"The --json test was added with the code and the description shows no red run, so nothing shows it failed before the change.\"}\n  ],\n  \"suggestions\": [\n    {\"id\": \"smell-data-clump\", \"file\": \"internal\u002Fcli\u002Fstatus.go\", \"line\": 60,\n     \"summary\": \"Possible Data Clumps: repository, task and step travel together through four functions; one small type would carry them.\"}\n  ],\n  \"dispositions\": [\n    {\"finding\": \"spec-json-output\", \"state\": \"unresolved\"},\n    {\"finding\": \"std-no-red-run\", \"state\": \"disputed\",\n     \"reason\": \"The builder says the test is obviously new; S2 still asks for the red run to be shown.\"},\n    {\"finding\": \"std-poll-race\", \"state\": \"resolved\"}\n  ],\n  \"revisions\": {\n    \"subject\": {\"code_head\": \"0123456789abcdef0123456789abcdef01234567\"},\n    \"spec_digest\": \"sha256:242df7188ef036fb7f2376eda94382b23f989a04a61db84ae59acba315fc21be\",\n    \"standards_revision\": \"standards-1\"\n  }\n}\n```\n\nThe wrong way: a reviewer dispositions `suggest-4`, a suggestion of the previous outcome, as resolved and lists it again in `suggestions`.\n\n```text\n\"suggestions\": [\n  {\"id\": \"suggest-4\", \"summary\": \"A shorter name would read better.\"}\n],\n\"dispositions\": [\n  {\"finding\": \"suggest-4\", \"state\": \"resolved\"}\n]\n```\n\nIntake refuses the outcome, and the whole review round is lost:\n\n```text\nresolved finding \"suggest-4\" is still listed in findings or suggestions\n```\n\nTo fix it, drop the disposition, since a suggestion is never dispositioned, and either keep the suggestion or remove it.\n",{"name":5,"description":7},"main","1e9f9a9f87ad9e114c05b6a88e99c9d150cee27c","skills\u002Fguildhall-review",0,"https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall","https:\u002F\u002Fgithub.com\u002Fndrwl","2026-11-14 03:29:50",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ndrwl\u002Fguildhall --skill guildhall-review",{"tool":37,"command":38},"bunx","bunx skills add ndrwl\u002Fguildhall --skill guildhall-review",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ndrwl\u002Fguildhall --skill guildhall-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-review\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"CREDITS.md","REFERENCE","参考文档",2290,"https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-review\u002FCREDITS.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"smells.md",2056,"https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-review\u002Fsmells.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7F6P3WD0T7JAMW5HREGA285","guildhall-steward-triage","Use as the Steward to collect Directors' lessons and incidents into the private config and present each triage decision to the Guildmaster, when they ask, a triage-opened message arrives or startup lists an open triage decision.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-steward-triage\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7F6P0E68S43TD4Z9C734PX0","guildhall-steward-startup","Use as the Steward when a Steward session starts and its first message names startup.md, to read your notes, work every in-flight rollout approval, then run guildhall steward ready.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-steward-startup\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7F6NV7NGV4MBBTSG0HKQ9RG","guildhall-steward-setup","Use as the Steward when the Guildmaster asks to take over an existing Director copy or provision a new one, to dry-run the plan, get approval of its exact digest, apply it, resume it after a failure or wizard step, or abandon a takeover.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-steward-setup\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F6NQ0KCE1GN1TD0K4GG865","guildhall-steward-rollout","Use as the Steward when the Guildmaster asks to roll out shared settings, check the roster or see what a copy last received, to dry-run, get approval of the exact plan digest and apply it.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-steward-rollout\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F6NF88643YK184BFMWJRZ6","guildhall-steward-handoff","Use as the Steward when a wake line says handoff due, your context fills, or the Guildmaster asks you to hand off, to keep your notes current and then run guildhall steward handoff.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-steward-handoff\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F6N3KN1NZ37CK4PMRJW5E5","guildhall-spec","Use in a plan stage to write the spec the Guildmaster accepts, including problem, solution, contracts, contract tests, acceptance criteria, out of scope and size.","https:\u002F\u002Fgithub.com\u002Fndrwl\u002Fguildhall\u002Fblob\u002Fmain\u002Fskills\u002Fguildhall-spec\u002FSKILL.md",[],[]]