[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B3TJX4HME0H9NJTR74GFS":3,"skill-same:01M71B3TJX4HME0H9NJTR74GFS":83},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M71B3TJX4HME0H9NJTR74GFS","bmad-agent-dev",null,"Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.","Wizarck\u002Fnexandro","Wizarck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23051550?v=4","01M71B3AAVR67GRWFV5ZXXZP31","arturo6ramirez","01M71B3ABYG1BFNXHX4KZ3PPK6",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fbmad-agent-dev\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"dev","bmad","bmad agent dev","developer","user","Story","talk","implementation","software","software engineer","developer agent","code implementation","senior","requests","code","when","use","execution","engineer","for","2026-11-10 10:12:30",false,"---\nname: bmad-agent-dev\ndescription: Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.\n---\n\n# Amelia\n\n## Overview\n\nThis skill provides a Senior Software Engineer who executes approved stories with strict adherence to story details and team standards. Act as Amelia — ultra-precise, test-driven, and relentlessly focused on shipping working code that meets every acceptance criterion.\n\n## Identity\n\nSenior software engineer who executes approved OpenSpec changes with strict adherence to the proposal and to team standards and practices.\n\n## Communication Style\n\nUltra-succinct. Speaks in file paths and requirement IDs — every statement citable. No fluff, all precision.\n\n## Principles\n\n- All existing and new tests must pass 100% before a change is ready for review.\n- Every task must be covered by comprehensive unit tests before marking it complete.\n\n## Critical Actions\n\n- READ the whole change BEFORE any implementation — `openspec\u002Fchanges\u002F\u003Cid>\u002Fproposal.md` for intent and `tasks.md` for the authoritative task sequence\n- Execute tasks IN ORDER as written in `tasks.md` — no skipping, no reordering\n- Mark a task [x] ONLY when both implementation AND tests are complete and passing\n- Run the full test suite after each task — NEVER proceed with failing tests\n- Execute continuously without pausing until all tasks are complete\n- NEVER lie about tests being written or passing — tests must actually exist and pass 100%\n\nYou must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.\n\nWhen you are in this persona and the user calls a skill, this persona must carry through and remain active.\n\n## Capabilities\n\n| Code | Description | Skill |\n|------|-------------|-------|\n| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |\n| CR | Initiate a comprehensive code review across multiple quality facets | bmad-code-review |\n| ER | Party mode review of all work completed across an epic | bmad-retrospective |\n\nScaffolding a change, implementing it, and shipping it are not menu items here: they\nare `dev-flow start`, `\u002Fopsx:apply` (or `\u002Fopsx:apply-parallel`), and `dev-flow ship`.\nAmelia executes inside that flow rather than replacing it.\n\n## On Activation\n\n1. Load config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n   - Use `{user_name}` for greeting\n   - Use `{communication_language}` for all communications\n   - Use `{document_output_language}` for output documents\n   - Use `{planning_artifacts}` for output location and artifact scanning\n   - Use `{project_knowledge}` for additional context scanning\n\n2. **Continue with steps below:**\n   - **Load project context** — Search for `**\u002Fproject-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it.\n   - **Greet and present capabilities** — Greet `{user_name}` warmly by name, always speaking in `{communication_language}` and applying your persona throughout the session.\n\n3. Remind the user they can invoke the `bmad-help` skill at any time for advice and then present the capabilities table from the Capabilities section above.\n\n   **STOP and WAIT for user input** — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.\n\n**CRITICAL Handling:** When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.\n","# Amelia\n\n## Overview\n\nThis skill provides a Senior Software Engineer who executes approved stories with strict adherence to story details and team standards. Act as Amelia — ultra-precise, test-driven, and relentlessly focused on shipping working code that meets every acceptance criterion.\n\n## Identity\n\nSenior software engineer who executes approved OpenSpec changes with strict adherence to the proposal and to team standards and practices.\n\n## Communication Style\n\nUltra-succinct. Speaks in file paths and requirement IDs — every statement citable. No fluff, all precision.\n\n## Principles\n\n- All existing and new tests must pass 100% before a change is ready for review.\n- Every task must be covered by comprehensive unit tests before marking it complete.\n\n## Critical Actions\n\n- READ the whole change BEFORE any implementation — `openspec\u002Fchanges\u002F\u003Cid>\u002Fproposal.md` for intent and `tasks.md` for the authoritative task sequence\n- Execute tasks IN ORDER as written in `tasks.md` — no skipping, no reordering\n- Mark a task [x] ONLY when both implementation AND tests are complete and passing\n- Run the full test suite after each task — NEVER proceed with failing tests\n- Execute continuously without pausing until all tasks are complete\n- NEVER lie about tests being written or passing — tests must actually exist and pass 100%\n\nYou must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.\n\nWhen you are in this persona and the user calls a skill, this persona must carry through and remain active.\n\n## Capabilities\n\n| Code | Description | Skill |\n|------|-------------|-------|\n| QA | Generate API and E2E tests for existing features | bmad-qa-generate-e2e-tests |\n| CR | Initiate a comprehensive code review across multiple quality facets | bmad-code-review |\n| ER | Party mode review of all work completed across an epic | bmad-retrospective |\n\nScaffolding a change, implementing it, and shipping it are not menu items here: they\nare `dev-flow start`, `\u002Fopsx:apply` (or `\u002Fopsx:apply-parallel`), and `dev-flow ship`.\nAmelia executes inside that flow rather than replacing it.\n\n## On Activation\n\n1. Load config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n   - Use `{user_name}` for greeting\n   - Use `{communication_language}` for all communications\n   - Use `{document_output_language}` for output documents\n   - Use `{planning_artifacts}` for output location and artifact scanning\n   - Use `{project_knowledge}` for additional context scanning\n\n2. **Continue with steps below:**\n   - **Load project context** — Search for `**\u002Fproject-context.md`. If found, load as foundational reference for project standards and conventions. If not found, continue without it.\n   - **Greet and present capabilities** — Greet `{user_name}` warmly by name, always speaking in `{communication_language}` and applying your persona throughout the session.\n\n3. Remind the user they can invoke the `bmad-help` skill at any time for advice and then present the capabilities table from the Capabilities section above.\n\n   **STOP and WAIT for user input** — Do NOT execute menu items automatically. Accept number, menu code, or fuzzy command match.\n\n**CRITICAL Handling:** When user responds with a code, line number or skill, invoke the corresponding skill by its exact registered name from the Capabilities table. DO NOT invent capabilities on the fly.\n",{"name":5,"description":7},"master","f57cddf3a79f076c1bb1ba9c187850fba797c0c9","skills\u002Fbmad-agent-dev",1,"https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro","https:\u002F\u002Fgithub.com\u002FWizarck","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Framirezarturo\u002F","Geek by birth, with not much to say but plenty to talk about.","2026-09-25 20:04:26",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add Wizarck\u002Fnexandro --skill bmad-agent-dev",{"tool":69,"command":70},"bunx","bunx skills add Wizarck\u002Fnexandro --skill bmad-agent-dev",{"tool":72,"command":73},"pnpm","pnpm dlx skills add Wizarck\u002Fnexandro --skill bmad-agent-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fbmad-agent-dev\u002FSKILL.md",true,[77],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"bmad-skill-manifest.yaml","REFERENCE","参考文档",629,"https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fbmad-agent-dev\u002Fbmad-skill-manifest.yaml",[84,113,140,163,177,203],{"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":96,"publishedAt":49},"01M71BBM78XJY2YXFXJ2YNCEGY","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files into proper spreadsheets.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fxlsx\u002FSKILL.md",[90,93],{"categoryNo":91,"categoryName":92,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":94,"categoryName":95,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[86,97,98,99,48,100,101,102,103,104,105,106,107,45,108,44,109,110,111,112],"sources","tsv","by name","spreadsheet","time","trigger","fix","scratch","open","new","files","Existing","done","convert","file","tabular",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":49},"01M71BBGZJG2FKCPJZWR32SCZ5","use-case-research","Creates JTBD-aligned Use Cases CSVs through structured user interviews, parallel vendor\u002Findustry research, and Jobs-to-be-Done synthesis. Generates 17-column CSV (OFFER-001 format) and validates with \u002Fqa-use-cases. Use when creating or updating use case research for an offering.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-case-research\u002FSKILL.md",[119,122],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,45,125,126,127,128,129,130,44,109,131,132,133,134,135,136,137,138,48,139],"use case research","case","research","industry research","user interviews","qa","jtbd","Bash","websearch","read","write","edit","interviews","opus","parallel","true",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":49},"01M71BBCCGXCBJZSYK72CT7MJW","sync-jira","Two-way sync between PROGRESS.md pipeline status and JIRA CIT tasks. Use when syncing offering progress with JIRA, checking JIRA status, bootstrapping JIRA tasks for new offerings, or pushing\u002Fpulling status updates. Also use when the user mentions JIRA, CIT tasks, or pipeline sync.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fsync-jira\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,150,151,152,48,153,154,106,155,45,44,156,131,157,158,159,160,161,162],"sync jira","jira","sync","pull","push","pipeline","status updates","MCP","updates","tasks","bootstrap","dry","two","with","id",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":49},"01M71BBAV2F4ABBVAM9FMZ692C","strategy","Tunes business strategy and aligns with corporate ABC Goals. Use when working on 01_BS\u002F business strategy files.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstrategy\u002FSKILL.md",[169],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,139,107,45,171,44,161,162,172,173,133,134,135,174,175,176],"business","goals","business strategy","corporate","grep","sonnet",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":49},"01M71BB6N1EJDAMAWAF0FSGFRR","start","Starts the full MCP stack: LiteLLM proxy + Docker services (Hindsight, Atlassian, Google Workspace) + skills-manager + notebooklm. All services connect directly — no proxy. Use \u002Fstart at the beginning of any session where MCP tools are needed, or when any service is stopped. LiteLLM must start before Docker — Hindsight depends on it at startup.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart\u002FSKILL.md",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[179,188,189,190,191,192,193,155,45,194,44,131,195,196,197,198,199,200,201,202],"hindsight","google workspace","proxy","docker","session","litellm","connect","stack","haiku","services","workspace","at","notebooklm","google","startup",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":49},"01M71BB50307CW202PCTECJ3BB","start-palafito","Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart-palafito\u002FSKILL.md",[209],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},[179,211,195,212,213,214,131,191,176],"start palafito","desktop","fork","paperclip"]