400건 · 관련도순
Use when urgent work surfaces mid-milestone and must land between two planned phases without renumbering the roadmap. Inserts it as a decimal phase such as 72.1 after the phase the user names.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs, data flows, and a build sequence. Use this skill when the user asks for an architecture design, an implementation plan for a non-trivial feature, or when dispatched as a sub-task during feature-dev architecture phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill for the architecture phases of an MBSE workflow in MATLAB, when writing idempotent buildXxx.m scripts that produce a three-layer RFLPV architecture (Functional, Logical, Physical) with interface dictionaries, stereotype profiles, allocation sets, and requirements Implement links. Trigger for defining stereotype properties, functional-to-logical / logical-to-physical allocation, mapping requirements to components via slreq Implement links, or running quantitative roll-up analysis on the architecture. Do NOT trigger for ad-hoc structural edits to an already-built System Composer model (adding one component, rewiring a port) — use `building-simulink-models` with `model_edit` for that. Works alongside the `system-composer` skill for detailed SC API patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research how to implement a phase (standalone - usually use /gsd:plan-phase instead)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks for a literature review, academic deep dive, research report, state-of-the-art survey, topic scoping, comparative analysis of methods/papers, grant background, or any request that needs multi-source scholarly evidence with citations. Also trigger proactively when a user question clearly requires academic grounding (e.g. "what's known about X", "compare approach A vs B in the literature", "summarize the field of Y"). Runs an 8-phase (Phase 0..7), script-driven research workflow across 7 federated sources (OpenAlex, arXiv, Crossref, PubMed, DBLP, bioRxiv, Exa) with optional Semantic Scholar / Brave MCP enrichment, with deduplication, transparent ranking, dual-backend citation chasing (OpenAlex + Semantic Scholar), self-critique, and structured report output with verifiable citations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The Mileva Method (CRISP) — Phase 3: Investigate. Process mapping for existing or greenfield processes, user journey mapping, UX discovery, project goals, system architecture (integration map + data flow). Use after outcome alignment. Triggers on "investigate", "phase 3", "map the process", "process mapping", "user journey", "as-is process", or after Phase R exit checklist is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 2 of 5 — collaborative system design plus change-footprint mapping; outputs an ARCH doc for generate-tasks. Use only when the user asks to run Phase 2, plan the architecture, or design the solution — never trigger automatically from a design question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS-<N>-<slug>.md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 4 of 5 — implements tasks from TASKS-<N>-<slug>.md (with ARCH-<N>-<slug>.md as architecture-only context) using mode-appropriate verification (tdd, test-after, ui, checklist); pass 'auto' to run without stepping. Use only when the user asks to run Phase 4 or implement tasks from an ARCH doc — never trigger automatically from a coding request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Semantic code search using Phase 1 vector embeddings and Phase 2 hybrid search.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
研究编辑（季要纲 Ji）。由 research-chief-editor 主理人调度，分析 Phase 1 初步调研摘要，提取核心观点，确定报告标题，规划章节大纲（3-5 章），管理章节不重叠、逻辑递进。也负责根据用户反馈修改大纲。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 2 规划任务时激活。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
报告发布员（傅梓铭 Fu）。由 research-chief-editor 主理人在 Phase 5 调度，整合所有部分（标题/日期/目录/引言/章节正文/结论/参考文献/审稿警告）输出最终 Markdown 研究报告。执行终校：格式统一、章节编号连续、分隔线、超链接检查、参考文献去重、术语一致性检查。不修改研究内容本身。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当 Phase 4 完成后，主理人下发 Phase 5 发布任务时激活。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/<YYYY-MM-DD>/<slug>/. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
긴 Claude Code 작업에서 대화와 읽어 들인 정보를 압축할 시점을 제안합니다. 문맥 크기와 도구 호출 횟수를 참고해 단계 전환 시 중요한 계획을 보존하도록 돕습니다.
아직 없는 기능을 조사와 계획부터 테스트 우선 구현, 검토, 커밋까지 진행합니다. 단계별로 ECC 에이전트에 작업을 나누고 계획 승인과 커밋 전 확인을 거칩니다.
Create diagrams that explain systems, workflows, and data relationships using a consistent brand style. The skill guides diagram selection, layout, and readability, with HTML, SVG, and PNG output and support for importing existing diagram formats.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan systems across AWS, Azure, GCP, and OCI by comparing services and architecture patterns. Helps guide service selection, disaster recovery, migration planning, and cost decisions while considering ways to reduce dependence on a single provider.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn an urban IoT idea, such as connected lighting or traffic monitoring, into an Azure architecture and delivery plan. Define device connections, data flows, security, operations, cost controls, and phased implementation tasks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.