moai-adk 0.7.0__py3-none-any.whl → 0.8.1__py3-none-any.whl

moai_adk/templates/.moai/config.json

@@ -92,5 +92,17 @@
       "scan_command": "rg '@TAG' -n",
       "philosophy": "The source of truth for TAGs lives in the code itself"
     }
+  },
+  "github": {
+    "@CODE:GITHUB-CONFIG-001": "@DOC:GITHUB-TEMPLATES-001",
+    "templates": {
+      "enable_trust_5": true,
+      "enable_tag_system": true,
+      "enable_alfred_commands": true,
+      "spec_directory": ".moai/specs",
+      "docs_directory": ".moai/docs",
+      "test_directory": "tests",
+      "notes": "Configure GitHub templates for project customization. When enable_* flags are false, corresponding MoAI-specific sections are omitted from templates."
+    }
   }
 }

moai_adk/templates/.moai/docs/quick-issue-creation-guide.md

@@ -0,0 +1,219 @@
+# 🎯 Quick Issue Creation Guide
+
+> **MoAI-ADK v0.7.0+** - Create GitHub Issues instantly with `/alfred:9-feedback` interactive dialog
+
+## Overview
+
+The Quick Issue Creation system allows developers to report bugs, request features, suggest improvements, and ask questions directly to GitHub Issues without leaving their development context.
+
+**Key Benefit**: Convert problems into tracked GitHub Issues in seconds, maintaining development flow.
+
+---
+
+## 🚀 Quick Start
+
+### Basic Usage
+
+```bash
+# Report a bug
+/alfred:9-help --bug 'Login button not responding on homepage'
+
+# Request a feature
+/alfred:9-help --feature 'Add dark mode theme support'
+
+# Suggest an improvement
+/alfred:9-help --improvement 'Optimize database query in UserService'
+
+# Ask a question
+/alfred:9-help --question 'What is the recommended approach for API versioning?'
+```
+
+### What Happens Next
+
+1. **Parsing**: Alfred extracts issue type and content
+2. **Priority Selection**: You select issue priority (critical/high/medium/low)
+3. **Issue Creation**: GitHub Issue is created with:
+   - Formatted title (with emoji and type indicator)
+   - Your description
+   - Automatic labels based on type and priority
+   - Metadata footer
+4. **Confirmation**: You receive the issue URL for immediate sharing
+
+**Example Output**:
+```
+✅ GitHub Issue #456 created successfully
+📋 Title: 🐛 [BUG] Login button not responding on homepage
+🔴 Priority: High
+🏷️  Labels: bug, reported, priority-high
+🔗 URL: https://github.com/owner/repo/issues/456
+```
+
+---
+
+## 📋 Issue Types & Labels
+
+### 🐛 Bug Reports (`--bug`)
+
+Use this when you discover a problem or unexpected behavior.
+
+**Automatic Labels**: `bug`, `reported`
+
+**Example**:
+```bash
+/alfred:9-help --bug 'Payment form crashes when credit card has < 4 digits'
+```
+
+---
+
+### ✨ Feature Requests (`--feature`)
+
+Use this to propose new functionality.
+
+**Automatic Labels**: `feature-request`, `enhancement`
+
+**Example**:
+```bash
+/alfred:9-help --feature 'Add webhook support for payment notifications'
+```
+
+---
+
+### ⚡ Improvement Suggestions (`--improvement`)
+
+Use this to suggest enhancements to existing features.
+
+**Automatic Labels**: `improvement`, `enhancement`
+
+**Example**:
+```bash
+/alfred:9-help --improvement 'Reduce database queries in checkout process by 50%'
+```
+
+---
+
+### ❓ Questions & Discussions (`--question`)
+
+Use this to ask questions or start discussions.
+
+**Automatic Labels**: `question`, `help-wanted`
+
+**Example**:
+```bash
+/alfred:9-help --question 'Should we migrate from Sequelize to Prisma ORM?'
+```
+
+---
+
+## 🎯 Priority Levels
+
+When you create an issue, you'll be prompted to select a priority:
+
+| Level | Emoji | Label | When to Use |
+|-------|-------|-------|------------|
+| 🔴 Critical | 🔴 | `priority-critical` | System down, data loss risk, security breach |
+| 🟠 High | 🟠 | `priority-high` | Major feature broken, significant impact |
+| 🟡 Medium | 🟡 | `priority-medium` | Normal bugs, typical features, default |
+| 🟢 Low | 🟢 | `priority-low` | Minor issues, nice-to-have features |
+
+---
+
+## 💡 Real-World Examples
+
+### Example 1: Emergency Bug Report
+
+**Scenario**: During production support, you find that users cannot reset their passwords.
+
+```bash
+/alfred:9-help --bug 'Password reset email not being sent after clicking "Forgot Password"'
+```
+
+**Result**: Issue #234 created and visible to team immediately with critical priority.
+
+### Example 2: Feature Request from Code Review
+
+**Scenario**: During code review, you think of a feature that would improve the codebase.
+
+```bash
+/alfred:9-help --feature 'Add request rate limiting middleware to prevent abuse'
+```
+
+**Result**: Issue #235 created for backlog planning.
+
+### Example 3: Performance Improvement Suggestion
+
+**Scenario**: You notice slow database queries in the user service.
+
+```bash
+/alfred:9-help --improvement 'Add database index on users.email for faster lookups'
+```
+
+**Result**: Issue #236 created for technical debt backlog.
+
+### Example 4: Architecture Question
+
+**Scenario**: You're uncertain about the best approach for API design.
+
+```bash
+/alfred:9-help --question 'Should we use REST or GraphQL for the new mobile API?'
+```
+
+**Result**: Issue #237 created for team discussion.
+
+---
+
+## 🔧 Prerequisites
+
+### Required
+
+1. **GitHub CLI installed**
+   ```bash
+   # macOS
+   brew install gh
+
+   # Ubuntu/Debian
+   sudo apt install gh
+
+   # Or visit: https://cli.github.com
+   ```
+
+2. **Authenticated with GitHub**
+   ```bash
+   gh auth login
+   ```
+
+3. **Git repository initialized**
+   ```bash
+   git init
+   git remote add origin https://github.com/owner/repo.git
+   ```
+
+---
+
+## 🔄 Related Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/alfred:0-project` | Initialize project |
+| `/alfred:1-plan` | Create SPEC documents |
+| `/alfred:2-run` | Implement features |
+| `/alfred:3-sync` | Sync documentation |
+| `/alfred:9-help` | **Create issues (this command)** |
+
+---
+
+## ✨ Summary
+
+The `/alfred:9-help` command enables:
+
+- ✅ **Fast issue creation** - Seconds, not minutes
+- ✅ **Standardized format** - Consistent labels and metadata
+- ✅ **Priority management** - Clear issue prioritization
+- ✅ **Team visibility** - Issues immediately visible and discussable
+- ✅ **Workflow integration** - Works with MoAI-ADK specs and planning
+
+**Start using it now**:
+```bash
+/alfred:9-help --bug 'Describe the issue you just found'
+```
+
+Happy issue reporting! 🎉

moai_adk/templates/.moai/memory/issue-label-mapping.md

@@ -0,0 +1,150 @@
+# 📌 GitHub Issue Label Mapping Configuration
+
+> **MoAI-ADK Label Management** - Centralized configuration for issue type labels and priority indicators
+
+**Version**: 1.0.0
+**Related**: `/alfred:9-feedback`
+
+---
+
+## 🏷️ Issue Type Label Mapping
+
+### Bug Issues (`--bug`)
+
+**Primary Labels**: `bug`, `reported`
+
+**Optional Labels** (based on priority):
+- `priority-critical` - System down, data loss risk
+- `priority-high` - Major feature broken
+- `priority-medium` - Normal bug
+- `priority-low` - Minor issue
+
+---
+
+### Feature Request Issues (`--feature`)
+
+**Primary Labels**: `feature-request`, `enhancement`
+
+**Optional Labels** (based on priority):
+- `priority-critical` - Blocking, must implement immediately
+- `priority-high` - Important feature
+- `priority-medium` - Normal priority feature (default)
+- `priority-low` - Nice to have
+
+---
+
+### Improvement Issues (`--improvement`)
+
+**Primary Labels**: `improvement`, `enhancement`
+
+**Optional Labels** (based on priority):
+- `priority-critical` - Critical refactoring needed
+- `priority-high` - Important improvement
+- `priority-medium` - Normal priority (default)
+- `priority-low` - Technical debt, can wait
+
+---
+
+### Question/Discussion Issues (`--question`)
+
+**Primary Labels**: `question`, `help-wanted`
+
+**Optional Labels** (based on priority):
+- `priority-critical` - Urgent decision needed
+- `priority-high` - Important decision
+- `priority-medium` - Normal discussion (default)
+- `priority-low` - Optional discussion
+
+---
+
+## 🎯 Priority Emoji Mapping
+
+| Priority | Emoji | Use Case |
+|----------|-------|----------|
+| Critical | 🔴 | System outage, data loss, security breach |
+| High | 🟠 | Major feature broken, significant impact |
+| Medium | 🟡 | Normal bugs/features (default) |
+| Low | 🟢 | Minor issues, nice-to-have features |
+
+---
+
+## 🚀 Issue Type Emoji Mapping
+
+| Type | Emoji | Description |
+|------|-------|-------------|
+| Bug | 🐛 | Defect or unexpected behavior |
+| Feature | ✨ | New functionality or capability |
+| Improvement | ⚡ | Code quality, performance, or design improvement |
+| Question | ❓ | Question, discussion, or decision needed |
+
+---
+
+## 🛠️ GitHub Labels Setup
+
+To create labels in your GitHub repository, use GitHub CLI:
+
+```bash
+# Authenticate first
+gh auth login
+
+# Create bug labels
+gh label create "bug" \
+  --description "Something isn't working" \
+  --color "d73a49"
+
+gh label create "reported" \
+  --description "User-reported issue" \
+  --color "fc2929"
+
+# Create feature labels
+gh label create "feature-request" \
+  --description "New feature or request" \
+  --color "a2eeef"
+
+gh label create "enhancement" \
+  --description "Improvement or enhancement" \
+  --color "0075ca"
+
+# Create improvement label
+gh label create "improvement" \
+  --description "Performance or code quality improvement" \
+  --color "5ebcf6"
+
+# Create question labels
+gh label create "question" \
+  --description "Question for discussion" \
+  --color "fbca04"
+
+gh label create "help-wanted" \
+  --description "We need help with this" \
+  --color "fcfc03"
+
+# Create priority labels
+gh label create "priority-critical" \
+  --description "Critical priority - URGENT" \
+  --color "ff0000"
+
+gh label create "priority-high" \
+  --description "High priority" \
+  --color "ff6600"
+
+gh label create "priority-medium" \
+  --description "Medium priority" \
+  --color "ffcc00"
+
+gh label create "priority-low" \
+  --description "Low priority" \
+  --color "00cc00"
+```
+
+---
+
+## ✨ Summary
+
+This configuration enables:
+- ✅ **Standardized issue labels** across all issue types
+- ✅ **Priority indicators** with emoji for visual identification
+- ✅ **Type emoji** for quick issue categorization
+- ✅ **Automated label assignment** via `/alfred:9-feedback`
+
+For more information, see `.moai/docs/quick-issue-creation-guide.md`

moai_adk/templates/CLAUDE.md

@@ -6,7 +6,7 @@
 > **Project Owner**: {{PROJECT_OWNER}}
 > **Config**: `.moai/config.json`
 >
-> **Note**: `Skill("moai-alfred-interactive-questions")` provides TUI-based responses when user interaction is needed. The skill loads on-demand.
+> **Note**: `AskUserQuestion tool (documented in moai-alfred-interactive-questions skill)` provides TUI-based responses when user interaction is needed. The skill loads on-demand.
 
 ---
 
@@ -213,6 +213,72 @@ Combine layers when necessary: a command triggers sub-agents, sub-agents activat
 
 ---
 
+## ⚡ Alfred Command Completion Pattern
+
+**CRITICAL RULE**: When any Alfred command (`/alfred:0-project`, `/alfred:1-plan`, `/alfred:2-run`, `/alfred:3-sync`) completes, **ALWAYS use `AskUserQuestion` tool** to ask the user what to do next.
+
+### Pattern for Each Command
+
+#### `/alfred:0-project` Completion
+```
+After project initialization completes:
+├─ Use AskUserQuestion to ask:
+│  ├─ Option 1: Proceed to /alfred:1-plan (plan specifications)
+│  ├─ Option 2: Start new session with /clear
+│  └─ Option 3: Review project structure
+└─ DO NOT suggest multiple next steps in prose - use AskUserQuestion only
+```
+
+#### `/alfred:1-plan` Completion
+```
+After planning completes:
+├─ Use AskUserQuestion to ask:
+│  ├─ Option 1: Proceed to /alfred:2-run (implement SPEC)
+│  ├─ Option 2: Revise SPEC before implementation
+│  └─ Option 3: Start new session with /clear
+└─ DO NOT suggest multiple next steps in prose - use AskUserQuestion only
+```
+
+#### `/alfred:2-run` Completion
+```
+After implementation completes:
+├─ Use AskUserQuestion to ask:
+│  ├─ Option 1: Proceed to /alfred:3-sync (synchronize docs)
+│  ├─ Option 2: Run additional tests/validation
+│  └─ Option 3: Start new session with /clear
+└─ DO NOT suggest multiple next steps in prose - use AskUserQuestion only
+```
+
+#### `/alfred:3-sync` Completion
+```
+After sync completes:
+├─ Use AskUserQuestion to ask:
+│  ├─ Option 1: Return to /alfred:1-plan (next feature)
+│  ├─ Option 2: Merge PR to main
+│  └─ Option 3: Complete session
+└─ DO NOT suggest multiple next steps in prose - use AskUserQuestion only
+```
+
+### Implementation Rules
+
+1. **Always use AskUserQuestion** - Never suggest next steps in prose (e.g., "You can now run `/alfred:1-plan`...")
+2. **Provide 3-4 clear options** - Not open-ended or free-form
+3. **Language**: Present options in user's `conversation_language` (Korean, Japanese, etc.)
+4. **Question format**: Use the `moai-alfred-interactive-questions` skill documentation as reference (don't invoke Skill())
+
+### Example (Correct Pattern)
+```markdown
+# CORRECT ✅
+After project setup, use AskUserQuestion tool to ask:
+- "프로젝트 초기화가 완료되었습니다. 다음으로 뭘 하시겠습니까?"
+- Options: 1) 스펙 작성 진행 2) 프로젝트 구조 검토 3) 새 세션 시작
+
+# INCORRECT ❌
+Your project is ready. You can now run `/alfred:1-plan` to start planning specs...
+```
+
+---
+
 ## Project Information
 
 - **Name**: MoAI-ADK

{moai_adk-0.7.0.dist-info → moai_adk-0.8.1.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: moai-adk
-Version: 0.7.0
+Version: 0.8.1
 Summary: MoAI Agentic Development Kit - SPEC-First TDD with Alfred SuperAgent & Complete Skills v2.0
 Project-URL: Homepage, https://github.com/modu-ai/moai-adk
 Project-URL: Repository, https://github.com/modu-ai/moai-adk
@@ -696,8 +696,11 @@ graph TD
 | `/alfred:1-plan <description>` | Analyze requirements, draft SPEC, write Plan Board                | `.moai/specs/SPEC-*/spec.md`, plan/acceptance docs, feature branch |
 | `/alfred:2-run <SPEC-ID>`      | Execute TDD, test/implement/refactor, verify quality              | `tests/`, `src/` implementation, quality report, TAG connection    |
 | `/alfred:3-sync`               | Sync docs/README/CHANGELOG, organize TAG/PR status                | `docs/`, `.moai/reports/sync-report.md`, Ready PR                  |
+| `/alfred:9-feedback` | Interactively create GitHub Issues (type → title → description → priority) | GitHub Issue with auto labels, priority, URL        |
 
 > ❗ All commands maintain **Phase 0 (optional) → Phase 1 → Phase 2 → Phase 3** cycle structure. Alfred automatically reports execution status and next-step suggestions.
+>
+> 💡 **New in v0.7.0+**: `/alfred:9-feedback` enables instant GitHub Issue creation during development, keeping your workflow uninterrupted while keeping issues tracked and visible to the team.
 
 ---
 
@@ -814,6 +817,125 @@ When working in your **local development environment**, CodeRabbit provides auto
 
 ---
 
+## Quick Issue Creation with `/alfred:9-feedback`
+
+MoAI-ADK v0.7.0+ includes the **Quick Issue Creation** feature, allowing developers to instantly create GitHub Issues without interrupting their development workflow.
+
+### Why Quick Issue Creation?
+
+During development, you frequently encounter:
+- 🐛 Bugs that need immediate reporting
+- ✨ Feature ideas that come to mind
+- ⚡ Performance improvements to suggest
+- ❓ Architecture questions that need team discussion
+
+**The old way**: Stop coding, go to GitHub, manually fill issue form, remember what you were working on.
+**The new way**: Type one command, GitHub Issue is created instantly, continue coding.
+
+### Interactive Dialog Flow
+
+When you run `/alfred:9-help`, Alfred guides you through an interactive multi-step dialog:
+
+**Step 1: Select Issue Type**
+```
+Alfred: What type of issue do you want to create?
+[ ] 🐛 Bug Report - Something isn't working
+[ ] ✨ Feature Request - Suggest new functionality
+[ ] ⚡ Improvement - Enhance existing features
+[ ] ❓ Question/Discussion - Ask the team
+```
+
+**Step 2: Enter Issue Title**
+```
+Alfred: What's the issue title?
+Your input: "Login button not responding to clicks"
+```
+
+**Step 3: Enter Description (Optional)**
+```
+Alfred: Provide a detailed description (optional—press Enter to skip)
+Your input: "When I click the login button on iPhone 15, it freezes for 5 seconds then crashes"
+```
+
+**Step 4: Select Priority Level**
+```
+Alfred: What's the priority level?
+[ ] 🔴 Critical - System down, data loss, security breach
+[ ] 🟠 High - Major feature broken, significant impact
+[✓] 🟡 Medium - Normal priority (default)
+[ ] 🟢 Low - Minor issues, nice-to-have
+```
+
+**Step 5: Automatic Issue Creation**
+```
+Alfred automatically:
+1. Determines appropriate labels based on issue type and priority
+2. Formats title with emoji: "🐛 [BUG] Login button not responding..."
+3. Creates GitHub Issue with all information
+4. Returns the issue number and URL
+```
+
+### Key Features
+
+1. **⚡ Instant Creation**: Create GitHub Issues in seconds
+2. **🏷️ Automatic Labels**: Issue type + priority automatically labeled
+3. **🎯 Priority Selection**: Choose from Critical/High/Medium/Low
+4. **🔗 Team Visibility**: Issues immediately visible and discussable
+5. **📋 Standardized Format**: All issues follow consistent structure
+
+### Complete Example: Bug Report During Code Review
+
+```bash
+# During code review, you notice a critical issue and want to report it instantly
+$ /alfred:9-feedback
+
+Alfred: What type of issue do you want to create?
+> 🐛 Bug Report
+
+Alfred: What's the issue title?
+> Login button crash on mobile devices
+
+Alfred: Provide a detailed description (optional—press Enter to skip)
+> Tapping the login button on iPhone 15 causes app to freeze for 5 seconds then crash.
+> Tested on iOS 17.2, Chrome 120 on macOS 14.2.
+> Expected: Login modal should appear
+> Actual: No response then crash
+
+Alfred: What's the priority level?
+> 🟠 High
+
+✅ GitHub Issue #234 created successfully!
+
+📋 Title: 🐛 [BUG] Login button crash on mobile devices
+🟠 Priority: High
+🏷️  Labels: bug, reported, priority-high
+🔗 URL: https://github.com/owner/repo/issues/234
+
+💡 Next: Continue with your work—the issue is now tracked!
+```
+
+### Integration with MoAI-ADK Workflow
+
+1. **During Development**: Use `/alfred:9-help` to report bugs/ideas instantly
+2. **In Code Review**: Convert improvement suggestions to tracked issues
+3. **When Planning**: Reference created issues in SPEC documents
+4. **During Sync**: Link issues to SPEC requirements with `/alfred:3-sync`
+
+### Prerequisites
+
+- GitHub CLI (`gh`) installed and authenticated
+- Repository initialized with Git
+
+### Learn More
+
+See `.moai/docs/quick-issue-creation-guide.md` for comprehensive documentation including:
+- Detailed usage examples
+- Best practices and tips
+- Troubleshooting guide
+- Integration with SPEC documents
+
+---
+
 ## 5 Key Concepts
 
 MoAI-ADK consists of 5 key concepts. Each concept connects to the others, and together they create a powerful development system.