[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JZ0X7XRP586PRGJDH0PRR8":3,"skill-same:01M6JZ0X7XRP586PRGJDH0PRR8":74},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6JZ0X7XRP586PRGJDH0PRR8","plan-to-tickets",null,"Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or chat-only summaries.","AnastasiyaW\u002Fcodex-claude-code-config","AnastasiyaW","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92753226?v=4","01M6JYPD9X5RRF8G7AH91NYD3R","Anastasiia Butova","01M6JYPDFBGM5EV8G8BABQ3GDY",214,"MIT","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fplan-to-tickets\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"to tickets","plan to tickets","plan","tickets","when","research","single","fixes","for","split","with","multi","feature","chat","task","do","ready","only","use","verification","acceptance","tasks","2026-11-10 10:12:30",false,"---\nname: plan-to-tickets\ndescription: Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or chat-only summaries.\n---\n\n# Plan To Tickets\n\nTurn a large plan into small, independently executable tickets. Use this before handing a broad plan to agents, before long autonomous work, or when the user asks for tickets\u002Fissues\u002Fslices.\n\n## Output Location\n\nIf no issue tracker is explicitly selected, write local tickets under:\n\n`\u003Cproject>\u002F.agent\u002Ftickets\u002F\u003CYYYY-MM-DD>-\u003Cslug>\u002F`\n\nEach ticket is one Markdown file:\n\n`TICKET-001-short-slug.md`\n\n## Required Ticket Shape\n\nEach ticket must include these headings exactly:\n\n- `## Status`\n- `## Parent`\n- `## What To Build`\n- `## Acceptance Criteria`\n- `## Verification`\n- `## Blocked By`\n- `## Notes`\n\n`## Status` must contain `ready-for-agent` only when all acceptance criteria and verification steps are concrete.\n\n`## Acceptance Criteria` must contain checklist items (`- [ ] ...`).\n\n`## Verification` must contain at least one command, script, test, artifact check, or explicit manual-review gate.\n\n## Slicing Rules\n\n- Prefer vertical tracer bullets: a narrow complete path through the required layers, not \"all backend\" then \"all UI\" then \"all tests\".\n- A ticket must be independently verifiable.\n- Put prefactoring first only when it makes a later slice smaller or safer.\n- Keep dependencies explicit in `## Blocked By`; write `None` when it can start immediately.\n- Do not include stale-prone file paths unless the path is already a stable contract or current codebase evidence.\n- Do not publish external tracker issues unless the user asked for that tracker.\n\n## Workflow\n\n1. Read the plan\u002Fspec and current repo context needed to avoid fake tickets.\n2. Draft ticket files in dependency order.\n3. Run the validator:\n\n```powershell\npython \"$env:USERPROFILE\\.claude\\claude-code-config\\scripts\\validate_agent_tickets.py\" --tickets-dir \u003Cticket-dir>\n```\n\n4. Fix every validator failure before claiming the ticket split is ready.\n5. Report the ticket directory and the count of ready tickets.\n\n## Gotchas\n\n- Horizontal tickets overload later agents. If a ticket cannot be verified alone, split it differently.\n- \"Implement feature\" is not an acceptance criterion. ACs must describe observable behavior or artifacts.\n- \"Run tests\" alone is weak verification. Name the test command or the artifact that proves success.\n- Do not use this to postpone work. Ticketization is for large plans; small tasks should be implemented directly.\n","# Plan To Tickets\n\nTurn a large plan into small, independently executable tickets. Use this before handing a broad plan to agents, before long autonomous work, or when the user asks for tickets\u002Fissues\u002Fslices.\n\n## Output Location\n\nIf no issue tracker is explicitly selected, write local tickets under:\n\n`\u003Cproject>\u002F.agent\u002Ftickets\u002F\u003CYYYY-MM-DD>-\u003Cslug>\u002F`\n\nEach ticket is one Markdown file:\n\n`TICKET-001-short-slug.md`\n\n## Required Ticket Shape\n\nEach ticket must include these headings exactly:\n\n- `## Status`\n- `## Parent`\n- `## What To Build`\n- `## Acceptance Criteria`\n- `## Verification`\n- `## Blocked By`\n- `## Notes`\n\n`## Status` must contain `ready-for-agent` only when all acceptance criteria and verification steps are concrete.\n\n`## Acceptance Criteria` must contain checklist items (`- [ ] ...`).\n\n`## Verification` must contain at least one command, script, test, artifact check, or explicit manual-review gate.\n\n## Slicing Rules\n\n- Prefer vertical tracer bullets: a narrow complete path through the required layers, not \"all backend\" then \"all UI\" then \"all tests\".\n- A ticket must be independently verifiable.\n- Put prefactoring first only when it makes a later slice smaller or safer.\n- Keep dependencies explicit in `## Blocked By`; write `None` when it can start immediately.\n- Do not include stale-prone file paths unless the path is already a stable contract or current codebase evidence.\n- Do not publish external tracker issues unless the user asked for that tracker.\n\n## Workflow\n\n1. Read the plan\u002Fspec and current repo context needed to avoid fake tickets.\n2. Draft ticket files in dependency order.\n3. Run the validator:\n\n```powershell\npython \"$env:USERPROFILE\\.claude\\claude-code-config\\scripts\\validate_agent_tickets.py\" --tickets-dir \u003Cticket-dir>\n```\n\n4. Fix every validator failure before claiming the ticket split is ready.\n5. Report the ticket directory and the count of ready tickets.\n\n## Gotchas\n\n- Horizontal tickets overload later agents. If a ticket cannot be verified alone, split it differently.\n- \"Implement feature\" is not an acceptance criterion. ACs must describe observable behavior or artifacts.\n- \"Run tests\" alone is weak verification. Name the test command or the artifact that proves success.\n- Do not use this to postpone work. Ticketization is for large plans; small tasks should be implemented directly.\n",{"name":5,"description":7},"main","ac20f93f36e574610dbc51743bb21e7765142e95","skills\u002Fplan-to-tickets",32,"https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config","https:\u002F\u002Fgithub.com\u002FAnastasiyaW","https:\u002F\u002Fhappyin.work","ComfyUI specialist · turnkey image-processing pipelines · diffusion models, computer vision · Belgrade","2026-11-11 23:32:39",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add AnastasiyaW\u002Fcodex-claude-code-config --skill plan-to-tickets",{"tool":66,"command":67},"bunx","bunx skills add AnastasiyaW\u002Fcodex-claude-code-config --skill plan-to-tickets",{"tool":69,"command":70},"pnpm","pnpm dlx skills add AnastasiyaW\u002Fcodex-claude-code-config --skill plan-to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fplan-to-tickets\u002FSKILL.md",true,[],[75,84,100,124,150,168],{"skillNo":76,"name":77,"nameZh":6,"description":6,"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":81,"publishedAt":46},"01M6JZ2SNGKFN8NK3HZBMVGQP1","owner-voice","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fowner-voice\u002FSKILL.md",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83],"owner voice","voice",{"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":91,"publishedAt":46},"01M6JZ2N0C2WFCAK6T8N3RMBVS","humanize-russian","Редактировать русский текст для ясности и естественного звучания, сохраняя факты,\nтермины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст\nживее, отредактировать русский черновик или статью перед публикацией.\nНе определяет авторство и не обещает обход детекторов. Для английского —\nhumanize-english; для структуры и доказательств — article-structure-review.","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fhumanize-russian\u002FSKILL.md",[90],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,93,94,95,96,97,98,99],"russian","humanize","humanize russian","english","review","structure","article","2026",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":46},"01M6JZ2GN264R6GKBQ5QVZE0ZS","humanize-english","Edit English drafts for clear, natural language while preserving facts, uncertainty,\ntechnical meaning, citations and genre. Use when: humanize this text, remove AI-style\nfiller, improve English prose, or edit an English article before publication.\nNot an authorship detector or a promise to bypass one. For Russian use\nhumanize-russian; for thesis\u002Fevidence and structure use article-structure-review.","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fhumanize-english\u002FSKILL.md",[],[93,95,107,108,92,109,42,110,111,97,112,113,114,96,115,99,28,32,116,117,118,119,120,121,98,122,123],"humanize english","technical","evidence","remove","edit","text","improve","Citations","Publication","facts","natural language","drafts","meaning","uncertainty","style","thesis","promise",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":46},"01M6JZ2BM31D5Y609DQJJJM6MM","caveman","Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse \"caveman\" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or Russian \"пещерный режим\", \"говори как пещерный\", \"кратко\", \"меньше токенов\", \"экономь токены\" — or invokes \u002Fcaveman. Preserves the user's language (Russian in → Russian caveman out). Off only: \"stop caveman\" \u002F \"normal mode\" \u002F \"обычный режим\". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fcaveman\u002FSKILL.md",[],[126,121,28,131,132,133,134,135,136,137,138,139,140,141,142,143,39,92,144,145,146,41,42,108,147,148,149],"normal","terse","accuracy","ultra","mode","document","requests","concise","output","intensity","tokens","full","time","action","default","stop","first","brief","state",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":165,"publishedAt":46},"01M6JZ25Y5GJXFKXNR6TRQX237","article-structure-review","Проверить структуру технической статьи после черновика: задача читателя, жанр,\nопора значимых утверждений на доказательства и честные ограничения.\nUse after the first draft, before publication. Исправлять структуру, когда это\nвходит в запрос; не создавать обязательный конвейер из других навыков.\nДля локальной языковой редактуры — humanize-english или humanize-russian.","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md",[156,159,160],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[166,98,97,96,167,93,92,42,147,95,115,99],"article structure review","draft",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":46},"01M6JZ1XN7WQQCWCHHMTTD8K28","video-post-production","Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames\u002Fscenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.","https:\u002F\u002Fgithub.com\u002FAnastasiyaW\u002Fcodex-claude-code-config\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-production\u002Fvideo-post-production\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[178,179,180,181,182,28,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197],"video post production","post","Production","Video","patterns","post-production","narrative","add","chain","tiktok","voiceover","master","export","write","music","Captions","Audio","Remotion","code","generate"]