bmad-cis-design-thinking
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"
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- bmad-cis-design-thinking
- description
- 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"
02 资源文件 3
- 其他customize.toml1.6 KB
- 资产文件design-methods.csv6.3 KB
- 参考文档template.md1.2 KB
03 SKILL.md 正文
Design Thinking Workflow
Goal: Guide human-centered design through empathy, definition, ideation, prototyping, and testing.
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.
Conventions
- Bare paths (e.g.
template.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
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:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
Any 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.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat 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.
Step 4: Load Config
Load config from {project-root}/_bmad/cis/config.yaml and resolve:
output_folderuser_namecommunication_languagedateas the system-generated current datetime
Step 5: Greet the User
Greet {user_name}, speaking in {communication_language}.
Step 6: Execute Append Steps
Execute each entry in {workflow.activation_steps_append} in order.
Activation is complete. Begin the workflow below.
Paths
template_file=./template.mddesign_methods_file=./design-methods.csvdefault_output_file={output_folder}/design-thinking-{date}.md
Inputs
- If the caller provides context via the data attribute, load it before workflow Step 1 and use it to ground the session.
- Load and understand the full contents of
{design_methods_file}before workflow Step 2. - Use
{template_file}as the structure when writing{default_output_file}.
Behavioral Constraints
- Do not give time estimates.
- After every
<template-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.
Facilitation Principles
- Keep users at the center of every decision.
- Encourage divergent thinking before convergent action.
- Make ideas tangible quickly; prototypes beat discussion.
- Treat failure as feedback.
- Test with real users rather than assumptions.
- Balance empathy with momentum.
Execution
<workflow>
<step n="1" goal="Gather context and define design challenge"> Ask the user about their design challenge:
- What problem or opportunity are you exploring?
- Who are the primary users or stakeholders?
- What constraints exist (time, budget, technology)?
- What does success look like for this project?
- What existing research or context should we consider?
Load any context data provided via the data attribute.
Create a clear design challenge statement.
<template-output>design_challenge</template-output> <template-output>challenge_statement</template-output> </step>
<step n="2" goal="EMPATHIZE - Build understanding of users"> Guide the user through empathy-building activities. Explain in your own voice why deep empathy with users is essential before jumping to solutions.
Review empathy methods from {design_methods_file} for the empathize phase and select 3-5 methods that fit the design challenge context. Consider:
- Available resources and access to users
- Time constraints
- Type of product or service being designed
- Depth of understanding needed
Offer 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.
Help gather and synthesize user insights:
- What did users say, think, do, and feel?
- What pain points emerged?
- What surprised you?
- What patterns do you see?
<template-output>user_insights</template-output> <template-output>key_observations</template-output> <template-output>empathy_map</template-output> </step>
<step n="3" goal="DEFINE - Frame the problem clearly"> <energy-checkpoint> Check in: "We've gathered rich user insights. How are you feeling? Ready to synthesize them into problem statements?" </energy-checkpoint>
Transform observations into actionable problem statements.
Guide the user through problem framing:
- Create a Point of View statement: "[User type] needs [need] because [insight]"
- Generate "How Might We" questions that open solution space
- Identify key insights and opportunity areas
Ask probing questions:
- What's the real problem we're solving?
- Why does this matter to users?
- What would success look like for them?
- What assumptions are we making?
<template-output>pov_statement</template-output> <template-output>hmw_questions</template-output> <template-output>problem_insights</template-output> </step>
<step n="4" goal="IDEATE - Generate diverse solutions"> Facilitate creative solution generation. Explain in your own voice the importance of divergent thinking and deferring judgment during ideation.
Review ideation methods from {design_methods_file} for the ideate phase and select 3-5 methods that fit the context. Consider:
- Group versus individual ideation
- Time available
- Problem complexity
- Team creativity comfort level
Offer the selected methods with brief descriptions of when each works best.
Walk through the chosen method or methods:
- Generate at least 15-30 ideas
- Build on others' ideas
- Go for wild and practical
- Defer judgment
Help cluster and select top concepts:
- Which ideas excite you most?
- Which ideas address the core user need?
- Which ideas are feasible given the constraints?
- Select 2-3 ideas to prototype
<template-output>ideation_methods</template-output> <template-output>generated_ideas</template-output> <template-output>top_concepts</template-output> </step>
<step n="5" goal="PROTOTYPE - Make ideas tangible"> <energy-checkpoint> Check in: "We've generated lots of ideas. How is your energy for making some of them tangible through prototyping?" </energy-checkpoint>
Guide 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.
Review prototyping methods from {design_methods_file} for the prototype phase and select 2-4 methods that fit the solution type. Consider:
- Physical versus digital product
- Service versus product
- Available materials and tools
- What needs to be tested
Offer the selected methods with guidance on fit.
Help define the prototype:
- What's the minimum needed to test your assumptions?
- What are you trying to learn?
- What should users be able to do?
- What can you fake versus build?
<template-output>prototype_approach</template-output> <template-output>prototype_description</template-output> <template-output>features_to_test</template-output> </step>
<step n="6" goal="TEST - Validate with users"> Design the validation approach and capture learnings. Explain in your own voice why observing what users do matters more than what they say.
Help plan testing:
- Who will you test with? Aim for 5-7 users.
- What tasks will they attempt?
- What questions will you ask?
- How will you capture feedback?
Guide feedback collection:
- What worked well?
- Where did they struggle?
- What surprised them, and you?
- What questions arose?
- What would they change?
Synthesize learnings:
- What assumptions were validated or invalidated?
- What needs to change?
- What should stay?
- What new insights emerged?
<template-output>testing_plan</template-output> <template-output>user_feedback</template-output> <template-output>key_learnings</template-output> </step>
<step n="7" goal="Plan next iteration"> <energy-checkpoint> Check in: "Great work. How is your energy for final planning and defining next steps?" </energy-checkpoint>
Define clear next steps and success criteria.
Based on testing insights:
- What refinements are needed?
- What's the priority action?
- Who needs to be involved?
- What sequence makes sense?
- How will you measure success?
Determine the next cycle:
- Do you need more empathy work?
- Should you reframe the problem?
- Are you ready to refine the prototype?
- Is it time to pilot with real users?
<template-output>refinements</template-output> <template-output>action_items</template-output> <template-output>success_metrics</template-output>
<action>Run: python3 {project-root}/_bmad/scripts/resolve_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.</action>
</step>
</workflow>
04 同仓库更多 Skills
tk-studio-track
Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to "Blocked - Awaiting User" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to "Done"); `reply` posts the owner's answer (or "Done.") with the owner's host-only token and moves the issue to "Block Resolved"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says "block this story", "tk track block", "put it in the owner's inbox", "reply to the blocked issue", "validate the resolution", or a supervisor or engagement payload names this skill.
tk-studio-session
Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says "hand off this run", "tk session", "resume the run", or a boundary/budget trigger says the session must split.
tk-studio-research
Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says "run the ecosystem watch", "tk research", or a research job's invoke-skill directive names this skill.
tk-studio-report
One-verb human defect report — "the skill did the wrong thing" — recorded as a report event in the local measurement ledger. Use when the user says "tk report", "report a defect", "that skill misbehaved", or "log a studio issue".
tk-studio-playable-judge
The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says "judge the playable frames".
tk-studio-plan-sync
Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says "sync the plan", "normalize planning artifacts", "tk plan sync", or after stock BMad planning flows produce or change epics/stories.