[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PQZ4KBF563MC4M96TYHN3":3,"skill-same:01M71PQZ4KBF563MC4M96TYHN3":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71PQZ4KBF563MC4M96TYHN3","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\"","developAgent\u002Fbmad-start","developAgent","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264530239?v=4","01M71J8X6CY24V5ZZHFGETRMSW","01M71J8X739FS28DGQAAY7V4QR",1,"MIT","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbmad-cis-design-thinking\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"design","bmad cis design thinking","cis","thinking","bmad","design thinking","run","user","guide","use","Empathy","human","driven","processes","apply","when","2026-11-10 13:02:02",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","1907bbe850fb749efa8b499b8da7ebb78a663519",".pi\u002Fskills\u002Fbmad-cis-design-thinking",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add developAgent\u002Fbmad-start --skill bmad-cis-design-thinking",{"tool":62,"command":63},"bunx","bunx skills add developAgent\u002Fbmad-start --skill bmad-cis-design-thinking",{"tool":65,"command":66},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill bmad-cis-design-thinking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbmad-cis-design-thinking\u002FSKILL.md",true,[70,76,82],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"customize.toml","OTHER","其他",1654,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbmad-cis-design-thinking\u002Fcustomize.toml",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"design-methods.csv","ASSET","资产文件",6412,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbmad-cis-design-thinking\u002Fdesign-methods.csv",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"template.md","REFERENCE","参考文档",1278,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.pi\u002Fskills\u002Fbmad-cis-design-thinking\u002Ftemplate.md",[89,107,136,154,168,194],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":98,"publishedAt":44},"01M71R3M9DJTTY0ARFQ6K04NMP","gds-correct-course","Manage significant changes during sprint execution. Use when the user says \"correct course\" or \"propose sprint change\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-correct-course\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000039","教师与教育",[99,100,101,35,102,103,43,37,104,105,106],"gds correct course","course","correct","changes","change","execution","manage","sprint",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":119,"publishedAt":44},"01M71R3GENSFD1A1XVZTTQG1KF","gds-code-review","Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says \"run code review\" or \"review this code\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-code-review\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":117,"categoryName":118,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[120,121,122,123,124,102,125,126,34,127,128,129,130,43,131,37,132,133,134,135],"code review","code","review","gds code review","categories","triage","review code","parallel","case","with","run code","acceptance","edge","actionable","layers","hunter",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":44},"01M71R3DD098MQRD6F8S4GG0AW","gds-check-implementation-readiness","Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says \"check readiness\" or \"implementation readiness\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-check-implementation-readiness\u002FSKILL.md",[],[143,144,145,146,147,148,35,149,150,151,152,43,37,153],"check","readiness","Implementation Readiness","gds check implementation readiness","implementation","check readiness","Production","ux","verify","architecture","alignment",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":44},"01M71R3ACAA1G0NVQ330JQNJPK","gds-brainstorm-game","Facilitate game brainstorming sessions with game-specific techniques. Use when the user says \"brainstorm game\" or \"game ideas\"","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-brainstorm-game\u002FSKILL.md",[],[161,162,163,35,164,129,43,37,165,166,167],"gds brainstorm game","game","brainstorm","brainstorming","techniques","sessions","ideas",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":44},"01M71R377MJ6WJTTFARGKH3HX7","gds-agent-tech-writer","Technical documentation specialist and knowledge curator for game projects. Use when the user asks to talk to Paige or requests the Technical Writer.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-tech-writer\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[178,179,180,181,37,182,183,184,185,43,35,186,187,188,189,190,191,192,162,193],"gds agent tech writer","tech","writer","technical writer","technical","knowledge","for","projects","technical documentation","talk","specialist","documentation specialist","knowledge curator","requests","documentation","curator",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":44},"01M71R34RGT2ZX3TSFA2CRT0NC","gds-agent-game-solo-dev","Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.rovodev\u002Fskills\u002Fgds-agent-game-solo-dev\u002FSKILL.md",[200],{"categoryNo":175,"categoryName":176,"taxonomyType":20,"taxonomyTypeDesc":21},[202,162,203,204,205,206,35,187,191,207,208,43,37,209,184,210,211],"solo","gds agent game solo dev","dev","flow","developer","RAPID","game developer","prototyping","development","quick"]