360 件 ・ 関連度順
概要と使いどころ
Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at `docs/specs/<slug>.md`. Never self-approves — approval happens via `/approve-direction`.
日本語の概要は準備中です。原文の説明を表示しています。
Review a planned deployment or release diff for rollback feasibility, mixed-version compatibility, migrations, and configuration readiness without deploying it.
日本語の概要は準備中です。原文の説明を表示しています。
Plan database migrations before executing them: risk assessment, dependency mapping, multi-service sequencing, rollback budgets, and stakeholder communication plans. Use when deciding HOW to migrate, not when writing the actual DDL. NOT for: writing migration SQL (use database-migration-manager), data ETL pipelines (use data-migration-specialist), query optimization, or ORM configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, write, and maintain automated tests in any language, with worked examples in Python and JavaScript/TypeScript. Use this skill whenever the user wants to write or plan tests, apply TDD (red-green-refactor), structure unit tests with arrange-act-assert and given-when-then naming, choose between fakes, stubs, and mocks, set up dependency injection for testability, build integration tests with testcontainers, database seeding, or transaction rollback, write Playwright or Cypress end-to-end tests, use property-based testing with Hypothesis or fast-check, create pytest fixtures or factory_boy factories, review coverage or mutation testing, or triage flaky tests in CI. Also trigger for "test pyramid", "test trophy", "test isolation", "mocking", "snapshot tests", "golden files", "parametrized tests", "make the tests pass".
日本語の概要は準備中です。原文の説明を表示しています。
Go / no-go gate before any deployment. Checks failure modes, rollback plan, cost, production bar, and definition of done. Trigger before releasing to any environment that carries real consequences.
日本語の概要は準備中です。原文の説明を表示しています。
Use before merging a release-shaped PR — pre-merge checklist, rollout plan, rollback criteria, ops handoff. Triggers on 'ready to ship', 'launch checklist', 'rollout plan for X'.
日本語の概要は準備中です。原文の説明を表示しています。
Princípios de deploy em produção e tomada de decisão. Workflows seguros de deployment, estratégias de rollback e verificação. Ensina raciocínio, não scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Domine migrações de schema e dados em ORMs (Sequelize, TypeORM, Prisma), incluindo estratégias de rollback e deployments sem downtime.
日本語の概要は準備中です。原文の説明を表示しています。
Generic read-only post-deployment verification workflow for confirming service health, artifact activation, routing, logs, and rollback signals after a deployment action.
日本語の概要は準備中です。原文の説明を表示しています。
Generic read-only checklist for preparing an application deployment by verifying host, artifacts, backups, service state, configuration, dependencies, and rollback readiness before any write action.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only workflow for discovering uploaded deployment artifacts, comparing them with current deployment state, and preparing a safe update and rollback plan.
日本語の概要は準備中です。原文の説明を表示しています。
GStack canary method for staged release thinking, smoke gates, rollout checks, and rollback signals before or after deployment.
日本語の概要は準備中です。原文の説明を表示しています。
GStack land-and-deploy method for explicit landing and deployment workflows with tests, release notes, rollout gates, and rollback planning.
日本語の概要は準備中です。原文の説明を表示しています。
Rehearse a live-app schema change + backfill on a snapshot-seeded preview deployment, verify, then promote the proven change to prod with the snapshot as rollback.
日本語の概要は準備中です。原文の説明を表示しています。
Rehearse a live-app schema change + backfill on a snapshot-seeded preview deployment, verify, then promote the proven change to prod with the snapshot as rollback.
日本語の概要は準備中です。原文の説明を表示しています。
Test or debug application use cases through their public Action API, including persistence, authorization failures, atomic rollback, and post-commit reactions. Use when adding regression tests for business operations.
日本語の概要は準備中です。原文の説明を表示しています。
Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Concrete remediation proposal with Safe Harbour confidence — version bump, inline as first-party code, patch, workaround, or advisory. Use when applying a fix for a triaged CVE, evaluating fix-type trade-offs across registry / source / distro patches, producing rollback-safe manifest edits with dry-run verification, or generating a CycloneDX SBOM after the fix lands.
日本語の概要は準備中です。原文の説明を表示しています。
Audit over-engineered codebases by factoring layers into live obligations, quotienting redundant distinctions, ablating unearned surface, and normalizing survivors while preserving required behavior. Use when change latency or agent difficulty comes from frameworks, plugins, DI, codegen, task runners, config indirection, ORMs, GraphQL, monorepo/infra tooling, or web stacks, or when asked to remove layers. Produces an evidence-backed Reduction Certificate, cuts, migration phases, proof signals, and rollback. Not for one local readability cleanup (use tw-complexity-mitigator).
日本語の概要は準備中です。原文の説明を表示しています。
Add or change stable public state, contracts, routes, migrations, adapters, rescue behavior, or compatibility-sensitive surfaces through the evolution ledger.
日本語の概要は準備中です。原文の説明を表示しています。
Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Turns process notes, a walkthrough or interview transcript, a transcript of a meeting recording or a stale existing procedure into a draft standard operating procedure: purpose and trigger, scope, definitions, roles with a RACI table, numbered steps with the check that closes each one, records produced, controls as stated, and open questions for the process owner. Every step traces to the source or reads UNKNOWN. Use when the user asks to "write an SOP from these notes", "turn this walkthrough into a procedure", "document how we do this", "draft the standard operating procedure for", "build a RACI for this process" or "tidy up this old procedure". Do not use for technical runbooks with commands and rollback, use runbook-drafter instead; for meeting minutes and action lists, use transcript-to-actions. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。