「age」の検索結果

Auto-generate knowledge YAML from the codebase. Use when the user runs /sync-knowledge or wants knowledge files refreshed.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-capture UI screenshots for PRs using Playwright MCP browser tools.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Grade and steer UI work using Anthropic-style design dimensions—coherence, originality, craft, and usability—for generators and evaluators.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Risk-tiered code review (Blocker / High / Medium / Low). Use when the user runs /review or wants the current branch or diff reviewed.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。