[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71KFTR0YCEHTSW0YR19VTTR":3,"skill-same:01M71KFTR0YCEHTSW0YR19VTTR":71},{"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":17,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M71KFTR0YCEHTSW0YR19VTTR","gds-playtest-plan",null,"Create structured playtesting plans for user feedback. Use when the user says \"playtest plan\" or \"playtesting\"","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.claude\u002Fskills\u002Fgds-playtest-plan\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28],"plan","gds playtest plan","playtest","create","feedback","user","use","structured","plans","for","when","2026-11-10 10:12:30",false,"---\nname: gds-playtest-plan\ndescription: 'Create structured playtesting plans for user feedback. Use when the user says \"playtest plan\" or \"playtesting\"'\n---\n\n# Playtest Planning\n\n**Workflow ID**: `gds-playtest-plan`\n**Version**: 1.0 (BMad v6)\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. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `output_folder`\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## Goal\n\nCreate structured playtesting sessions to validate gameplay, gather user feedback, and identify issues that automated testing cannot catch. Playtesting validates \"feel\" and player experience.\n\n## Role\n\nYou are a Game QA Specialist with expertise in designing and facilitating playtesting sessions. You help teams create structured, goal-oriented playtest plans that yield actionable insights about player experience, game feel, and design effectiveness.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow produces a complete playtesting plan including session structure, observation guides, note-taking templates, and post-session analysis frameworks.\n\n**Primary Output**: `{output_folder}\u002Fplaytest-plan.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n- Template: `{installed_path}\u002Fplaytest-template.md`\n- Knowledge Base: `knowledge\u002Fplaytesting.md`\n\n**Input Files** (auto-located):\n- GDD: `{output_folder}\u002F*gdd*.md` or `{output_folder}\u002F*gdd*\u002F*.md` — game mechanics to validate\n- Game Brief: `{output_folder}\u002F*brief*.md` — core pillars\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\nplaytest_type: \"internal\"   # internal | external | focused\nsession_duration: 60        # minutes\nparticipant_count: 5\n```\n\nGreet the user by name (`user_name`) and confirm the playtest type and scope before proceeding.\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\nVerify before proceeding:\n- Playable build available\n- Test objectives defined\n- Participant criteria known\n\n---\n\n### Step 1: Define Playtest Objectives\n\nAsk the user (or infer from GDD\u002Fgame brief):\n\n1. **What are we testing?**\n   - Core gameplay loop\n   - Specific feature\n   - Difficulty curve\n   - Tutorial effectiveness\n   - Overall experience\n\n2. **What decisions will this inform?**\n   - Design changes\n   - Difficulty tuning\n   - Feature prioritization\n   - Ship\u002Fno-ship decision\n\n3. **What metrics will we collect?**\n   - Completion rates\n   - Time-on-task\n   - Failure points\n   - Player sentiment\n\n---\n\n### Step 2: Choose Playtest Type\n\nPresent options and confirm with user:\n\n#### Internal Playtest\n**Best for**: Early validation, bug finding, quick iterations\n\n| Aspect       | Details                   |\n| ------------ | ------------------------- |\n| Participants | Team members, other teams |\n| Duration     | 30-60 minutes             |\n| Frequency    | Weekly or per-milestone   |\n| Setup        | Minimal, informal         |\n\n#### External Playtest\n**Best for**: Unbiased feedback, market validation\n\n| Aspect       | Details                           |\n| ------------ | --------------------------------- |\n| Participants | Target audience, external testers |\n| Duration     | 1-2 hours                         |\n| Frequency    | Monthly or milestone              |\n| Setup        | Formal, NDA if needed             |\n\n#### Focused Playtest\n**Best for**: Specific feature validation\n\n| Aspect       | Details                      |\n| ------------ | ---------------------------- |\n| Participants | Selected for specific traits |\n| Duration     | 20-45 minutes                |\n| Frequency    | As needed                    |\n| Setup        | Specific build\u002Fscenario      |\n\n---\n\n### Step 3: Create Session Structure\n\n#### Pre-Session (10-15 min)\n\n1. **Welcome & Context**\n   - Brief game description (no spoilers)\n   - Session goals (what we're testing)\n   - Comfort check (breaks, questions)\n\n2. **Consent & Setup**\n   - Recording consent (if applicable)\n   - Controller\u002Finput preferences\n   - Any accessibility needs\n\n3. **Instructions**\n   - \"Play as you normally would\"\n   - \"Think aloud if comfortable\"\n   - \"There are no wrong answers\"\n\n#### Gameplay Session (30-90 min)\n\n1. **Observation Focus Areas**\n   - Where do players get stuck?\n   - What do they try first?\n   - What surprises them?\n   - Where do they express frustration\u002Fjoy?\n\n2. **Note-Taking Template**\n\n   ```\n   [TIME] [LOCATION] [OBSERVATION] [PLAYER REACTION]\n   0:05   Tutorial    Skipped help text    Seemed impatient\n   0:12   Combat      Died to first enemy  Frustrated, retried\n   ```\n\n3. **Intervention Rules**\n   - Let players struggle (within reason)\n   - Note when you want to help\n   - Only intervene for:\n     - Critical bugs\n     - Genuine distress\n     - Session time running out\n\n#### Post-Session (10-20 min)\n\n1. **Immediate Reactions**\n   - \"What was your overall impression?\"\n   - \"What stood out most?\"\n   - \"Would you play again?\"\n\n2. **Specific Questions**\n   - Feature-specific feedback\n   - Difficulty perception\n   - Clarity of objectives\n\n3. **Open Feedback**\n   - \"Anything else?\"\n   - \"Questions for us?\"\n\n---\n\n### Step 4: Create Observation Guide\n\n| Category    | Signals                               | Record             |\n| ----------- | ------------------------------------- | ------------------ |\n| Confusion   | Pausing, wandering, repeating actions | Location, duration |\n| Frustration | Sighing, repeated failures, quitting  | Cause, frequency   |\n| Engagement  | Leaning in, exclaiming, continuing    | Features that work |\n| Boredom     | Checking phone, disengaging           | Drop-off points    |\n\n**Quantitative Metrics**:\n- Time to complete tutorial\n- Deaths per section\n- Items\u002Ffeatures discovered\n- Session duration\n- Completion rate\n\n---\n\n### Step 5: Generate Playtest Plan Document\n\nWrite `{output_folder}\u002Fplaytest-plan.md` using the `playtest-template.md` structure:\n\n```markdown\n# Playtest Plan: {Build\u002FFeature Name}\n\n## Overview\n\n- Build version: {version}\n- Session date(s): {dates}\n- Objective: {primary goal}\n\n## Participant Criteria\n\n- Target: {player type}\n- Experience: {gaming background}\n- Count: {number}\n\n## Session Structure\n\n### Pre-Session (15 min)\n\n- Welcome and consent\n- Setup and preferences\n- Brief instructions\n\n### Gameplay (60 min)\n\n- Free play \u002F guided tasks\n- Observation focus: {areas}\n- Intervention threshold: {criteria}\n\n### Post-Session (15 min)\n\n- Immediate reactions\n- Structured questions\n- Open feedback\n\n## Observation Guide\n\n{observation_template}\n\n## Data Collection\n\n- Recording: {yes\u002Fno}\n- Notes template: {attached}\n- Metrics: {list}\n\n## Team Roles\n\n- Facilitator: {name}\n- Note-taker: {name}\n- Technical support: {name}\n\n## Post-Playtest Analysis\n\n- Session debrief: {date}\n- Report due: {date}\n- Action items review: {date}\n```\n\n---\n\n### Step 6: Post-Playtest Analysis Framework\n\nInclude in the plan document:\n\n#### Synthesize Findings\n\n1. **Pattern Identification**\n   - What issues appeared multiple times?\n   - What worked consistently well?\n\n2. **Severity Assessment**\n   - Critical: Blocks progression\n   - Major: Significantly impacts experience\n   - Minor: Noticeable but manageable\n\n3. **Recommendations**\n   - Immediate fixes\n   - Design considerations\n   - Further investigation needed\n\n#### Report Template\n\n```markdown\n## Playtest Report: {Session}\n\n### Summary\n\n- Participants: {count}\n- Completion rate: {%}\n- Overall sentiment: {positive\u002Fmixed\u002Fnegative}\n\n### Key Findings\n\n1. {Finding with evidence}\n2. {Finding with evidence}\n\n### Recommendations\n\n| Issue   | Severity | Recommendation | Priority |\n| ------- | -------- | -------------- | -------- |\n| {issue} | {sev}    | {rec}          | {P0-P3}  |\n\n### Quotes\n\n> \"{Notable player quote}\" - Participant {N}\n\n### Next Steps\n\n1. {action item}\n2. {action item}\n```\n\n---\n\n## Deliverables\n\n1. **Playtest Plan Document** — Session structure and logistics\n2. **Observation Guide** — What to watch for\n3. **Note-Taking Template** — Standardized recording\n4. **Report Template** — Post-session analysis format\n\n---\n\n## Validation\n\nRefer to `checklist.md` for validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n","# Playtest Planning\n\n**Workflow ID**: `gds-playtest-plan`\n**Version**: 1.0 (BMad v6)\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. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n- `output_folder`\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## Goal\n\nCreate structured playtesting sessions to validate gameplay, gather user feedback, and identify issues that automated testing cannot catch. Playtesting validates \"feel\" and player experience.\n\n## Role\n\nYou are a Game QA Specialist with expertise in designing and facilitating playtesting sessions. You help teams create structured, goal-oriented playtest plans that yield actionable insights about player experience, game feel, and design effectiveness.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow produces a complete playtesting plan including session structure, observation guides, note-taking templates, and post-session analysis frameworks.\n\n**Primary Output**: `{output_folder}\u002Fplaytest-plan.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n- Template: `{installed_path}\u002Fplaytest-template.md`\n- Knowledge Base: `knowledge\u002Fplaytesting.md`\n\n**Input Files** (auto-located):\n- GDD: `{output_folder}\u002F*gdd*.md` or `{output_folder}\u002F*gdd*\u002F*.md` — game mechanics to validate\n- Game Brief: `{output_folder}\u002F*brief*.md` — core pillars\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\nplaytest_type: \"internal\"   # internal | external | focused\nsession_duration: 60        # minutes\nparticipant_count: 5\n```\n\nGreet the user by name (`user_name`) and confirm the playtest type and scope before proceeding.\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\nVerify before proceeding:\n- Playable build available\n- Test objectives defined\n- Participant criteria known\n\n---\n\n### Step 1: Define Playtest Objectives\n\nAsk the user (or infer from GDD\u002Fgame brief):\n\n1. **What are we testing?**\n   - Core gameplay loop\n   - Specific feature\n   - Difficulty curve\n   - Tutorial effectiveness\n   - Overall experience\n\n2. **What decisions will this inform?**\n   - Design changes\n   - Difficulty tuning\n   - Feature prioritization\n   - Ship\u002Fno-ship decision\n\n3. **What metrics will we collect?**\n   - Completion rates\n   - Time-on-task\n   - Failure points\n   - Player sentiment\n\n---\n\n### Step 2: Choose Playtest Type\n\nPresent options and confirm with user:\n\n#### Internal Playtest\n**Best for**: Early validation, bug finding, quick iterations\n\n| Aspect       | Details                   |\n| ------------ | ------------------------- |\n| Participants | Team members, other teams |\n| Duration     | 30-60 minutes             |\n| Frequency    | Weekly or per-milestone   |\n| Setup        | Minimal, informal         |\n\n#### External Playtest\n**Best for**: Unbiased feedback, market validation\n\n| Aspect       | Details                           |\n| ------------ | --------------------------------- |\n| Participants | Target audience, external testers |\n| Duration     | 1-2 hours                         |\n| Frequency    | Monthly or milestone              |\n| Setup        | Formal, NDA if needed             |\n\n#### Focused Playtest\n**Best for**: Specific feature validation\n\n| Aspect       | Details                      |\n| ------------ | ---------------------------- |\n| Participants | Selected for specific traits |\n| Duration     | 20-45 minutes                |\n| Frequency    | As needed                    |\n| Setup        | Specific build\u002Fscenario      |\n\n---\n\n### Step 3: Create Session Structure\n\n#### Pre-Session (10-15 min)\n\n1. **Welcome & Context**\n   - Brief game description (no spoilers)\n   - Session goals (what we're testing)\n   - Comfort check (breaks, questions)\n\n2. **Consent & Setup**\n   - Recording consent (if applicable)\n   - Controller\u002Finput preferences\n   - Any accessibility needs\n\n3. **Instructions**\n   - \"Play as you normally would\"\n   - \"Think aloud if comfortable\"\n   - \"There are no wrong answers\"\n\n#### Gameplay Session (30-90 min)\n\n1. **Observation Focus Areas**\n   - Where do players get stuck?\n   - What do they try first?\n   - What surprises them?\n   - Where do they express frustration\u002Fjoy?\n\n2. **Note-Taking Template**\n\n   ```\n   [TIME] [LOCATION] [OBSERVATION] [PLAYER REACTION]\n   0:05   Tutorial    Skipped help text    Seemed impatient\n   0:12   Combat      Died to first enemy  Frustrated, retried\n   ```\n\n3. **Intervention Rules**\n   - Let players struggle (within reason)\n   - Note when you want to help\n   - Only intervene for:\n     - Critical bugs\n     - Genuine distress\n     - Session time running out\n\n#### Post-Session (10-20 min)\n\n1. **Immediate Reactions**\n   - \"What was your overall impression?\"\n   - \"What stood out most?\"\n   - \"Would you play again?\"\n\n2. **Specific Questions**\n   - Feature-specific feedback\n   - Difficulty perception\n   - Clarity of objectives\n\n3. **Open Feedback**\n   - \"Anything else?\"\n   - \"Questions for us?\"\n\n---\n\n### Step 4: Create Observation Guide\n\n| Category    | Signals                               | Record             |\n| ----------- | ------------------------------------- | ------------------ |\n| Confusion   | Pausing, wandering, repeating actions | Location, duration |\n| Frustration | Sighing, repeated failures, quitting  | Cause, frequency   |\n| Engagement  | Leaning in, exclaiming, continuing    | Features that work |\n| Boredom     | Checking phone, disengaging           | Drop-off points    |\n\n**Quantitative Metrics**:\n- Time to complete tutorial\n- Deaths per section\n- Items\u002Ffeatures discovered\n- Session duration\n- Completion rate\n\n---\n\n### Step 5: Generate Playtest Plan Document\n\nWrite `{output_folder}\u002Fplaytest-plan.md` using the `playtest-template.md` structure:\n\n```markdown\n# Playtest Plan: {Build\u002FFeature Name}\n\n## Overview\n\n- Build version: {version}\n- Session date(s): {dates}\n- Objective: {primary goal}\n\n## Participant Criteria\n\n- Target: {player type}\n- Experience: {gaming background}\n- Count: {number}\n\n## Session Structure\n\n### Pre-Session (15 min)\n\n- Welcome and consent\n- Setup and preferences\n- Brief instructions\n\n### Gameplay (60 min)\n\n- Free play \u002F guided tasks\n- Observation focus: {areas}\n- Intervention threshold: {criteria}\n\n### Post-Session (15 min)\n\n- Immediate reactions\n- Structured questions\n- Open feedback\n\n## Observation Guide\n\n{observation_template}\n\n## Data Collection\n\n- Recording: {yes\u002Fno}\n- Notes template: {attached}\n- Metrics: {list}\n\n## Team Roles\n\n- Facilitator: {name}\n- Note-taker: {name}\n- Technical support: {name}\n\n## Post-Playtest Analysis\n\n- Session debrief: {date}\n- Report due: {date}\n- Action items review: {date}\n```\n\n---\n\n### Step 6: Post-Playtest Analysis Framework\n\nInclude in the plan document:\n\n#### Synthesize Findings\n\n1. **Pattern Identification**\n   - What issues appeared multiple times?\n   - What worked consistently well?\n\n2. **Severity Assessment**\n   - Critical: Blocks progression\n   - Major: Significantly impacts experience\n   - Minor: Noticeable but manageable\n\n3. **Recommendations**\n   - Immediate fixes\n   - Design considerations\n   - Further investigation needed\n\n#### Report Template\n\n```markdown\n## Playtest Report: {Session}\n\n### Summary\n\n- Participants: {count}\n- Completion rate: {%}\n- Overall sentiment: {positive\u002Fmixed\u002Fnegative}\n\n### Key Findings\n\n1. {Finding with evidence}\n2. {Finding with evidence}\n\n### Recommendations\n\n| Issue   | Severity | Recommendation | Priority |\n| ------- | -------- | -------------- | -------- |\n| {issue} | {sev}    | {rec}          | {P0-P3}  |\n\n### Quotes\n\n> \"{Notable player quote}\" - Participant {N}\n\n### Next Steps\n\n1. {action item}\n2. {action item}\n```\n\n---\n\n## Deliverables\n\n1. **Playtest Plan Document** — Session structure and logistics\n2. **Observation Guide** — What to watch for\n3. **Note-Taking Template** — Standardized recording\n4. **Report Template** — Post-session analysis format\n\n---\n\n## Validation\n\nRefer to `checklist.md` for validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n",{"name":5,"description":7},"main","1907bbe850fb749efa8b499b8da7ebb78a663519",".claude\u002Fskills\u002Fgds-playtest-plan",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add developAgent\u002Fbmad-start --skill gds-playtest-plan",{"tool":47,"command":48},"bunx","bunx skills add developAgent\u002Fbmad-start --skill gds-playtest-plan",{"tool":50,"command":51},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill gds-playtest-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgds-playtest-plan\u002FSKILL.md",true,[55,61,67],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"checklist.md","REFERENCE","参考文档",1793,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgds-playtest-plan\u002Fchecklist.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"customize.toml","OTHER","其他",1647,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgds-playtest-plan\u002Fcustomize.toml",{"path":68,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":69,"sourceHtmlUrl":70},"playtest-template.md",4695,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgds-playtest-plan\u002Fplaytest-template.md",[72,93,125,143,157,182],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":92},"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",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[84,85,86,23,87,88,28,24,89,90,91],"gds correct course","course","correct","changes","change","execution","manage","sprint","2026-11-10 13:02:02",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":107,"publishedAt":92},"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",[99,104],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":105,"categoryName":106,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000030","开发工程师",[108,109,110,111,112,87,113,114,115,116,117,118,119,28,120,24,121,122,123,124],"code review","code","review","gds code review","categories","triage","review code","run","parallel","case","with","run code","acceptance","edge","actionable","layers","hunter",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":92},"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",[],[132,133,134,135,136,137,23,138,139,140,141,28,24,142],"check","readiness","Implementation Readiness","gds check implementation readiness","implementation","check readiness","Production","ux","verify","architecture","alignment",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":92},"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",[],[150,151,152,23,153,118,28,24,154,155,156],"gds brainstorm game","game","brainstorm","brainstorming","techniques","sessions","ideas",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":92},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",[167,168,169,170,24,171,172,27,173,28,23,174,175,176,177,178,179,180,151,181],"gds agent tech writer","tech","writer","technical writer","technical","knowledge","projects","technical documentation","talk","specialist","documentation specialist","knowledge curator","requests","documentation","curator",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":92},"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",[188],{"categoryNo":164,"categoryName":165,"taxonomyType":102,"taxonomyTypeDesc":103},[190,151,191,192,193,194,23,175,179,195,196,28,24,197,27,198,199],"solo","gds agent game solo dev","dev","flow","developer","RAPID","game developer","prototyping","development","quick"]