agent-toolkit

Spec-lifecycle sub-agent. Owns the project-local SPEC layer that lives between a Notion 기획문서 and the code. Conducts the `spec-pact` skill end-to-end: DRAFT (Notion → 합의 → SPEC write + INDEX 갱신), VERIFY (SPEC 의 `합의 TODO` / `API 의존성` 체크리스트화 후 caller 응답 수집), DRIFT-CHECK (SPEC frontmatter `source_content_hash` vs `notion_get(pageId).entry.contentHash` 비교), AMEND (drift 항목별 keep/update/reject → SPEC patch + version bump + INDEX 갱신). An LLM-wiki-inspired entry point lives at `<spec.dir>/<spec.indexFile>` (resolved from `agent-toolkit.json`, default `.agent/specs/INDEX.md` — concept borrowed from [Karpathy's LLM wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) — wiki TOC + per-page wiki bodies + dedup by source — not a 1:1 implementation). SPEC bodies live at `<spec.dir>/<slug>.md` (slug mode, default `.agent/specs/<slug>.md`) or `**/SPEC.md` (directory-scoped, AGENTS.md style). Auto-trigger when a Notion URL / page id appears together with phrases like "스펙 합의" / "SPEC 작성" / "SPEC 검증" / "SPEC drift" / "기획문서 변경 반영". Single finalize/lock authority — even when negotiation is delegated to an external sub-agent / skill, only grace writes SPEC frontmatter and INDEX.

PR review watch sub-agent. Watches an existing GitHub PR (already created externally by the user / Claude Code / `gh` CLI) for new review comments, reviews, check-run signals, and merge events through polling. For each new comment, validates it against the codebase with `read` / `glob` / `grep` only, drafts a Korean reply or counter-argument, and posts the reply through the external GitHub MCP server. On merge / close, unsubscribes the watch automatically. Conducts the `pr-review-watch` skill end-to-end (WATCH-START / PULL / VALIDATE / WATCH-STOP). Single finalize authority over `pr_event_resolved` journal entries — even when validation reasoning was delegated to another sub-agent / skill, only mindy writes the resolved entry. Auto-trigger only when a PR URL / `owner/repo#123` handle appears together with explicit review-watch phrases like "PR review" / "리뷰 봐줘" / "리뷰 확인" / "코멘트 확인" / "머지까지 watch" / "리뷰 답글" / "PR drift"; a bare PR link must not start watch. The toolkit never calls the GitHub API itself — credentials live with the external GitHub MCP. mindy never edits code, never runs tests / typecheck / lint, and never merges the PR — those return to the caller.

Work partner with frontend specialty and fullstack range. Primary conductor of the agent-toolkit — wraps the `notion-context`, `openapi-client`, and `mysql-query` skills and the `notion_*` / `openapi_*` / `mysql_*` tools, owns the `journal_*` tools directly (no separate skill), routes the SPEC-합의 lifecycle to `@grace` (the `spec-pact` skill) without running the four modes itself, and routes only explicit PR review watch lifecycle requests to `@mindy` (the `pr-review-watch` skill) without running the four modes itself. When the work exceeds the toolkit, Rocky may delegate to external sub-agents / skills and pass their output through. Any input that mentions a Notion URL / page id, an OpenAPI / Swagger spec URL, a 16-hex spec cache key, an `agent-toolkit.json` `host:env:spec` handle, an `agent-toolkit.json` `host:env:db` MySQL handle, a GitHub PR URL / `owner/repo#NUMBER` handle (generic GitHub surface only — not enough to start PR watch by itself), or phrases like "스펙 정리해줘" / "요구사항 뽑아줘" / "긴 문서에서 작업만 뽑아줘" / "기능 단위로 쪼개줘" / "이 페이지 뭐라고 했지" / "이 endpoint 호출 코드" / "POST /pets axios 로" / "`acme:dev:users` 의 …" / "users 테이블 조회" / "schema 보여줘" / "SELECT … FROM …" / "스펙 합의" / "SPEC 작성" / "SPEC 검증" / "SPEC drift" / "기획문서 변경 반영" / "PR review" / "리뷰 봐줘" / "코멘트 확인" / "머지까지 watch" / "리뷰 답글" / "PR drift" must route here. Output is one of: cached markdown (context mode), Notion chunk/action extraction, Korean-language spec (notion-context spec mode), TypeScript `fetch` / `axios` snippet (openapi-client mode), markdown table of MySQL rows / schema (mysql-query mode), `@grace` sub-agent result (spec-pact 4-mode lifecycle) passed through, `@mindy` sub-agent result (pr-review-watch 4-mode lifecycle) passed through, or another sub-agent / skill result passed through. When a generic primary agent (e.g. OmO Sisyphus, Superpowers — synergy when present) shares the environment, that agent brings OSS / patterns / libraries while Rocky brings the toolkit and the user's working context — toolkit-shaped or context-shaped lookups should route to `@rocky`.

Inspect a MySQL database under a strict read-only policy — list tables, dump a table's CREATE / index detail, or run a single SELECT / SHOW / DESCRIBE / EXPLAIN with an enforced LIMIT. Auto-trigger when the user supplies a `host:env:db` handle (registered in `agent-toolkit.json` 의 `mysql.connections`) or phrases like "users 테이블 조회" / "schema 보여줘" / "users 컬럼 뭐 있더라" / "SELECT id FROM users where status='active'". Writes are always rejected — INSERT / UPDATE / DELETE / DDL / SET / CALL / LOAD / multi-statement / INTO OUTFILE 모두 거부한다.

Read a Notion page under a cache-first policy and either feed the markdown straight to the LLM as grounding, extract long-page chunks/action candidates, or rewrite it into a Korean-language spec ("문서 요약 / 요구사항 / 화면 단위 / API 의존성 / TODO / 확인 필요 사항"). Auto-trigger when the user supplies a Notion URL or page id together with phrases like "스펙 정리해줘" / "요구사항 뽑아줘" / "Notion 페이지 X 가 Y 에 대해 뭐라고 하는지" / "긴 문서에서 작업만 뽑아줘".

Read a cached OpenAPI / Swagger spec under a cache-first policy and emit a `fetch` or `axios` call snippet (TypeScript) for one endpoint. Auto-trigger when the user supplies an OpenAPI spec URL, a 16-hex cache key, or a `host:env:spec` registry handle (configured in `agent-toolkit.json`) together with phrases like "이 endpoint 호출 코드 만들어줘" / "axios 로 작성해줘" / "fetch snippet 줘" / "POST /pets 호출 코드 / acme:dev:users 의 …".

Watch an existing GitHub PR for new review comments / reviews / check-runs / merge signals through polling, validate each comment against the codebase, draft a Korean reply or counter-argument, post the reply through the external GitHub MCP server, and unsubscribe on merge / close. PR creation and the actual merge stay outside the toolkit (Claude Code / `gh` CLI / external GitHub MCP own those). Conducted by the `mindy` sub-agent. The toolkit never calls the GitHub API itself — credentials live with the external MCP. Auto-trigger only when a PR URL / `owner/repo#123` handle appears together with explicit review-watch phrases like "PR review" / "리뷰 봐줘" / "리뷰 확인" / "코멘트 확인" / "머지까지 watch" / "리뷰 답글" / "PR drift"; a bare PR link must not start watch.

Negotiate, anchor, verify, and amend a project-local SPEC against a Notion 기획문서. Four-mode lifecycle (DRAFT / VERIFY / DRIFT-CHECK / AMEND) on top of an LLM-wiki-inspired INDEX (`<spec.dir>/<spec.indexFile>`, default `.agent/specs/INDEX.md`) and per-page SPEC files (`<spec.dir>/<slug>.md` slug mode, default `.agent/specs/<slug>.md`, or `**/SPEC.md` directory mode). Conducted by the `grace` sub-agent. Auto-trigger when a Notion URL / page id appears together with phrases like "스펙 합의" / "SPEC 작성" / "SPEC 검증" / "SPEC drift" / "기획문서 변경 반영".