moai-adk 0.15.0__py3-none-any.whl → 0.25.4__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-alfred-ears-authoring/examples.md

@@ -1,29 +0,0 @@
-# moai-alfred-ears-authoring - Working Examples
-
-_Last updated: 2025-10-22_
-
-## Example 1: Basic Setup
-
-```bash
-# Setup commands
-# ...
-```
-
-## Example 2: TDD Workflow
-
-```bash
-# RED: Write failing test
-# GREEN: Implement feature
-# REFACTOR: Improve code
-```
-
-## Example 3: Quality Gate
-
-```bash
-# Run quality checks
-# Verify coverage ≥85%
-```
-
----
-
-_For more examples, see SKILL.md reference section_

moai_adk/templates/.claude/skills/moai-alfred-ears-authoring/reference.md

@@ -1,28 +0,0 @@
-# moai-alfred-ears-authoring - CLI Reference
-
-_Last updated: 2025-10-22_
-
-## Quick Reference
-
-### Installation
-
-```bash
-# Installation commands
-```
-
-### Common Commands
-
-```bash
-# Test
-# Lint
-# Format
-# Build
-```
-
-## Tool Versions (2025-10-22)
-
-_No specific tool versions (workflow/process Skill)_
-
----
-
-_For detailed usage, see SKILL.md_

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

@@ -1,323 +0,0 @@
----
-name: moai-alfred-expertise-detection
-version: 1.0.0
-created: 2025-11-02
-updated: 2025-11-02
-status: active
-description: Guide Alfred to detect user expertise level (Beginner/Intermediate/Expert) through in-session behavioral signals without memory file access
-keywords: ['expertise', 'detection', 'adaptive', 'heuristic', 'beginner', 'intermediate', 'expert', 'signals']
-allowed-tools:
-  - Read
----
-
-# Alfred Expertise Detection - Behavioral Signal Analysis
-
-## Skill Metadata
-
-| Field | Value |
-| ----- | ----- |
-| **Skill Name** | moai-alfred-expertise-detection |
-| **Version** | 1.0.0 (2025-11-02) |
-| **Status** | Active |
-| **Tier** | Alfred |
-| **Purpose** | Detect user expertise through in-session behavioral signals |
-
----
-
-## What It Does
-
-Alfred detects user expertise level (Beginner/Intermediate/Expert) by analyzing observable behaviors within the current session. No memory file access required.
-
-**Key capabilities**:
-- ✅ Real-time signal analysis (request patterns, command style, corrections)
-- ✅ Adaptive response tuning (verbosity, confirmations, suggestions)
-- ✅ Zero memory overhead (no file reads)
-- ✅ Continuous refinement throughout session
-
----
-
-## When to Use
-
-**Automatic activation**:
-- Every user request triggers subtle expertise assessment
-- Alfred adjusts behavior based on detected level
-- Signals accumulate throughout session for accuracy
-
-**Manual reference**:
-- Understanding Alfred's adaptation logic
-- Debugging unexpected behavior patterns
-- Customizing expertise thresholds
-
----
-
-## Three Expertise Levels
-
-### 🌱 Beginner (Learning Mode)
-
-**Characteristics**:
-- First time using MoAI-ADK or specific feature
-- Asks "how" and "why" questions frequently
-- Needs guidance on SPEC format, @TAG system, TDD workflow
-- Prefers step-by-step instructions
-
-**Alfred adaptations**:
-- Verbose explanations with background context
-- Proactive Skill suggestions (`Skill("name")`)
-- Frequent confirmations before actions
-- Educational tone (Technical Mentor bias)
-
----
-
-### 🔧 Intermediate (Proficient Mode)
-
-**Characteristics**:
-- Familiar with core MoAI-ADK concepts
-- Uses commands correctly but occasionally needs clarification
-- Self-corrects minor errors
-- Balanced use of commands and questions
-
-**Alfred adaptations**:
-- Concise explanations with examples
-- Conditional confirmations (ask only for high-risk)
-- Moderate proactive suggestions
-- Balanced tone (Project Manager default)
-
----
-
-### ⚡ Expert (Efficiency Mode)
-
-**Characteristics**:
-- Deep understanding of MoAI-ADK architecture
-- Direct command usage with precise syntax
-- Rarely asks clarification questions
-- Uses advanced features (custom TAGs, parallel workflows)
-
-**Alfred adaptations**:
-- Minimal explanations (action-first)
-- Skip confirmations for low/medium-risk operations
-- Automation suggestions prioritized
-- Efficiency-focused tone (Efficiency Coach bias)
-
----
-
-## Detection Signals (Heuristic Categories)
-
-### Signal Category 1: Command Usage Patterns
-
-**Beginner signals**:
-- Uses GUI-equivalent commands (`/alfred:0-project` vs manual setup)
-- Asks for command syntax help
-- Trial-and-error approach
-- Frequent "how do I..." questions
-
-**Intermediate signals**:
-- Correct command syntax with occasional flags omission
-- Asks for specific feature clarification
-- Self-corrects syntax errors
-- Balanced exploratory vs direct commands
-
-**Expert signals**:
-- Direct command invocation with correct flags
-- Chains commands efficiently
-- Uses advanced features (custom agents, hooks)
-- No syntax questions
-
----
-
-### Signal Category 2: AskUserQuestion Interaction Style
-
-**Beginner signals**:
-- Frequently selects "Other" option (unfamiliar with choices)
-- Requests explanations of options
-- Needs multiple rounds of clarification
-- Long deliberation before answering
-
-**Intermediate signals**:
-- Selects from provided options confidently
-- Occasional "Other" for valid custom cases
-- Asks follow-up questions for edge cases
-- Quick decision-making
-
-**Expert signals**:
-- Rarely triggered (request clarity high)
-- Immediate option selection
-- Provides custom input correctly
-- Requests batch questions to speed up flow
-
----
-
-### Signal Category 3: Error Recovery Behavior
-
-**Beginner signals**:
-- Requests full explanation when error occurs
-- Asks Alfred to fix errors automatically
-- Needs guidance on error message interpretation
-- Repeats similar errors
-
-**Intermediate signals**:
-- Analyzes error messages independently
-- Asks targeted questions about specific error
-- Self-corrects common errors
-- Learns from previous mistakes
-
-**Expert signals**:
-- Immediately identifies root cause
-- Proposes fix before Alfred suggests
-- Debugs independently
-- Rarely encounters errors
-
----
-
-### Signal Category 4: SPEC & Documentation Interaction
-
-**Beginner signals**:
-- Asks "What is a SPEC?"
-- Requests SPEC templates and examples
-- Needs guidance on EARS format
-- Frequently invokes `Skill("moai-foundation-specs")`
-
-**Intermediate signals**:
-- Creates SPECs with minor guidance
-- Understands EARS but occasionally needs validation
-- References documentation proactively
-- Asks for best practices
-
-**Expert signals**:
-- Creates complex SPECs independently
-- Follows EARS format naturally
-- Rarely references basic documentation
-- Contributes custom SPEC patterns
-
----
-
-### Signal Category 5: Git & Workflow Sophistication
-
-**Beginner signals**:
-- Relies on `/alfred:*` commands exclusively
-- Asks about git workflow steps
-- Needs PR creation guidance
-- Unfamiliar with branch strategies
-
-**Intermediate signals**:
-- Comfortable with basic git operations
-- Uses `/alfred:*` for complex workflows
-- Occasionally performs git operations manually
-- Understands PR review process
-
-**Expert signals**:
-- Direct git commands alongside Alfred
-- Custom branching strategies
-- Manual conflict resolution
-- Advanced git operations (rebase, cherry-pick)
-
----
-
-## Detection Algorithm
-
-```
-User Request Received
-    ↓
-Signal Analysis (5 categories)
-    ↓
-├─ Command Usage: Beginner(+2) | Intermediate(+1) | Expert(0)
-├─ AskUserQuestion: Beginner(+2) | Intermediate(+1) | Expert(0)
-├─ Error Recovery: Beginner(+2) | Intermediate(+1) | Expert(0)
-├─ SPEC Interaction: Beginner(+2) | Intermediate(+1) | Expert(0)
-└─ Git Workflow: Beginner(+2) | Intermediate(+1) | Expert(0)
-    ↓
-Weighted Score Calculation
-    ↓
-├─ Score 0-3: Expert
-├─ Score 4-7: Intermediate
-└─ Score 8-10: Beginner
-    ↓
-Adjust Alfred Behavior (verbosity, confirmations, suggestions)
-```
-
----
-
-## Behavioral Adaptations by Level
-
-### Verbosity Adjustment
-
-| Level | Explanation Length | Example Count | Context Depth |
-|-------|-------------------|---------------|---------------|
-| **Beginner** | Verbose (200-400 words) | 2-3 examples | Deep background |
-| **Intermediate** | Moderate (100-200 words) | 1-2 examples | Key points only |
-| **Expert** | Concise (50-100 words) | 0-1 examples | Action-focused |
-
----
-
-### Confirmation Threshold
-
-| Level | Low Risk | Medium Risk | High Risk |
-|-------|----------|-------------|-----------|
-| **Beginner** | Confirm | Confirm | Confirm + explanation |
-| **Intermediate** | Skip | Confirm | Confirm |
-| **Expert** | Skip | Skip | Confirm |
-
-**Risk classification** (see `moai-alfred-proactive-suggestions`):
-- Low: Read-only, typo fixes, documentation updates
-- Medium: Code changes, SPEC edits, test updates
-- High: Database migrations, destructive operations, production changes
-
----
-
-### Proactive Suggestion Frequency
-
-| Level | Suggestions/Session | Pattern Detection Threshold |
-|-------|---------------------|----------------------------|
-| **Beginner** | 3-5 | Low (suggest common patterns) |
-| **Intermediate** | 2-3 | Medium (suggest optimizations) |
-| **Expert** | 1-2 | High (suggest advanced techniques) |
-
----
-
-## Key Principles
-
-1. **No Memory Required**: Detect expertise from current session only
-2. **Continuous Refinement**: Update expertise estimate throughout session
-3. **Graceful Degradation**: Default to Intermediate if signals unclear
-4. **User Override**: Respect explicit user requests (e.g., "quick" keyword forces Expert mode)
-5. **Transparency**: Behavioral changes subtle, not disruptive
-
----
-
-## Integration with Persona Roles
-
-**Expertise detection influences role selection**:
-
-```
-Detected: Beginner
-    ↓
-Role bias: Technical Mentor (education priority)
-
-Detected: Intermediate
-    ↓
-Role bias: Project Manager (structure priority)
-
-Detected: Expert
-    ↓
-Role bias: Efficiency Coach (speed priority)
-```
-
-**Override rules**:
-- User keywords ("quick", "explain") override expertise detection
-- Command type (`/alfred:*`) forces Project Manager regardless of expertise
-- Team mode forces Collaboration Coordinator
-
----
-
-## Observable Signals Summary
-
-| Signal Type | Beginner | Intermediate | Expert |
-|-------------|----------|--------------|--------|
-| **Questions** | "How?", "Why?", "What is?" | "Can I?", "Should I?" | Direct commands |
-| **Corrections** | Repeats errors | Self-corrects | Rarely errors |
-| **Syntax** | Trial-and-error | Mostly correct | Always correct |
-| **Docs** | Frequent Skill refs | Occasional refs | Rare refs |
-| **Workflow** | GUI-equivalent | Commands + questions | Direct commands |
-
----
-
-**End of Skill** | 2025-11-02

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

@@ -1,286 +0,0 @@
-# Alfred Expertise Detection - Real-World Examples
-
-> **Main Skill**: [SKILL.md](SKILL.md)  
-> **API Reference**: [reference.md](reference.md)
-
----
-
-## Example 1: Beginner Detection (First-Time User)
-
-### User Behavior
-
-```
-User: "What is MoAI-ADK?"
-User: "How do I start?"
-User: "What's a SPEC?"
-User: (tries command) "/alfred project"
-User: "It didn't work, what's the right syntax?"
-```
-
-### Signal Analysis
-
-| Signal Category | Observation | Score |
-|-----------------|-------------|-------|
-| Command Usage | Incorrect syntax, asks for help | +2 |
-| Questions | Fundamental "what is" questions | +2 |
-| Error Recovery | Needs syntax guidance | +2 |
-| Documentation | Unfamiliar with SPEC concept | +2 |
-| Git Workflow | N/A (not yet used) | 0 |
-
-**Total Score**: 8 → **Beginner**
-
-### Alfred Adaptation
-
-**Verbosity**: High (300-word explanations)
-**Confirmations**: All operations confirmed
-**Suggestions**: 4-5 proactive tips per session
-**Role Bias**: Technical Mentor
-
-**Response Example**:
-```
-MoAI-ADK is an Agentic Development Kit that follows SPEC-first TDD workflow.
-
-Background:
-SPECs are structured requirements documents following EARS format. They 
-define what to build before writing code. Alfred helps you create SPECs, 
-implement them via TDD, and keep documentation synchronized.
-
-To start:
-1. Run /alfred:0-project to initialize project
-2. Then /alfred:1-plan to create your first SPEC
-3. Then /alfred:2-run to implement via TDD
-
-Related Skills to learn:
-- Skill("moai-foundation-specs") - SPEC structure
-- Skill("moai-foundation-tags") - @TAG traceability
-- Skill("moai-foundation-trust") - TRUST 5 principles
-
-Would you like me to guide you through /alfred:0-project step-by-step?
-```
-
----
-
-## Example 2: Intermediate Detection (Regular User)
-
-### User Behavior
-
-```
-User: "/alfred:1-plan"
-Alfred: "What's the SPEC title?"
-User: "User authentication with JWT"
-User: (creates SPEC, but forgets @TAG in one section)
-User: "Can I add the @TAG retroactively?"
-```
-
-### Signal Analysis
-
-| Signal Category | Observation | Score |
-|-----------------|-------------|-------|
-| Command Usage | Correct command syntax | +1 |
-| Questions | Specific clarification ("Can I?") | +1 |
-| Error Recovery | Notices mistake, asks fix | +1 |
-| Documentation | Knows SPEC format, @TAG concept | +1 |
-| Git Workflow | Uses /alfred commands | +1 |
-
-**Total Score**: 5 → **Intermediate**
-
-### Alfred Adaptation
-
-**Verbosity**: Moderate (150-word explanations)
-**Confirmations**: Only for medium/high-risk
-**Suggestions**: 2-3 optimizations per session
-**Role Bias**: Project Manager
-
-**Response Example**:
-```
-Yes, you can add @TAGs retroactively.
-
-Edit .moai/specs/SPEC-AUTH-001/spec.md and insert:
-  @SPEC:AUTH-001:JWT-VALIDATION
-
-Then run /alfred:3-sync to update documentation links.
-
-Best practice: Add @TAGs during SPEC creation to avoid this step.
-
-Proceed with manual edit?
-  [Yes, I'll edit now] [No, regenerate SPEC]
-```
-
----
-
-## Example 3: Expert Detection (Power User)
-
-### User Behavior
-
-```
-User: "/alfred:2-run SPEC-AUTH-001 && git add . && git commit -m 'feat(auth): JWT impl'"
-User: (test fails)
-User: (fixes code directly without asking)
-User: (reruns tests)
-User: (creates PR with gh CLI)
-```
-
-### Signal Analysis
-
-| Signal Category | Observation | Score |
-|-----------------|-------------|-------|
-| Command Usage | Advanced command chaining | 0 |
-| Questions | Zero questions asked | 0 |
-| Error Recovery | Self-debugs, fixes independently | 0 |
-| Documentation | No documentation references | 0 |
-| Git Workflow | Direct git + gh commands | 0 |
-
-**Total Score**: 0 → **Expert**
-
-### Alfred Adaptation
-
-**Verbosity**: Minimal (50-word updates)
-**Confirmations**: Skip all except high-risk
-**Suggestions**: 1 advanced tip per session
-**Role Bias**: Efficiency Coach
-
-**Response Example**:
-```
-SPEC-AUTH-001 implemented.
-
-Files: src/auth/jwt.py, tests/test_auth.py
-Tests: 12/12 passing
-Coverage: 95%
-Commit: c9f82a3
-
-PR #142 created.
-```
-
----
-
-## Example 4: Adaptive Learning (Beginner → Intermediate)
-
-### Session Start (Beginner)
-
-```
-User: "How do I create a SPEC?" (Question keyword +2)
-Alfred: (Verbose explanation with examples)
-
-User: (follows steps, creates SPEC)
-Alfred: "Great! Ready for /alfred:2-run?" (Confirmation)
-```
-
-**Score**: 8 → Beginner
-
-### Session Middle (Still Beginner, but improving)
-
-```
-User: "/alfred:2-run SPEC-PROFILE-001" (Correct syntax +1)
-Alfred: (Moderate explanation, less verbose)
-```
-
-**Score**: 6 → Beginner (borderline)
-
-### Session End (Intermediate)
-
-```
-User: "Fix typo in line 42" (Direct command +1, no question)
-User: (self-corrects minor error without asking +1)
-```
-
-**Score**: 4 → Intermediate
-
-**Alfred adaptation**: Switches from Technical Mentor to Project Manager mid-session
-
----
-
-## Example 5: Override Mechanism (Expert User Asks for Explanation)
-
-### User Behavior
-
-```
-User: (Detected as Expert from previous commands)
-User: "Explain why TRUST 5 requires test-first?"
-```
-
-### Signal Analysis
-
-**Baseline**: Expert (score 0 from previous requests)
-
-**Override detected**:
-- Keyword: "Explain" → Force Beginner mode for this request
-
-### Alfred Adaptation
-
-**Normal Expert response**: "TRUST 5 = Test First, Readable, Unified, Secured, Trackable."
-
-**Override to Beginner mode**:
-```
-TRUST 5 principle "Test First" ensures code correctness through TDD.
-
-Why test-first matters:
-- Write failing test (RED) → defines expected behavior
-- Implement code (GREEN) → satisfies test requirements
-- Refactor (REFACTOR) → improve code with safety net
-
-Without test-first:
-- Risk: Code written without clear requirements
-- Risk: Tests written to match code (not requirements)
-- Risk: "Works on my machine" syndrome
-
-Example from your workflow:
-  1. Write test: test_jwt_validation_rejects_expired_token()
-  2. Run test: FAIL (function not implemented)
-  3. Implement: def validate_jwt(token) → checks expiry
-  4. Run test: PASS (behavior verified)
-  5. Refactor: Optimize without breaking test
-
-This cycle ensures every line of code has a verified purpose.
-
-Related: Skill("moai-foundation-trust") for full TRUST 5 guide
-```
-
-**Characteristics**: Expert user received Beginner-level explanation due to "Explain" keyword
-
----
-
-## Example 6: Signal Conflict Resolution
-
-### User Behavior
-
-```
-User: "/alfred:1-plan" (Correct syntax +1)
-User: "What's the difference between SPEC and plan?" (Basic question +2)
-User: (Creates SPEC successfully) (+1)
-User: "How do @TAGs work?" (Basic question +2)
-```
-
-### Signal Analysis
-
-**Conflicting signals**:
-- Command usage: Intermediate (+1)
-- Questions: Beginner (+2, +2)
-- SPEC creation: Intermediate (+1)
-- @TAG knowledge: Beginner (+2)
-
-**Total Score**: 8 → **Beginner**
-
-**Resolution**: Beginner dominates (questions outweigh command proficiency)
-
-### Alfred Adaptation
-
-**Behavior**: Technical Mentor mode
-**Rationale**: User understands mechanics (commands) but lacks conceptual knowledge (@TAGs, SPEC)
-
-**Response Strategy**: Provide educational explanations while leveraging command proficiency
-
----
-
-## Summary: Expertise Level Indicators
-
-| Observable Behavior | Beginner | Intermediate | Expert |
-|---------------------|----------|--------------|--------|
-| **First request** | "What is...?" | Correct command | Command chain |
-| **Error handling** | "Fix this for me" | "Why did this fail?" | (Fixes silently) |
-| **Documentation** | Frequent Skill() | Occasional Skill() | No Skill() |
-| **Confirmations** | Needs all | Needs some | Needs none |
-| **Learning curve** | Steep | Moderate | Flat |
-
----
-
-**End of Examples** | 2025-11-02