586 件 ・ 関連度順
概要と使いどころ
Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan. Creates TEST_SPEC.md from PRD and implementation specs. Use when creating QA strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestrator that generates all implementation specs (PRD, Architecture, UX, Implementation, Test, Release) from product plan. Use when generating complete specification package.
日本語の概要は準備中です。原文の説明を表示しています。
Generates detailed implementation guide with pseudo-code and step-by-step development instructions. Creates IMPLEMENTATION_GUIDE.md from PRD, Architecture, and UX specs. Use when creating development roadmap.
日本語の概要は準備中です。原文の説明を表示しています。
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end product development for iOS/macOS apps. Covers market research, competitive analysis, PRD generation, architecture specs, UX design, implementation guides, testing, and App Store release. Use for product planning, validation, or generating specification documents.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
日本語の概要は準備中です。原文の説明を表示しています。
Run a task through your Executor Cloud tool catalog - one MCP endpoint proxying every integration you connected (MCP servers, OpenAPI specs, GraphQL APIs), with per-tool allow/approve/block policies. OAuth Connect via the dashboard MCP panel.
日本語の概要は準備中です。原文の説明を表示しています。
Negotiate a pre-code contract between generator and evaluator personas that defines what "done" means before any code is written. Turns fuzzy specs into a testable target the evaluator can hold the generator to.
日本語の概要は準備中です。原文の説明を表示しています。
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
日本語の概要は準備中です。原文の説明を表示しています。
Use when briefing or managing an EXTERNAL agency, freelancer, or production vendor — scope of work, deliverable specs, revision rounds, approval process, USD payment milestones, IP assignment and confidentiality terms, communication rules, and a post-project vendor scorecard. Trigger on 'brief an agency', 'hire a freelancer', 'scope of work', 'the agency is not delivering', 'onboard a new vendor', 'we keep paying for work we have to redo'. Also use when the user is about to sign a supplier with nothing written down. Not for — briefing an internal team member, see `64-team-brief-global`; the campaign brief itself, see `02-campaign-brief-global`; the asset list the vendor produces, see `41-campaign-asset-list-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an editor or videographer needs production direction — beat-by-beat storyboard, footage to shoot, b-roll, text overlays, music and pacing, transitions, CTA end frame, and per-channel export specs. This is the EDIT instruction, not the spoken script. Trigger on 'video brief', 'editor brief', 'storyboard', 'brief for the video editor', 'how should this video be cut', 'we have the footage and no direction'. Also use when raw clips exist and nobody knows what the final should look like. Not for — the words said on camera, see `04-script-video-global`; briefing a creator to film their own, see `06-ugc-egc-brief-global`; resizing a finished video, see `50-asset-resize-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.
日本語の概要は準備中です。原文の説明を表示しています。
Design Spring Boot APIs with OpenAPI, Versioning, and Global Error Handling. Use when designing Spring Boot APIs with OpenAPI specs, versioning, or global error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Automate Swagger/OpenAPI documentation and standardize API response schemas in NestJS. Use when generating OpenAPI specs, documenting paginated or generic responses, configuring the Nest CLI Swagger plugin, or publishing versioned API docs.
日本語の概要は準備中です。原文の説明を表示しています。
Apply REST API conventions — HTTP semantics, status codes, versioning, pagination, and OpenAPI standards for any framework. Use when designing endpoints, choosing HTTP methods, implementing pagination, or writing OpenAPI specs.
日本語の概要は準備中です。原文の説明を表示しています。
Universal team coordination skill with dynamic role generation. Uses team-worker agent architecture with role-spec files. Only coordinator is built-in -- all worker roles are generated at runtime as role-specs and spawned via team-worker agent. Beat/cadence model for orchestration. Triggers on "Team Coordinate ".
日本語の概要は準備中です。原文の説明を表示しています。
Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.
日本語の概要は準備中です。原文の説明を表示しています。
Product Requirements Document writing - PRD templates, MoSCoW prioritization, user personas, competitive analysis, feature specs, acceptance criteria, risk assessment
日本語の概要は準備中です。原文の説明を表示しています。
Voice framework, visual identity standards, color palette management, typography specs, brand consistency
日本語の概要は準備中です。原文の説明を表示しています。
Draft non-prose visuals artifacts (timeline, figure specs) for a survey, grounded in evidence and using citation keys from `citations/ref.bib`.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds eval.yaml evaluation specs for skills, custom agents, and redistributable gh-aw workflow packages in the dotnet/skills repository. Use when creating skill or workflow-package tests, writing evaluation stimuli, defining graders and rubrics, sizing an eval for statistical power, or setting up test fixture files. Handles the Vally eval.yaml schema, fixture organization, and overfitting avoidance. Do not use for running or debugging existing evals (use improve-skill-quality) nor for skills authoring (use create-skill).
日本語の概要は準備中です。原文の説明を表示しています。
Builds an app, site, bot, or feature end-to-end from a dictated idea — requirements, briefing, spec, tickets, subagents, review, acceptance — with a live dashboard, for users who expect a finished result without reviewing specs or code. Starts only on /autopilot; a bare /autopilot resumes an interrupted run.
日本語の概要は準備中です。原文の説明を表示しています。