403건 · 관련도순
Use when the user wants a dashboard of all phases or to run more than one phase in parallel. Shows phase status with recommended next actions, runs discuss inline, and dispatches plan and execute as background agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to add a phase, feature, or scope to the end of the current milestone roadmap. Adds the next sequential phase directory, updates ROADMAP.md, and tracks the change in STATE.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to execute a phase's plans, resume the remaining plans, or run only one wave. Discovers plans, groups them into dependency waves, spawns a fresh subagent per plan, then verifies the phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before archiving a milestone, or when the user asks whether a milestone met its definition of done. Aggregates phase VERIFICATION.md files, tech debt and deferred gaps, then runs a cross-phase integration check.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used only when the user explicitly asks to use `$ralph-specum-research`, or explicitly asks Ralph Specum in Codex to run the research phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an engineering goal through the gated SPARC phases when the user wants a new implementation, integration, redesign, or other substantial delivery workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query ClinicalTrials.gov API v2 for trial data. Search by condition, drug/intervention, location, sponsor, or phase; fetch details by NCT ID; filter by status; paginate; export CSV. For clinical research, patient matching, and trial portfolio analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building a 2D web game with Phaser (3.x/4.x) or PixiJS 8 in TypeScript - framework vs renderer, Phaser scenes/game objects/arcade physics/groups as pools/scale manager/loader, scene shutdown cleanup, PixiJS 8 async init, Assets bundles, ticker units and destroy, and keeping rules in plain TS modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut command.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for code-mode teams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared conventions for every SDLC development-phase architect agent: hard rules, code quality bar, workflow steps (superpowers invocation, spec reading, codebase exploration, verification), and the report/compact-summary contract. Architects load this skill first, then apply their stack-specific instructions on top.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
报告撰写人（程文成 Cheng）。由 research-chief-editor 主理人在 Phase 4 调度，汇总所有章节通过稿，撰写报告框架部分——深度引言（带引用）、结论（带引用）、目录、APA 格式参考文献列表。输出 JSON。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当所有章节通过审稿后，主理人下发 Phase 4 撰写任务时激活。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Understand what Skmtc is, how its engine works, and the architectural invariants — for agents building or extending infrastructure *around* Skmtc rather than authoring generators or running the CLI. Covers the three-phase pipeline, the host/Worker boundary, cross-generator coordination, the manifest, the attribution / gen-maps (provenance) subsystem, the package graph, the Deno and JSR platform, and the design decisions that make Skmtc behave unlike a typical codegen tool. Use this skill when the user asks "what is Skmtc", "how does the Skmtc engine work", "explain the Skmtc architecture", or is building platform infrastructure around Skmtc — a hosted generate API, a schema or generator registry, tracing or provenance tooling, a web app or SaaS that wraps the engine, or platform-level CI integration. This skill is the system mental model. It does NOT cover authoring generators (→ skmtc-generator), running CLI commands (→ skmtc-cli), or diagnosing broken runs (→ skmtc-debug).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Workflow Phase 3 — Research and Solution Exploration. Surfaces 2–4 candidate solution approaches with concrete tradeoffs, grounded in current library docs (fetched through the provider named in `.claude/docs-provider.json`) — never in training-data recall. Output lives at `docs/research/<slug>.md`. Candidate ranking and the memo execute in main context; doc/source gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
증상을 재현하는 테스트나 명령을 준비하고 원인 조사, 정상 사례 비교, 가설 검증, 수정의 네 단계를 진행합니다. 근본 원인을 찾고 회귀 테스트로 결과를 확인합니다.