moai-adk 0.4.5__py3-none-any.whl → 0.20.1__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-alfred-expertise-detection/reference.md

@@ -0,0 +1,126 @@
+# Alfred Expertise Detection - Quick Reference
+
+> **Main Skill**: [SKILL.md](SKILL.md)  
+> **Examples**: [examples.md](examples.md)
+
+---
+
+## Signal Detection Cheat Sheet
+
+| Signal Type | Beginner | Intermediate | Expert | Weight |
+|-------------|----------|--------------|--------|--------|
+| **Command Syntax** | Trial-and-error | Mostly correct | Always correct | +2/+1/0 |
+| **Questions** | "How?", "Why?" | "Can I?" | Direct commands | +2/+1/0 |
+| **Error Recovery** | Needs help | Self-corrects | Debugs alone | +2/+1/0 |
+| **Documentation** | Frequent refs | Occasional refs | Rare refs | +2/+1/0 |
+| **Git Workflow** | `/alfred:*` only | Mixed usage | Direct git | +2/+1/0 |
+
+**Score calculation**: Sum all weights → 0-3=Expert, 4-7=Intermediate, 8-10=Beginner
+
+---
+
+## Behavioral Adaptation Matrix
+
+### Response Verbosity
+
+| Level | Length | Examples | Context |
+|-------|--------|----------|---------|
+| Beginner | 200-400 words | 2-3 | Deep background |
+| Intermediate | 100-200 words | 1-2 | Key points |
+| Expert | 50-100 words | 0-1 | Action-focused |
+
+### Confirmation Gates
+
+| Risk Level | Beginner | Intermediate | Expert |
+|------------|----------|--------------|--------|
+| **Low** | Confirm | Skip | Skip |
+| **Medium** | Confirm | Confirm | Skip |
+| **High** | Confirm + explain | Confirm | Confirm |
+
+### Proactive Suggestions
+
+| Level | Suggestions/Session | Threshold |
+|-------|---------------------|-----------|
+| Beginner | 3-5 | Low (common patterns) |
+| Intermediate | 2-3 | Medium (optimizations) |
+| Expert | 1-2 | High (advanced techniques) |
+
+---
+
+## Quick Decision Tree
+
+```
+User Request
+    ↓
+Analyze 5 signals (commands, questions, errors, docs, git)
+    ↓
+Calculate weighted score (0-10)
+    ↓
+├─ 0-3: Expert → Efficiency Coach bias
+├─ 4-7: Intermediate → Project Manager bias
+└─ 8-10: Beginner → Technical Mentor bias
+    ↓
+Apply adaptations (verbosity, confirmations, suggestions)
+```
+
+---
+
+## Override Mechanisms
+
+**User keywords override detection**:
+- "quick", "fast" → Force Expert mode
+- "explain", "how", "why" → Force Beginner mode
+- `/alfred:*` commands → Force Project Manager (Intermediate)
+
+**Example**:
+- Detected: Expert (score 2)
+- User says: "explain @TAG system"
+- Override: Beginner mode (verbose explanation)
+
+---
+
+## Signal Examples
+
+### Beginner Signal Pattern
+
+```
+User: "How do I create a SPEC?"
+Alfred detects:
+  - Question keyword: "How" (+2)
+  - Documentation unfamiliarity (+2)
+  - No direct command usage (+2)
+  
+Score: 6 → Beginner
+
+Response: Verbose explanation with Skill("moai-foundation-specs")
+```
+
+### Expert Signal Pattern
+
+```
+User: "/alfred:2-run SPEC-AUTH-001"
+Alfred detects:
+  - Direct command with correct syntax (0)
+  - No questions (0)
+  - Knows SPEC ID format (0)
+  
+Score: 0 → Expert
+
+Response: Execute immediately, minimal output
+```
+
+---
+
+## Integration Hooks
+
+**Called by**:
+- Every Alfred request (implicit)
+- `moai-alfred-persona-roles` (role selection)
+- `moai-alfred-proactive-suggestions` (suggestion threshold)
+
+**Calls**:
+- None (standalone signal analysis)
+
+---
+
+**End of Reference** | 2025-11-02

moai_adk/templates/.claude/skills/moai-alfred-issue-labels/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: moai-alfred-issue-labels
+version: 1.1.0
+created: 2025-11-05
+updated: 2025-11-05
+status: active
+description: GitHub issue label configuration, label taxonomy, and workflow automation mapping for MoAI-ADK projects
+keywords: ['github', 'issues', 'labels', 'workflow', 'taxonomy', 'automation']
+allowed-tools:
+  - Read
+  - Bash
+---
+
+# Alfred Issue Labels Skill
+
+## Skill Metadata
+
+| Field | Value |
+| ----- | ----- |
+| **Skill Name** | moai-alfred-issue-labels |
+| **Version** | 1.1.0 (2025-11-05) |
+| **Status** | Active |
+| **Tier** | Alfred |
+| **Purpose** | Standardize GitHub issue labeling and workflow automation |
+
+---
+
+## What It Does
+
+Provides comprehensive GitHub issue label configuration, taxonomy management, and workflow automation mapping for MoAI-ADK projects. Ensures consistent issue categorization and priority management across all repositories.
+
+**Key capabilities**:
+- ✅ Standardized label taxonomy for all issue types
+- ✅ Priority-based labeling system (critical/high/medium/low)
+- ✅ Workflow automation mappings
+- ✅ Consistent issue management across projects
+- ✅ Integration with Alfred command workflows
+
+---
+
+## When to Use
+
+**Automatic triggers**:
+- Creating new issues via `/alfred:9-feedback`
+- Issue triage and classification
+- Project setup and configuration
+- Label management and cleanup
+
+**Manual reference**:
+- Understanding label taxonomy
+- Setting up new repositories
+- Training team members on issue management
+- Customizing workflow automation
+
+---
+
+## Label Taxonomy System
+
+### Bug Issues (`--bug`)
+
+**Primary Labels**: `bug`, `reported`
+
+**Priority Labels**:
+- `priority-critical` - System down, data loss risk
+- `priority-high` - Major feature broken
+- `priority-medium` - Normal bug (default)
+- `priority-low` - Minor issue, cosmetic
+
+**Usage Pattern**:
+```bash
+/alfred:9-feedback --bug --priority-high "Login system broken"
+```
+
+### Feature Request Issues (`--feature`)
+
+**Primary Labels**: `feature-request`, `enhancement`
+
+**Priority Labels**:
+- `priority-critical` - Blocking, must implement immediately
+- `priority-high` - Important feature
+- `priority-medium` - Normal priority (default)
+- `priority-low` - Nice to have
+
+**Usage Pattern**:
+```bash
+/alfred:9-feedback --feature --priority-medium "Add dark mode support"
+```
+
+### Improvement Issues (`--improvement`)
+
+**Primary Labels**: `improvement`, `enhancement`
+
+**Priority Labels**:
+- `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`, `discussion`
+
+**Usage Patterns**:
+- Technical questions and clarifications
+- Architecture discussions
+- Feature feedback and suggestions
+- Community engagement
+
+---
+
+## Workflow Automation Mappings
+
+### Label-Based Automation
+
+**Critical Priority**:
+- Immediate notification to maintainers
+- Auto-assignment to lead developers
+- SLA: 24-hour response time
+
+**High Priority**:
+- Enhanced visibility in project boards
+- Auto-add to milestone planning
+- SLA: 72-hour response time
+
+**Medium Priority**:
+- Standard workflow processing
+- Regular backlog grooming
+- Normal development cycle
+
+**Low Priority**:
+- Future consideration queue
+- Community contribution opportunities
+- Best-effort timeline
+
+---
+
+## Integration with Alfred Commands
+
+### `/alfred:9-feedback` Command Integration
+
+```bash
+# Create bug report with automatic labeling
+/alfred:9-feedback --bug --priority-high "Critical issue description"
+
+# Create feature request
+/alfred:9-feedback --feature --priority-medium "Feature description"
+
+# Create improvement suggestion
+/alfred:9-feedback --improvement --priority-low "Improvement idea"
+```
+
+### Auto-Assignment Rules
+
+- **Bug issues** → Assign to bug-fix team
+- **Feature requests** → Assign to feature team
+- **Documentation** → Assign to docs team
+- **Infrastructure** → Assign to DevOps team
+
+---
+
+## Best Practices
+
+✅ **DO**:
+- Always select appropriate primary label type
+- Use priority labels consistently
+- Provide detailed descriptions
+- Link related issues with dependencies
+- Update labels when issue scope changes
+- Follow team response SLAs
+
+❌ **DON'T**:
+- Mix primary label types (bug + feature)
+- Use priority labels without justification
+- Leave issues unlabeled
+- Ignore label-based automation
+- Create custom labels without team consensus
+
+---
+
+## Repository Setup
+
+### Required Labels (Minimum Set)
+
+```bash
+# Primary type labels
+bug, feature-request, improvement, question, documentation
+
+# Priority labels  
+priority-critical, priority-high, priority-medium, priority-low
+
+# Status labels
+needs-triage, in-progress, blocked, ready-for-review, done
+```
+
+### Optional Enhanced Labels
+
+```bash
+# Team labels
+team-frontend, team-backend, team-devops, team-docs
+
+# Component labels
+component-ui, component-api, component-database, component-auth
+
+# Type-specific labels
+performance, security, accessibility, testing, refactoring
+```
+
+---
+
+## Quality Metrics
+
+**Label Compliance Rate**: Target >95%
+- Issues with proper primary label
+- Issues with appropriate priority
+- Response time compliance by priority
+
+**Automation Success Rate**: Target >90%
+- Correct auto-assignments
+- Proper workflow routing
+- SLA compliance tracking
+
+---
+
+Learn more in `reference.md` for complete label definitions, automation workflows, and team configuration details.
+
+**Related Skills**: 
+- `moai-alfred-workflow` - Issue workflow management
+- `moai-alfred-agent-guide` - Team coordination
+- `moai-foundation-specs` - Requirements management

moai_adk/templates/.claude/skills/moai-alfred-issue-labels/examples.md

@@ -0,0 +1,4 @@
+# Examples
+
+See `reference.md` for practical examples and usage patterns.
+

moai_adk/templates/.claude/skills/moai-alfred-issue-labels/reference.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/skills/moai-alfred-language-detection/SKILL.md

@@ -1,99 +1,113 @@
 ---
-
 name: moai-alfred-language-detection
-description: Detects the project’s primary language/runtime and recommends default testing tooling when initializing or planning workflows. Use when sizing up the project language and default tooling.
+version: 2.0.0
+created: 2025-10-22
+updated: 2025-10-22
+status: active
+description: Auto-detects project language and framework from package.json, pyproject.toml, etc.
+keywords: ['language', 'detection', 'framework', 'auto']
 allowed-tools:
   - Read
-  - Write
-  - Edit
   - Bash
-  - TodoWrite
 ---
 
-# Alfred Language Detection
+# Alfred Language Detection Skill
 
 ## Skill Metadata
+
 | Field | Value |
 | ----- | ----- |
-| Allowed tools | Read (read_file), Write (write_file), Edit (edit_file), Bash (terminal), TodoWrite (todo_write) |
-| Auto-load | /alfred:0-project bootstrap |
-| Trigger cues | Repository language probing, framework detection, tooling recommendation via Alfred. |
-
-## What it does
-
-Automatically detects project's primary language and framework by scanning configuration files, then recommends appropriate testing tools and linters.
-
-## When to use
-
-- Activates when Alfred needs to detect project languages or recommend toolchains.
-- "Detect language", "Check project language", "Recommend testing tools"
-- Automatically invoked by `/alfred:0-project`, `/alfred:2-run`
-- Setting up new project
-
-## How it works
-
-**Configuration File Scanning**:
-- `package.json` → TypeScript/JavaScript (Jest/Vitest, ESLint/Biome)
-- `pyproject.toml` → Python (pytest, ruff, black)
-- `Cargo.toml` → Rust (cargo test, clippy, rustfmt)
-- `go.mod` → Go (go test, golint, gofmt)
-- `Gemfile` → Ruby (RSpec, RuboCop)
-- `pubspec.yaml` → Dart/Flutter (flutter test, dart analyze)
-- `build.gradle` → Java/Kotlin (JUnit, Checkstyle)
-- `Package.swift` → Swift (XCTest, SwiftLint)
-
-**Toolchain Recommendation**:
-```json
-{
-  "language": "Python",
-  "test_framework": "pytest",
-  "linter": "ruff",
-  "formatter": "black",
-  "type_checker": "mypy",
-  "package_manager": "uv"
-}
-```
-
-**Framework Detection**:
-- **Python**: FastAPI, Django, Flask
-- **TypeScript**: React, Next.js, Vue
-- **Java**: Spring Boot, Quarkus
-
-**Supported Languages**: Python, TypeScript, Java, Go, Rust, Ruby, Dart, Swift, Kotlin, PHP, C#, C++, Elixir, Scala, Clojure (20+ languages)
+| **Skill Name** | moai-alfred-language-detection |
+| **Version** | 2.0.0 (2025-10-22) |
+| **Allowed tools** | Read (read_file), Bash (terminal) |
+| **Auto-load** | On demand when keywords detected |
+| **Tier** | Alfred |
 
-## Best Practices
-- The text shown to the user is written using TUI/report expressions.
-- When running the tool, a summary of commands and results are recorded.
+---
 
-## Examples
-```markdown
-- Call this skill inside the /alfred command to generate a report.
-- Add summary to Completion Report.
-```
+## What It Does
+
+Auto-detects project language and framework from package.json, pyproject.toml, etc.
+
+**Key capabilities**:
+- ✅ Best practices enforcement for alfred domain
+- ✅ TRUST 5 principles integration
+- ✅ Latest tool versions (2025-10-22)
+- ✅ TDD workflow support
+
+---
+
+## When to Use
+
+**Automatic triggers**:
+- Related code discussions and file patterns
+- SPEC implementation (`/alfred:2-run`)
+- Code review requests
+
+**Manual invocation**:
+- Review code for TRUST 5 compliance
+- Design new features
+- Troubleshoot issues
+
+---
 
 ## Inputs
-- MoAI-ADK project context (`.moai/project/`, `.claude/` templates, etc.).
-- Parameters passed from user commands or higher commands.
+
+- Language-specific source directories
+- Configuration files
+- Test suites and sample data
 
 ## Outputs
-- Reports, checklists or recommendations for your Alfred workflow.
-- Structured data for subsequent subagent calls.
+
+- Test/lint execution plan
+- TRUST 5 review checkpoints
+- Migration guidance
 
 ## Failure Modes
-- When required input documents are missing or permissions are limited.
-- When disruptive changes are required without user approval.
+
+- When required tools are not installed
+- When dependencies are missing
+- When test coverage falls below 85%
 
 ## Dependencies
-- Cooperation with higher-level agents such as cc-manager and project-manager is required.
 
-## References
-- GitHub Linguist. "Programmatic language detection." https://github.com/github-linguist/linguist (accessed 2025-03-29).
-- JetBrains. "Project language insights." https://www.jetbrains.com/help/idea/project-tool-window.html (accessed 2025-03-29).
+- Access to project files via Read/Bash tools
+- Integration with `moai-foundation-langs` for language detection
+- Integration with `moai-foundation-trust` for quality gates
+
+---
+
+## References (Latest Documentation)
+
+_Documentation links updated 2025-10-22_
+
+---
 
 ## Changelog
-- 2025-03-29: Added input/output/failure response to Alfred-specific skills.
 
-## Works well with
+- **v2.0.0** (2025-10-22): Major update with latest tool versions, comprehensive best practices, TRUST 5 integration
+- **v1.0.0** (2025-03-29): Initial Skill release
+
+---
+
+## Works Well With
+
+- `moai-foundation-trust` (quality gates)
+- `moai-alfred-code-reviewer` (code review)
+- `moai-essentials-debug` (debugging support)
+
+---
+
+## Best Practices
 
-- alfred-trust-validation (language-specific tool verification)
-- alfred-code-reviewer (language-specific review criteria)
+✅ **DO**:
+- Follow alfred best practices
+- Use latest stable tool versions
+- Maintain test coverage ≥85%
+- Document all public APIs
+
+❌ **DON'T**:
+- Skip quality gates
+- Use deprecated tools
+- Ignore security warnings
+- Mix testing frameworks