oh-my-customcode 0.1.3 → 0.2.0

package/templates/agents/manager/supplier/refs/rules/MUST-continuous-improvement.md

@@ -1,132 +0,0 @@
-# [MUST] Continuous Improvement Rules
-
-> **Priority**: MUST - Top-level enforcement
-> **ID**: R016
-> **Trigger**: User points out rule violation
-
-## CRITICAL
-
-**When user points out a rule violation, you MUST update the rules to prevent future violations BEFORE continuing with the task.**
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  WHEN USER POINTS OUT A VIOLATION:                               ║
-║                                                                   ║
-║  1. STOP current task immediately                                ║
-║  2. UPDATE the relevant rule to be clearer/stronger              ║
-║  3. COMMIT the rule update                                       ║
-║  4. THEN continue with the original task                         ║
-║                                                                   ║
-║  DO NOT just apologize and continue.                             ║
-║  DO NOT promise to do better next time.                          ║
-║  ACTUALLY UPDATE THE RULES.                                      ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-## Workflow
-
-```
-User points out violation
-         │
-         ▼
-┌─────────────────────────┐
-│ 1. Acknowledge violation │
-└───────────┬─────────────┘
-            │
-            ▼
-┌─────────────────────────┐
-│ 2. Identify root cause   │
-│    - Which rule was weak?│
-│    - What was unclear?   │
-└───────────┬─────────────┘
-            │
-            ▼
-┌─────────────────────────┐
-│ 3. Update the rule       │
-│    - Add clarity         │
-│    - Add examples        │
-│    - Add self-checks     │
-└───────────┬─────────────┘
-            │
-            ▼
-┌─────────────────────────┐
-│ 4. Commit the change     │
-└───────────┬─────────────┘
-            │
-            ▼
-┌─────────────────────────┐
-│ 5. Continue original task│
-│    (now following rules) │
-└─────────────────────────┘
-```
-
-## Examples
-
-### Example 1: Parallel Execution Violation
-
-```
-User: "병렬 실행을 안 지킨거 아닌가?"
-
-WRONG Response:
-  "맞습니다, 죄송합니다. 다음부터 잘 지키겠습니다."
-  [continues task without updating rules]
-
-CORRECT Response:
-  1. "맞습니다. R009 위반입니다."
-  2. [Updates MUST-parallel-execution.md with clearer guidance]
-  3. [Commits the update]
-  4. [Continues task with proper parallel execution]
-```
-
-### Example 2: Wrong Agent Used
-
-```
-User: "creator 에이전트를 써야 하는거 아닌가?"
-
-WRONG Response:
-  "맞습니다. creator를 사용하겠습니다."
-  [continues without updating rules]
-
-CORRECT Response:
-  1. "맞습니다. R010 위반입니다."
-  2. [Updates relevant rules to clarify agent delegation]
-  3. [Commits the update]
-  4. [Continues with proper agent delegation]
-```
-
-## Why This Matters
-
-```
-Without rule updates:
-  Violation → Apology → Same mistake later → Apology → ...
-
-With rule updates:
-  Violation → Rule improvement → Better behavior → Learning preserved
-```
-
-1. **Institutional Memory**: Rules capture learnings permanently
-2. **Prevents Recurrence**: Clearer rules = fewer future violations
-3. **Continuous Improvement**: System gets better over time
-4. **Accountability**: Actions, not just words
-
-## Integration with Other Rules
-
-This rule takes precedence when violations are pointed out:
-
-| Situation | Action |
-|-----------|--------|
-| User points out violation | STOP → Update rule → Continue |
-| Self-detected violation | Fix immediately, consider rule update |
-| Ambiguous situation | Ask user, then update if needed |
-
-## Enforcement
-
-```
-Violation of this rule = Ignoring user feedback = Unacceptable
-
-When caught violating this rule:
-1. Stop immediately
-2. Update THIS rule to be even clearer
-3. Update the ORIGINAL violated rule
-4. Continue with proper behavior
-```

package/templates/agents/manager/supplier/refs/rules/MUST-intent-transparency.md

@@ -1,199 +0,0 @@
-# [MUST] Intent Transparency Rules
-
-> **Priority**: MUST - Required for user control
-> **ID**: R015
-
-## Purpose
-
-Ensure transparency when automatically detecting user intent and routing to agents. Users should always understand why a specific agent was chosen.
-
-## Detection Display (REQUIRED)
-
-When intent is detected, display the reasoning:
-
-```
-[Intent Detected]
-├── Input: "{user input}"
-├── Agent: {detected-agent}
-├── Confidence: {percentage}%
-└── Reason: {explanation}
-```
-
-## Confidence Thresholds
-
-| Confidence | Action |
-|------------|--------|
-| >= 90% | Auto-execute with display |
-| 70-89% | Request confirmation |
-| < 70% | List options for user to choose |
-
-## Detection Factors
-
-Intent is detected using multiple factors:
-
-```yaml
-factors:
-  keywords:
-    weight: 40
-    description: Language-specific keywords in input
-    example: "Go", "Python", "리뷰", "생성"
-
-  file_patterns:
-    weight: 30
-    description: File extensions mentioned or in context
-    example: "*.go", "main.py"
-
-  action_verbs:
-    weight: 20
-    description: Action words in user input
-    example: "review", "create", "fix", "리뷰", "생성"
-
-  context:
-    weight: 10
-    description: Recent conversation context
-    example: Previous agent used, current working directory
-```
-
-## High Confidence Display (>= 90%)
-
-```
-[Intent Detected]
-├── Input: "Go 코드 리뷰해줘"
-├── Agent: golang-expert
-├── Confidence: 95%
-└── Reason: "Go" keyword (40%) + "리뷰" action verb (55%)
-
-Executing...
-```
-
-## Medium Confidence Display (70-89%)
-
-```
-[Intent Detected]
-├── Input: "백엔드 코드 체크해줘"
-├── Agent: go-backend-expert (?)
-├── Confidence: 75%
-└── Reason: "백엔드" keyword (40%) + "체크" action (35%)
-
-Possible alternatives:
-  1. go-backend-expert (75%)
-  2. fastapi-expert (65%)
-  3. springboot-expert (60%)
-
-Proceed with go-backend-expert? [Y/n/1-3]
-```
-
-## Low Confidence Display (< 70%)
-
-```
-[Intent Unclear]
-├── Input: "이 코드 좀 봐줘"
-├── Confidence: < 70%
-└── Need more context
-
-Available agents for code review:
-  1. golang-expert (Go files)
-  2. python-expert (Python files)
-  3. typescript-expert (TypeScript files)
-  4. rust-expert (Rust files)
-
-Which agent should review the code? [1-4]
-```
-
-## Override Syntax
-
-Users can explicitly specify an agent:
-
-```
-@{agent-name} {command}
-```
-
-Examples:
-```
-@golang-expert review this code
-@python-expert src/main.py 분석해줘
-@secretary create a new agent
-```
-
-Override bypasses intent detection:
-
-```
-[Override] Agent explicitly specified: python-expert
-Executing...
-```
-
-## Implementation
-
-### Secretary Workflow
-
-```
-1. Receive user input
-2. Check for explicit override (@agent)
-3. If no override:
-   a. Extract keywords, file patterns, action verbs
-   b. Match against agent triggers
-   c. Calculate confidence score
-   d. Display detection reasoning
-   e. Execute or request confirmation based on threshold
-4. Route to selected agent
-```
-
-### Detection Log
-
-For debugging and transparency:
-
-```yaml
-detection_log:
-  input: "Go 코드 리뷰해줘"
-  extracted:
-    keywords: ["Go"]
-    file_patterns: []
-    action_verbs: ["리뷰"]
-  matches:
-    - agent: golang-expert
-      score: 95
-      breakdown:
-        keyword_go: 40
-        action_review: 40
-        context: 15
-  selected: golang-expert
-  confidence: 95%
-```
-
-## Agent Triggers
-
-Each agent has defined triggers in:
-`skills/orchestration/intent-detection/patterns/agent-triggers.yaml`
-
-```yaml
-agents:
-  golang-expert:
-    keywords: [go, golang, "go 언어"]
-    file_patterns: ["*.go", "go.mod", "go.sum"]
-    actions: [review, analyze, fix, optimize]
-    base_confidence: 40
-
-  python-expert:
-    keywords: [python, py, "파이썬"]
-    file_patterns: ["*.py", "requirements.txt", "pyproject.toml"]
-    actions: [review, analyze, fix, optimize]
-    base_confidence: 40
-```
-
-## Benefits
-
-1. **Transparency**: Users understand agent selection
-2. **Control**: Users can override or choose alternatives
-3. **Trust**: Clear reasoning builds user confidence
-4. **Learning**: Users learn which agents handle what
-5. **Debugging**: Clear logs for troubleshooting
-
-## Violations
-
-Proceeding without displaying intent reasoning = Rule violation
-
-The user must always know:
-- Which agent was selected
-- Why it was selected
-- What confidence level
-- How to override if needed

package/templates/agents/manager/supplier/refs/rules/MUST-language-policy.md

@@ -1,62 +0,0 @@
-# [MUST] Language & Delegation Policy
-
-> **Priority**: MUST - Never violate
-> **ID**: R000
-
-## Core Principles
-
-### 1. User Input Language
-```
-User prompts are in Korean.
-Always understand and process Korean input.
-```
-
-### 2. Output Language
-
-| Context | Language | Example |
-|---------|----------|---------|
-| User communication | Korean | 상태 보고, 질문, 설명 |
-| Code | English | variables, functions, comments |
-| File contents | English | .md, .yaml, configs |
-| Commit messages | English | git commits |
-| Error messages to user | Korean | 에러 설명, 해결 방안 |
-
-### 3. Delegation Model
-```
-User does NOT directly edit files.
-User delegates ALL file operations to AI agent.
-
-User → (Korean prompt) → Agent → (file operations)
-```
-
-### 4. Context Efficiency
-```
-All file contents in English for:
-- Token efficiency
-- Consistent parsing
-- Universal compatibility
-```
-
-## Examples
-
-### Correct
-```
-User: "새로운 에이전트를 만들어줘"
-Agent: "에이전트를 생성하겠습니다." (Korean to user)
-Agent writes AGENT.md in English
-```
-
-### Incorrect
-```
-Agent writes: "# 에이전트 이름" in file  ← Wrong
-Agent writes: "# Agent Name" in file     ← Correct
-```
-
-## File Naming
-
-| Type | Convention | Example |
-|------|------------|---------|
-| Rules | `{PRIORITY}-{name}.md` | `MUST-safety.md` |
-| Agents | `AGENT.md` | - |
-| Skills | `SKILL.md` | - |
-| Index | `index.yaml` | - |

package/templates/agents/manager/supplier/refs/rules/MUST-orchestrator-coordination.md

@@ -1,291 +0,0 @@
-# [MUST] Orchestrator Coordination Rules
-
-> **Priority**: MUST - ENFORCED for multi-agent tasks
-> **ID**: R010
-> **Violation**: Direct agent execution without orchestrator = Rule violation
-
-## CRITICAL
-
-**When a task requires multiple agents, the APPROPRIATE orchestrator MUST coordinate.**
-
-### Session Continuity (MANDATORY)
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  AFTER SESSION RESTART / CONTEXT COMPACTION:                     ║
-║                                                                   ║
-║  1. Re-read CLAUDE.md and rules IMMEDIATELY                      ║
-║  2. Agent delegation rules STILL APPLY                           ║
-║  3. Orchestrator must NOT execute work directly                  ║
-║  4. Must spawn Task agents for actual work                       ║
-║                                                                   ║
-║  WRONG after session restart:                                    ║
-║    dev-lead → directly runs Bash/Edit/Write                     ║
-║                                                                   ║
-║  CORRECT after session restart:                                  ║
-║    dev-lead → Task(springboot-expert) → runs Bash/Edit/Write    ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-### Orchestrator Direct Action Prohibition (MANDATORY)
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  ORCHESTRATORS (secretary, dev-lead) MUST NOT:                   ║
-║                                                                   ║
-║  ✗ Directly run Bash commands for code/build tasks              ║
-║  ✗ Directly Edit/Write source code files                        ║
-║  ✗ Directly modify project configuration                        ║
-║                                                                   ║
-║  ORCHESTRATORS MUST:                                             ║
-║                                                                   ║
-║  ✓ Analyze task and identify required agents                    ║
-║  ✓ Spawn Task agents with appropriate expert roles              ║
-║  ✓ Aggregate results from spawned agents                        ║
-║  ✓ Report summary to user                                       ║
-║                                                                   ║
-║  Only allowed direct tools: Read, Glob, Grep (for analysis)     ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-### Orchestrator Role Separation (MANDATORY)
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  WHICH ORCHESTRATOR TO USE?                                      ║
-║                                                                   ║
-║  Task Domain                    → Orchestrator                   ║
-║  ─────────────────────────────────────────────────               ║
-║  Agent creation/update/audit    → secretary                      ║
-║  Code review/refactoring        → dev-lead                       ║
-║  Feature implementation         → dev-lead                       ║
-║  Multi-language development     → dev-lead                       ║
-║  Manager agent coordination     → secretary                      ║
-║  SW/Backend engineer tasks      → dev-lead                       ║
-║                                                                   ║
-║  WRONG: secretary directing kotlin-expert for code work         ║
-║  RIGHT: dev-lead directing kotlin-expert for code work          ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-### Orchestrator Responsibilities
-
-| Orchestrator | Supervises | Handles |
-|--------------|------------|---------|
-| **secretary** | manager/* (creator, updater, supplier, memory-keeper) | Agent management, system operations |
-| **dev-lead** | sw-engineer/*, sw-engineer/backend/* | Development, code review, implementation |
-
-```
-Multi-agent detection:
-- Task spans multiple domains (frontend + backend)
-- Task requires different expertise (golang + python)
-- Task involves batch operations on different resources
-
-If multi-agent needed → secretary MUST coordinate
-```
-
-## Coordination Flow
-
-```
-CORRECT:
-User Request
-    │
-    ▼
-┌─────────────────────────────┐
-│  secretary (orchestrator)    │
-│  - Analyzes task             │
-│  - Identifies required agents│
-│  - Plans execution           │
-└─────────────┬───────────────┘
-              │
-    ┌─────────┼─────────┐
-    ▼         ▼         ▼
-[Agent-1] [Agent-2] [Agent-3]
-    │         │         │
-    └─────────┼─────────┘
-              ▼
-┌─────────────────────────────┐
-│  secretary (orchestrator)    │
-│  - Aggregates results        │
-│  - Reports to user           │
-└─────────────────────────────┘
-
-WRONG:
-User Request
-    │
-    ▼
-[Agent-1] → [Agent-2] → [Agent-3]
-(No coordination, ad-hoc execution)
-```
-
-## Secretary Responsibilities
-
-```yaml
-before_execution:
-  - Analyze user request
-  - Identify required agents
-  - Check agent availability
-  - Plan execution order (parallel vs sequential)
-  - Announce coordination plan
-
-during_execution:
-  - Spawn agent instances
-  - Monitor progress
-  - Handle failures
-  - Coordinate dependencies
-
-after_execution:
-  - Aggregate results
-  - Report summary to user
-  - Clean up resources
-```
-
-## Announcement Format
-
-Secretary MUST announce before delegating:
-
-```
-┌─ Agent: secretary (orchestrator)
-└─ Task: Coordinating multi-agent task
-
-[Plan]
-├── Agent 1: golang-expert → Review Go code
-├── Agent 2: python-expert → Review Python code
-└── Agent 3: typescript-expert → Review TS code
-
-[Execution] Parallel (3 instances)
-
-Spawning agents...
-```
-
-## When to Use Orchestrator
-
-| Scenario | Orchestrator Required |
-|----------|----------------------|
-| Single domain, single file | No |
-| Single domain, multiple files | Maybe (if parallel) |
-| Multiple domains | **Yes** |
-| Batch operations | **Yes** |
-| Complex workflow | **Yes** |
-
-## Exception: Simple Tasks
-
-Orchestrator NOT required for:
-- Single file operations
-- Single domain questions
-- Direct tool usage (Read, Write, etc.)
-
-These can be handled by the appropriate agent directly.
-
-## CRITICAL: Use Specialized Manager Agents
-
-**When a task matches a manager agent's purpose, you MUST delegate to that agent.**
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  MANAGER AGENT DELEGATION (MANDATORY)                            ║
-║                                                                   ║
-║  Task Type              → Required Agent                         ║
-║  ─────────────────────────────────────────────────               ║
-║  Create new agent       → creator                                ║
-║  Update external agent  → updater                                ║
-║  Audit dependencies     → supplier                               ║
-║  Memory operations      → memory-keeper                          ║
-║                                                                   ║
-║  DO NOT use general-purpose agents for these tasks.              ║
-║  DO NOT have secretary do the work directly.                     ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-### Correct Delegation Pattern
-
-```
-User: "java21-expert 에이전트를 만들어줘"
-
-WRONG:
-  secretary → Task(general-purpose) → creates files directly
-
-CORRECT:
-  secretary → Task(creator agent role) → follows creator workflow
-```
-
-### Manager Agents Reference
-
-| Agent | Location | Purpose |
-|-------|----------|---------|
-| creator | agents/manager/creator/ | Create new agents |
-| updater | agents/manager/updater/ | Update external sources |
-| supplier | agents/manager/supplier/ | Audit dependencies |
-| gitnerd | agents/manager/gitnerd/ | Git operations (commit, push, PR) |
-| sync-checker | agents/manager/sync-checker/ | Documentation sync verification |
-
-### System Agents Reference
-
-| Agent | Location | Purpose |
-|-------|----------|---------|
-| memory-keeper | agents/system/memory-keeper/ | Memory operations |
-| naggy | agents/system/naggy/ | TODO management |
-
-## CRITICAL: Use Specialized Expert Agents for Code Work
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  CODE WORK MUST USE SPECIALIZED EXPERT AGENTS                    ║
-║                                                                   ║
-║  Language/Framework           → Required Agent                   ║
-║  ─────────────────────────────────────────────────               ║
-║  Python/FastAPI backend       → python-expert or fastapi-expert  ║
-║  TypeScript/Next.js frontend  → typescript-expert or vercel-agent║
-║  Go code                      → golang-expert                    ║
-║  Kotlin/Spring                → kotlin-expert or springboot-expert║
-║                                                                   ║
-║  WRONG:                                                          ║
-║    secretary → Task(general-purpose) → writes Python code        ║
-║                                                                   ║
-║  CORRECT:                                                        ║
-║    secretary → Task(python-expert) → writes Python code          ║
-║                                                                   ║
-║  general-purpose should ONLY be used when:                       ║
-║  - No specialized agent exists for the task                      ║
-║  - Task is truly generic (file moves, simple scripts)            ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-## CRITICAL: Git Operations Delegation
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  GIT OPERATIONS MUST BE DELEGATED TO gitnerd                    ║
-║                                                                   ║
-║  WRONG:                                                          ║
-║    secretary/dev-lead → directly runs git commit/push            ║
-║                                                                   ║
-║  CORRECT:                                                        ║
-║    secretary → Task(gitnerd) → git commit/push                   ║
-║                                                                   ║
-║  gitnerd handles:                                                ║
-║  ✓ git commit (with proper message format)                       ║
-║  ✓ git push                                                      ║
-║  ✓ git branch operations                                        ║
-║  ✓ PR creation                                                   ║
-║                                                                   ║
-║  This ensures:                                                   ║
-║  - Consistent commit message format                              ║
-║  - Safety checks before destructive operations                  ║
-║  - Proper Co-Authored-By attribution                            ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-## Enforcement
-
-```
-Violation examples:
-✗ Reviewing Go + Python + TypeScript without secretary
-✗ Creating multiple agents without coordination plan
-✗ Running parallel tasks without announcing execution plan
-
-Correct examples:
-✓ Secretary announces plan, spawns agents, aggregates results
-✓ Clear execution plan with agent assignments
-✓ Progress updates during multi-agent execution
-```