koizumikento

Use when the author asks if local Git state is ready to push or an open pull request is ready for initial or repeat human review. Owns a read-only, state-sealed readiness decision. Do not use for general code review, fixes, security preflights, GitHub…

Use when the user wants working code for an end-to-end web, mobile, or desktop app flow spanning UI and its API, data, auth, or background behavior. Do not use for Slack apps, static corporate sites, landing pages, reviews, test-design-only work, product…

Use when the user wants an e-Stat 統計表 searched, retrieved, filtered, compared, or analyzed, including a statsDataId. Do not use for KPI ideation or tracing an identified whitepaper chart before its source table is known.

Use when the user wants MLIT Real Estate Information Library data retrieved, mapped, compared, or analyzed for a defined place/layer. Do not trigger on 地価・不動産 policy discussion without a data operation.

Use when a durable, source-backed report requires multiple independent research tracks, broad source coverage, conflict resolution, and explicit uncertainty. Do not use for concise web answers, single-track domain briefs, page extraction, or work owned by a…

Use when one specialized technical, standards, regulatory, market, or academic question needs a focused source-backed brief from authoritative current evidence. Do not use for generic web answers, multi-track deep reports, product decisions, page extraction,…

Use when current web signals should generate, widen, compare, or tentatively rank idea directions before a final choice is made. Do not use for evidence-free brainstorming, product selection or scope, PRDs, acceptance criteria, validation plans, or finished…

Use when a named Japanese company, corporate number, or explicit gBizINFO entity lookup needs official corporate-profile or activity data through gbizinfo-mcp. Do not trigger on subsidy, procurement, patent, award, or market topics without a company/entity…

Use when a dataq automation task needs a new or revised `assert --rules` file or `dataq.recipe.v1` recipe, including lock/replay verification. Do not use for general dataq command selection, CLI or schema implementation changes, or routing-only evaluation.

Use when an agent needs to choose, inspect, or run an existing dataq CLI or MCP workflow with deterministic machine-readable output. Do not use for authoring rules or recipes, changing dataq behavior, or AI inference.

Use when a dataq automation task needs a new or revised `assert --rules` file or `dataq.recipe.v1` recipe, including lock/replay verification. Do not use for general dataq command selection, CLI or schema implementation changes, or routing-only evaluation.

Use when an agent needs to choose, inspect, or run an existing dataq CLI or MCP workflow with deterministic machine-readable output. Do not use for authoring rules or recipes, changing dataq behavior, or AI inference.

Use when one completed dataq feature needs a read-only, diff-scoped review pass with merge-blocking findings and an exact verdict. Do not use to implement fixes, map an unfinished feature, review an unspecified range, or audit the whole repository.

Use when exactly one dataq Rust CLI feature—such as a subcommand, option/output contract, or validation/normalization/diff behavior—must be implemented with tests and docs in an isolated branch and worktree. Do not use for multiple features, review-only work,…

Create, revise, execute, and validate SKiDL-based electronic circuit designs, BOM/ERC artifacts, KiCad 9 schematics, and optional ngspice/PySpice analyses. Use for component-level connectivity, power and signal conditioning, interfaces, schematic generation,…

Validate mechanical-electrical interfaces between a PCB, enclosure, connectors, controls, cables, thermal features, and mounting hardware. Use when checking board-to-enclosure fit, coordinate transforms, mounting alignment, keep-outs, access, assembly/service…

Create, revise, execute, and validate parametric mechanical designs in build123d, including parts, enclosures, brackets, shafts, fixtures, assemblies, and PCB-housing geometry. Use when the requested deliverable includes CAD Python, STEP/STL exports,…

Create or refine reviewable Markdown specifications for mechanical, electronic, or PCB-enclosure integrated designs. Use when requirements must be elicited, made testable, assigned identifiers and verification methods, or recorded under specs/ before or…