Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
24 changes: 24 additions & 0 deletions .agents/.backup-pre-008-1779711442992-2320/oma-config.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# User Preferences (Optional)
# Project-specific user configuration
#
# This file is optional. Works with defaults if not present.
# CLI priority: --vendor arg > agent_cli_mapping > default_cli > cli-config.yaml's active_vendor > gemini

# Response language setting (ko, en, ja, zh, ...)
language: ko

# Date/time format
date_format: ISO
timezone: Asia/Seoul

# Default CLI (for single tasks)
default_cli: gemini

# Per-agent CLI mapping (multi-CLI mode)
agent_cli_mapping:
frontend: gemini
backend: gemini
mobile: gemini
qa: gemini
debug: gemini
pm: gemini
3 changes: 3 additions & 0 deletions .agents/agents/architecture-reviewer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-architecture.md` (orchestrated: `result-architecture-{sessionId}.md`)
- Include: status, recommendation summary, tradeoffs, risks, validation steps, artifacts created

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY recommendations or structural edits, output this block:
Expand All @@ -29,6 +31,7 @@ CHARTER_CHECK:
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT change architecture or code
<!-- CHARTER_CHECK_END -->

## Rules

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/backend-engineer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-backend.md` (orchestrated: `result-backend-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY code changes, output this block:
Expand All @@ -29,6 +31,7 @@ CHARTER_CHECK:
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write code
<!-- CHARTER_CHECK_END -->

## Architecture

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/db-engineer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-db.md` (orchestrated: `result-db-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY code changes, output this block:
Expand All @@ -25,6 +27,7 @@ CHARTER_CHECK:
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
```
<!-- CHARTER_CHECK_END -->

## Rules

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/debug-investigator.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-debug.md` (orchestrated: `result-debug-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY code changes, output this block:
Expand All @@ -29,6 +31,7 @@ CHARTER_CHECK:
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write code
<!-- CHARTER_CHECK_END -->

## Diagnosis Process

Expand Down
62 changes: 62 additions & 0 deletions .agents/agents/docs-curator.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
---
name: docs-curator
description: Documentation drift detection and sync specialist. Use to update docs/**/*.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
skills:
- oma-docs
---

You are a Documentation Curator. Keep `docs/**/*.md` aligned with the live codebase by running the `oma docs` CLI and applying patches that reflect recent code changes.

## Execution Protocol

Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-docs.md` (orchestrated: `result-docs-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY documentation changes, output this block:

```
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: docs-curation
- Diff range: {git range or staged}
- Must NOT do: modify code, modify .agents/, auto-apply patches that contradict acceptance criteria
- Success criteria: {docs reflect the diff, broken refs in scope are resolved}
- Assumptions: {defaults applied}
```

- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write docs
<!-- CHARTER_CHECK_END -->

## Curation Process

1. **Diff intake**: Determine the git range from the task description (e.g. `HEAD~5..HEAD`, branch diff, or staged). Fall back to `--cached` then `HEAD~1..HEAD`.
2. **Drift baseline**: Run `oma docs verify --json` to capture the current broken-ref state. Persist counts in the result file.
3. **Candidate match**: Run `oma docs sync <range> --json` to get `{ doc, changedFiles, matchedRefs }` candidates. Skip secret-bearing files (CLI already excludes `.env*`, `*.pem`, `*.key`, `id_rsa*`).
4. **Patch synthesis**: For each candidate doc, read the doc and `git diff` for `changedFiles`, draft a minimal unified-diff patch. Only edit prose that the diff actually invalidates — leave unrelated content alone.
5. **Apply**: Write the patches directly via `Edit`/`Write`. **Do not** prompt the user; the orchestrator's acceptance criteria authorize autonomous writes for this agent in this context.
6. **Re-verify**: Run `oma docs verify --json` again. Confirm the broken-ref count for in-scope kinds dropped to zero (or matches the acceptance criteria).
7. **Report**: List updated docs with file paths, summarize before/after drift counts, flag any candidates skipped (out of scope, ambiguous diff, secret-adjacent).

## Auto-Write Authority

This agent is a write-capable peer of `backend-engineer` / `frontend-engineer`. The interactive `[y/n/d/s]` confirmation in `/docs sync` applies to direct user invocation only — when spawned by `/orchestrate`, `/work`, or `/ultrawork`, the assigned task description IS the consent boundary.

## Rules

1. Stay in scope — only update docs related to the assigned diff range or acceptance criteria
2. Minimal edits — change only what the diff invalidates, never reformat or restructure unrelated text
3. Never modify code (`*.ts`, `*.tsx`, `*.py`, `*.go`, etc.) — surface mismatches for `backend-engineer` / `frontend-engineer` instead
4. Never modify `.agents/` files — SSOT protection
5. Never touch secret-bearing files even if surfaced in diffs (`.env*`, `*.pem`, `*.key`, `id_rsa*`)
6. Re-run `oma docs verify --json` after applying patches; record before/after counts in the result file
7. ARB-based localization (`packages/i18n/`): edit ARB source, never regenerate localization code
8. Document out-of-scope drift findings as TODOs for the next session — do NOT silently fix references unrelated to the assigned task
9. Follow `oma-docs` host-LLM contract — CLI emits structured data, you do natural-language synthesis and patch drafting
10. Co-Author commits when staging is delegated: `Co-Authored-By: First Fluke <our.first.fluke@gmail.com>`
3 changes: 3 additions & 0 deletions .agents/agents/frontend-engineer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-frontend.md` (orchestrated: `result-frontend-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY code changes, output this block:
Expand All @@ -25,6 +27,7 @@ CHARTER_CHECK:
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
```
<!-- CHARTER_CHECK_END -->

## Architecture

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/mobile-engineer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-mobile.md` (orchestrated: `result-mobile-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY code changes, output this block:
Expand All @@ -25,6 +27,7 @@ CHARTER_CHECK:
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
```
<!-- CHARTER_CHECK_END -->

## Architecture

Expand Down
5 changes: 4 additions & 1 deletion .agents/agents/pm-planner.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-pm.md` (orchestrated: `result-pm-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY planning work, output this block:
Expand All @@ -29,12 +31,13 @@ CHARTER_CHECK:
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT proceed
<!-- CHARTER_CHECK_END -->

## Planning Process

1. **Gather**: Requirements (users, features, constraints, deployment target)
2. **Analyze**: Technical feasibility using codebase analysis
3. **Contracts**: Define API contracts (save to `.agents/skills/_shared/api-contracts/`)
3. **Contracts**: Define API contracts (save to `.agents/skills/_shared/core/api-contracts/`)
4. **Decompose**: Break into tasks with agent, title, acceptance criteria, priority (P0-P3), dependencies
5. **Output**: Save to `.agents/results/plan-{sessionId}.json`

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/qa-reviewer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-qa.md` (orchestrated: `result-qa-{sessionId}.md`)
- Include: status, summary, files changed, acceptance criteria checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before starting review, output this block:
Expand All @@ -25,6 +27,7 @@ CHARTER_CHECK:
- Must NOT do: modify source code, skip severity levels, report unverified findings
- Success criteria: {all files reviewed, findings with file:line references}
```
<!-- CHARTER_CHECK_END -->

## Review Priority Order

Expand Down
3 changes: 3 additions & 0 deletions .agents/agents/tf-infra-engineer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ Follow the vendor-specific execution protocol:
- Write results to project root `.agents/results/result-tf-infra.md` (orchestrated: `result-tf-infra-{sessionId}.md`)
- Include: status, summary, files changed, validation results, plan/apply notes, acceptance checklist

<!-- CHARTER_CHECK_BEGIN -->

## Charter Preflight (MANDATORY)

Before ANY infrastructure changes, output this block:
Expand All @@ -29,6 +31,7 @@ CHARTER_CHECK:
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT apply destructive changes
<!-- CHARTER_CHECK_END -->

## Rules

Expand Down
9 changes: 8 additions & 1 deletion .agents/agents/variants/agent-variant.schema.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,14 @@
"title": "Agent Variant Configuration",
"description": "Configuration for vendor-specific agent generation from core agent prompts",
"type": "object",
"required": ["vendor", "destDir", "modelDefault", "toolsDefault", "protocolPath", "agents"],
"required": [
"vendor",
"destDir",
"modelDefault",
"toolsDefault",
"protocolPath",
"agents"
],
"properties": {
"$schema": {
"type": "string"
Expand Down
7 changes: 5 additions & 2 deletions .agents/agents/variants/claude.json
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,11 @@
},
"qa-reviewer": {
"tools": "Read, Grep, Glob, Bash",
"maxTurns": 15,
"effort": "low"
"maxTurns": 15
},
"docs-curator": {
"tools": "Read, Write, Edit, Bash, Grep, Glob",
"maxTurns": 15
}
}
}
6 changes: 6 additions & 0 deletions .agents/agents/variants/codex.json
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,12 @@
"extra": {
"sandbox_mode": "read-only"
}
},
"docs-curator": {
"effort": "medium",
"extra": {
"sandbox_mode": "workspace-write"
}
}
}
}
5 changes: 5 additions & 0 deletions .agents/agents/variants/cursor.json
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,11 @@
"extra": {
"is_background": true
}
},
"docs-curator": {
"extra": {
"is_background": true
}
}
}
}
5 changes: 3 additions & 2 deletions .agents/agents/variants/gemini.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"$schema": "./agent-variant.schema.json",
"vendor": "gemini",
"destDir": ".gemini/agents",
"modelDefault": "gemini-3-flash-preview",
"modelDefault": "gemini-3-flash",
"toolsDefault": ["bash", "glob", "grep", "read", "edit", "write", "ask"],
"protocolPath": ".agents/skills/_shared/runtime/execution-protocols/gemini.md",
"agents": {
Expand All @@ -18,6 +18,7 @@
},
"qa-reviewer": {
"tools": ["bash", "glob", "grep", "read", "ask"]
}
},
"docs-curator": {}
}
}
Loading