1.3천건 · 관련도순
Scaffold course exercise directories with numbered sections, exercise variants, required readmes, and repo-specific validation. Use when creating exercise stubs, adding a course section, or safely renaming exercises.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 3 of the Forge pipeline. Execute the plan's Beads tasks with red-green-refactor TDD, committing per checkpoint and pausing at each natural stopping point so the user can run a live demo or test and see the work themselves. Use when starting /forge-implement or the implement step of /forgemaster.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Risk-tiered code review (Blocker / High / Medium / Low). Use when the user runs /review or wants the current branch or diff reviewed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register a new sub-repo in the knowledge base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a higher-level architecture and context map for unfamiliar code. Use when you need to understand how a file, module, feature, or issue fits into the bigger picture, including relevant modules, callers, callees, dependencies, and next context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract a DDD-style domain glossary from conversation context, choosing canonical terms and flagging ambiguity. Use when the user asks to define domain terms, build a glossary, clarify terminology, create a ubiquitous language, or mentions domain modeling or DDD.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ultra-compressed communication mode that preserves technical accuracy while dropping filler. Use when the user explicitly says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Relentlessly stress-test a plan or design through a one-question-at-a-time interview that researches available context first and includes a recommended answer with every question. Use when the user asks to "grill me", wants a plan/design challenged, or needs decisions resolved before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auto-generate knowledge YAML from the codebase. Use when the user runs /sync-knowledge or wants knowledge files refreshed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 4 of the Forge pipeline. Summarize the whole workload — what was built, which Beads issues closed, a before/after, and a step-by-step walkthrough the user can run to verify it themselves — then run quality gates, push, and open the PR. Use when starting /forge-ship or the ship step of /forgemaster.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Edit and improve article drafts by confirming a heading-based section plan, dependency order, then rewriting section by section with short paragraphs. Use when the user wants to revise or improve an article draft.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deadline management and capacity planning across epics and PRs. Use when the user runs /triage or wants deadline/capacity triage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Route a task by complexity and run the gated Forge pipeline (research → plan → implement → ship). Use when the user runs /forgemaster or wants the full guided feature pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a conversational QA session where the user reports bugs or issues, and file durable Beads issues using project domain language. Use when the user wants to report bugs, do QA, file issues conversationally, or mentions a QA session.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report git state, ready work, blocked items, and PR health. Use when the user runs /status or wants a workspace snapshot.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trimmed Forge pipeline (scope → build → wrap) for small, clear-scope work. Use when the user runs /forgemaster-mini or has a small, well-scoped task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-test a plan against existing domain language, code behavior, and durable decisions. Use when the user wants DDD/domain-model grilling, glossary refinement, terminology challenges, context documentation, ADR candidates, or plan validation against a repo's language.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Grade and steer UI work using Anthropic-style design dimensions—coherence, originality, craft, and usability—for generators and evaluators.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.