[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDYYY1KHASERFSW5V2PD64":3,"skill-same:01M7CDYYY1KHASERFSW5V2PD64":51},{"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":29,"updatedAt":30,"install":31,"resources":44},"01M7CDYYY1KHASERFSW5V2PD64","pipeliner-audit-backlog",null,"Audit and, when explicitly requested, repair Backlog Issue classification without consuming the active work slot.","Zuriel-Labs\u002Fpipeliner","Zuriel-Labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288671560?v=4","01M7CDYRRP6T1PMC5J81EW7THP","Zuriel Labs","01M7CDYRSB5S6R80KG66ENXD5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-audit-backlog\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pipeliner-audit-backlog\ndescription: Audit and, when explicitly requested, repair Backlog Issue classification without consuming the active work slot.\n---\n\n# Audit the Backlog\n\nApply the shared [installed repository home](..\u002Fpipeliner-maintain\u002Freferences\u002Fhome.md) and [message-only questions](..\u002Fpipeliner-maintain\u002Freferences\u002Fquestions.md) contracts. First adoption retains its explicit-target gate. When an answer is needed, ask in the final ordinary message and end the turn immediately; no work or tool calls follow until the Human replies.\n\nFollow [Issue-based communication](..\u002F..\u002F..\u002FAGENTS.md#issue-based-communication): lead each finding, recommendation, and status with the Backlog Issue number. Include linked pull requests as supporting evidence and distinguish delivered implementation from an Issue that has passed all completion gates.\n\nRead `AGENTS.md`, `pipeliner.config.json`, the live Project schema, every Backlog Issue, open pull requests, and relevant repository or dependency evidence.\n\n- Account for every Backlog Issue and classify it as ready, blocked, dependent, duplicate, superseded, delivered, or needing PM clarification.\n- Verify each is open, inactive, normally unassigned, has one governed type, applicable areas, and complete configured Priority, Impact, and Effort fields.\n- Rank ready work by security, privacy, data integrity, release reliability, user impact, dependency value, urgency, readiness, risk, and effort. Reserve P0 for genuinely urgent blockers.\n- Default to read-only reporting. Apply Backlog-only metadata repairs only when the PM explicitly requests correction; never change scope, body, status lane, or active work without the corresponding workflow authority.\n- Read every permitted mutation back and report before\u002Fafter values with evidence. Report a no-op audit plainly.\n- If no Issue is active, recommend the top three ready outcomes and wait for PM selection. Do not start one from this skill.\n\nWhen `release.cycle` is configured, follow [release scope and phase governance](..\u002Fpipeliner-maintain\u002Freferences\u002Frelease-cycle.md): inspect target\u002Fmilestone, Release Issue, phase, freeze and blockers without treating phase as Status. Read-only inspection never starts or advances a cycle. Related findings stay on the same Issue; unrelated intake requires exact draft approval.\n","# Audit the Backlog\n\nApply the shared [installed repository home](..\u002Fpipeliner-maintain\u002Freferences\u002Fhome.md) and [message-only questions](..\u002Fpipeliner-maintain\u002Freferences\u002Fquestions.md) contracts. First adoption retains its explicit-target gate. When an answer is needed, ask in the final ordinary message and end the turn immediately; no work or tool calls follow until the Human replies.\n\nFollow [Issue-based communication](..\u002F..\u002F..\u002FAGENTS.md#issue-based-communication): lead each finding, recommendation, and status with the Backlog Issue number. Include linked pull requests as supporting evidence and distinguish delivered implementation from an Issue that has passed all completion gates.\n\nRead `AGENTS.md`, `pipeliner.config.json`, the live Project schema, every Backlog Issue, open pull requests, and relevant repository or dependency evidence.\n\n- Account for every Backlog Issue and classify it as ready, blocked, dependent, duplicate, superseded, delivered, or needing PM clarification.\n- Verify each is open, inactive, normally unassigned, has one governed type, applicable areas, and complete configured Priority, Impact, and Effort fields.\n- Rank ready work by security, privacy, data integrity, release reliability, user impact, dependency value, urgency, readiness, risk, and effort. Reserve P0 for genuinely urgent blockers.\n- Default to read-only reporting. Apply Backlog-only metadata repairs only when the PM explicitly requests correction; never change scope, body, status lane, or active work without the corresponding workflow authority.\n- Read every permitted mutation back and report before\u002Fafter values with evidence. Report a no-op audit plainly.\n- If no Issue is active, recommend the top three ready outcomes and wait for PM selection. Do not start one from this skill.\n\nWhen `release.cycle` is configured, follow [release scope and phase governance](..\u002Fpipeliner-maintain\u002Freferences\u002Frelease-cycle.md): inspect target\u002Fmilestone, Release Issue, phase, freeze and blockers without treating phase as Status. Read-only inspection never starts or advances a cycle. Related findings stay on the same Issue; unrelated intake requires exact draft approval.\n",{"name":5,"description":7},"main","0af6febf92f8cca2ec3f78d5446d27cc4cfcf428",".agents\u002Fskills\u002Fpipeliner-audit-backlog","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner","https:\u002F\u002Fgithub.com\u002FZuriel-Labs","Our playground for apps, scripts, and code.","2026-11-12 05:17:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-audit-backlog",{"tool":37,"command":38},"bunx","bunx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-audit-backlog",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-audit-backlog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-audit-backlog\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",192,"https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-audit-backlog\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7CE1MBMP52YARSJZ8N9ER7K","pipeliner-work-issue","Use the canonical workflow to start or resume one Issue and lead the next authorized stage.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-work-issue\u002FSKILL.md",[],[],{"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},"01M7CE1CETB40RGJA8EM3R4ZGZ","pipeliner-update","Use the canonical workflow to update an existing Pipeliner adoption while preserving local configuration.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-update\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},"01M7CE15VYS22AX9XGSGQCF61E","pipeliner-review-issue","Use the canonical workflow to resume review or feedback before or after merge and guide PM Testing.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-review-issue\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},"01M7CE0YV6EN1ZC6ESJ0TEK41V","pipeliner-release-production","Use the canonical workflow to release an approved candidate.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-release-production\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},"01M7CE0P9YF5V416HMK6Z8YB6R","pipeliner-release-candidate","Use the canonical workflow to prepare an exact release candidate.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-release-candidate\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},"01M7CE0MXSSR5STYA5P5VMT5VS","pipeliner-pipeline-health","Use the canonical workflow to audit pipeline health read-only.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-pipeline-health\u002FSKILL.md",[],[]]