Asking User Questions
JetBrains/thinkrail/packages/pi-thinkrail-workflow/skills/asking-user-questionsdevopsResmi
Resmi Sağlayıcı Skill'iView repo
Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
Dosyalar1 dosya
SKILL.md113 satır
Loading editor…
Kurulum
ÖnerilenTek komut — ajanınız otomatik olarak devreye alır.
Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.
veya
Manuel Kurulum
Daha fazla adımDosyayı indirin ve ajanınızın sistem istemine yapıştırın.
Skill detayları
Versiyonv1.0.0
YazarJetBrains
Kategoridevops
Skill IDJetBrains/thinkrail/packages/pi-thinkrail-workflow/skills/asking-user-questions
İlgili skill'ler
BrainstormingUse before implementation when a request requires choosing product scope, user-visible behavior, or architecture. Not for fully specified fixes, mechanical refactors, documentation, or configuration-only changes.Choosing A WorkflowUse at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or localized fully specified work.Importing A CodebaseUse when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.Setting Up A ProjectUse when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.Shipping A PrUse when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.Spec GraphUse when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or architecture decision.