업무 효율화 스킬

Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when acting as the workflow manager for Syntropic137 - owning the SDLC workflow suite, its evals and its triggers as a product. Covers deciding which workflow a kind of work goes through, improving a workflow's quality and then its cost and time, judging whether a prompt, model or phase change is proven, designing the draft-to-ready PR lifecycle, and deciding when triggers should fire. Trigger phrases include "you are the workflow manager", "start as workflow manager", "improve our SDLC", "which workflow should handle this", "make the workflow cheaper without losing quality", "is v4 better than v3", "promote this workflow", "what do our evals say", "eval coverage", "evals for the whole workflow", "draft PR lifecycle", "when should this trigger fire", "triggers fire too often", "workflow suite health". Do NOT use for running one workflow (syn-workflow), diagnosing one execution (execution-control), workflow YAML mechanics (authoring-workflows), the dispatch, land and deploy loop (orchestrating), or the detailed design of one A/B (workflow-experimentation).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operate desktop apps and isolated browsers on registered computers. Use for tasks that require an app interface, accessibility, screenshots or recording. Use Chromewhale for the user's signed-in Chrome.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search, read, draft, and send Gmail when the user asks to work with their inbox or email.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read and act on selected Chrome tabs and frames — their real browser, their logged-in sessions. Use for questions about the current page, filling a form the user is on, following a link they mentioned, or checking what a site actually renders. Not for throwaway automation in a clean profile.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read schedules, check availability, and create or update Google Calendar events when the user asks to work with their calendar.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate Codewhale’s native plan state; do not build a parallel planner.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user says /update, @update, update project docs, or asks to sync task.md, changelog.md, and files.md after completing work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing, running, or judging an experiment on a Syntropic137 workflow - comparing prompt variants, fan-out vs single agent, adversarial cross-model review, model selection (can Haiku do this job), phase splits, or tool grants. Trigger phrases include "run a workflow experiment", "A/B the workflow", "does fan-out help", "which model for this phase", "is this prompt better", "measure review quality", "why did the workflow do that". Do NOT use for a one-off workflow run that is just doing work, for authoring a workflow that is not being compared against anything, or for debugging a single failed execution (that is ordinary debugging).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

delta step of mspec workflow — generate Delta Spec with auto-numbered FR-NNN

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

checklist step of mspec workflow — produce checklist.md via subagent

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

proposal step of mspec workflow — clarify intent and write proposal.md

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tasks step of mspec workflow — produce tasks.md with anchor blocks

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

quickstart step of mspec workflow — write quickstart.md

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

new step of mspec workflow — bootstrap a change directory and readme.md

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

self-review step of mspec workflow — sanity-check all artifacts via subagent

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

archive step of mspec workflow — deterministic merge into SoT spec and archive move

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for choosing models in Tinker — available model families, model types (base, instruction, reasoning, hybrid, vision), architecture (dense vs MoE), and how to match renderers to models. Use when the user asks which model to use, what models are available, or how to pick a model for their task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: 'intake this repo/skill', 'evaluate external skill', 'should we adopt X', a candidate repo URL plus an adoption question, or any external skill/workflow/tool surfaces as a possible fit for Agistra. Structured front-door evaluation of external skills, workflows, and similar capability artifacts before any install, promotion, or adaptation decision. Ends in exactly one classification: Install candidate, Adapt concept, or Reject. Never install first — intake first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writing skill for freelancers and independent consultants. Covers project proposals, bids, client emails, and scope summaries. Leads with the client's problem, not the consultant's background.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: Tester needs UI state evidence for VBR, or Builder needs to verify an integration wire is observable end-to-end. Powered by agent-browser MCP — token-efficient browser automation (200–400 tokens/page).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.