'phase arc' 검색 결과

Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기능 추가와 버그 수정 등 개발 작업을 변경 규모에 따라 조사·계획·테스트·검토 단계로 배분합니다. 관련 스킬이 공유하는 절차에 계획 승인과 커밋 전 확인을 포함합니다.

• 기능 추가와 버그 수정 절차를 통일합니다
• 변경 규모에 맞는 단계를 선택합니다
• 설계 문서에서 MVP 개발을 진행합니다

Turn a Zoom integration idea into a practical implementation plan. Identify the required products and APIs, authentication and access permissions, delivery phases, and risks, then define a small first deliverable to test the proposed architecture.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a Zoom integration idea into a build plan
• Clarifying authentication and access permissions
• Planning delivery from prototype to launch

Plan a prospective clinical study by ranking endpoints, estimating participant numbers and statistical power, and assessing feasibility. Outputs include assumptions and named reviewers, providing material for expert review before a protocol is finalized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing primary and secondary study endpoints
• Estimating sample size with dropout allowance
• Assessing feasibility before a study review

Turn a founder’s business vision into linked Markdown files through a phased interview covering strategy, finance, sales, operations, and governance. Build a company knowledge bundle that people and AI agents can read, with progress tracking and decision history.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Structure a new business through phased interviews
• Build a company knowledge base for AI agents
• Document decisions and track planning progress

Plan smart contract audits using research from security organizations. Combine threat modeling, static code analysis, fuzzing that varies test inputs, and manual review, while using attack patterns and a four-phase roadmap to guide further learning.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a smart contract security audit
• Setting up Echidna or Medusa fuzzing
• Reviewing attack patterns and past audit findings

Clarify implementation choices before planning a development phase. The skill reviews existing project context and code, asks about unresolved decisions, and records the answers in a context file for research and planning agents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying unresolved specifications before planning
• Discussing only decisions that remain open
• Documenting implementation choices for other agents

Start a new development milestone for an existing project. The skill gathers goals, updates project documents, optionally researches new features, and creates scoped requirements and a phased roadmap for the next cycle of work.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the next release of an existing project
• Defining requirements for new features
• Updating goals and a phased roadmap

Explore a development idea through probing questions before committing to a plan. The skill can initiate research when needed and route the resulting ideas into GSD notes, tasks, research questions, requirements, or development phases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Think through a development idea before planning
• Explore options for an authentication strategy
• Turn an open question into a research topic

Set up a new project by gathering context, optionally researching the domain, defining requirements, and building a roadmap. It creates planning files that record the project’s background, workflow preferences, phased structure, and ongoing state.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify a new project idea through questions
• Define requirements and a phased roadmap
• Save project context and workflow preferences

Analyze a monolithic codebase before splitting it into modules or services. The skill inventories components, examines duplication, hierarchy, and dependencies, then proposes groupings aligned with business domains, with optional checks against business terminology and boundaries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing component sizes before splitting a monolith
• Finding duplicated business logic across modules
• Reviewing module hierarchy and dependencies

Turn a feature request into an implementation plan before coding. Five planning phases cover requirements, interface design, technical choices, research, and metrics, producing ordered tasks, a test plan, and records explaining major decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a feature that touches several files
• Resolving unclear requirements before implementation
• Recording architecture and interface decisions

Organize complex tasks using persistent Markdown files for plans, research notes, and final deliverables. Track completed phases, decisions, and errors, and revisit the plan before major actions to keep work aligned with its goal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a task with multiple stages
• Organizing research findings and sources
• Recording progress, decisions, and errors

Choose quantitative or qualitative methods that fit a research question and dataset. Compare alternatives, check assumptions, generate analysis code, interpret results, and examine sensitivity, meaning how conclusions change under different analytical choices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing methods for a research question
• Generating analysis code in R or Python
• Planning theme identification in interview data

Comet Phase 5: Archive. Invoke with /comet-archive. Merge delta specs into main specs with OpenSpec semantics, archive change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, domain-driven-design - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, REMOVE-TECHNICAL-DEBT-PLAN.md) so the journey resumes across sessions. Use when the user wants to tame a legacy codebase, pay down technical debt safely, avoid a big-bang rewrite, or says 'we are afraid to touch this code'. For a fresh vibe-coded prototype, improve-code-quality; for greenfield structure, design-code-architecture; for a product-and-UX pass, improve-app; to optimize a working codebase for speed, architecture-optimization. For one framework in isolation, invoke that skill directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a phase has unresolved decisions before planning and no CONTEXT.md exists. Asks adaptive questions on the phase's gray areas and writes {phase_num}-CONTEXT.md with locked decisions; --auto, --chain, --power change the questioning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a planned but unstarted phase should come off the roadmap. Removes the phase, renumbers the phases after it into a clean sequence, and commits the change as the historical record.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.