'phases' 검색 결과

Manage development phases in ROADMAP.md with one command. Add work to a milestone, insert urgent work between existing phases, edit phase fields, or remove future phases and renumber those that follow.

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

• Add a phase to the current milestone
• Insert urgent work between existing phases
• Remove a future phase and renumber later phases

Run remaining GSD project phases through discussion, planning, and execution, while recording progress and phase documents. You can limit the phase range or keep decisions interactive; after all phases finish, the workflow audits and closes the milestone.

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

• Running all remaining milestone phases
• Executing a selected phase or range of phases
• Answering discussion questions before background execution

Audit acceptance tests, which check whether features meet user needs, and verification records across project phases. Compare outstanding items with the codebase, flag outdated documentation, and produce a prioritized plan for human testing.

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

• Finding outstanding acceptance tests across phases
• Collecting blocked items and checks needing human input
• Checking whether verification records match the code

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

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

Turn implementation plan phases into GitHub Issues with structured titles, descriptions, and labels. Check existing issues first, then create or update one issue per phase using feature or chore templates where available.

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

• Turning implementation plan phases into GitHub Issues
• Updating existing issues to reflect a plan
• Structuring feature and chore work with issue templates

Map intrusion evidence to the seven stages of the Lockheed Martin Cyber Kill Chain, a model of attack progression. Show where defenses worked or missed activity, and recommend prioritized controls that could interrupt attacks earlier.

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

• Mapping attack progression after an incident
• Finding detection gaps at each attack stage
• Planning layered defenses to stop attacks earlier

Manage project phases from one terminal with a status dashboard and suggested next actions. Discuss one phase while background agents plan or execute another, keeping work across a milestone visible in one place.

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

• Checking progress across project phases
• Discussing one phase while another runs
• Choosing the next task based on dependencies

Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.

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

• Checking completion criteria before archiving a milestone
• Reviewing coverage of milestone requirements
• Checking connections and user flows across phases

Design and test combat encounters in Three.js action games. Plan arenas, enemy roles, spawn timing, objectives, boss phases, and rewards, then check fairness and difficulty using repeatable starting conditions on desktop and mobile.

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

• Planning combat arenas and enemy combinations
• Tuning enemy waves and boss phases
• Checking attack warnings and recovery opportunities

Convert agreed scope into a structured matter plan — phases, workstreams, milestones, dependencies, owner assignments, and matter setup decisions. Use when planning a new matter, running a kickoff, building a workstream plan, structuring phases, setting up task codes, or producing a plan to drive status reporting. Trigger on: 'build a plan', 'matter plan', 'project plan', 'what are the phases', 'workstream plan', 'how do we sequence this', 'who owns what', 'task codes', 'matter setup', 'workstream plan', 'matter plan', 'rolling wave', 'plan the next phase', 'what comes first', 'kickoff agenda'.

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

Generate structured planning documentation for web projects with context-safe phases, verification criteria, and exit conditions. Creates IMPLEMENTATION_PHASES.md plus conditional docs (DATABASE_SCHEMA, API_ENDPOINTS, UI_COMPONENTS, CRITICAL_WORKFLOWS). Use when: starting new Cloudflare Workers/React projects, adding major features to existing apps, breaking large work into manageable phases, or need verified planning before coding begins.

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

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.

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

Interactive Domain-Driven Design modeling sessions based on DDD Distilled (Vaughn Vernon) and Domain Modeling Made Functional (Scott Wlaschin). Guides users through strategic and tactical design via 13 phases: discover, storming, contexts, mapping, aggregates, events, validate, glossary, workflows, types, simulate, publish, sync. Phase 13 (sync) reconciles divergences found by --analyze between the domain model and the implementation — judging whether the model or the code is authoritative, then planning and implementing the fix and re-aligning the model. Phases 9-11 take the conceptual model from phases 1-8 and produce workflow pipeline designs, compilable type definitions (TypeScript, Kotlin, Scala, Rust, C#, F#), workflow verification via type-level tests, and automatic UI field enumeration from the domain model. Phase 12 (publish) renders all docs/domain artifacts into one self-contained, cross-linked HTML site (separate files joined by a shared nav). Each phase is an interactive dialogue where AI acts as facilitator and domain expert challenger. Use when: "DDD", "ドメイン設計", "ドメインモデリング", "Event Storming", "Bounded Context", "集約設計", "ユビキタス言語", "コンテキストマップ", "ワークフロー設計", "パイプライン設計", "ステップ分割", "中間型", "型駆動フロー", "型駆動設計", "Domain Modeling Made Functional", "Railway Oriented Programming", "入力画面項目", "フォーム項目洗い出し", "UI 項目抽出", "HTMLにまとめる", "ドキュメントサイト化", "成果物を1つのHTMLに", "publish", "モデルと実装の差異", "差異解消", "実装との乖離", "モデルとコードを一致", "差異の実装計画", "sync", "複数フェーズを逐次実行", "フェーズをまとめて実行", "/ddd run", "サブコマンド一覧", "/ddd list", "/ddd", "ドメイン分析したい", "モデリングしたい", or any domain design / type modeling activity.

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

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.

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

Analyzes intrusion activity against the Lockheed Martin Cyber Kill Chain framework to identify which phases an adversary has completed, where defenses succeeded or failed, and what controls would have interrupted the attack at earlier phases. Use when conducting post-incident analysis, building prevention-focused security controls, or mapping detection gaps to kill chain phases. Activates for requests involving kill chain analysis, intrusion kill chain, attack phase mapping, or Lockheed Martin kill chain framework.

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

긴 Claude Code 작업에서 대화와 읽어 들인 정보를 압축할 시점을 제안합니다. 문맥 크기와 도구 호출 횟수를 참고해 단계 전환 시 중요한 계획을 보존하도록 돕습니다.

• 긴 대화가 문맥 한도에 가까워질 때
• 조사 내용을 정리하고 구현으로 넘어갈 때
• 디버깅 후 다른 작업으로 전환할 때

Turn a vague request into a precise specification through five phases and file it as a GitHub issue. Optionally start a Claude Code agent in a separate working directory to begin implementation.

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

• Turn a rough idea into an actionable specification
• Create a GitHub issue from a request
• Convert a request into a backlog item

Turn a feature brief into a one-page product requirements document in HTML. Organize the problem, goals, success measures, user needs, delivery phases, and open questions so the team can review the proposed feature and its scope.

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

• Draft a requirements document for a new feature
• Align a team on goals and excluded work
• Define success measures and measurement methods

Turn a feature idea into a structured specification before coding. Review requirements, system connections, constraints, and failure scenarios, define testable acceptance criteria, and save the specification in memory for later development phases.

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

• Defining requirements before building a new feature
• Writing testable acceptance criteria
• Documenting constraints and failure scenarios

Calculate equilibrium phases, their molar fractions, and compositions from a local thermodynamic database using pycalphad. Compare temperatures, check material balance and sampling stability, and export results with recorded conditions and database identifiers.

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

• Calculate equilibrium phase fractions for an alloy composition
• Compare stable phases across specified temperatures
• Check material balance and sampling stability

View project statistics covering phase progress, plan execution, completed requirements, Git history, and the project timeline. Use the combined view to check how development is progressing across plans, requirements, and recorded changes.

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

• Check progress across project phases
• Review plan execution and requirement completion
• Review Git history statistics and the project timeline

Organize accumulated planning folders by archiving phase directories from completed milestones. Review a preview of the proposed moves, then confirm to place those directories in a versioned milestone archive.

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

• Organize phase folders after a milestone is completed
• Review proposed archive moves before confirming
• Keep completed phase records in versioned archives

Turn existing decision records, product requirements, specifications, and other documents into GSD planning files. Create a new planning setup or add requirements and phases to an existing one, while identifying conflicts and blocking writes when contradictions remain unresolved.

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

• Build planning files from existing project documents
• Add documented requirements and phases to an existing plan
• Identify conflicting statements across planning documents

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