oh-my-customcode 0.1.4 → 0.2.0

package/templates/agents/orchestrator/secretary/refs/rules/SHOULD-hud-statusline.md

@@ -1,96 +0,0 @@
-# [SHOULD] HUD Statusline Rules
-
-> **Priority**: SHOULD - Recommended for visibility
-> **ID**: R012
-
-## Purpose
-
-Display real-time status information during agent operations for improved visibility and progress tracking.
-
-## Format
-
-```
-─── [Agent] {name} | [Progress] {n}/{total} | [Parallel] {count} ───
-```
-
-## Update Triggers
-
-| Trigger | Description |
-|---------|-------------|
-| Agent activation | When an agent starts handling a task |
-| Task start | When a specific task begins execution |
-| Task complete | When a task finishes (success or failure) |
-| Parallel spawn | When parallel instances are created |
-| Parallel complete | When parallel instances finish |
-
-## Components
-
-| Component | Description | Example |
-|-----------|-------------|---------|
-| Agent | Active agent name | `golang-expert` |
-| Model | Model used (for parallel) | `sonnet` |
-| Progress | Task progress (current/total) | `2/5` |
-| Parallel | Parallel instance count | `3` |
-
-## Display Rules
-
-### Single Agent
-
-```
-─── [Agent] creator | [Progress] 1/3 ───
-```
-
-### With Parallel Execution (Model Display REQUIRED)
-
-```
-─── [Agent] secretary | [Progress] 0/4 | [Parallel] 4 ───
-
-Instances:
-  [1] readme-update:sonnet
-  [2] code-review:haiku
-  [3] architecture:opus
-  [4] validation:haiku
-```
-
-### Completion
-
-```
-─── [Agent] supplier | [Progress] 5/5 | [Done] ───
-```
-
-## Implementation
-
-Status updates via stderr to avoid output pollution:
-
-```bash
-echo "─── [Agent] $AGENT | [Progress] $PROGRESS ───" >&2
-```
-
-## Integration with Other Rules
-
-| Rule | Integration |
-|------|-------------|
-| R007 (Agent ID) | HUD complements agent identification |
-| R008 (Tool ID) | HUD shows overall progress, tool ID shows specific operations |
-| R009 (Parallel) | HUD displays parallel instance count |
-
-## When to Display
-
-| Situation | Display HUD |
-|-----------|-------------|
-| Single file operation | No (too brief) |
-| Multi-step task | Yes |
-| Parallel execution | Yes |
-| Long-running operations | Yes |
-
-## Hook Usage
-
-The HUD statusline hook can be triggered via:
-
-```bash
-~/.claude/hooks/hud/update-status.sh <agent> [progress] [parallel_count]
-
-# Examples
-~/.claude/hooks/hud/update-status.sh "creator" "1/3"
-~/.claude/hooks/hud/update-status.sh "secretary" "0/4" "4"
-```

package/templates/agents/orchestrator/secretary/refs/rules/SHOULD-interaction.md

@@ -1,103 +0,0 @@
-# [SHOULD] Interaction Rules
-
-> **Priority**: SHOULD - Strongly recommended
-> **Exception**: Emergency or explicit user request
-
-## Response Principles
-
-### 1. Brevity
-```
-✓ Key information first
-✓ Skip unnecessary preamble
-✓ Answer only what's asked
-✗ Over-explanation
-✗ Repetitive confirmation
-```
-
-### 2. Clarity
-```
-✓ Specific expressions
-✓ Unambiguous instructions
-✓ Executable code format
-✗ Abstract descriptions only
-✗ Overuse of "maybe", "probably"
-```
-
-### 3. Transparency
-```
-✓ State actions performed
-✓ Report changes
-✓ Acknowledge uncertainty
-✗ Hide actions
-✗ Present guesses as facts
-```
-
-## Status Report Format
-
-### Start
-```
-[Start] {task name}
-```
-
-### In Progress
-```
-[Progress] {current step} ({n}/{total})
-```
-
-### Complete
-```
-[Done] {task name}
-Result: {summary}
-```
-
-### Failed
-```
-[Failed] {task name}
-Cause: {reason}
-Alternative: {possible solutions}
-```
-
-## Handling Requests
-
-### Clear Request
-→ Execute immediately
-
-### Ambiguous Request
-```
-[Confirm]
-Understood "{request}" as {interpretation}.
-
-Proceed?
-```
-
-### Risky Request
-```
-[Warning]
-This action has {risk factor}.
-
-Continue?
-- Yes: {action to perform}
-- No: Cancel
-```
-
-## Multiple Tasks
-
-### Order
-1. Dependent tasks: Sequential
-2. Independent tasks: Parallel allowed
-
-### Report
-```
-[Task 1/3] Done - {result}
-[Task 2/3] In progress...
-[Task 3/3] Pending
-```
-
-## Long-running Tasks
-
-```
-[In Progress] {task name}
-Elapsed: {time}
-Current: {step}
-Remaining: {work left}
-```

package/templates/agents/orchestrator/secretary/refs/rules/SHOULD-memory-integration.md

@@ -1,114 +0,0 @@
-# [SHOULD] Memory Integration Rules
-
-> **Priority**: SHOULD - Recommended for context persistence
-> **ID**: R011
-
-## Purpose
-
-Integrate claude-mem for session context persistence across compaction.
-
-## Requirements
-
-### 1. Save Before Compaction
-```yaml
-trigger: PreCompact hook
-action:
-  - Collect session context (tasks, decisions, key info)
-  - Format with project tag "baekgom-agents"
-  - Store in claude-mem with metadata
-```
-
-### 2. Restore on Session Start
-```yaml
-trigger: SessionStart hook
-action:
-  - Build semantic query with project prefix
-  - Search claude-mem for relevant context
-  - Load and present context to agent
-```
-
-### 3. Project Isolation
-```yaml
-rule: Always include project name in queries
-reason: Prevent cross-contamination between projects
-```
-
-## Storage Format
-
-```yaml
-project: baekgom-agents
-session: {date}-{uuid}
-tags: [session, task, decision]
-content:
-  summary: Brief description of session context
-  tasks_completed: List of completed tasks
-  decisions: Key decisions made
-  open_items: Unfinished work
-```
-
-## Query Pattern
-
-Always include project name in queries:
-- `"baekgom-agents session authentication"`
-- `"baekgom-agents 2025-01-24 bug fix"`
-- `"baekgom-agents agent creation workflow"`
-
-### Effective Queries
-```yaml
-good:
-  - "baekgom-agents implementing oauth" (semantic, project-scoped)
-  - "baekgom-agents 2025-01-24 memory system" (temporal)
-  - "baekgom-agents decision agent architecture" (topic-based)
-
-bad:
-  - "implementing oauth" (missing project scope)
-  - "session context" (too generic)
-```
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `memory:save` | Save current context to claude-mem |
-| `memory:recall` | Search and recall relevant memories |
-
-## Integration with Agents
-
-### memory-keeper Agent
-```
-Responsible for:
-- Executing save/recall operations
-- Managing session metadata
-- Handling PreCompact and SessionStart hooks
-```
-
-### Other Agents
-```
-When to trigger memory:save:
-- Before complex task completion
-- When making significant decisions
-- Before expected context compaction
-```
-
-## Storage Provider
-
-```yaml
-provider: claude-mem
-collection: claude_memories
-project_tag: baekgom-agents
-archive_path: ~/.claude-mem/archives/
-```
-
-## Error Handling
-
-```yaml
-on_save_failure:
-  - Log error
-  - Continue without blocking main task
-  - Notify user of memory save failure
-
-on_recall_failure:
-  - Log error
-  - Continue with available context
-  - Notify user that memory recall failed
-```

package/templates/agents/orchestrator/secretary/refs/rules/SHOULD-pipeline-mode.md

@@ -1,165 +0,0 @@
-# [SHOULD] Pipeline Mode Rules
-
-> **Priority**: SHOULD - Recommended for sequential workflows
-> **ID**: R014
-
-## Purpose
-
-Enable declarative, sequential multi-step workflows with variable passing between steps.
-
-## Pipeline Definition Format
-
-```yaml
-name: pipeline-name
-description: What this pipeline does
-
-inputs:
-  - name: input_name
-    required: true
-    description: Input description
-
-steps:
-  - id: step_1
-    agent: agent-name
-    action: action_name
-    input: { key: "${input_name}" }
-    output: result_variable
-
-  - id: step_2
-    agent: another-agent
-    action: action_name
-    input: { data: "${result_variable}" }
-    output: final_result
-```
-
-## Variable Syntax
-
-- `${variable}`: Reference input or previous step output
-- `${step_id.field}`: Reference specific field from step output
-- `${inputs.name}`: Explicit input reference
-
-## Execution Rules
-
-### Sequential by Default
-
-Steps execute in order. Each step waits for previous step completion.
-
-```
-Step 1 → complete → Step 2 → complete → Step 3
-```
-
-### Output Passing
-
-Output from step N is available to step N+1 and beyond.
-
-```yaml
-steps:
-  - id: analyze
-    output: analysis    # Creates ${analysis}
-
-  - id: review
-    input: { data: "${analysis}" }  # Uses ${analysis}
-```
-
-### Error Handling
-
-```yaml
-error_handling:
-  default: stop              # stop | continue | retry
-
-steps:
-  - id: risky_step
-    on_error: continue       # Override for this step
-    retry:
-      max_attempts: 3
-      delay: 1000
-```
-
-## Pipeline Commands
-
-| Command | Description |
-|---------|-------------|
-| `pipeline:run <name>` | Execute a pipeline |
-| `pipeline:list` | List available pipelines |
-| `pipeline:status` | Show running pipeline status |
-
-## Pipeline Locations
-
-```
-pipelines/
-├── index.yaml              # Pipeline registry
-├── templates/              # Pipeline templates
-│   └── pipeline-template.yaml
-└── examples/               # Example pipelines
-    └── code-review.yaml
-```
-
-## Example Pipeline
-
-### code-review.yaml
-
-```yaml
-name: code-review
-description: Full code review workflow
-
-inputs:
-  - name: file_path
-    required: true
-
-steps:
-  - id: detect_language
-    agent: secretary
-    action: detect_language
-    input: { file: "${file_path}" }
-    output: language
-
-  - id: analyze
-    agent: "${language}-expert"
-    action: analyze
-    input: { file: "${file_path}" }
-    output: analysis
-
-  - id: security_check
-    agent: qa-lead
-    action: security_review
-    input: { findings: "${analysis}" }
-    output: security
-
-  - id: report
-    agent: documenter
-    action: summarize
-    input:
-      analysis: "${analysis}"
-      security: "${security}"
-    output: report
-```
-
-## Execution Output
-
-```
-[Pipeline] code-review
-├── [1/4] detect_language: ✓ Go detected
-├── [2/4] analyze: ✓ 5 issues found
-├── [3/4] security_check: ✓ No vulnerabilities
-└── [4/4] report: ✓ Summary generated
-
-[Complete] Pipeline finished successfully
-Output: ${report}
-```
-
-## Secretary Integration
-
-Secretary can:
-1. Load and validate pipeline definitions
-2. Execute pipelines step-by-step
-3. Pass variables between steps
-4. Report progress and results
-5. Handle errors according to policy
-
-## Benefits
-
-1. **Reproducibility**: Same workflow, consistent results
-2. **Composability**: Build complex workflows from simple steps
-3. **Visibility**: Clear step-by-step progress
-4. **Error Recovery**: Defined error handling per step
-5. **Reusability**: Save and reuse common workflows

package/templates/agents/orchestrator/secretary/refs/rules/index.yaml

@@ -1,125 +0,0 @@
-# Baekgom Agents - Global Rules
-# Priority: MUST > SHOULD > MAY
-
-rules:
-  # MUST - Never violate
-  - id: R000
-    name: language-policy
-    title: Language & Delegation Policy
-    path: ./MUST-language-policy.md
-    priority: MUST
-    scope: all
-
-  - id: R001
-    name: safety
-    title: Safety Rules
-    path: ./MUST-safety.md
-    priority: MUST
-    scope: all
-
-  - id: R002
-    name: permissions
-    title: Permission Rules
-    path: ./MUST-permissions.md
-    priority: MUST
-    scope: all
-
-  # SHOULD - Strongly recommended
-  - id: R003
-    name: interaction
-    title: Interaction Rules
-    path: ./SHOULD-interaction.md
-    priority: SHOULD
-    scope: all
-
-  - id: R004
-    name: error-handling
-    title: Error Handling Rules
-    path: ./SHOULD-error-handling.md
-    priority: SHOULD
-    scope: all
-
-  - id: R007
-    name: agent-identification
-    title: Agent Identification Rules
-    path: ./SHOULD-agent-identification.md
-    priority: SHOULD
-    scope: all
-
-  - id: R008
-    name: tool-identification
-    title: Tool Usage Identification Rules
-    path: ./SHOULD-tool-identification.md
-    priority: SHOULD
-    scope: all
-
-  # MAY - Optional
-  - id: R005
-    name: optimization
-    title: Optimization Guide
-    path: ./MAY-optimization.md
-    priority: MAY
-    scope: all
-
-  - id: R009
-    name: parallel-execution
-    title: Parallel Execution Rules
-    path: ./MAY-parallel-execution.md
-    priority: MAY
-    scope: agents
-
-  # Agent Design - MUST
-  - id: R006
-    name: agent-design
-    title: Agent Design Rules
-    path: ./MUST-agent-design.md
-    priority: MUST
-    scope: agents
-
-  # Orchestrator Coordination - MUST
-  - id: R010
-    name: orchestrator-coordination
-    title: Orchestrator Coordination Rules
-    path: ./MUST-orchestrator-coordination.md
-    priority: MUST
-    scope: agents
-
-  # Memory Integration - SHOULD
-  - id: R011
-    name: memory-integration
-    title: Memory Integration Rules
-    path: ./SHOULD-memory-integration.md
-    priority: SHOULD
-    scope: all
-
-  # HUD Statusline - SHOULD
-  - id: R012
-    name: hud-statusline
-    title: HUD Statusline Rules
-    path: ./SHOULD-hud-statusline.md
-    priority: SHOULD
-    scope: all
-
-  # Ecomode - SHOULD
-  - id: R013
-    name: ecomode
-    title: Ecomode Rules
-    path: ./SHOULD-ecomode.md
-    priority: SHOULD
-    scope: all
-
-  # Pipeline Mode - SHOULD
-  - id: R014
-    name: pipeline-mode
-    title: Pipeline Mode Rules
-    path: ./SHOULD-pipeline-mode.md
-    priority: SHOULD
-    scope: orchestrator
-
-  # Intent Transparency - MUST
-  - id: R015
-    name: intent-transparency
-    title: Intent Transparency Rules
-    path: ./MUST-intent-transparency.md
-    priority: MUST
-    scope: orchestrator

package/templates/agents/qa-team/qa-engineer/index.yaml

@@ -1,59 +0,0 @@
-# QA Engineer Agent
-
-metadata:
-  name: qa-engineer
-  type: qa-team
-  description: Executes tests based on detailed plans and documentation
-
-source:
-  type: internal
-
-capabilities:
-  - Manual test execution
-  - Automated test creation
-  - Defect identification
-  - Fix verification
-  - Regression testing
-  - Cross-platform testing
-
-tools:
-  allowed:
-    - Bash
-    - Read
-    - Write
-    - Edit
-    - Glob
-    - Grep
-
-commands:
-  - name: execute
-    description: Execute test cases
-  - name: verify
-    description: Verify bug fixes
-  - name: automate
-    description: Create automated tests
-  - name: regress
-    description: Run regression tests
-
-collaboration:
-  receives_from:
-    - qa-writer
-    - qa-planner
-  outputs_to:
-    - dev-lead
-    - qa-writer
-
-test_frameworks:
-  javascript: [jest, vitest, playwright, cypress]
-  python: [pytest]
-  go: [go test]
-  java: [junit]
-  kotlin: [junit, kotest]
-
-triggers:
-  - "run tests"
-  - "execute tests"
-  - "test execution"
-  - "verify fix"
-  - "regression"
-  - "automate test"

package/templates/agents/qa-team/qa-planner/index.yaml

@@ -1,47 +0,0 @@
-# QA Planner Agent
-
-metadata:
-  name: qa-planner
-  type: qa-team
-  description: Creates detailed QA plans from requirements and specifications
-
-source:
-  type: internal
-
-capabilities:
-  - Test strategy design
-  - Risk-based prioritization
-  - Test scenario identification
-  - Acceptance criteria definition
-  - Coverage analysis
-  - Edge case planning
-
-tools:
-  allowed:
-    - Read
-    - Write
-    - Glob
-    - Grep
-
-commands:
-  - name: plan
-    description: Create QA plan from requirements
-  - name: scenarios
-    description: Generate test scenarios
-  - name: criteria
-    description: Define acceptance criteria
-
-collaboration:
-  receives_from:
-    - speckit-agent
-    - documenter
-  outputs_to:
-    - qa-writer
-    - qa-engineer
-
-triggers:
-  - "test plan"
-  - "qa plan"
-  - "test strategy"
-  - "test scenarios"
-  - "acceptance criteria"