jupes

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.

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

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.

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

Investigate a reported problem, diagnose root cause, and file a Beads issue with a behavior-level TDD fix plan.

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

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.

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

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.

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

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.

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

Surface architectural friction and propose deepening opportunities that improve testability and AI-navigability. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase easier for agents to navigate.

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

Migrate test files from `as` assertions to @total-typescript/shoehorn helpers. Use when tests need partial fixtures, intentionally invalid data, or safer replacements for TypeScript assertions.

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

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.

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

Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.

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

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.

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

Set up repository-local Husky pre-commit hooks with lint-staged, Prettier, and optional typecheck/test gates. Use when a user asks to add pre-commit hooks, configure lint-staged, enforce staged formatting, or add commit-time checks.

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

Multi-repo git operations — init, reset, status, branch management, refresh (rebase), stacked rebase. JSON output for agent consumption.

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

Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.

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

Synthesize current context into a PRD and file it as a Beads feature/epic issue.

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

Reference definitions for the Agent Forge orchestration roles (lead, worker, planner, evaluator). Use when coordinating multi-agent Forge work or when you need one role's responsibilities and constraints.

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

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.

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

Classify a task and route it to the right workflow (fix / feature / epic). Use when the user runs /go or wants the adaptive workflow router.

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

Explore the codebase and produce an implementation plan. Use when the user runs /plan or wants a plan before building.

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

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 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.

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

Register a new sub-repo in the knowledge base.

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

Capture free-text work as a tracked Beads issue. Use when the user runs /add-bead or wants to quickly file a Beads issue.

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