القائمة
Use only when the user explicitly asks Gambit to route a concrete software task and has not already named a public workflow owner.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/joshsymonds/gambit --skill using-gambitيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | using-gambit |
| description | Use only when the user explicitly asks Gambit to route a concrete software task and has not already named a public workflow owner. |
Route only an explicit request for Gambit workflow selection. Do not activate this router automatically.
Choose exactly one owner; first match wins:
executing-plans — an active approved epic.debugging — a concrete bug or unexpected behavior.review — an explicit independent review.finishing-branch — integration, merge, or pull-request work.writing-skills — skill authoring or modification.brainstorming — new or uncontracted design and planning.Once selected, stop routing and follow that owner.
test-driven-development (TDD), verification, refactoring, testing-quality, and task-refinement are internal mechanics, not workflow owners. Parallelism is an implementation detail inside the selected owner.
Turns a rough idea into an approved epic contract with immutable requirements, anti-patterns, and a first wave of executable tasks.
Turns a rough idea into an approved epic contract with immutable requirements, anti-patterns, and a first wave of executable tasks.
Executes an approved epic one wave at a time, dispatching a worker per task and stopping at a checkpoint after each wave. Use when an approved epic contract and native wave plan exist in the current root session, when resuming work after a previous checkpoint, or when iteratively building a feature and execution learnings require a later wave. User phrases like "continue the plan", "next wave", "resume where we left off", "pick up the epic".