[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MZ07ZGSAMX5NPS8B2M5A1":3,"skill-same:01M71MZ07ZGSAMX5NPS8B2M5A1":84},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M71MZ07ZGSAMX5NPS8B2M5A1","skills-index",null,"Use when the user asks which skill to use, how to start delivery, or what to do next without naming a skill. Routes to product, tasks, tdd, etc. Triggers on \"which skill should I use\", \"what can I do here\", \"how do I start\", \"what's next\", \"where do I begin\". Do NOT produce artefacts or implement code — only recommend skill and mode.","carinyadigital\u002Fskills","carinyadigital","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F185663942?v=4","01M71MWSF49DXG75MCNJ5D9CE2","Carinya Digital","01M71MWSFRXEATZ2MQGKD8A2S2",2,"MIT","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fskills-index\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],"index","skills index","routing","can","implement","tasks","code","query","when","use","utility","produce","decision-support","only","how to","triggers","decision","mode","which","do","2026-11-10 10:56:23",false,"---\nname: skills-index\ndescription: >\n  Use when the user asks which skill to use, how to start delivery, or what to\n  do next without naming a skill. Routes to product, tasks, tdd, etc.\n  Triggers on \"which skill should I use\", \"what can I do here\", \"how do I\n  start\", \"what's next\", \"where do I begin\".\n  Do NOT produce artefacts or implement code — only recommend skill and mode.\nlicense: MIT\nallowed-tools: Read\nargument-hint: \u003Cquery>\nmetadata:\n  author: Carinya Parc\n  version: \"1.0\"\n  owner: utility\n  work_shape: routing\n  output_class: decision-support\n---\n\n# Skills index\n\nYou are a Skill Router. When the user asks a vague question — \"which skill\nshould I use?\", \"what can I do here?\", \"how do I start?\" — use the table below\nto identify the best match and direct them to the right skill.\n\n## How to route\n\n1. Read the user's request carefully.\n2. Scan the **Description** column for skills that match the intent.\n3. Pick the single best skill. When multiple match, prefer the one whose\n   **Track** matches the current delivery context.\n4. Tell the user: \"The best skill for this is **{skill-name}**.\" followed by one\n   sentence explaining why. Include the **mode** when the skill uses modes\n   (e.g. `adr plan CHK01`, `tasks checkout-foundation`, `sprint-planning 3`).\n   Most artefact skills are write-only — drafting or re-authoring from scratch.\n   For reviewing or critiquing an existing artefact, route to **docs-review**\n   instead. `adr` is the exception: it keeps its own **plan**, **write**, and\n   **review** modes.\n\nFor end-to-end delivery, suggest the next skill in the flow\n(product → roadmap → tasks → tdd → tasks → implement → validate) or ask\nwhich phase the user is in.\n\n## Skill index\n\n| Skill | Description (excerpt) | Artefact | Track | Role | Consumes | Produces |\n| --- | --- | --- | --- | --- | --- | --- |\n| adr | Plan the register — survey product\u002Fsolution for decisions still to make, or `adr plan \u003Cwork-id>` to harvest decisions already made in tdd.md — then write or review ADRs | register.md \u002F ADR-NNNN.md | architecture | architect | solution.md, tdd.md | ADR-NNNN.md |\n| tasks | Decompose any work item: product\u002Froadmap into epics, an epic into stories and tasks with Gherkin AC, a story into sub-tasks, or any spec\u002FRFC into both. Resolves Linear\u002FJira\u002FGitHub\u002Ffilesystem first | backlog.md \u002F tasks.md, or the tracker | strategy \u002F discovery | delivery | product.md, roadmap.md, tdd.md, any spec | backlog.md, tasks.md |\n| backlog-refine | Groom a backlog or judge sprint readiness: reprioritise, split, re-estimate, defer; amends in place with a verdict | backlog.md \u002F tasks.md | discovery \u002F delivery | delivery | backlog.md, tasks.md | groomed artefact |\n| implement | Implements a task against tdd.md and tasks.md, tests included | code | delivery | engineer | tdd.md, tasks.md | code |\n| code-review | Code review of a branch, PR, or working diff | code review | delivery | engineer | tdd.md, tasks.md | review |\n| code-review-fix | Addresses code review findings without behaviour change | code | delivery | engineer | review output | code |\n| ux-design-review | Read-only UX review of implemented UI vs its design source: accessibility, states, responsiveness, fidelity | UX review | delivery | engineer | design source, UI diff | review |\n| ux-design-fix | Change how existing UI looks or behaves, from a UX review verdict or a direct instruction; verifies visually and commits | code | delivery | engineer | UX review output, or an instruction | code |\n| merge-request | Open an MR\u002FPR for the current branch on any provider: title, description, labels, reviewer suggestions | MR \u002F PR | delivery | engineer | — | MR \u002F PR |\n| merge-request-babysit | Drive an open MR\u002FPR to merge-ready: watch CI, fix objective failures, triage threads, sync conflicts | merge-ready MR | delivery | engineer | open MR \u002F PR | code \u002F MR |\n| merge-request-review | Review an MR\u002FPR as its reviewer; publish inline comments and a verdict | published review | delivery | engineer | MR \u002F PR | published review |\n| ralph-loop-setup | Seed and configure a Ralph loop: pick a preset (engineering delivery, ad-hoc, custom), resolve the environment, set the completion promise and iteration budget; never starts the loop | seeded loop | delivery | delivery | tdd.md, tasks.md | loop files |\n| ralph-loop | Run an autonomous loop: one step per iteration until a completion promise or a safety rail (`start`, `status`, `cancel`) | committed work item + MR | delivery | delivery | seeded loop | code \u002F MR |\n| tdd | Technical design document at docs\u002Fwork\u002F{work-id}\u002Ftdd.md for any work item — epic, story, bug, or spike (review via docs-review). Not test-driven development — that is implement | tdd.md | discovery | architect | solution.md, backlog.md | tdd.md |\n| docs-review | Review any set of documents: per-document writing and structure, boundaries and duplication between documents, consistency and cohesion across the set. Read-only | doc review | any | architect | any doc set | review |\n| product | product.md: write (review via docs-review) | docs\u002Fproduct\u002Fproduct.md | strategy | pm | — | product.md |\n| sprint-planning | Plan a sprint: goal, carry-over, capacity, committed scope, dependencies, DoD | docs\u002Fwork\u002Fsprint-{id}\u002Fplan.md | delivery | delivery | backlog.md, tasks.md, prior retrospective.md | plan.md |\n| sprint-retro | Review a finished sprint: commitment vs actual, themes with evidence, actions routed to owning skills | docs\u002Fwork\u002Fsprint-{id}\u002Fretrospective.md | delivery | delivery | plan.md, tasks.md | retrospective.md |\n| roadmap | roadmap.md: write (review via docs-review) | docs\u002Fproduct\u002Froadmap.md | strategy | pm | product.md | roadmap.md |\n| solution | Architecture solution.md: write (review via docs-review) | docs\u002Farchitecture\u002Fsolution.md | architecture | architect | product.md | solution.md |\n| skills-index | Routes vague requests to the right skill | skill-routing | utility | utility | — | skill-routing |\n| validate | Work item sign-off vs AC and, for an epic, roadmap gates | validation report | delivery | delivery | backlog.md, tasks.md, solution.md | validation |\n\n## Output format\n\nFollow [assets\u002Fskills-index.template.md](assets\u002Fskills-index.template.md) —\nname the skill, one sentence on why, the invocation line, and a \"why not X\"\nonly when a close alternative exists.\n\n## Negative constraints\n\nThe skills-index response MUST NOT contain:\n\n- Implementation details of any recommended skill — direct the user to that\n  skill's own `SKILL.md`\n- Multiple simultaneous recommendations without a clear primary choice\n- Business rationale for why a skill exists — the descriptions are sufficient\n","# Skills index\n\nYou are a Skill Router. When the user asks a vague question — \"which skill\nshould I use?\", \"what can I do here?\", \"how do I start?\" — use the table below\nto identify the best match and direct them to the right skill.\n\n## How to route\n\n1. Read the user's request carefully.\n2. Scan the **Description** column for skills that match the intent.\n3. Pick the single best skill. When multiple match, prefer the one whose\n   **Track** matches the current delivery context.\n4. Tell the user: \"The best skill for this is **{skill-name}**.\" followed by one\n   sentence explaining why. Include the **mode** when the skill uses modes\n   (e.g. `adr plan CHK01`, `tasks checkout-foundation`, `sprint-planning 3`).\n   Most artefact skills are write-only — drafting or re-authoring from scratch.\n   For reviewing or critiquing an existing artefact, route to **docs-review**\n   instead. `adr` is the exception: it keeps its own **plan**, **write**, and\n   **review** modes.\n\nFor end-to-end delivery, suggest the next skill in the flow\n(product → roadmap → tasks → tdd → tasks → implement → validate) or ask\nwhich phase the user is in.\n\n## Skill index\n\n| Skill | Description (excerpt) | Artefact | Track | Role | Consumes | Produces |\n| --- | --- | --- | --- | --- | --- | --- |\n| adr | Plan the register — survey product\u002Fsolution for decisions still to make, or `adr plan \u003Cwork-id>` to harvest decisions already made in tdd.md — then write or review ADRs | register.md \u002F ADR-NNNN.md | architecture | architect | solution.md, tdd.md | ADR-NNNN.md |\n| tasks | Decompose any work item: product\u002Froadmap into epics, an epic into stories and tasks with Gherkin AC, a story into sub-tasks, or any spec\u002FRFC into both. Resolves Linear\u002FJira\u002FGitHub\u002Ffilesystem first | backlog.md \u002F tasks.md, or the tracker | strategy \u002F discovery | delivery | product.md, roadmap.md, tdd.md, any spec | backlog.md, tasks.md |\n| backlog-refine | Groom a backlog or judge sprint readiness: reprioritise, split, re-estimate, defer; amends in place with a verdict | backlog.md \u002F tasks.md | discovery \u002F delivery | delivery | backlog.md, tasks.md | groomed artefact |\n| implement | Implements a task against tdd.md and tasks.md, tests included | code | delivery | engineer | tdd.md, tasks.md | code |\n| code-review | Code review of a branch, PR, or working diff | code review | delivery | engineer | tdd.md, tasks.md | review |\n| code-review-fix | Addresses code review findings without behaviour change | code | delivery | engineer | review output | code |\n| ux-design-review | Read-only UX review of implemented UI vs its design source: accessibility, states, responsiveness, fidelity | UX review | delivery | engineer | design source, UI diff | review |\n| ux-design-fix | Change how existing UI looks or behaves, from a UX review verdict or a direct instruction; verifies visually and commits | code | delivery | engineer | UX review output, or an instruction | code |\n| merge-request | Open an MR\u002FPR for the current branch on any provider: title, description, labels, reviewer suggestions | MR \u002F PR | delivery | engineer | — | MR \u002F PR |\n| merge-request-babysit | Drive an open MR\u002FPR to merge-ready: watch CI, fix objective failures, triage threads, sync conflicts | merge-ready MR | delivery | engineer | open MR \u002F PR | code \u002F MR |\n| merge-request-review | Review an MR\u002FPR as its reviewer; publish inline comments and a verdict | published review | delivery | engineer | MR \u002F PR | published review |\n| ralph-loop-setup | Seed and configure a Ralph loop: pick a preset (engineering delivery, ad-hoc, custom), resolve the environment, set the completion promise and iteration budget; never starts the loop | seeded loop | delivery | delivery | tdd.md, tasks.md | loop files |\n| ralph-loop | Run an autonomous loop: one step per iteration until a completion promise or a safety rail (`start`, `status`, `cancel`) | committed work item + MR | delivery | delivery | seeded loop | code \u002F MR |\n| tdd | Technical design document at docs\u002Fwork\u002F{work-id}\u002Ftdd.md for any work item — epic, story, bug, or spike (review via docs-review). Not test-driven development — that is implement | tdd.md | discovery | architect | solution.md, backlog.md | tdd.md |\n| docs-review | Review any set of documents: per-document writing and structure, boundaries and duplication between documents, consistency and cohesion across the set. Read-only | doc review | any | architect | any doc set | review |\n| product | product.md: write (review via docs-review) | docs\u002Fproduct\u002Fproduct.md | strategy | pm | — | product.md |\n| sprint-planning | Plan a sprint: goal, carry-over, capacity, committed scope, dependencies, DoD | docs\u002Fwork\u002Fsprint-{id}\u002Fplan.md | delivery | delivery | backlog.md, tasks.md, prior retrospective.md | plan.md |\n| sprint-retro | Review a finished sprint: commitment vs actual, themes with evidence, actions routed to owning skills | docs\u002Fwork\u002Fsprint-{id}\u002Fretrospective.md | delivery | delivery | plan.md, tasks.md | retrospective.md |\n| roadmap | roadmap.md: write (review via docs-review) | docs\u002Fproduct\u002Froadmap.md | strategy | pm | product.md | roadmap.md |\n| solution | Architecture solution.md: write (review via docs-review) | docs\u002Farchitecture\u002Fsolution.md | architecture | architect | product.md | solution.md |\n| skills-index | Routes vague requests to the right skill | skill-routing | utility | utility | — | skill-routing |\n| validate | Work item sign-off vs AC and, for an epic, roadmap gates | validation report | delivery | delivery | backlog.md, tasks.md, solution.md | validation |\n\n## Output format\n\nFollow [assets\u002Fskills-index.template.md](assets\u002Fskills-index.template.md) —\nname the skill, one sentence on why, the invocation line, and a \"why not X\"\nonly when a close alternative exists.\n\n## Negative constraints\n\nThe skills-index response MUST NOT contain:\n\n- Implementation details of any recommended skill — direct the user to that\n  skill's own `SKILL.md`\n- Multiple simultaneous recommendations without a clear primary choice\n- Business rationale for why a skill exists — the descriptions are sufficient\n",{"name":5,"license":15,"metadata":49,"description":52,"allowed-tools":53,"argument-hint":54},{"owner":34,"author":50,"version":51,"work_shape":26,"output_class":36},"Carinya Parc","1.0","Use when the user asks which skill to use, how to start delivery, or what to do next without naming a skill. Routes to product, tasks, tdd, etc. Triggers on \"which skill should I use\", \"what can I do here\", \"how do I start\", \"what's next\", \"where do I begin\". Do NOT produce artefacts or implement code — only recommend skill and mode.\n","Read","\u003Cquery>","main","a130b08e73c014d346320ba5258cf89d60b5e070","skills\u002Fskills-index",0,"https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills","https:\u002F\u002Fgithub.com\u002Fcarinyadigital","carinyadigital.com","AI agents and agentic operations for small and medium businesses.","2026-08-20 06:13:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add carinyadigital\u002Fskills --skill skills-index",{"tool":70,"command":71},"bunx","bunx skills add carinyadigital\u002Fskills --skill skills-index",{"tool":73,"command":74},"pnpm","pnpm dlx skills add carinyadigital\u002Fskills --skill skills-index","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fskills-index\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fskills-index.template.md","ASSET","资产文件",858,"https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fskills-index\u002Fassets\u002Fskills-index.template.md",[85,99,127,158,183,199],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":92,"publishedAt":44},"01M71N0PD9RJD79MXQR54DART2","skill-name","Replace with description of the skill and when the agent should use it.","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95,96,33,32,97,98],"skill name","name","with","replace","author","it",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":112,"publishedAt":44},"01M71N0D9N2NSX040S4WST3TG3","validate","Use when the user wants final completion sign-off on any work item — epic, story, bug, or spike: every task in docs\u002Fwork\u002F{work-id}\u002Ftasks.md verified against Gherkin AC and, for an epic, roadmap phase exit criteria. Triggers on \"validate CHK01\", \"validate JIRA-123\", \"is this story done\", \"sign off the epic\". Builds an acceptance matrix with evidence, updates task and work-item status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or the technical design (tdd).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate\u002FSKILL.md",[105,108,111],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[101,113,114,115,116,40,117,118,36,119,120,121,122,32,123,124,125,30,29,126],"back","branch","sprint","code review","design","remote","MCP","writing","acceptance","roadmap","updates","done","Bash","drafting",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":140,"publishedAt":44},"01M71N056DQWSSSYHSWYF7MNM6","ux-design-review","Use when the user wants a UX or design review of implemented UI — components, pages, or flows — against its design source, covering accessibility (WCAG 2.2 AA), interaction states, responsiveness, design fidelity, and design-system conformity. Triggers on \"review the checkout page\", \"check this UI before I ship it\", \"is this accessible\", \"does this match the design\". Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Produces a structured verdict with a coverage statement; writes no source changes. Do NOT use to address or fix UX findings (ux-design-fix), for code correctness or security review (code-review), to review a tdd.md document (docs-review), or to implement features (implement).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux-design-review\u002FSKILL.md",[133,134,135],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[117,141,142,143,144,145,146,114,147,148,149,150,119,151,152,153,154,155,156,157],"ux design review","review","ux","ux design","design review","reviews","figma","browser mcp","static","fix","URL","components","server","interaction","security review","figma mcp","read",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":170,"publishedAt":44},"01M71MZV7G5S97AVBNRSR60NAS","ux-design-fix","Use when the user wants to change how existing UI looks or behaves — fix spacing, colour, layout, states, responsiveness, or accessibility on a component, page, or flow. Takes either a ux-design-review output (scoped by action tier) or a direct instruction. Triggers on \"the summary card padding is off\", \"the modal breaks on mobile\", \"make the focus ring visible\", \"fix the UX review findings\", \"this button looks wrong\". Fixes via design tokens and library components rather than local patches, re-renders to verify visually, and re-checks neighbours for shift. Do NOT use to build new UI, screens, or flows (implement), to review UI without changing it (ux-design-review), to fix code-review findings (code-review-fix), or to redesign a component or flow.","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fux-design-fix\u002FSKILL.md",[164,165,166,169],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":167,"categoryName":168,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},[150,117,143,171,144,172,148,173,174,175,176,177,178,179,180,181,119,182,32,125],"ux design fix","design fix","states","project","re","review findings","card","flows","local","ux-design","new","either",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":44},"01M71MZNT1G9Q83P374S8KCPTY","tdd","Use when the user wants a technical design document (TDD) for any work item — epic, story, bug, or spike — at docs\u002Fwork\u002F{work-id}\u002Ftdd.md, in skeleton or full mode. Pass a work item ID (CHK01, or a Linear\u002FJira\u002FGitHub key like JIRA-123). Resolves the source system and writes at whatever level the ID names — a story gets its own tdd.md beside its parent epic's, not nested inside it. Cite solution.md — do not re-narrate architecture. Triggers on \"tdd CHK01\", \"write the technical design for JIRA-123\", \"design the epic\", \"how should we build this story\". For reviewing an existing tdd.md, use docs-review instead. Do NOT use for test-driven development — writing a failing test first, red\u002Fgreen\u002Frefactor, or any test-authoring task is implement. Do NOT use to write the breakdown itself — stories, tasks, or sub-tasks (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[189,190],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[185,113,192,193,175,41,194,195,117,118,119,120,32,125,30,29,196,142,197,198],"test-driven","green","failing","skeleton","architecture","notes","work",{"skillNo":200,"name":29,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":208,"publishedAt":44},"01M71MZCPYDVZQCS12F54SJHHS","Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic into stories and tasks with Gherkin acceptance criteria, a story into sub-tasks, or an external spec, RFC, or PRD into both in one pass. Resolves the work item's source system (Linear, Jira, GitHub\u002FGitLab issues, or filesystem) and its type first. Writes docs\u002Fproduct\u002Fbacklog.md and docs\u002Fwork\u002F{work-id}\u002Ftasks.md, or the tracker directly when one is resolved. Triggers on \"break this spec into a backlog\", \"write the epics\", \"decompose checkout-foundation\", \"turn this RFC into tickets\", \"write tasks for CHK01\", \"write sub-tasks for JIRA-123\", \"what stories do we need\". EARS with --ears. Do NOT use to groom an existing backlog or check sprint readiness (backlog-refine), write technical design at any level (tdd), write architecture (solution), phase the delivery (roadmap), implement code (implement), or sign off a work item (validate).","https:\u002F\u002Fgithub.com\u002Fcarinyadigital\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftasks\u002FSKILL.md",[204,205],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":206,"categoryName":207,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000031","产品经理",[29,113,115,209,210,117,211,118,119,121,122,32,125,30,196,212,197,198,213,214],"checkout","issues","gherkin acceptance criteria","phase","solution","gitlab"]