Loading...
Loading...
Found 117 Skills
Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
ISD 연구계획서 통합 입력 템플릿 - Orchestrator용 입력 양식
Generate a phase-based task breakdown in tasks.md from spec.md and plan.md
This skill must be used before any creative work—creating features, building components, adding functionality, or modifying behavior. Explore user intentions, requirements, and designs before implementation.
Check project progress, show context, and route to next action (execute or plan). Triggers include "progress".
Generate multiple viable solution options after research is complete, before converging on a single approach. Use when you need to explore the solution space, ask clarifying questions, and produce 3-5 distinct options to consider.
Provide development estimates for tasks, features, or projects. Use when user asks for time estimates, effort assessment, or project sizing.
Structured Autonomy Planning Prompt
Creates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use when planning features, documenting system design, or creating architecture decision records.
Define a new task with structured requirements before implementation. Use when the user says "define task", "new task", "spec this", or wants to formalize a feature/bug/refactor before planning.
Structured spec-driven workflow for planning and executing software projects with GitHub Copilot CLI.