Claude Code Slash Commands · page 7

Orchestrate a tagged release using the release workflow.

Perform local security scanning and dispatch the security audit workflow.

Sync feature branch with the latest main branch.

Convert TodoWrite task list to GitHub plan issue (triggers automation)

전문 에이전트 자동 라우팅. 법률, 재무, 특허, SEO, 마케팅, 기획, BM 설계(BMC/Lean/JTBD/Wardley/Blue Ocean/Lightning Sprint), 코드리뷰, 아키텍처, 견적, CRM, HR/인사, 노무(노동법/해고/산재/취업규칙), 리서치, 데이터 분석, 제1원칙 사고, 주식 투자, 부동산 투자, 명리학, 회사운영(노란우산/창업혜택/고용지원/세무일정), 디자인 제작(배너/카드뉴스/SNS/광고/인포그래픽), FAQ/지식베이스(KCS/셀프서비스/아티클), 고객지원(CS응답/에스컬레이션) 등 50+ 에이전트

계획부터 PR까지 원버튼 자동 실행. 중간에 멈추지 않습니다.

빌드 에러를 자동으로 분석하고 수정합니다.

작업 상태 저장/복원 (v6)

방금 작성한 코드를 보안+품질 검사합니다.

머지 전 /sync-docs 문서 동기화 의무 게이트 → 검증 → 커밋 & PR & 머지 + MCP 알림 (v7)

Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.

Manage eval-driven development workflow (define, check, report, list)

코드베이스를 탐색하여 구조를 파악합니다.

Claude Forge 프레임워크를 원격에서 최신 버전으로 업데이트

처음 사용자를 위한 인터랙티브 가이드. 약 3분이면 끝납니다.

8 reviewer 병렬 검증 (Workflow tool 결정론 fan-out + CRITICAL/HIGH adversarial 재검증)

프로젝트 초기 설정 (v6)

교훈 기록 + 자동화 제안 (v6 - suggest-automation 통합)

다음 작업 추천 (v6)

Agent Teams 기반 병렬 오케스트레이션 (v6)

AI가 구현 계획을 세워줍니다. 확인 후 코딩 시작.

git pull origin main 빠르게 실행

간단한 수정용 빠른 커밋 (v6)

Safely identify and remove dead code with test verification

CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제)

현재 Claude Forge 설치 상태와 프로젝트 정보를 보여줍니다.

반복 패턴 분석하여 자동화 기회 제안 (주기적 실행 권장)

prompt_plan.md, spec.md, CLAUDE.md + rules/ 문서 동기화 (v7.1 — 흩어진 파일 housekeeping scan 통합)

git pull + 문서 동기화 통합 (pull → sync-docs v7 순차 실행)

테스트 먼저 만들고 코드 작성. 한 단위 작업에 사용.

자동 재검증 루프 (최대 3회 재시도, 실패 시 자동 수정)

머지 후 웹 테스트 체크리스트 + 완료 추적 (v6)

PR 완료 후 Git Worktree 정리 (v6)

병렬 개발용 Git Worktree 생성 + 도메인 템플릿 (v6)

Draft blog posts, ad copy, emails, social media, landing pages, and video scripts with brand voice and SEO

Wire DMP for Anthropic Cowork team usage: verifies Cowork sandbox, checks for a Drive MCP, creates the canonical Drive folder layout, and persists the team's routing config. Run once per team.

Per-action readiness diagnostic. Shows which campaign-audit and launch-campaign actions are live (manifest-ready) vs blocked (stub-unconfigured) in the current environment, with one-step setup hints for the blocked ones. Now includes model-registry freshness + Cowork+Drive routing status.

Design complete email sequences with subject lines, body copy, timing, segmentation, and deliverability guidance

Run a marketing engagement using the 12-Part methodology. Subcommands: start, next, status, validate, re-run-decision, update-back, lif-show, file-tree, list-engagements, four-core, growth-plan, yearly-planner, loop.

Actually fire a campaign-audit / launch-campaign action against its real API (vs returning a manifest). Reads credentials from env vars (no OAuth flow). Read ops auto-execute with --execute; write ops require --confirm. Logs every execution to the audit trail.

Build a pillar+spokes content cluster plan from seed keywords with SERP-overlap clustering, intent grouping, internal-link map, and a four-gate quality scorecard

Print + open the user-visible DMP output folder for a brand (~/Documents/DigitalMarketingPro/{brand}/). Direct answer to "where did my engagement deliverables save?

Generate a marketing performance report with KPI tracking, trend analysis, anomaly detection, and recommendations

Resume a long-running DMP workflow (engagement / campaign-plan / content-engine / seo-audit / competitor-analysis / campaign-audit / launch-campaign) that was interrupted partway through

Run a comprehensive SEO audit — technical health, on-page, content gaps, E-E-A-T, link profile, and competitor benchmarking

Compare two SEO snapshots (GSC / GSC AI Performance / rank tracker / AEO probe) and surface top movers per metric with auto-classification — growth / decline / reshuffle / stable / new / lost

Unified status snapshot of the active brand: profile, engagements, recent insights, recent compliance violations, Python dependency mode.

Show the local Recall history log (.recall/history.md)

Generate / overwrite .recall/context.md from the local history using the offline summarizer

Show this project's saved Recall context (.recall/context.md)

Run an accessibility audit on the current project for WCAG compliance.

Reverse-engineer a Product Requirements Document from existing code.

Build a competitive analysis matrix comparing products or tools.

Assess financial health of a SaaS business using key metrics.

Apply a focused, minimal-change bugfix with minimal blast radius.

Stage working tree changes and create a Conventional Commit (no push).

Stage, commit, and push the current branch following git governance rules.

Create a pull request from the current branch.

Create or review OKRs (Objectives and Key Results).

Activate a cross-domain persona for the current session.

Design or review a CI/CD pipeline for the current project.

Audit installed plugins, extensions, and dependencies for security and health.

Create a Product Requirements Document from scratch.

Assess overall project health across code quality, tests, docs, and activity.

Run a sprint retrospective with data-driven insights from git history.

Run the local review gate before pushing.

RICE-score features or tasks for prioritization.

Generate a SaaS health dashboard with key business metrics.

Run the security scan gate before pushing.

Run an SEO audit on web content and HTML files.

Check current sprint health and identify risks.

Plan a sprint by analyzing backlog, estimating capacity, and selecting work.

Guide a Test-Driven Development workflow for the current task.

Scan and prioritize technical debt in the codebase.

Create well-structured user stories with acceptance criteria.

Quick check-in. Works as manual command or scheduled trigger.

Evening review. Captures wins, lessons.

Deep reflection. Creates journal entry.

Morning kickoff. Sets MIT for the day.

First-run setup. Interviews the user and fills the template files.

Run pre-commit checks identical to GitHub CI (ruff, mypy, tests)

Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity, Kimi, and a local ollama model) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Use this whenever the user names the council directly, whatever the topic — ask the council, council review, full council review, what does the council think, get a second opinion from the council, run this past the council — including reviews of code, documents, plans or artifacts. Also suggest it unprompted when the user is choosing between competing approaches (e.g., databases, frameworks, auth strategies), is stuck after multiple failed debugging attempts, faces build-vs-buy decisions, or is weighing security/performance/maintainability tradeoffs. Do NOT suggest it unprompted for simple implementation tasks, quick fixes, or questions with clear single answers; a direct request for the council overrides that exclusion.

Fetch, list, or cancel background council jobs started with --async

Check connectivity and configuration status of all council providers

Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem)

Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)

Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories)

Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis)

Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff

Run the Post-Launch Learning workflow (instrumentation -> dashboard -> results -> retro -> lessons)

Run the Product Strategy workflow (competitive analysis -> stakeholders -> opportunities -> solution -> ADR)

Run the Sprint Planning workflow (refinement -> stories -> edge cases)

Run the Stakeholder Alignment workflow (stakeholders -> problem -> solution -> launch)

Run the Technical Discovery workflow (spike -> ADR -> design rationale)

Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)

Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.

Review the current working diff for correctness, security, and reuse.

|

Automated multi-agent development workflow with quality gates from idea to production code

Ask questions about memories and get context-aware answers