sungjunlee

spec-charter

Create, amend, or reassess spec/charter.md. Use for project direction, Objectives, Non-Goals, Decisions, stale spec findings, 기준, 헌장, 방향성, or spec axis.

spec-grill

Create or refine spec/capabilities.md from repo signals. Use after spec-charter or for capability specs, component contracts, middle-layer specs, repo boundaries, 능력 명세, or grill.

spec-system-map

Create or amend spec/system-map.md. Use for architecture scope, system shape, runtime boundaries, core flows, invariants, storage/external systems, or SYSTEM_MAP.

craft-autoresearch

Optimize prompts or skills with measured eval loops. Use for repeatable test inputs, eval runners, scoring, bounded mutations, or written stop conditions.

craft-critique

Critique prompts or skills and surface what actually needs fixing. Use for review, audit, "feels off" artifacts, or diagnosis before a rewrite; applies fixes only when asked.

Produce paired session-handoff artifacts: a rich doc plus a resume prompt. Use when wrapping up, clearing context, pausing work, or the user says "마무리", "세션 정리", "핸드오프", "다음 세션으로 넘겨", or "next session으로 넘겨".

craft-harness

Given a repo, decide where agent guidance belongs and make or propose the smallest useful harness change. Use for AGENTS.md/CLAUDE.md placement, skills, hooks, MCP, plugins, sync, or pruning.

craft-skill-spec

Design a skill-like artifact before writing it. Use for skill specs, suites, subagents, plugins, artifact-class decisions, triggers, file shape, or "meta-skill" requests.

craft-survey

Survey prior art for prompts, skills, or repo assets. Use for "how others do this", adopt/avoid patterns, older assets, or pre-draft research.

braid

Decompose one accepted goal into a cheap tree of relay-able leaves, then fold relay's durable evidence back up — a node is done only when every child is done-with-evidence. v0 is read-only (validate/status); leaves are driven by ordinary relay.

relay-config

Interactive setup for relay routes. Use when the user asks to set up relay, configure company/personal relay routing, enable OpenCode or Pi, resolve model names, add provider/model routes, check advisory-review routing, or run relay-config doctor/check.

relay-dispatch

Dispatch implementation tasks via worktree isolation. Use when delegating work to an executor, running background dispatches, or parallelizing independent tasks.

relay-fleet

Drive already-planned relay leaves through fan-out, review, serial merge, crash recovery, and fleet status.

relay-merge

Merge a reviewed PR, clean up worktree/branch, and close GitHub issues. Use after relay-review returns LGTM.

relay-orca

SUPERSEDED — FROZEN 2026-07-24, DO NOT USE OR INVOKE (see SUPERSEDED.md). Learning-spike program-altitude coordinator; retired in favor of a lighter decompose-deep/execute-flat successor. Not maintained; kept only as a reference tombstone.

relay-plan

Use when a relay run needs its review anchor, evaluation channels, or dispatch prompt — always before relay-dispatch, whether AC are explicit, vague, or missing.

relay-ready

Verify a task is ready to relay — score readiness on clarity, granularity, and verifiability, then ask bounded questions when the task is too ambiguous to plan.

relay-review

Use when completed relay executor work needs independent review against frozen Done Criteria — internal pre-publication rounds or post-publication PR rounds.

relay

Use when a GitHub issue, sprint item, task description, or natural-language handoff should be implemented through autonomous executor dispatch; stops at ready_to_merge — merge only on explicit request.

craft-prompt

Craft copy-paste-ready prompts. Use to write prompts, turn notes into templates, draft `/goal` conditions, or answer "프롬프트 만들어" requests.

beopsuny

한국 법령·판례·행정규칙·계약·컴플라이언스 질문에 사용한다. 사용자가 조문, 시행일, 판례, 과징금, 인허가, 노동·해고, 개인정보, 주총·등기, 중대재해, 계약서 위험 조항, 법령 변경, 한국 법률상 의무나 리스크를 묻는 경우 이 스��을 사용한다. 공식 1차 소스 확인, 출처 권위 라벨, 자가 검증이 필요한 한국법 답변에 적합하며, 한국법 질문은 기억만으로 답하지 않는다.

3 Updated yesterday