'phase arc' 검색 결과

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.

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

• Planning a system across multiple cloud providers
• Designing disaster recovery in another cloud
• Comparing cloud services for a workload

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.

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

• Plan an Azure IoT platform for city services
• Design data flows from devices to analytics and alerts
• Review security, operations, and cost requirements

Organize complex tasks with three Markdown files for plans, findings, and progress. Keep goals, decisions, errors, and test results available across sessions so the agent can review its position and continue work with a clear next step.

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

• Planning and tracking a task with multiple phases
• Saving findings during a research project
• Recording implementation progress and test results

Plan database, service, and infrastructure migrations with phased steps, compatibility checks, and rollback procedures for returning to the previous system. Define risks and validation checkpoints to guide transitions with minimal disruption to business operations.

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

• Planning a database schema migration
• Checking API changes for compatibility
• Preparing a phased cloud migration

Keep plans, research findings, and progress in Markdown files for complex agent work. Separate task plans and automatic planning reminders help the agent recover saved context, track decisions, and identify the next action.

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

• Resuming long research tasks
• Tracking phases and the next action
• Separating plans for concurrent tasks

Organize multi-step research and project work with Markdown files for plans, findings, and progress. Gemini hooks, automatic actions at session events, surface planning context so the agent can resume from saved records.

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

• Resuming research after a break
• Tracking project phases and decisions
• Recording errors and test results

Organize multi-step research and project work in Continue using Markdown files for plans, findings, and progress. When invoked, the skill reads saved planning context to support resuming work and reviewing earlier decisions.

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

• Resuming interrupted work in Continue
• Recording findings during research
• Tracking project phases and decisions

Keep plans, research findings, and progress in Markdown files for multi-step work in Kiro. Read saved project records when resuming a task to recover goals, decisions, and recent actions.

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

• Organizing findings during extended research
• Tracking a refactor across multiple phases
• Resuming work after a long break

Reviews deferred project tasks alongside their descriptions and supporting files, then lets users promote, keep, or remove each item. Promoted tasks join the active milestone with updated phase numbers and roadmap entries.

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

• Review deferred tasks and their supporting materials
• Move selected backlog items into the active milestone
• Remove outdated backlog items

Manage parallel tracks of milestone work with commands to create, list, switch, inspect, archive, and resume them. View each track’s phase status or a combined progress summary in a readable format.

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

• Create a separate workstream for a milestone
• Switch the active workstream
• Review phase status and progress across workstreams

Build a paid advertising plan around business goals and financial constraints. Define channels, campaigns, audiences, budgets, creative, tracking, and experiments, then organize the work into phases with owners, success measures, and conditions for stopping or reversing changes.

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

• Creating an advertising strategy around business goals
• Planning channel roles and budget allocation
• Defining launch phases, owners, and success measures

Plan a browser game's architecture before coding. Choose an engine, separate game rules from rendering, and define input, assets, menus, saves, debugging, and performance checks within a shared design.

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

• Choose an engine for a 2D or 3D browser game
• Separate game state from rendering responsibilities
• Plan input mappings and asset organization

Trace how AI tooling developed in a Git repository by identifying configuration file origins, monthly commit activity, major changes, and relevant releases. Produce a Markdown report that explains adoption phases and turning points using Git evidence.

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

• Finding when AI configuration files were first introduced
• Reviewing monthly activity around AI tooling changes
• Tracing major integrations and workflow changes

Keeps multi-step work organized with Markdown files for the plan, research notes, and final deliverable. Tracks completed phases, decisions, and errors so the agent can revisit goals and resume work with durable records.

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

• Tracking progress through a multi-step task
• Keeping research findings and sources on disk
• Resuming work after a pause

Analyze interviews, focus groups, and open-ended survey responses using Braun and Clarke's six-phase framework. Label meaningful passages, develop and review themes, and produce an academic Word report with an annotated map showing theme relationships.

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

• Identifying themes across interview transcripts
• Analyzing open-ended survey responses
• Choosing an approach before coding qualitative data

Research technical or business questions through multiple available AI providers, each assigned a different perspective. Combine usable results into a report covering findings, disagreements, evidence gaps, priorities, and recommended next steps.

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

• Compare libraries and technical approaches
• Research markets and competitor strategies
• Synthesize literature from multiple perspectives

Carry out approved technical plans in phases, checking success criteria and recording progress as work proceeds. Larger plans can use separate agents with saved handoff notes, while manual verification keeps users involved at phase boundaries.

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

• Implementing an approved technical plan
• Checking results at each implementation phase
• Resuming work from unfinished plan items

Turn a feature specification into a technical implementation plan. Organizes technology choices, research decisions, data models, and interface agreements into project files, while checking that the design follows the project's documented principles.

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

• Create a technical plan from a feature specification
• Resolve open questions about technology choices
• Document data models and external interfaces

Detect insecure JWT (JSON Web Token) implementations in a codebase using a two-phase approach: first map all JWT issuance and verification sites to understand the token lifecycle and signing configuration, then check each verification site for exploitable weaknesses such as algorithm confusion, missing signature verification, weak secrets, header injection, and missing claim validation. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/jwt-results.md. If no JWT usage is found in Phase 1, Phase 2 is skipped. Use when asked to find JWT, token forgery, or authentication bypass bugs.

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

Detect GraphQL injection vulnerabilities in a codebase using a three-phase approach: recon (confirm GraphQL usage and find unsafe operation document assembly sites), batched verify (trace user input to those sites in parallel subagents, up to 3 candidate sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/graphql-results.md. If no GraphQL technology is found in Phase 1, later phases are skipped. Use when asked to find GraphQL injection, unsafe GraphQL document construction, or operation string injection bugs.

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

Perform codebase analysis and architecture mapping as the first phase of a security assessment. Explores the tech stack, frameworks, entry points, data flows, and trust boundaries. Outputs sast/architecture.md. Run this before any vulnerability detection skill. Use when asked to analyze a codebase for security or when sast/architecture.md does not yet exist.

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

Use to re-verify the threat mitigations of a phase that already shipped, or when the user asks to audit SECURITY.md. Audits an existing SECURITY.md, runs from a PLAN.md threat model, or exits if the phase never ran.

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

Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase.

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

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.

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