بنقرة واحدة
tr-behaviour
Define a UseCase (observable system behaviour) under an intent or another behaviour
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Define a UseCase (observable system behaviour) under an intent or another behaviour
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Assist when a developer cannot confidently answer a domain question during a skill session — scan the project for evidence, apply domain knowledge, and propose a concrete answer with reasoning and alternatives
Collaborative requirement exploration — think through a vague idea before speccing it; asks one focused question at a time and hands off to the right skill when ready
Run a comprehensive review of an entire subtree — an intent and all its descendants, or the entire `taproot/` root
Stress-test a single Taproot artifact — an `intent.md`, `usecase.md`, or `impl.md` — by challenging it from multiple angles
Capture ideas, findings, and deferred work mid-session with a single command — without interrupting current flow
Read a taproot hierarchy document section by section in the terminal — without opening an external editor
| name | tr-behaviour |
| description | Define a UseCase (observable system behaviour) under an intent or another behaviour |
Load and follow the full skill definition at taproot/agent/skills/behaviour.md in the current workspace.
Follow every step in the skill's ## Steps section precisely and in order. Use the cli: value from taproot/settings.yaml for all taproot CLI commands (default: taproot).