「readiness」の検索結果

Use when reviewing an app for launch-readiness — Product Hunt polish, first impression, visual hierarchy, onboarding, empty states, screenshots, positioning, and the tiny details that make it feel premium.

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

Use when work produces a deliverable, factual claim, dataset, code change, decision, publication, deployment, automation, or irreversible action whose failure would matter; when the user asks for a quality gate, acceptance criteria, QA, completeness, validation, audit, evidence, preflight, release readiness, or a definition of done; or before claiming completion on medium- or high-risk work. Automatically decide whether a formal gate is warranted, derive task-specific pass/fail criteria, gather evidence, and block unsupported completion. Make sure to use this skill even when the user does not say "quality gate" if consequential work needs acceptance criteria or completion evidence. Skip formal gating for trivial, reversible, low-impact requests.

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

Prepare deployment configs, final checks, and pre-launch readiness artifacts for production release.

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

Read-only diagnosis workflow for Python services whose external HTTP or WebSocket readiness differs between manual tests and service runtime behind a proxy.

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

Read-only first troubleshooting workflow for Python project deployments, including systemd startup failures, dependency issues, encoding problems, permissions, proxy setup, and readiness gates.

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

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.

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

GStack ship method for final landing, PR, changelog, release, and deploy readiness checklists when the user explicitly wants to ship.

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

GStack health-check method for broad project or repository health review across tests, docs, DX, release readiness, and maintainability.

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

SOP for the architect-tier campaign workflow (/campaign): exhaustive survey, mitigation planning, tiered orchestration, and reconciliation. Trigger when: - Running a multi-workstream initiative where an expensive architect-tier council surveys, plans, emits worker prompts, and judges landed work. - Conducting production-readiness assessments that fan out into autonomous mitigation dispatches across model tiers. - Prompt contains: /campaign, campaign workflow, survey, orchestrate, reconcile, premise freshness, tier routing, worker IBC, scratch.

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

Tech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.

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

AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.

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

Resolve, validate, and audit manuscript integrity and applicable requirements for academic manuscripts and paper artifacts. Use when Codex needs to determine active paper rules from manuscript state, paper type, venue, submission stage, or workflow mode; lint a LaTeX paper project; assess submission readiness; create or update a paper policy profile; explain why a rule is active; or validate the paper-policy registries. Do not use as the primary skill for prose drafting, peer review, rebuttal writing, citation discovery, or figure/table creation.

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

Review an author's manuscript, its argument and paragraph structure, analyze reviewer comments, draft rebuttals, and verify revisions. Use for self-review, structural edit plans, simulated reviewer objections, author responses, revision closure, and submission-readiness assessment. Formal assigned peer review is outside this skill; manuscript edits and final figures/tables use their owning skills.

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

Use at the start of a Codex task to inspect repo readiness, project profile, monorepo shape, role docs, spec status, knowledge index, and recommend the next workflow.

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

Use when work needs Scrum roles, ceremonies, backlog refinement, sprint planning, story delivery, release readiness, or role handoffs.

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

Review a PR end-to-end with CI checks, fix cycles, and optional auto-merge. Use for PR review, cleanup, or readiness checks. Don't use for creating PRs, raw issue analysis, or non-PR code review.

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

Assess and migrate cross-cloud workloads to Azure. Generates assessment reports and converts code from AWS, GCP, or other providers to Azure services. WHEN: migrate Lambda to Azure Functions, migrate AWS to Azure, Lambda migration assessment, convert AWS serverless to Azure, migration readiness r...

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

Operational readiness checklist (security, cost, legal, data design, performance, incident response, LLM integration defenses) applied when a change touches deployment, infrastructure, external services, secrets, or user data.

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

Evaluate project deliverables (code, docs, config) and calculate a 0-100 completeness score with weighted criteria and prioritized action items. Use when assessing project readiness, reviewing milestones, or identifying gaps before release.

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

Use when explaining a technical concept and adapting depth, pacing, and examples to the learner's readiness.

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

Use when evaluating, designing, drafting, revising, stress-testing, or preparing academic articles, empirical research reports, literature reviews, systematic reviews, meta-analyses, journal submissions, reviewer responses, research methods, sampling, measurement, analysis, publication readiness, or citation/source audits.

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

Load for pre-PR self-review or pull-request review that must verify the matched intent, allowed scope, required tests/docs, forbidden actions, architecture gates, and merge readiness; not for a general code-quality diff review alone.

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

Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.

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

Knowledge base from the GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices; the 12-step cost estimating process (purpose, plan, technical baseline, WBS, ground rules and assumptions, data, point estimate, sensitivity, risk/uncertainty, document, present, update); estimating methods (analogy, parametric, engineering build-up, learning curves); Monte Carlo risk/uncertainty analysis, confidence levels and contingency; auditing and validating an estimate against the characteristics; earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR); and specialized techniques (software cost estimating, learning curves, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). This is the cost-estimating companion to the GAO Schedule and Technology Readiness Assessment guides. Does not cover schedule estimating/risk in depth (see the GAO Schedule Assessment Guide), agency-specific cost models, or the full text of referenced standards (EIA-748, MIL-STD-881D, the Green Book) — these are named, not reproduced.

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