Loading...
Loading...
Found 144 Skills
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.
Decompose work into well-sized, well-ordered implementation units and plan each one thoroughly. Use when the user asks to "plan this implementation", "break this into steps", "help me plan the work", "decompose this into tasks", "create an implementation plan", "how should I break down this project", or "size this work".
[Planning] Intelligent plan creation with prompt enhancement
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
Guided Shape Up workflow for taking projects from idea to working software. Orchestrates the /shaping and /breadboarding skills through a structured process: Frame, Shape, Breadboard, Slice, Build. Works for both greenfield (0-1) and existing projects. Use when: starting a new project or feature, planning a significant change to an existing codebase, user says "shape this", "let's shape", "shape up", or wants to go from idea to implementation with structured problem/solution separation. Proactively guides each phase and suggests next steps.
Transform feature descriptions into well-structured project plans following conventions
Use this before touching code when you have a requirement for a specification or multi-step task
Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.
Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Structured spec-driven workflow for planning and executing software projects with GitHub Copilot CLI.
This skill should be used when the user asks to "create an implementation plan", "plan a feature", "create detailed plan", "analyze requirements", or needs comprehensive project planning with requirements gathering and architectural analysis.
Use when you have a spec or requirements for a multi-step task, before writing implementation code. Helps break down complex features into bite-sized, verifiable tasks.