「phases」の検索結果

Refresh tracked pre-launch stablecoin milestones, dates, launch phases, featured content, and promotion evidence. Use for the recurring upcoming-assets review.

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

Canonical entry point for the full Gaia evidence verification pipeline. Invoke as /evidence-verification-pipeline or /ev-pipeline — both names trigger this skill. Use whenever you need to run the evidence phases end-to-end: collecting raw evidence from the data lake, verifying live GitHub star counts, running Phase 2B benchmark-source verification, running adversarial auditing for noise and URL errors, and checking link health via Firecrawl. Also use when someone says "run the evidence pipeline", "verify the evidence lake", "audit evidence", "run ev-pipeline", "full evidence check", "pipeline run", "prepare evidence for ingestion", or "refresh the data lake". This is the pre-ingestion step — run it before importing any evidence into the registry.

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

Multi-agent exploration-to-PR pipeline for safely exploring, fixing, and shipping a feature or CLI. Use when the user says: "explore X", "test and ship X", "run the pipeline on X", "run /feature-pipeline on X", "let's properly investigate X", "stress-test X and file issues", or "take X through the full pipeline." Also triggers on: "find what's broken in X", "test X end-to-end", "do a sandbox review of X", "file issues for X and fix them." Do NOT use for single-file bug fixes or one-off edits — the overhead is only justified when exploration, planning approval, and CI watching all matter. Manages state via scripts/state.sh (jq required). Five phases: LIGHTER explores → ORCHESTRATOR drafts PR → HEAVIER plans (user approves first) → ORCHESTRATOR commits → HEAVIER sandbox review → LIGHTER iterates CI → LIGHTER drift check + summary. Four mandatory stop hooks (M1–M4) gate each phase transition.

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

Reference guide for the full manual Gaia curation pipeline. Invoke at any phase when unsure what command to type next: gaia-curate, L4 review, gaia push, ev-pipeline (Phases 0–4), gaia-ingest, or close. Trigger phrases: "/gaia-consult", "what's the command for", "remind me how to", "I'm lost in the pipeline", "what do I do next", "consult the pipeline doc", "pipeline reference".

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

Multi-agent management workflow — task delegation, progress monitoring, quality verification with regression testing, feedback delivery, and cross-review orchestration. Use this skill when coordinating multiple agents on a shared task, monitoring delegated work, ensuring quality across agent outputs, or implementing a multi-phase plan (3+ phases or 10+ file changes).

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

Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

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

Interface-based state machine patterns for Unity game states, character controllers, and UI flows. Use when implementing game flow (menu -> gameplay -> game over), character states (idle -> run -> jump -> fall), AI behavior states, or UI screen transitions. Triggers on "state machine", "game states", "character states", "screen flow", "game flow", "add states to", "idle/run/jump", "menu flow", "AI states", "boss phases", or any task involving managing discrete states with transitions between them. Reads ProjectConfig.yaml -> architecture_pattern to adapt patterns for SO-first or DI-first.

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

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.

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

Use this whenever the user asks to "implement", "add", "build", "create", or "modify" a feature, page, view, component, or module in this Vue project. Three phases: Phase 0 scope analysis (flows + edge cases + UI needs + plan validation, STOP for user), Phase 1 implementation (layered UI → Store → API, Vue 3 Composition + Vuetify 4, /ui design rules), Phase 2 Definition-of-Done checklist + /verify + /pull-request. Auto-runs /create-module if the target module doesn't exist.

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

Run the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.

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

Designing clinical trials — phases, randomization, endpoints, sample size, and CONSORT-compliant reporting.

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

Compiles binary analysis findings into structured reports — correlates facts from triage, static, and dynamic phases, validates hypotheses against evidence, and produces traceable documentation. Use when ready to summarize findings, generate a report, document what a binary does, or prepare results for handoff or archival.

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

Standalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).

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

Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

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

Utility skill. Lists all projects under the projects/ directory and shows which Virtual Team pipeline phases have been completed for each project.

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

Standalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).

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

Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.

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

Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

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

Comprehensive test suite review across five phases. Surveys unit coverage, integration coverage, E2E (browser) coverage for webapps, fuzz coverage, and test quality — in that order. Advisory only — produces findings and proposes tickets; does not implement test changes.

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

Writing tests, running validation, and (TDD mode) red-green-refactor. Active in Test + Build phases. NOT for coverage-gap mapping (mk:nyquist) or sprint contracts (mk:sprint-contract).

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

Task claiming and file-ownership tracking for parallel execution: agents claim tasks from a shared queue with ownership enforced. Use during parallel phases with multiple simultaneous agents.

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

Maps test coverage to plan acceptance criteria and flags requirements with no tests. Use during Test/Review phases. NOT for running tests (mk:testing); NOT for structural review (mk:review).

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

Task claiming and ownership tracking for parallel agent execution. Agents claim tasks from a shared queue with file ownership enforcement. Use during parallel execution phases when multiple agents work simultaneously.

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

Quantitative agent evaluation using 4-metric framework (correctness/step_ratio/tool_call_ratio/latency_ratio) with ideal trajectory annotation and capability-categorical taxonomy. Use when measuring agent efficiency, comparing agent variants, or gating new agents through correctness→efficiency phases. Complements harness-eval (SE benchmarks) and evaluator-optimizer (qualitative rubric).

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