1,763 件 ・ 関連度順
概要と使いどころ
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
日本語の概要は準備中です。原文の説明を表示しています。
Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).
日本語の概要は準備中です。原文の説明を表示しています。
Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
日本語の概要は準備中です。原文の説明を表示しています。
First-time onboarding — asks where you are, then guides you to the right workflow or to pre-workflow exploration. No assumptions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
日本語の概要は準備中です。原文の説明を表示しています。
Run an automated smoke test using the godot-mcp server. Launches the project, captures debug output, and checks for errors or crashes.
日本語の概要は準備中です。原文の説明を表示しています。
Fast-lane prototype skill for the hybrid workflow. Builds a playable prototype in 2-3 days with minimal process overhead. Designed for discovery phase.
日本語の概要は準備中です。原文の説明を表示しています。
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do
日本語の概要は準備中です。原文の説明を表示しています。
Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
日本語の概要は準備中です。原文の説明を表示しています。
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
日本語の概要は準備中です。原文の説明を表示しています。
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
日本語の概要は準備中です。原文の説明を表示しています。
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
日本語の概要は準備中です。原文の説明を表示しています。
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /concept-brainstorm is approved and before /map-systems or any GDD authoring begins.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.
日本語の概要は準備中です。原文の説明を表示しています。
Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.
日本語の概要は準備中です。原文の説明を表示しています。
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.
日本語の概要は準備中です。原文の説明を表示しています。
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
日本語の概要は準備中です。原文の説明を表示しています。
Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.
日本語の概要は準備中です。原文の説明を表示しています。