@musashishao/agent-kit 1.9.0 → 1.9.1

package/.agent/workflows/gamekit-plan.md

@@ -0,0 +1,204 @@
+---
+description: "Generate implementation plan from approved game specification."
+description_vi: "Tạo kế hoạch triển khai từ đặc tả game đã được duyệt."
+description_en: "Generate implementation plan from approved game specification."
+---
+
+# /gamekit.plan - Game Implementation Plan
+
+Generate a detailed implementation plan from an approved specification. Includes task breakdown, agent assignments, and file structure.
+
+---
+
+## 🎯 Purpose
+
+Transform SPEC into actionable PLAN:
+1. Define tech stack with rationale
+2. Create file/folder structure
+3. Break down into tasks with dependencies
+4. Assign agents to each task
+5. Define verification criteria
+
+---
+
+## Prerequisites
+
+- `SPEC-{game}.md` exists in `docs/specs/`
+- SPEC has been reviewed and approved by user
+
+---
+
+## 📋 Workflow Steps
+
+### Step 0: Read SPEC and Decisions
+
+```markdown
+🔍 **Reading specification...**
+
+**SPEC file:** docs/specs/SPEC-{game}.md
+**Decisions:** .agent/memory/decisions.md
+
+**Key points from SPEC:**
+- Platform: [from SPEC]
+- Core Loop: [from SPEC]
+- Constraints: [from SPEC]
+```
+
+### Step 1: Tech Stack Selection
+
+Using `explained-qa` skill:
+
+```markdown
+### ❓ Engine nào phù hợp cho game này?
+
+> 💡 **Giải thích:** Engine là "xưởng sản xuất" game.
+> Mỗi engine có thế mạnh riêng.
+
+**Phân tích dựa trên SPEC:**
+| Factor | Requirement | Best Fit |
+|--------|-------------|----------|
+| Platform: [X] | [constraint] | [engine] |
+| Art Style: [X] | [constraint] | [engine] |
+| Complexity: [X] | [constraint] | [engine] |
+
+**Đề xuất:**
+| Option | Lý do | Trade-off |
+|--------|-------|-----------|
+| (A) Unity 6 | Industry standard, mobile strong | Learning curve, runtime fee |
+| (B) Godot 4.3 | Free, 2D excellent | Smaller community |
+| (C) Phaser/Web | Browser instant-play | Limited 3D |
+
+**Dựa trên SPEC, AI gợi ý:** [Recommendation]
+```
+
+→ Log to `decisions.md`
+
+### Step 2: Architecture Decisions
+
+Ask about (using `explained-qa`):
+- State management approach
+- Save system design
+- Event system architecture
+- Asset organization
+
+→ Log each to `decisions.md`
+
+### Step 3: File Structure Generation
+
+Based on tech stack and architecture:
+
+```markdown
+📁 **Proposed Structure:**
+
+[Generate structure based on engine selection]
+
+**Unity Example:**
+Assets/
+├── _Project/
+│   ├── Scripts/
+│   │   ├── Core/
+│   │   │   ├── GameManager.cs
+│   │   │   ├── GameEvents.cs
+│   │   │   └── SaveSystem.cs
+│   │   ├── Gameplay/
+│   │   │   └── [Core loop scripts]
+│   │   └── UI/
+│   │       └── [UI controllers]
+│   ├── ScriptableObjects/
+│   │   └── [Data definitions]
+│   └── Scenes/
+│       ├── Bootstrap.unity
+│       └── Game.unity
+└── Art/
+    └── [Based on art style]
+```
+
+### Step 4: Task Breakdown
+
+Generate tasks following pattern:
+
+```markdown
+## Phase 1: Core Systems
+
+| Task | Agent | Priority | Depends | I→O→V |
+|------|-------|----------|---------|-------|
+| 1.1 Create GameEvents.cs (Event Bus) | unity-mobile-master | P0 | None | SPEC → Script → Events fire |
+| 1.2 Create GameManager.cs | unity-mobile-master | P0 | 1.1 | Events → Manager → Game state works |
+| 1.3 Create SaveSystem.cs | unity-mobile-master | P0 | 1.1 | Design → Script → Save/Load works |
+
+## Phase 2: Gameplay (from Core Loop)
+
+[Tasks derived from SPEC core loop]
+
+## Phase 3: UI
+
+[Tasks for UI based on SPEC]
+
+## Phase 4: Audio & Polish
+
+[Tasks for audio, effects, juice]
+```
+
+### Step 5: Agent Assignment Matrix
+
+```markdown
+## Agent Assignments
+
+| Agent | Responsibility | Tasks |
+|-------|----------------|-------|
+| `unity-mobile-master` | Core systems, gameplay | 1.1-1.3, 2.1-2.x |
+| `game-developer` | Architecture decisions | Review all |
+| `ai-asset-factory` | Art assets | 4.x |
+| `ai-audio-factory` | Audio assets | 4.x |
+```
+
+### Step 6: Generate PLAN File
+
+Using template from `spec-ecosystem/templates/PLAN-template.md`:
+
+```bash
+# Generate PLAN file
+# Location: docs/plans/PLAN-{game-slug}.md
+```
+
+---
+
+## 📁 Output Files
+
+| File | Location | Content |
+|------|----------|---------|
+| PLAN | `docs/plans/PLAN-{game}.md` | Full implementation plan |
+| Decisions | `.agent/memory/decisions.md` | Tech stack decisions |
+
+---
+
+## ⏭️ Next Steps
+
+```markdown
+✅ Implementation Plan created!
+
+**File:** `docs/plans/PLAN-{game}.md`
+**Total tasks:** X tasks across Y phases
+
+**Review Checklist:**
+- [ ] Tech stack justified?
+- [ ] File structure complete?
+- [ ] All tasks have I→O→V?
+- [ ] Dependencies clear?
+- [ ] Phase X verification defined?
+
+**Sau khi review và approve:**
+→ Chạy `/gamekit.tasks` để tạo task list executable
+→ Hoặc `/game-hybrid` để bắt đầu implementation
+```
+
+---
+
+## 🔗 Integration
+
+| Skill | Usage |
+|-------|-------|
+| `explained-qa` | Tech stack questions |
+| `spec-ecosystem` | PLAN template |
+| `game-developer` | Architecture decisions |
+| `project-planner` | Task breakdown logic |

package/.agent/workflows/gamekit-qa.md

@@ -0,0 +1,153 @@
+---
+description: "Playtest and QA loop for iterative game refinement."
+description_vi: "Vòng lặp playtest và QA để tinh chỉnh game liên tục."
+description_en: "Playtest and QA loop for iterative game refinement."
+---
+
+# /gamekit-qa - Evaluative Loop (QA & Refinement)
+
+Playtest, collect feedback, and iteratively refine game feel and balance.
+
+> 💡 **Migrated from:** `/game-hybrid` Tier 3
+
+---
+
+## 🎯 Purpose
+
+After implementation, enter the QA loop to:
+1. Playtest the game
+2. Collect feedback (user or AI)
+3. Refine values via ScriptableObjects
+4. Run automated balance testing
+5. Loop until satisfied
+
+---
+
+## Prerequisites
+
+- Game is playable (core loop working)
+- ScriptableObjects configured for tuning
+- Basic gameplay complete
+
+---
+
+## 📋 Workflow Steps
+
+### Step 1: Playtest Session
+
+// turbo
+```bash
+# Open Unity and play
+echo "Open Unity Editor and Play game"
+```
+
+Manual playtest checklist:
+- [ ] Core loop feels good?
+- [ ] Controls responsive?
+- [ ] Difficulty appropriate?
+- [ ] Any bugs encountered?
+
+### Step 2: Collect Feedback
+
+User or AI notes issues:
+
+```markdown
+## Playtest Feedback - [DATE]
+
+### Feel Issues
+- "Jump feels too heavy"
+- "Enemies spawn too fast"
+
+### Balance Issues  
+- "Level 3 is impossible"
+- "Gold rewards too low"
+
+### Bug Reports
+- "Sound cuts out after 5 minutes"
+```
+
+→ Log to `.agent/memory/playtest-log.md`
+
+### Step 3: AI Refinement
+
+Using `unity-mobile-master` or `game-developer`:
+
+```markdown
+INPUT: "Make character jump higher and feel lighter"
+
+ACTION: Modify CharacterData.asset
+- JumpForce: 10 → 15
+- Gravity: 2 → 1.5
+
+VERIFY: Playtest again, compare feel
+```
+
+> 🔴 **RULE:** Only modify ScriptableObject values, NOT code.
+
+### Step 4: Automated Balance Testing
+
+Using `game-developer`:
+
+```markdown
+INPUT: "Run 100 combat simulations, report win rate"
+
+OUTPUT:
+- Player win rate: 65%
+- Average fight duration: 12s
+- Most used skill: Dash (78%)
+- Recommended: Increase enemy HP by 10%
+```
+
+### Step 5: Loop Back
+
+```
+IF feedback addressed AND feel good:
+    → Exit QA loop, proceed to /gamekit-launch
+ELSE:
+    → Return to Step 1 (Playtest again)
+```
+
+---
+
+## 📊 QA Metrics Dashboard
+
+| Metric | Target | Current |
+|--------|--------|---------|
+| Core Loop Fun | 8/10 | [?] |
+| Control Responsiveness | 9/10 | [?] |
+| Difficulty Balance | 7/10 | [?] |
+| Session Length | 5-15 min | [?] |
+| Retention Intent | "Would play again" | [?] |
+
+---
+
+## 📁 Output Files
+
+| File | Location | Content |
+|------|----------|---------|
+| Playtest Log | `.agent/memory/playtest-log.md` | All feedback sessions |
+| Tuning Changes | ScriptableObjects | Modified values |
+
+---
+
+## ⏭️ Next Steps
+
+```markdown
+✅ QA Loop complete!
+
+**Iterations:** X playtest sessions
+**Key changes:** [summary of tuning]
+
+**Game feels good?**
+→ Chạy `/gamekit-launch` để chuẩn bị release
+```
+
+---
+
+## 🔗 Integration
+
+| Skill | Usage |
+|-------|-------|
+| `game-development/data-driven-balance` | ScriptableObject tuning |
+| `game-development/testing-qa` | Playtest methodology |
+| `unity-mobile-master` | Value adjustments |

package/.agent/workflows/gamekit-spec.md

@@ -0,0 +1,243 @@
+---
+description: "Create game specification with Explained Q&A for all stakeholders."
+description_vi: "Tạo đặc tả game với Q&A có giải thích cho mọi stakeholders."
+description_en: "Create game specification with Explained Q&A for all stakeholders."
+---
+
+# /gamekit.spec - Game Specification Creation
+
+Create a comprehensive game specification using the Explained Q&A system. Designed for ALL stakeholders (Developer, PM, Designer).
+
+---
+
+## 🎯 Purpose
+
+Transform a game idea into a formal specification:
+1. Use `explained-qa` for all technical questions
+2. Log all decisions to `decisions.md`
+3. Generate `SPEC-{game}.md` following template
+
+---
+
+## Prerequisites
+
+- Project initialized with `/gamekit.init` OR
+- `.agent/memory/decisions.md` exists
+
+---
+
+## 📋 Workflow Steps
+
+### Step 0: Check Existing Context
+
+```markdown
+🔍 **Reading existing decisions...**
+
+[If decisions.md exists, summarize existing decisions]
+[Skip questions that are already answered]
+```
+
+### Step 1: Problem Statement
+
+Using `explained-qa` skill:
+
+```markdown
+### ❓ Game này giải quyết vấn đề gì?
+
+> 💡 **Giải thích:** Mỗi game tốt đều giải quyết một "nhu cầu" của người chơi.
+> Có thể là: giải trí, thư giãn, thử thách, kết nối xã hội, học hỏi...
+
+**Gợi ý:**
+| Need | Ví dụ game |
+|------|------------|
+| Giải trí nhanh (3-5 phút) | Candy Crush, Subway Surfers |
+| Thử thách/Thành tựu | Dark Souls, Hollow Knight |
+| Thư giãn/Zen | Stardew Valley, Journey |
+| Kết nối xã hội | Among Us, Fall Guys |
+| Học hỏi/Sáng tạo | Minecraft, Kerbal Space Program |
+
+**Câu hỏi:** Game của bạn đáp ứng nhu cầu nào của người chơi?
+```
+
+→ Log to `decisions.md`
+
+### Step 1.5: Generate 3 Professional Concepts
+
+> 💡 **From /game-from-idea**: Tạo 3 hướng đi khác nhau để user chọn.
+
+Present 3 distinct directions with:
+
+| Concept | USP | Core Loop | Monetization |
+|---------|-----|-----------|--------------|
+| A: [Name] | [Unique Selling Point] | [Action→Reward→Progression] | [F2P/Premium/Hybrid] |
+| B: [Name] | [Unique Selling Point] | [Action→Reward→Progression] | [F2P/Premium/Hybrid] |
+| C: [Name] | [Unique Selling Point] | [Action→Reward→Progression] | [F2P/Premium/Hybrid] |
+
+```markdown
+### ❓ Bạn thích hướng nào nhất?
+
+> 💡 **Giải thích:** USP (Unique Selling Point) = Điểm khác biệt khiến game nổi bật.
+> Core Loop = Vòng lặp 30 giây mà người chơi lặp lại liên tục.
+
+**Chọn A, B, hoặc C (hoặc mix)?**
+```
+
+→ Log to `decisions.md`
+
+### Step 1.6: Create Mini-GDD
+
+> 💡 **From /game-from-idea**: Expand concept thành Game Design Document.
+
+Once a concept is selected, create `docs/GDD.md`:
+
+```markdown
+# Mini-GDD: [Game Name]
+
+## Core Mechanics
+- [Mechanic 1]
+- [Mechanic 2]
+
+## Player Progression
+| Milestone | Unlock |
+|-----------|--------|
+| Level 5   | [Feature] |
+| Level 10  | [Feature] |
+
+## Art Style
+- Style: [e.g., Pixel Art, Low Poly, Hand-drawn]
+- Palette: [Color scheme]
+
+## Audio Direction
+- Music: [Mood/Genre]
+- SFX: [Style]
+```
+
+→ Log to `decisions.md`
+
+### Step 2: User Stories
+
+```markdown
+### ❓ Ai là người chơi chính của game?
+
+> 💡 **Giải thích:** "User Story" mô tả AI là, TÔI MUỐN gì, ĐỂ được gì.
+> Ví dụ: "Là người chơi casual, tôi muốn chơi một tay để chơi trên bus."
+
+**Gợi ý đối tượng:**
+| Persona | Đặc điểm |
+|---------|----------|
+| Casual Gamer | Chơi 5-15 phút, không muốn phức tạp |
+| Core Gamer | Chơi 30-60 phút, thích thử thách |
+| Hardcore | Chơi hàng giờ, master mọi thứ |
+| Social Player | Chơi vì bạn bè, không cần giỏi |
+
+**Câu hỏi:** Mô tả 2-3 loại người chơi và họ muốn gì từ game?
+```
+
+→ Log to `decisions.md`
+
+### Step 3: Core Loop
+
+```markdown
+### ❓ Vòng lặp 30 giây của game là gì?
+
+> 💡 **Giải thích:** Core Loop = Hành động → Phần thưởng → Tiến bộ
+> Đây là trải nghiệm người chơi lặp đi lặp lại mỗi 30 giây.
+
+**Ví dụ:**
+| Game | Action | Reward | Progression |
+|------|--------|--------|-------------|
+| Candy Crush | Ghép kẹo | Điểm + Effects | Level mới |
+| Flappy Bird | Tap để bay | Qua ống = +1 | High score |
+| Clash Royale | Đặt quân | Phá tháp | Trophies |
+
+**Câu hỏi:** Mô tả core loop của game bạn: [Action] → [Reward] → [Progression]
+```
+
+→ Log to `decisions.md`
+
+### Step 4: Platform & Constraints
+
+Using `explained-qa`, ask about:
+- Target platform (Mobile/PC/Web)
+- Art style preference
+- Audio direction
+- Performance requirements
+
+→ Log each to `decisions.md`
+
+### Step 5: Out of Scope
+
+```markdown
+### ❓ Những gì KHÔNG làm trong phiên bản đầu?
+
+> 💡 **Giải thích:** Định nghĩa rõ "Out of Scope" giúp AI không đề xuất features không cần thiết.
+> MVP = Minimum Viable Product = Phiên bản nhỏ nhất mà vẫn chơi được.
+
+**Gợi ý cắt bỏ cho MVP:**
+- [ ] Multiplayer (làm single-player trước)
+- [ ] Cloud Save (local save trước)
+- [ ] IAP/Monetization (free prototype trước)
+- [ ] Social features (standalone trước)
+- [ ] Localization (1 ngôn ngữ trước)
+
+**Câu hỏi:** Liệt kê những features bạn muốn LÀM SAU, không trong MVP?
+```
+
+→ Log to `decisions.md`
+
+### Step 6: Generate SPEC File
+
+Using template from `spec-ecosystem/templates/SPEC-template.md`:
+
+```bash
+# Generate SPEC file
+# Location: docs/specs/SPEC-{game-slug}.md
+```
+
+Fill template with:
+- Problem Statement (from Step 1)
+- User Stories (from Step 2)
+- Core Loop (from Step 3)
+- Technical Constraints (from Step 4)
+- Out of Scope (from Step 5)
+- Acceptance Criteria (derived from above)
+
+---
+
+## 📁 Output Files
+
+| File | Location | Content |
+|------|----------|---------|
+| GDD | `docs/GDD.md` | Mini Game Design Document |
+| SPEC | `docs/specs/SPEC-{game}.md` | Full specification |
+| Decisions | `.agent/memory/decisions.md` | All Q&A logged |
+
+---
+
+## ⏭️ Next Steps
+
+```markdown
+✅ Specification created!
+
+**File:** `docs/specs/SPEC-{game}.md`
+**Decisions logged:** X questions answered
+
+**Review Checklist:**
+- [ ] Problem statement clear?
+- [ ] User stories have benefits?
+- [ ] Core loop defined?
+- [ ] Out of scope explicit?
+
+**Sau khi review và approve:**
+→ Chạy `/gamekit.plan` để tạo implementation plan
+```
+
+---
+
+## 🔗 Integration
+
+| Skill | Usage |
+|-------|-------|
+| `explained-qa` | All questions use this format |
+| `spec-ecosystem` | Template and structure |
+| `brainstorming` | Dynamic question generation |