Explore skills

Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.

Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.

Elixir testing patterns — ExUnit, Mox, factories, LiveView test helpers. Use when working on *_test.exs, test/support/, factory files, or fixing test failures.

This skill should be used when the user asks about the invoice system (インボイス制度), qualified invoices (適格請求書), registration numbers (登録番号), input tax credits (仕入税額控除), the 20% special measure (2割特例), the 30% special measure (3割特例), tax-exempt businesses (免税事業者), transitional measures (経過措置), small-amount exceptions (少額特例), corrected invoices (修正インボイス), or any related topics. Trigger phrases include:

This skill should be used when the user needs to perform year-end closing adjustments (決算整理), review financial statements (決算書), compute depreciation, or review their trial balance. Trigger phrases include: "決算", "決算整理", "決算書を作る", "減価償却", "試算表", "残高試算表", "損益計算書", "貸借対照表", "BS", "PL", "期末処理", "棚卸し", "未払計上", "前払処理".

This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.

Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.

This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.

This skill should be used only when the user explicitly asks to use `$ralph-specum-start`, or explicitly asks Ralph Specum in Codex to start or resume a spec.

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.