3K skills · sorted by relevance
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.
Check the `.planning/` directory for missing files, invalid settings, inconsistent state, and orphaned plans. Report issues to address, optionally request repairs, or check context usage—the share of the session’s text capacity already used.
Create a pull request branch from the current branch while excluding .planning/ commits. This keeps planning documents out of the review so reviewers can focus on the code changes.
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.
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.
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.
口腔种植 (含 单牙/多牙缺失种植 / 全口 All-on-X / 即刻种植 即刻负重 / 上颌窦提升 / 牙槽嵴骨增量 GBR / 软组织移植 / 数字化种植 (CBCT 设计 + 口扫 + 导板 + CAD-CAM 上部) / 种植体周炎防治 / 种植修复 (基台 + 冠 + 杆卡 + 覆盖义齿) — 不含 普通牙体牙髓 / 正畸 / 儿牙 / 口腔颌面外科肿瘤 / 隐形矫治商业) (implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.) Master OS — automated mastery of implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business. problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「种植牙」「种植」「口腔种植」「牙种植」「implant」
The English summary is being prepared. Showing the original description.
Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.
The English summary is being prepared. Showing the original description.
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.
Create and validate SRDF files that define how MoveIt2 plans robot motion. Check planning groups, named poses, end effectors, and collision exclusions against an existing URDF robot model, then review the model visually.
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
The English summary is being prepared. Showing the original description.
Film and video storyboarding with shot vocabulary, continuity rules, and panel layout. Covers shot types, camera angles, movement, 180-degree rule, and annotation format. Use for: video planning, film pre-production, ad storyboards, music video planning, animation. Triggers: storyboard, storyboarding, shot list, film planning, video planning, pre production, shot composition, camera angles, scene planning, visual script, animatic, storyboard panels, video storyboard
The English summary is being prepared. Showing the original description.
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining `04-prd.md` into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different decision at step 5/8. Phase 0 also defines compressed intake, the path a user's explicit "just build it" choice takes on full-stack-app, pwa-app, authored, and copywriting cores: one batched round of questions in place of the shelf, writing a thinned archive at the same paths so Phase 1 (or, on copywriting, that core's own mining step), `ux-planner`, and the Re-entry pass all keep their documented source. Also use for the Re-entry pass, which mines new scope into additional intents without re-running the shelf, on any core with a module axis to add an intent to (full-stack-app, pwa-app, authored) — landing-page has none, so its own new-scope path runs through `hedgehog-landing-loop`'s Correction Protocol instead. Invoked by the `planner` agent, which decides the path; don't run standalone. landing-page runs this skill's Phase 0 on first run, then mines the same archive through `hedgehog-landing-loop`'s own planning-intake section, that core's counterpart to this skill's Phase 1. copywriting runs this skill's Phase 0 the same way (full or compressed), then mines the same archive through `hedgehog-copywriting-loop`'s own planning-intake section into a what/audience/register brief — no module axis, so its own new-scope path runs through that loop's Correction Protocol rather than the Re-entry pass below. An authored core runs this skill's Phase 0, then `hedgehog-core-design`, then this skill's Phase 1 mining against the designed layer sequence. A brownfield adoption (`hedgehog-adopt`) never runs this skill's shelf at all — the drivers BMAD elicits are already settled facts of a repo that already exists.
The English summary is being prepared. Showing the original description.
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
The English summary is being prepared. Showing the original description.
Plan inventory for retailers with multiple stores by choosing demand forecasts, calculating stock buffers and replenishment quantities, and assessing promotions. Account for demand drops after promotions, supplier lead times, and seasonal markdown timing.
Set up and use gstack in Capy or Claude Code for planning, code review, debugging, and release work. It checks the local environment, handles installation or repairs when needed, and selects the workflow instructions for the task.
Have agents with different roles challenge a proposed approach, exposing weak assumptions, missed interactions, and unnecessary complexity. Surviving findings go to a dedicated planning agent, which produces sequenced tasks with explicit success criteria.
Inspect CPU, memory, disk, and accelerator information alongside container and scheduler limits. Produce a JSON snapshot with identifying details removed and conservative worker and memory estimates for planning local workloads, without running stress tests.
Plan complex enterprise sales by mapping stakeholders, checking qualification with MEDDICC, a framework for assessing deals, and building shared action plans. Review buyer alignment, purchasing steps, and customer participation to identify stalled opportunities and next actions.
Turn large product requirements into user stories with acceptance criteria, effort estimates, and priorities. The toolkit supports backlog management, sprint planning based on team capacity, and tracking how much work the team completes over time.
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.
Organize multi-step agent tasks with persistent Markdown files for plans, findings, and progress. Records decisions, errors, and test results, then reloads the selected task's planning files to resume work after an interruption.
Organize multi-step agent tasks with persistent Markdown files for plans, findings, and progress. Records decisions, errors, and test results, then reloads the selected task's planning files to resume work after an interruption.
Investigate failed or stuck GSD workflows using Git history, planning documents, and file state. Produce a structured diagnostic report with evidence, detected anomalies, and recommendations to help identify causes and decide corrective actions.