[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CENP131PTC96YPRX9F4RQG":3,"skill-same:01M6CENP131PTC96YPRX9F4RQG":95},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6CENP131PTC96YPRX9F4RQG","bmad-cis-design-thinking",null,"Guide human-centered design processes using empathy-driven methodologies. Use when the user says \"lets run design thinking\" or \"I want to apply design thinking\"","amalik\u002Fconvoke-agents","amalik","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90366?v=4","01M6CEG0NCQPX8YRE9K9986FXF","Amalik Amriou","01M6CEG0SR51MB08ENNJWZNJDM",69,"MIT","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36],"design","bmad cis design thinking","cis","run","user","guide","use","Empathy","2026-11-10 10:12:30",false,"---\nname: bmad-cis-design-thinking\ndescription: 'Guide human-centered design processes using empathy-driven methodologies. Use when the user says \"lets run design thinking\" or \"I want to apply design thinking\"'\n---\n\n# Design Thinking Workflow\n\n**Goal:** Guide human-centered design through empathy, definition, ideation, prototyping, and testing.\n\n**Your Role:** You are a human-centered design facilitator. Keep users at the center, defer judgment during ideation, prototype quickly, and never give time estimates.\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. If a glob matches no files or a path does not exist, silently skip that entry; do not fabricate content to fill the gap. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fcis\u002Fconfig.yaml` and resolve:\n\n- `output_folder`\n- `user_name`\n- `communication_language`\n- `date` as the system-generated current datetime\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `template_file` = `.\u002Ftemplate.md`\n- `design_methods_file` = `.\u002Fdesign-methods.csv`\n- `default_output_file` = `{output_folder}\u002Fdesign-thinking-{date}.md`\n\n## Inputs\n\n- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.\n- Load and understand the full contents of `{design_methods_file}` before workflow Step 2.\n- Use `{template_file}` as the structure when writing `{default_output_file}`.\n\n## Behavioral Constraints\n\n- Do not give time estimates.\n- After every `\u003Ctemplate-output>`, immediately save the current artifact to `{default_output_file}`, show a clear checkpoint separator, display the generated content, present options `[a] Advanced Elicitation`, `[c] Continue`, `[p] Party-Mode`, `[y] YOLO`, and wait for the user's response before proceeding.\n\n## Facilitation Principles\n\n- Keep users at the center of every decision.\n- Encourage divergent thinking before convergent action.\n- Make ideas tangible quickly; prototypes beat discussion.\n- Treat failure as feedback.\n- Test with real users rather than assumptions.\n- Balance empathy with momentum.\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Gather context and define design challenge\">\nAsk the user about their design challenge:\n\n- What problem or opportunity are you exploring?\n- Who are the primary users or stakeholders?\n- What constraints exist (time, budget, technology)?\n- What does success look like for this project?\n- What existing research or context should we consider?\n\nLoad any context data provided via the data attribute.\n\nCreate a clear design challenge statement.\n\n\u003Ctemplate-output>design_challenge\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>challenge_statement\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"EMPATHIZE - Build understanding of users\">\nGuide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions.\n\nReview empathy methods from `{design_methods_file}` for the `empathize` phase and select 3-5 methods that fit the design challenge context. Consider:\n\n- Available resources and access to users\n- Time constraints\n- Type of product or service being designed\n- Depth of understanding needed\n\nOffer the selected methods with guidance on when each works best, then ask which methods the user has used or can use, or make a recommendation based on the specific challenge.\n\nHelp gather and synthesize user insights:\n\n- What did users say, think, do, and feel?\n- What pain points emerged?\n- What surprised you?\n- What patterns do you see?\n\n\u003Ctemplate-output>user_insights\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_observations\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>empathy_map\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"DEFINE - Frame the problem clearly\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've gathered rich user insights. How are you feeling? Ready to synthesize them into problem statements?\"\n\u003C\u002Fenergy-checkpoint>\n\nTransform observations into actionable problem statements.\n\nGuide the user through problem framing:\n\n1. Create a Point of View statement: \"[User type] needs [need] because [insight]\"\n2. Generate \"How Might We\" questions that open solution space\n3. Identify key insights and opportunity areas\n\nAsk probing questions:\n\n- What's the real problem we're solving?\n- Why does this matter to users?\n- What would success look like for them?\n- What assumptions are we making?\n\n\u003Ctemplate-output>pov_statement\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>hmw_questions\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>problem_insights\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"IDEATE - Generate diverse solutions\">\nFacilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation.\n\nReview ideation methods from `{design_methods_file}` for the `ideate` phase and select 3-5 methods that fit the context. Consider:\n\n- Group versus individual ideation\n- Time available\n- Problem complexity\n- Team creativity comfort level\n\nOffer the selected methods with brief descriptions of when each works best.\n\nWalk through the chosen method or methods:\n\n- Generate at least 15-30 ideas\n- Build on others' ideas\n- Go for wild and practical\n- Defer judgment\n\nHelp cluster and select top concepts:\n\n- Which ideas excite you most?\n- Which ideas address the core user need?\n- Which ideas are feasible given the constraints?\n- Select 2-3 ideas to prototype\n\n\u003Ctemplate-output>ideation_methods\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>generated_ideas\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>top_concepts\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"PROTOTYPE - Make ideas tangible\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've generated lots of ideas. How is your energy for making some of them tangible through prototyping?\"\n\u003C\u002Fenergy-checkpoint>\n\nGuide creation of low-fidelity prototypes for testing. Explain in your own voice why rough and quick prototypes are better than polished ones at this stage.\n\nReview prototyping methods from `{design_methods_file}` for the `prototype` phase and select 2-4 methods that fit the solution type. Consider:\n\n- Physical versus digital product\n- Service versus product\n- Available materials and tools\n- What needs to be tested\n\nOffer the selected methods with guidance on fit.\n\nHelp define the prototype:\n\n- What's the minimum needed to test your assumptions?\n- What are you trying to learn?\n- What should users be able to do?\n- What can you fake versus build?\n\n\u003Ctemplate-output>prototype_approach\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>prototype_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>features_to_test\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"TEST - Validate with users\">\nDesign the validation approach and capture learnings. Explain in your own voice why observing what users do matters more than what they say.\n\nHelp plan testing:\n\n- Who will you test with? Aim for 5-7 users.\n- What tasks will they attempt?\n- What questions will you ask?\n- How will you capture feedback?\n\nGuide feedback collection:\n\n- What worked well?\n- Where did they struggle?\n- What surprised them, and you?\n- What questions arose?\n- What would they change?\n\nSynthesize learnings:\n\n- What assumptions were validated or invalidated?\n- What needs to change?\n- What should stay?\n- What new insights emerged?\n\n\u003Ctemplate-output>testing_plan\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>user_feedback\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_learnings\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"7\" goal=\"Plan next iteration\">\n\u003Cenergy-checkpoint>\nCheck in: \"Great work. How is your energy for final planning and defining next steps?\"\n\u003C\u002Fenergy-checkpoint>\n\nDefine clear next steps and success criteria.\n\nBased on testing insights:\n\n- What refinements are needed?\n- What's the priority action?\n- Who needs to be involved?\n- What sequence makes sense?\n- How will you measure success?\n\nDetermine the next cycle:\n\n- Do you need more empathy work?\n- Should you reframe the problem?\n- Are you ready to refine the prototype?\n- Is it time to pilot with real users?\n\n\u003Ctemplate-output>refinements\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>action_items\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>success_metrics\u003C\u002Ftemplate-output>\n\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n","# Design Thinking Workflow\n\n**Goal:** Guide human-centered design through empathy, definition, ideation, prototyping, and testing.\n\n**Your Role:** You are a human-centered design facilitator. Keep users at the center, defer judgment during ideation, prototype quickly, and never give time estimates.\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. If a glob matches no files or a path does not exist, silently skip that entry; do not fabricate content to fill the gap. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fcis\u002Fconfig.yaml` and resolve:\n\n- `output_folder`\n- `user_name`\n- `communication_language`\n- `date` as the system-generated current datetime\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `template_file` = `.\u002Ftemplate.md`\n- `design_methods_file` = `.\u002Fdesign-methods.csv`\n- `default_output_file` = `{output_folder}\u002Fdesign-thinking-{date}.md`\n\n## Inputs\n\n- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.\n- Load and understand the full contents of `{design_methods_file}` before workflow Step 2.\n- Use `{template_file}` as the structure when writing `{default_output_file}`.\n\n## Behavioral Constraints\n\n- Do not give time estimates.\n- After every `\u003Ctemplate-output>`, immediately save the current artifact to `{default_output_file}`, show a clear checkpoint separator, display the generated content, present options `[a] Advanced Elicitation`, `[c] Continue`, `[p] Party-Mode`, `[y] YOLO`, and wait for the user's response before proceeding.\n\n## Facilitation Principles\n\n- Keep users at the center of every decision.\n- Encourage divergent thinking before convergent action.\n- Make ideas tangible quickly; prototypes beat discussion.\n- Treat failure as feedback.\n- Test with real users rather than assumptions.\n- Balance empathy with momentum.\n\n## Execution\n\n\u003Cworkflow>\n\n\u003Cstep n=\"1\" goal=\"Gather context and define design challenge\">\nAsk the user about their design challenge:\n\n- What problem or opportunity are you exploring?\n- Who are the primary users or stakeholders?\n- What constraints exist (time, budget, technology)?\n- What does success look like for this project?\n- What existing research or context should we consider?\n\nLoad any context data provided via the data attribute.\n\nCreate a clear design challenge statement.\n\n\u003Ctemplate-output>design_challenge\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>challenge_statement\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"2\" goal=\"EMPATHIZE - Build understanding of users\">\nGuide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions.\n\nReview empathy methods from `{design_methods_file}` for the `empathize` phase and select 3-5 methods that fit the design challenge context. Consider:\n\n- Available resources and access to users\n- Time constraints\n- Type of product or service being designed\n- Depth of understanding needed\n\nOffer the selected methods with guidance on when each works best, then ask which methods the user has used or can use, or make a recommendation based on the specific challenge.\n\nHelp gather and synthesize user insights:\n\n- What did users say, think, do, and feel?\n- What pain points emerged?\n- What surprised you?\n- What patterns do you see?\n\n\u003Ctemplate-output>user_insights\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_observations\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>empathy_map\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"3\" goal=\"DEFINE - Frame the problem clearly\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've gathered rich user insights. How are you feeling? Ready to synthesize them into problem statements?\"\n\u003C\u002Fenergy-checkpoint>\n\nTransform observations into actionable problem statements.\n\nGuide the user through problem framing:\n\n1. Create a Point of View statement: \"[User type] needs [need] because [insight]\"\n2. Generate \"How Might We\" questions that open solution space\n3. Identify key insights and opportunity areas\n\nAsk probing questions:\n\n- What's the real problem we're solving?\n- Why does this matter to users?\n- What would success look like for them?\n- What assumptions are we making?\n\n\u003Ctemplate-output>pov_statement\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>hmw_questions\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>problem_insights\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"4\" goal=\"IDEATE - Generate diverse solutions\">\nFacilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation.\n\nReview ideation methods from `{design_methods_file}` for the `ideate` phase and select 3-5 methods that fit the context. Consider:\n\n- Group versus individual ideation\n- Time available\n- Problem complexity\n- Team creativity comfort level\n\nOffer the selected methods with brief descriptions of when each works best.\n\nWalk through the chosen method or methods:\n\n- Generate at least 15-30 ideas\n- Build on others' ideas\n- Go for wild and practical\n- Defer judgment\n\nHelp cluster and select top concepts:\n\n- Which ideas excite you most?\n- Which ideas address the core user need?\n- Which ideas are feasible given the constraints?\n- Select 2-3 ideas to prototype\n\n\u003Ctemplate-output>ideation_methods\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>generated_ideas\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>top_concepts\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"5\" goal=\"PROTOTYPE - Make ideas tangible\">\n\u003Cenergy-checkpoint>\nCheck in: \"We've generated lots of ideas. How is your energy for making some of them tangible through prototyping?\"\n\u003C\u002Fenergy-checkpoint>\n\nGuide creation of low-fidelity prototypes for testing. Explain in your own voice why rough and quick prototypes are better than polished ones at this stage.\n\nReview prototyping methods from `{design_methods_file}` for the `prototype` phase and select 2-4 methods that fit the solution type. Consider:\n\n- Physical versus digital product\n- Service versus product\n- Available materials and tools\n- What needs to be tested\n\nOffer the selected methods with guidance on fit.\n\nHelp define the prototype:\n\n- What's the minimum needed to test your assumptions?\n- What are you trying to learn?\n- What should users be able to do?\n- What can you fake versus build?\n\n\u003Ctemplate-output>prototype_approach\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>prototype_description\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>features_to_test\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"6\" goal=\"TEST - Validate with users\">\nDesign the validation approach and capture learnings. Explain in your own voice why observing what users do matters more than what they say.\n\nHelp plan testing:\n\n- Who will you test with? Aim for 5-7 users.\n- What tasks will they attempt?\n- What questions will you ask?\n- How will you capture feedback?\n\nGuide feedback collection:\n\n- What worked well?\n- Where did they struggle?\n- What surprised them, and you?\n- What questions arose?\n- What would they change?\n\nSynthesize learnings:\n\n- What assumptions were validated or invalidated?\n- What needs to change?\n- What should stay?\n- What new insights emerged?\n\n\u003Ctemplate-output>testing_plan\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>user_feedback\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>key_learnings\u003C\u002Ftemplate-output>\n\u003C\u002Fstep>\n\n\u003Cstep n=\"7\" goal=\"Plan next iteration\">\n\u003Cenergy-checkpoint>\nCheck in: \"Great work. How is your energy for final planning and defining next steps?\"\n\u003C\u002Fenergy-checkpoint>\n\nDefine clear next steps and success criteria.\n\nBased on testing insights:\n\n- What refinements are needed?\n- What's the priority action?\n- Who needs to be involved?\n- What sequence makes sense?\n- How will you measure success?\n\nDetermine the next cycle:\n\n- Do you need more empathy work?\n- Should you reframe the problem?\n- Are you ready to refine the prototype?\n- Is it time to pilot with real users?\n\n\u003Ctemplate-output>refinements\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>action_items\u003C\u002Ftemplate-output>\n\u003Ctemplate-output>success_metrics\u003C\u002Ftemplate-output>\n\n\u003Caction>Run: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete` — if the resolved value is non-empty, follow it as the final terminal instruction before exiting.\u003C\u002Faction>\n\u003C\u002Fstep>\n\n\u003C\u002Fworkflow>\n",{"name":5,"description":7},"main","2115eb8f78e64732a8310cc2e8372fb7c90fbf26","tests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking",3,"https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents","https:\u002F\u002Fgithub.com\u002Famalik","https:\u002F\u002Famalik.github.io\u002F","Data & AI product lead","2026-11-07 23:16:33",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add amalik\u002Fconvoke-agents --skill bmad-cis-design-thinking",{"tool":57,"command":58},"bunx","bunx skills add amalik\u002Fconvoke-agents --skill bmad-cis-design-thinking",{"tool":60,"command":61},"pnpm","pnpm dlx skills add amalik\u002Fconvoke-agents --skill bmad-cis-design-thinking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking\u002FSKILL.md",true,[65,71,77,83,87,91],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"customize.toml","OTHER","其他",1654,"https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking\u002Fcustomize.toml",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"design-methods.csv","ASSET","资产文件",6412,"https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking\u002Fdesign-methods.csv",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fagile-field-ids.md","REFERENCE","参考文档",2984,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fpackages\u002Fmewkit\u002Fsrc\u002Fmigrate\u002Fmodules\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-jira-fields\u002Freferences\u002Fagile-field-ids.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Ffield-discovery.md",4656,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fpackages\u002Fmewkit\u002Fsrc\u002Fmigrate\u002Fmodules\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-jira-fields\u002Freferences\u002Ffield-discovery.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Ffield-types-reference.md",6816,"https:\u002F\u002Fgithub.com\u002Fngocsangyem\u002FMeowKit\u002Fblob\u002Fmain\u002Fpackages\u002Fmewkit\u002Fsrc\u002Fmigrate\u002Fmodules\u002Fcodex\u002Froot\u002F.agents\u002Fskills\u002Fmk-jira-fields\u002Freferences\u002Ffield-types-reference.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"template.md",1278,"https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcis\u002Fskills\u002Fbmad-cis-design-thinking\u002Ftemplate.md",[96,112,128,142,160,170],{"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":105,"publishedAt":37},"01M6CEPZ2DZXFTGNZJKDCK5PH9","bmad-testarch-atdd","Generate red-phase acceptance test scaffolds using the TDD cycle. Use when the user says \"lets write acceptance tests\" or \"I want to do ATDD\"","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Ftea\u002Fworkflows\u002Ftestarch\u002Fbmad-testarch-atdd\u002FSKILL.md",[102],{"categoryNo":103,"categoryName":104,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[106,107,108,109,110,111,33,35],"bmad testarch atdd","tdd","test","generate","acceptance","write",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":37},"01M6CEPTQ58B7FKX67HVS2HZE8","bmad-create-prd","Create a PRD from scratch. Use when the user says \"lets create a product requirements document\" or \"I want to create a new PRD\"","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcore\u002Ftasks\u002Fbmad-create-prd\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[122,123,124,125,126,127,33,35],"create prd","bmad create prd","prd","create","document","product",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":37},"01M6CEPR5DZM5R114GR67XCP7Z","bmad-shard-doc","Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-shard-doc\u002FSKILL.md",[],[135,136,137,126,138,139,140,141,33,35],"shard","bmad shard doc","doc","files","default","documents","markdown",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":37},"01M6CEPNHE5WR48JRJH6390EMF","bmad-review-edge-case-hunter","Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-review-edge-case-hunter\u002FSKILL.md",[],[149,150,151,35,152,153,154,155,156,157,158,159],"bmad review edge case hunter","edge","review","diffs","adversarial review","code","report","content","analysis","boundary","only",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":37},"01M6CEPK135DVWESJSFN4M34AZ","bmad-review-adversarial-general","Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-review-adversarial-general\u002FSKILL.md",[],[151,167,168,155,35,33,169],"general","bmad review adversarial general","produce",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":37},"01M6CEPG9CYFQYJWH7ECRC3E9G","bmad-party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.","https:\u002F\u002Fgithub.com\u002Famalik\u002Fconvoke-agents\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fportability-project\u002F_bmad\u002Fcore\u002Fskills\u002Fbmad-party-mode\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[180,35,33,181],"bmad party mode","multi-agent"]