[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDX97RMCKMRGS31PH3ZCFM":3,"skill-same:01M7CDX97RMCKMRGS31PH3ZCFM":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CDX97RMCKMRGS31PH3ZCFM","implement",null,"Use when agreed work is to be written into code.","dveyarangi\u002Fgoodwolf-harness","dveyarangi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F693404?v=4","01M77KAGWZ8X0CNA092ZDNEF6T","Fima Rotter","01M7CDVSGB58A879MVTYC1SVD0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implement\ndescription: Use when agreed work is to be written into code.\n---\n\n\u003Cstraw-dog question=\"q-jbv3d6\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\nImplement the work described by the relevant architecture decisions (the\nquestion, ticket, RFC, prior discussion).\n\nPick entity names in vibe with the project glossary.\nDo not use implementation-shaped names or parameters; orient them at the\nfunction's meaning toward the client.\n\nUse `\u002Ftdd` where possible, at pre-agreed seams. Make sure implementation, even\nin dummy\u002Fdegenerate form, fully follows contract surfaces in the docs.\n\nMake methods behind main architectural boundaries clear — they should read\nalmost as a story explaining the boundary logic, with separate concerns\nextracted to properly named sub-methods. Prefer to split submethods by\nresponsibility.\n\nThe code should read as a story. Make sure the main process appears first in\nthe file, where possible, and main boundaries' implementation reads through\nentities, interfaces and submethods used as nouns, adjectives and verbs.\n\nMark code an open question's answer will change with a comment line beginning\n`TODO` that names the question, per the entry file's straw-dog rule, and say so\nin the docstring.\n\n\u003Cstraw-dog question=\"q-jbv3d6\">\nWhere the code you write follows a rule that a load-bearing record of the project states — its\narchitecture or an ADR — name each such rule at the end of the comment phrase it backs, as\n`(\u003Cpath from the tree's root>: \"\u003Cthe rule's name>\")`, whole on one line — wrap the comment before\nit, never inside it — the name being the rule's heading or the bold lead of its paragraph, word for\nword. A rule with no such name gets one in its record first. Code no such rule governs carries no\npointer.\n\u003C\u002Fstraw-dog>\n\nMake sure the errors follow error rules.\n\nMake sure to read and follow `\u002Fimprove-comments` rules. Mark other pending\nactions — hotpaths that may need optimization, work with no named successor —\nas `TODO` too; without a ticket they are notes, and the listing script reports\nthem as guesses.\n\nDuring the work, run the checks in the project's verification set, as\n[`\u002Fverify`](..\u002Fverify\u002FSKILL.md#the-verification-set) defines it. `\u002Fverify` is the\nverification of landed work; a local run of a subset is not that pass.\n\nOnce done, and unless you need to take a break, use `\u002Fverify`.\n\nCommit once `\u002Fverify` has passed on the work. Mending during the work stands\non the rung of what it mends; it is not a substitute for `\u002Fverify`.\n\n## Installed from other mechanisms\n\n\u003Cinstalled by=\"session\">\n**S7** At the step's start, hold the unit by the question its work answers, `sessions.py --hold \u003Cq-id>\n--session \u003Ctag>`; a unit this session held is let go by it: say which, and that it is nobody's\nnow. A refusal naming another running session stops the step: say whose the unit is, and do\nnothing on it. A refusal saying the question is no unit leaves the step to go on, holding\nnothing.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L3** The verification set: the checks always; the tests too when the work changed a file that is not\nmarkdown, the question store's own writes aside.\n\n```\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fmechanisms.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Finject_rules.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Ftickets.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fedges.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fmaintain.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fquestions.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fsessions.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fproduct.py --check\n```\n\n```\nuv run --offline --no-project python -m unittest discover -s .agents\u002Fscripts\u002Fgw\u002Ftest -p \"test_*.py\"\n```\n\n**L10** What the harness ships names under `docs\u002F` only where a mechanism keeps a kind of record — the\ndirectory, or the one file that is a record — never a record inside one; a question only as a\nstraw dog's binding or a `TODO q-N`; a ticket never.\n\u003C\u002Finstalled>\n","\u003Cstraw-dog question=\"q-jbv3d6\">Mechanism: not yet\u003C\u002Fstraw-dog>\n\nImplement the work described by the relevant architecture decisions (the\nquestion, ticket, RFC, prior discussion).\n\nPick entity names in vibe with the project glossary.\nDo not use implementation-shaped names or parameters; orient them at the\nfunction's meaning toward the client.\n\nUse `\u002Ftdd` where possible, at pre-agreed seams. Make sure implementation, even\nin dummy\u002Fdegenerate form, fully follows contract surfaces in the docs.\n\nMake methods behind main architectural boundaries clear — they should read\nalmost as a story explaining the boundary logic, with separate concerns\nextracted to properly named sub-methods. Prefer to split submethods by\nresponsibility.\n\nThe code should read as a story. Make sure the main process appears first in\nthe file, where possible, and main boundaries' implementation reads through\nentities, interfaces and submethods used as nouns, adjectives and verbs.\n\nMark code an open question's answer will change with a comment line beginning\n`TODO` that names the question, per the entry file's straw-dog rule, and say so\nin the docstring.\n\n\u003Cstraw-dog question=\"q-jbv3d6\">\nWhere the code you write follows a rule that a load-bearing record of the project states — its\narchitecture or an ADR — name each such rule at the end of the comment phrase it backs, as\n`(\u003Cpath from the tree's root>: \"\u003Cthe rule's name>\")`, whole on one line — wrap the comment before\nit, never inside it — the name being the rule's heading or the bold lead of its paragraph, word for\nword. A rule with no such name gets one in its record first. Code no such rule governs carries no\npointer.\n\u003C\u002Fstraw-dog>\n\nMake sure the errors follow error rules.\n\nMake sure to read and follow `\u002Fimprove-comments` rules. Mark other pending\nactions — hotpaths that may need optimization, work with no named successor —\nas `TODO` too; without a ticket they are notes, and the listing script reports\nthem as guesses.\n\nDuring the work, run the checks in the project's verification set, as\n[`\u002Fverify`](..\u002Fverify\u002FSKILL.md#the-verification-set) defines it. `\u002Fverify` is the\nverification of landed work; a local run of a subset is not that pass.\n\nOnce done, and unless you need to take a break, use `\u002Fverify`.\n\nCommit once `\u002Fverify` has passed on the work. Mending during the work stands\non the rung of what it mends; it is not a substitute for `\u002Fverify`.\n\n## Installed from other mechanisms\n\n\u003Cinstalled by=\"session\">\n**S7** At the step's start, hold the unit by the question its work answers, `sessions.py --hold \u003Cq-id>\n--session \u003Ctag>`; a unit this session held is let go by it: say which, and that it is nobody's\nnow. A refusal naming another running session stops the step: say whose the unit is, and do\nnothing on it. A refusal saying the question is no unit leaves the step to go on, holding\nnothing.\n\u003C\u002Finstalled>\n\n\u003Cinstalled by=\"local\">\n**L3** The verification set: the checks always; the tests too when the work changed a file that is not\nmarkdown, the question store's own writes aside.\n\n```\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fmechanisms.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Finject_rules.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Ftickets.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fedges.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fmaintain.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fquestions.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fsessions.py --check\nuv run --offline --no-project python .agents\u002Fscripts\u002Fgw\u002Fproduct.py --check\n```\n\n```\nuv run --offline --no-project python -m unittest discover -s .agents\u002Fscripts\u002Fgw\u002Ftest -p \"test_*.py\"\n```\n\n**L10** What the harness ships names under `docs\u002F` only where a mechanism keeps a kind of record — the\ndirectory, or the one file that is a record — never a record inside one; a question only as a\nstraw dog's binding or a `TODO q-N`; a ticket never.\n\u003C\u002Finstalled>\n",{"name":5,"description":7},"main","a43633f7ef0eeeb220f42872be487150daec8575",".agents\u002Fskills\u002Fimplement","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness","https:\u002F\u002Fgithub.com\u002Fdveyarangi","http:\u002F\u002Fdveyarangi.blogspot.com\u002F","2026-11-14 12:09:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add dveyarangi\u002Fgoodwolf-harness --skill implement",{"tool":37,"command":38},"bunx","bunx skills add dveyarangi\u002Fgoodwolf-harness --skill implement",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dveyarangi\u002Fgoodwolf-harness --skill implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplement\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7CDYHDFRAZP8T121PGMZ46R","verify","Use after an implementation pass, or to verify a landed slice before close. Whole verification of landed work: ticket, RFC, governing docs, and the project's verification set.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7CDYES9QW4N2JZ8GX1Q9DMV","ticket","Use to decompose a parent work into independently-workable child tickets. Use to mint ticket(s), possibly a single one, when planning implementation without one.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fticket\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7CDYB6CFM7PD0APTBBS17HH","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\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CDY7V9VR5DDC0TPXQRB6K1","skill-up","Aid agent skill creation or modification. Use when creating a new skill or changing an existing one. Use whenever writing any agent instructions, whether to a file or directly in a reply.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-up\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CDY4B01RZP7Y90JGTCHNY5","setup-devops","Set up the project's engineering scaffolding, from toolchain to CICD and observability. Use when initializing a repo or filling a setup gap.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsetup-devops\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CDY1P8T9VT2W2ZXEH1H4PR","review-architecture","Explore the codebase for module-deepening opportunities — architectural improvements that raise testability and navigability. Use when asked to improve or refactor the architecture.","https:\u002F\u002Fgithub.com\u002Fdveyarangi\u002Fgoodwolf-harness\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-architecture\u002FSKILL.md",[],[]]