업무 효율화 스킬

Use to keep moving without inspecting progress, or when the user asks what is next in the GSD workflow. Reads STATE.md, ROADMAP.md and phase dirs to invoke the next step; --force skips safety and verification gates.

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

End-of-session brain flush. Scans the full conversation, extracts all new entities, decisions, tasks, events, relationships, and updates, presents a summary, and writes to project_brain.db after confirmation. Use at end of every session or when you want to capture everything discussed.

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

Use when you have a spec or requirements for a multi-step task, before touching code

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

Use when executing implementation plans with independent tasks in the current session

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

Use when the user says brain, project knowledge, what do we know about, open tasks, or recent decisions, or runs /brain or /brain-update. SQLite project_brain.db tracker for entities, relationships, tasks, threads, decisions, events.

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

Generate templated stakeholder communications from project context. Use when someone asks to "write a go-live email", "create a status update", "onboard someone", "write an announcement", "steerco update", "incident summary", "change notification", or any stakeholder communication task. Reads project memory, stakeholder directory, PRD, and meeting notes to pre-fill real names, dates, and context. Produces ready-to-send Markdown.

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

Use when setting up project memory in a new folder or on the first brain:init in a project. Creates project_brain.db, registers the project, and bootstraps it from CLAUDE.local.md, memory files, docs, and emails; safe to re-run.

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

Use when the user asks for a knowledge article, wiki page, or entity summary from the brain, or wants to search, list, or review merges across brain DB articles. Generates Wikipedia-style articles from entities, decisions, and emails.

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

Use when starting any task, before invoking any other skill or GSD command, to route between Superpowers skills and GSD commands from project state and task scope. Fires first when both systems are installed.

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

Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.

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

Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).

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

Generate structured meeting notes from transcripts or pasted text. Use when someone says "meeting notes", "process this transcript", "summarize this call", "notes from today's meeting", or pastes/references a meeting transcript. Auto-enriches attendees from stakeholder directory, routes output to correct project subfolder, flags downstream artifact impacts (PRD, deck, architecture), and proposes CLAUDE.local.md updates. Produces date-first Markdown files.

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

Use when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live page. Covers two providers (agent-browser local CLI, agentic-browser cloud) and the shared @e ref workflow.

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

Build AI applications with OpenAI Agents SDK - text agents, voice agents, multi-agent handoffs, tools with Zod schemas, guardrails, and streaming. Prevents 11 documented errors. Use when: building agents with tools, voice agents with WebRTC, multi-agent workflows, or troubleshooting MaxTurnsExceededError, tool call failures, reasoning defaults, JSON output leaks.

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

Use when the user invokes /coco or /coco!, says catch me up, or asks what needs attention, a project status, their todos, decisions or people. Renders the PM dashboard and routes each subcommand to its platform tool or a PM skill.

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

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

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

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

When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's "work backwards from availability" method. Combines Vercel CLI, whois, Domainr, Namecheap, and agent-browser, each for what it reliably does. Workflow: budget → brainstorm → availability check → whois cross-check → price → aftermarket sweep (plus liveness probe and drop-watch) → bucket → negotiate → trademark + socials → buy. Triggers on "/domain," "find a domain," "check domain availability," "brainstorm a domain," "what .com is available for X," "domain hunt," "name my project," "is X.com available," "aftermarket price on X.com," "trademark check for X."

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

When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into structured work. Extracts decisions, action items (yours vs theirs), bugs/feature requests, and facts worth keeping; files GitHub issues in the right repo, captures to the second-brain vault, and drafts (never sends) the reply. Triggers on "/ingest", "ingest this", "here's my call with X," "here's the transcript," "this is from [person]," "[person] asked me this," "from [person]:", a pasted transcript with speaker labels, or a forwarded client message that clearly expects processing. Person→project routing lives in a private config; unknown senders get asked about once, then remembered.

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

When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them, reaches a call (or "wait"), and archives the rationale for future reference. Based on the 37signals Guide to Making Decisions (38 questions) plus house additions like Q39 opportunity cost ("what does saying yes displace?"). Triages to 6–8 relevant questions per decision instead of forcing the full set. Archives every decision to ~/.config/makerskills/decide/archive/ with a revisit date so you can check later whether the call was right. Triggers on "/decide," "help me decide," "should I [X]," "I need to make a decision about," "stuck on a decision," "deciding between," "go/no-go on," "what should I do about." This is both the decision-making workflow AND the decision log — making the decision is the act of logging it.

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

Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Triggers on /orchestrate, multi-agent coordination, parallel team work, task delegation to teammates.

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

Use when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development. Covers Spec-Driven Development, Context Engineering, and post-dev workflow.

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

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

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