スキルを探す

Performs a fast 6-point quality check for technical documents (specs, design docs, READMEs). Use after editing any specification or design document.

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

Assesses production readiness or audits a codebase against its specs. Supports quick static mode, deep 17-dimension audit, or single-dimension focus. Use before a production launch, after a major refactor, when inheriting a codebase, or when someone asks how done the project is.

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

Runs the Implement→Review→Test→Fix cycle until the work is actually clean, with evidence. Use after any non-trivial implementation and before claiming it is done.

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

Researches real projects, papers, and documented failures before proposing a new feature, architecture, or technology choice. Use for design decisions with multiple valid approaches, not for implementing an existing spec or fixing a known bug.

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

Queries all configured services for health status — uptime, restarts, errors, resources. Use when checking the health of running services.

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

Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording, rebase-before-commit, stale-checkout detection, and shared-machine hygiene (ports, processes, measurement noise). Use when a project spans several phases or sessions with three or more agents working at once.

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

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.

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

Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.

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

Keeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.

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

Refuses "flaky" as a diagnosis. Turns an intermittent failure into a reproduction by isolating it from the environment, naming the variable that controls it, forcing that variable, and measuring before and after with enough runs to count. Separates real defects from environment contention with evidence, and never retries to green or widens a threshold. Use when a test, performance check, or deploy step fails intermittently or passes on rerun.

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

Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass. Use when implementing or changing a parser, or any code that ingests user input, webhook payloads, API responses, or file formats.

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

Performs end-of-iteration review with quality grading, metrics, and trend analysis. Use at the end of each development iteration or sprint.

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

Analyzes large tasks for independent subtasks that can be safely parallelized. Produces a DAG-based dispatch plan with dependency ordering and maximum parallelism. Use when a task has 5+ subtasks touching independent files, or the user asks to speed up or parallelize the work.

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

Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.

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

Generates a behavioral scenario acceptance matrix for comprehensive test coverage planning. Maps user scenarios to acceptance criteria with stable IDs. Use when planning test coverage for a complex feature, before a release or milestone review, or when someone asks what is tested.

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

Detects and redirects scope creep during implementation — unrequested features, drive-by refactors, premature abstraction, and over-engineering. Use while implementing, especially when a change is growing beyond the original request.

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

Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.

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

Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.

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

Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.

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

Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.

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

Extracts and records architectural decisions from diffs, conversation context, and explicit choices. Supports automatic extraction from staged changes, deduplication against prior decisions, and persistent ADR-format logging with spec traceability. Use after a significant design or architecture choice, before committing a diff that embeds implicit decisions, or when the same question keeps resurfacing.

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

Challenges a recommendation, design, large change, or any artifact submitted for hard review (spec, proposal, policy, plan) across 5 dimensions (consistency, completeness, actionability, alignment, risk), from the standards of a named senior expert in the artifact's domain and ideally from a fresh context or a different model. Searches assuming defects exist and reports only those that survive evidence. Panel mode runs several independent lenses in parallel on a release candidate, verifies every finding against the current head, and routes confirmed ones to file owners. Use before shipping a significant recommendation, design, large branch, or multi-agent release, or when asked to tear something apart, be brutally honest, or poke holes in it.

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

Closes a large backlog of findings (a gap analysis, an audit, or 10+ bugs) in prioritized waves. Loops through triage, dependency analysis, parallel fix streams, a test gate, and re-audit until the target is met. Use after a gap analysis, audit, or review produces 10+ findings, or to burn down a large bug or tech-debt backlog.

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

Implements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.

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