Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
日本語の概要は準備中です。原文の説明を表示しています。
4.1万 件 ・ 関連度順
概要と使いどころ
Choose Beads issue priority (P0–P4, numeric, or named) from urgency, impact, and risk when creating or triaging work.
日本語の概要は準備中です。原文の説明を表示しています。
Register a new sub-repo in the knowledge base.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical PR description template for every PR shipped from this harness, with a validator that enforces the required sections. Use when opening or editing a PR (the /ship and /forge-ship steps), or when asked for the standard PR format or to check a PR body.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Explore the codebase and produce an implementation plan. Use when the user runs /plan or wants a plan before building.
日本語の概要は準備中です。原文の説明を表示しています。
Break a plan/PRD into independent vertical-slice Beads issues with explicit dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured weekly status reports covering initiatives, progress, blockers, risks, and KPIs.
日本語の概要は準備中です。原文の説明を表示しています。
Answer questions about the codebase from knowledge files. Use when the user runs /ask or asks a domain/knowledge question about the repos.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize current context into a PRD and file it as a Beads feature/epic issue.
日本語の概要は準備中です。原文の説明を表示しています。
Create a Beads-first refactor plan through detailed interview, repo verification, alternatives, scope boundaries, testing decisions, and tiny working increments. Use when the user wants to plan a refactor, write a refactoring RFC, or turn a risky change into safe incremental 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 Claude Code git safety guardrails that block dangerous git commands before execution. Use when the user asks to prevent git push, hard reset, git clean, destructive checkout/restore, or branch deletion from Claude Code hooks.
日本語の概要は準備中です。原文の説明を表示しています。
蒸馏协议:为个人数字资料生成人类可读条款与机器可读 manifest;戏称「牛马保护法」仅为传播梗,非法律意见。
日本語の概要は準備中です。原文の説明を表示しています。
Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.
日本語の概要は準備中です。原文の説明を表示しています。
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
日本語の概要は準備中です。原文の説明を表示しています。
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and resolve production issues. The intelligent debugging strategy combines automated root cause analysis with human expertise, using modern 2024/2025 practices including AI code assistants (GitHub Copilot, Claude Code), observability platforms (Sentry, DataDog, OpenTelemetry), git bisect automation for ...
日本語の概要は準備中です。原文の説明を表示しています。