[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C1DK695CS7ESGDFAM7809G":3,"skill-same:01M7C1DK695CS7ESGDFAM7809G":52},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":28,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C1DK695CS7ESGDFAM7809G","implement",null,"Implement a piece of work based on a spec or set of tickets. Use when the user says \"implement\", or asks to build, execute or work on a ticket, spec or plan.","meldomapp\u002Fskills","meldomapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F301474652?v=4","01M7C1CSB68BPWJ2SRPQ7C46S3","Meldom","01M7C1CSBT0YWKNH60MET3GEVR",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implement\ndescription: \"Implement a piece of work based on a spec or set of tickets. Use when the user says \\\"implement\\\", or asks to build, execute or work on a ticket, spec or plan.\"\n---\n\nImplement the work described by the user in the spec or tickets.\n\nIf the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.\n\nCall the Skill tool with \"meldom:tdd\" where possible, at pre-agreed seams.\n\nRun typechecking regularly, single test files regularly, and the full test suite once at the end.\n\nOnce done, call the Skill tool with \"meldom:code-review\" to review the work.\n\nCommit your work to the current branch.\n\n## On Meldom\n\n- **Review the whole run, then commit.** Capture `git rev-parse HEAD` before building. After all tickets supplied to this run are implemented, run the final checks and call `meldom:code-review` against that captured commit, covering every ticket together. Fix findings, rerun affected checks and review until there are no findings. Then commit through `meldom:ship`.\n- **Claim before building.** Move the ticket you are about to build, and its parent spec, to `in_progress` with `mcp__meldom__ticket_batch_update`, keyed by each ticket's **ULID** (the `id` field), never its `KEY-42` key. Work on one child ticket at a time; its parent stays `in_progress` through final review.\n- **Report progress.** On the first pass, send one plan with exactly one step per ticket, each its ticket's key and sized `S`, `M` or `L`: `mcp__meldom__progress({ \"goal\": \"\u003Cspec title>\", \"plan\": [\"KEY-42:M\"] })`. Moving a ticket to `done` marks its step done, so send no `done` for it. Send `{ \"add\": [\"KEY-43:S\"] }` for each ticket added later, and `{ \"finish\": true }` with the run's last tool call. If the tool is not there after one search, skip every progress call silently.\n- **Mark each ticket done as it passes.** The moment a ticket's acceptance criteria pass, `mcp__meldom__ticket_update` it to `done` with a `reason`, then claim the next one.\n- **Build what you file.** Work the build surfaces beyond the tickets is a follow-up: file it at once with `mcp__meldom__ticket_create`, `parent_id` set to the spec or the ticket's own parent, and build it in this session. Before you finish, read `mcp__meldom__conversation_status`; while any ticket this session created is open, build it. The one exception is a step only a human can take: hand it over through `meldom:wizard` or a question.\n- **Record the final review per ticket.** For each ticket the review's Spec axis confirms, set `mcp__meldom__ticket_outcome({ \"id\": \u003Culid>, \"outcome\": \"verified\" })`. A ticket it contradicts gets `\"failed\"`, goes back to `open`, and is built again.\n- **Close the parent.** Parent status never rolls up on its own: after final checks and review pass and every child is `done` or `closed`, move the parent to `done` with `reason: \"All children done: \u003Csummary>\"`, then check its own parent the same way.\n","Implement the work described by the user in the spec or tickets.\n\nIf the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.\n\nCall the Skill tool with \"meldom:tdd\" where possible, at pre-agreed seams.\n\nRun typechecking regularly, single test files regularly, and the full test suite once at the end.\n\nOnce done, call the Skill tool with \"meldom:code-review\" to review the work.\n\nCommit your work to the current branch.\n\n## On Meldom\n\n- **Review the whole run, then commit.** Capture `git rev-parse HEAD` before building. After all tickets supplied to this run are implemented, run the final checks and call `meldom:code-review` against that captured commit, covering every ticket together. Fix findings, rerun affected checks and review until there are no findings. Then commit through `meldom:ship`.\n- **Claim before building.** Move the ticket you are about to build, and its parent spec, to `in_progress` with `mcp__meldom__ticket_batch_update`, keyed by each ticket's **ULID** (the `id` field), never its `KEY-42` key. Work on one child ticket at a time; its parent stays `in_progress` through final review.\n- **Report progress.** On the first pass, send one plan with exactly one step per ticket, each its ticket's key and sized `S`, `M` or `L`: `mcp__meldom__progress({ \"goal\": \"\u003Cspec title>\", \"plan\": [\"KEY-42:M\"] })`. Moving a ticket to `done` marks its step done, so send no `done` for it. Send `{ \"add\": [\"KEY-43:S\"] }` for each ticket added later, and `{ \"finish\": true }` with the run's last tool call. If the tool is not there after one search, skip every progress call silently.\n- **Mark each ticket done as it passes.** The moment a ticket's acceptance criteria pass, `mcp__meldom__ticket_update` it to `done` with a `reason`, then claim the next one.\n- **Build what you file.** Work the build surfaces beyond the tickets is a follow-up: file it at once with `mcp__meldom__ticket_create`, `parent_id` set to the spec or the ticket's own parent, and build it in this session. Before you finish, read `mcp__meldom__conversation_status`; while any ticket this session created is open, build it. The one exception is a step only a human can take: hand it over through `meldom:wizard` or a question.\n- **Record the final review per ticket.** For each ticket the review's Spec axis confirms, set `mcp__meldom__ticket_outcome({ \"id\": \u003Culid>, \"outcome\": \"verified\" })`. A ticket it contradicts gets `\"failed\"`, goes back to `open`, and is built again.\n- **Close the parent.** Parent status never rolls up on its own: after final checks and review pass and every child is `done` or `closed`, move the parent to `done` with `reason: \"All children done: \u003Csummary>\"`, then check its own parent the same way.\n",{"name":5,"description":7},"main","6c7a6b13c6aaa8bf63b72e9498b421c0af05e532","skills\u002Fimplement","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills","https:\u002F\u002Fmeldom.com","https:\u002F\u002Fgithub.com\u002Fmeldomapp","Run your AI coding agents as a team. Local-first desktop app for Claude Code, Codex and OpenCode.","2026-11-14 16:57:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add meldomapp\u002Fskills --skill implement",{"tool":38,"command":39},"bunx","bunx skills add meldomapp\u002Fskills --skill implement",{"tool":41,"command":42},"pnpm","pnpm dlx skills add meldomapp\u002Fskills --skill implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",96,"https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fimplement\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"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},"01M7C1FYKG3G9QSH4VGJ4V2R3X","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\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},"01M7C1FK3302JGFJMMQ0R34RZH","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\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},"01M7C1F9XJHRNXPCYEAZRQN5JH","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\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},"01M7C1F0YM1VKPJPT9JYG5QRMF","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\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},"01M7C1EYSDDGMYAS895TABK7B3","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7C1EVKH03P4S11WDNSFYNRR","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fmeldomapp\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[]]