[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D02JQ8ZQW8ZMJJS5MJTMXF":3,"skill-same:01M7D02JQ8ZQW8ZMJJS5MJTMXF":62},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D02JQ8ZQW8ZMJJS5MJTMXF","progress-check",null,"Give sparse, evidence-based progress updates during long-running work: observable milestones weighted by work and risk, an update only when something material changed, one rounded-down bar. Use while long work with several milestones runs between replies, never for a short answer or work with no intermediate state; and the moment the owner asks to change how or how often you report progress, whether more updates, total silence or an estimated clock, BEFORE any such preference is saved anywhere.","fern-works\u002Fgreenline","fern-works","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330252531?v=4","01M7CZ6VNSYC4MB0XZS6BWJRX3","fernworks","01M7CZ6VPZYZWBPRG404SRBNA9",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"progress-check\"\ndescription: \"Give sparse, evidence-based progress updates during long-running work: observable milestones weighted by work and risk, an update only when something material changed, one rounded-down bar. Use while long work with several milestones runs between replies, never for a short answer or work with no intermediate state; and the moment the owner asks to change how or how often you report progress, whether more updates, total silence or an estimated clock, BEFORE any such preference is saved anywhere.\"\n---\n\n# Progress Check\n\nprogress-check is the habit for the moment long work runs between replies: a\nchange with several milestones, a build of many slices, delegated agents\nrunning one after another. It never fires on a short answer or on work whose\nonly honest states are started and finished, and its cadence is judgment,\nnever spam. It also fires the moment the owner asks to change how or how often\nyou report, whether more updates, silence or an estimated clock: follow the\npreference within the current task, keep reporting actionable blockers, and\nsave nothing anywhere unless the owner asks for a lasting rule (Persist a\npreference, below). It writes no record of its own: progress stays in the\nconversation, the evidence behind it belongs to the change record's sections\nand the checks the change recorded, and an estimated clock is an\nunmeasured claim this habit never makes.\n\nGreenline's paths and commands for this skill stand on its references page, [references\u002Fgreenline.md](references\u002Fgreenline.md): read it when the work lands in the workspace.\n\nFull method: [METHODOLOGY.md](.\u002FMETHODOLOGY.md). Chat shape:\n[RESPONSE.md](.\u002FRESPONSE.md). Examples: [EXAMPLES.md](.\u002FEXAMPLES.md).\n\n## Choose the mode\n\n- **Report progress:** default for qualifying long-running work.\n- **Persist a preference:** only when the owner asks for a lasting rule. The\n  greenline CLI installs this skill, so there is no install-globally mode here.\n\n## Report progress\n\n1. Define a small set of observable milestones before estimating a percentage.\n   Weight by work and risk, not elapsed time. Where a change owns the work, the\n   milestones are its acceptance items and every update quotes their evidence.\n2. Send one baseline update after scope is understood.\n3. Send a routine update only when turns of work have passed since the previous\n   routine update or a step of the change has ended, **and** one of these is\n   true: a milestone completed, verified progress rose by at least 10 percentage\n   points, or the next action materially changed. Never estimate elapsed time to\n   open the gate; an estimated clock is an unmeasured claim.\n4. Report a new blocker immediately when the user can act on it. Report\n   completion immediately.\n5. Never repeat an unchanged bar or send a routine “still working” message.\n\nThe update is conversation and nothing else: milestone evidence belongs to the\nchange record and its checks, and no parallel progress file or tracker is\ncreated. Keep each update to at most three short items: completed\nevidence, current work, and next step or blocker. End with exactly one overall\nbar styled as inline code on its own line:\n\n`Performance rollout  [██████████████████░░] 90%`\n\nUse one pair of backticks for inline-code styling. Do not indent the line by\nfour spaces and do not use a fenced code block; both create a separate block\nthat interfaces may label or make copyable.\n\n- Replace the label with a short task-specific label.\n- Use 20 cells: `█` completed and `░` remaining.\n- Round down to the nearest 5% unless completion evidence supports 100%.\n- Show only the overall bar unless the user requests subtask bars.\n- In multi-agent work, only the coordinator shows the overall bar.\n- The progress line is the final content in the update. End immediately after\n  it with no note, recap, or closer.\n\n## Persist a preference\n\nThe greenline CLI installs this skill; there is no global installation step\nhere and no machine-global instruction write. A request to change how or how\noften you report is followed within the current task and saved nowhere.\nPersist a preference only when the owner asks for a lasting repository\nrule, as a house ruling in the repository's user-owned instruction home, in the\nformat the work guide defines. The next context reads that rule without\ndemanding a second confirmation.\n\nDurable output: none. Applied on its own cadence while long work runs, and the moment the owner asks to change how or how often you report, before any preference is saved anywhere.\n","# Progress Check\n\nprogress-check is the habit for the moment long work runs between replies: a\nchange with several milestones, a build of many slices, delegated agents\nrunning one after another. It never fires on a short answer or on work whose\nonly honest states are started and finished, and its cadence is judgment,\nnever spam. It also fires the moment the owner asks to change how or how often\nyou report, whether more updates, silence or an estimated clock: follow the\npreference within the current task, keep reporting actionable blockers, and\nsave nothing anywhere unless the owner asks for a lasting rule (Persist a\npreference, below). It writes no record of its own: progress stays in the\nconversation, the evidence behind it belongs to the change record's sections\nand the checks the change recorded, and an estimated clock is an\nunmeasured claim this habit never makes.\n\nGreenline's paths and commands for this skill stand on its references page, [references\u002Fgreenline.md](references\u002Fgreenline.md): read it when the work lands in the workspace.\n\nFull method: [METHODOLOGY.md](.\u002FMETHODOLOGY.md). Chat shape:\n[RESPONSE.md](.\u002FRESPONSE.md). Examples: [EXAMPLES.md](.\u002FEXAMPLES.md).\n\n## Choose the mode\n\n- **Report progress:** default for qualifying long-running work.\n- **Persist a preference:** only when the owner asks for a lasting rule. The\n  greenline CLI installs this skill, so there is no install-globally mode here.\n\n## Report progress\n\n1. Define a small set of observable milestones before estimating a percentage.\n   Weight by work and risk, not elapsed time. Where a change owns the work, the\n   milestones are its acceptance items and every update quotes their evidence.\n2. Send one baseline update after scope is understood.\n3. Send a routine update only when turns of work have passed since the previous\n   routine update or a step of the change has ended, **and** one of these is\n   true: a milestone completed, verified progress rose by at least 10 percentage\n   points, or the next action materially changed. Never estimate elapsed time to\n   open the gate; an estimated clock is an unmeasured claim.\n4. Report a new blocker immediately when the user can act on it. Report\n   completion immediately.\n5. Never repeat an unchanged bar or send a routine “still working” message.\n\nThe update is conversation and nothing else: milestone evidence belongs to the\nchange record and its checks, and no parallel progress file or tracker is\ncreated. Keep each update to at most three short items: completed\nevidence, current work, and next step or blocker. End with exactly one overall\nbar styled as inline code on its own line:\n\n`Performance rollout  [██████████████████░░] 90%`\n\nUse one pair of backticks for inline-code styling. Do not indent the line by\nfour spaces and do not use a fenced code block; both create a separate block\nthat interfaces may label or make copyable.\n\n- Replace the label with a short task-specific label.\n- Use 20 cells: `█` completed and `░` remaining.\n- Round down to the nearest 5% unless completion evidence supports 100%.\n- Show only the overall bar unless the user requests subtask bars.\n- In multi-agent work, only the coordinator shows the overall bar.\n- The progress line is the final content in the update. End immediately after\n  it with no note, recap, or closer.\n\n## Persist a preference\n\nThe greenline CLI installs this skill; there is no global installation step\nhere and no machine-global instruction write. A request to change how or how\noften you report is followed within the current task and saved nowhere.\nPersist a preference only when the owner asks for a lasting repository\nrule, as a house ruling in the repository's user-owned instruction home, in the\nformat the work guide defines. The next context reads that rule without\ndemanding a second confirmation.\n\nDurable output: none. Applied on its own cadence while long work runs, and the moment the owner asks to change how or how often you report, before any preference is saved anywhere.\n",{"name":5,"description":7},"main","c4a6bc27da835d109348b8708301821838e98db2","test\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline","https:\u002F\u002Fgithub.com\u002Ffern-works","2026-10-21 15:51:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add fern-works\u002Fgreenline --skill progress-check",{"tool":36,"command":37},"bunx","bunx skills add fern-works\u002Fgreenline --skill progress-check",{"tool":39,"command":40},"pnpm","pnpm dlx skills add fern-works\u002Fgreenline --skill progress-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002FSKILL.md",true,[44,50,54,58],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"EXAMPLES.md","REFERENCE","参考文档",2214,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002FEXAMPLES.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"METHODOLOGY.md",4361,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002FMETHODOLOGY.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fgreenline.md",409,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002Freferences\u002Fgreenline.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"RESPONSE.md",844,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fprogress-check\u002FRESPONSE.md",[63,70,75,82,89,96],{"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},"01M7D04ARSVW93Y1EGVM7HQQR8","use-garden","Consulting garden, the separately installed guidance command this repository's owner enabled, when an open engineering choice the repository does not settle, made in a change or only recommended, would be informed by published guidance. Use for a choice between approaches, a pattern or pitfall for a technology or concern the work touches, or a unit a repository decision names; not for a question about this repository's own facts or a change whose choices are already settled.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fgarden-enabled\u002Fdot-claude\u002Fskills\u002Fuse-garden\u002FSKILL.md",[],[],{"skillNo":71,"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":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D045RXH0SEYZKHHW2YD0FQ","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fgarden-enabled\u002Fdot-agents\u002Fskills\u002Fuse-garden\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D03ZXQHBP1RASSRHH5DX7S","what-to-build","Propose what this product could do next at three altitudes: sharpen a shipped slice, extend one, or open ground the product does not stand on yet. Use for 'what should we build next', 'any ideas for this app', 'what's missing', 'is this done or is there more in it', and quick-win hunts. Not for refactors, which belong to the architecture survey.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fwhat-to-build\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D03WVYR3NN0N0CTN51RWBV","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets in a plan directory's map.md, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7D03R6MAHHKQ42E5NBRHSF6","verify","Prove a change's claims with fresh evidence: restate each item of its acceptance so it can fail, capture a baseline and a treatment with the same command, compare the raw artifacts, and return VERIFIED, NOT VERIFIED or INCONCLUSIVE for each, at the depth the change's mode gives the verify step. Use when the mode reaches verify, or when the owner says \"verify this\", \"prove it works\" or \"did this fix it\".","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7D03JYGW4945FSJV6CDE2K9","tdd","Test-first development at any step: discover the repository's own test commands, name the break a test catches, watch it fail for the intended reason, make it pass with the smallest change, and add a new test only where it catches a realistic failure the existing ones would miss. Use when writing or changing a test, building a feature or fixing a bug test-first, or deciding whether a change needs a new test; also on 'red-green-refactor' and integration tests.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]