القائمة
Use when opening or rewriting a work item on any git-based SCM. Source-control agnostic; GitHub, GitLab, and Azure Boards are adapters only.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/ShaftHQ/SHAFT_ENGINE --skill work-itemيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Load the canonical ChaosEngine policy and this repository's selected project profile before every task.
Optional local coding loop as a mechanical or default delegate. Use when the decider model wants a cheap local coder and a hardware probe says the host can run one.
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
عرض SKILL.md
| name | work-item |
| description | Use when opening or rewriting a work item on any git-based SCM. Source-control agnostic; GitHub, GitLab, and Azure Boards are adapters only. |
| license | MIT |
Load this skill when the deliverable is open or rewrite a work item. Do not
vendor Spec Kit or create .specify/. Keep GitHub PR delivery on
work-github-playbook.md.
Contract and adapters: work-item.md.
One work item owns one actionable problem. Trackers list children; they do not absorb them. Preserve existing acceptance when rewriting.
Every body must include:
Keep adopter template headings (for example bug or feature fields) so existing validators still match.
When rewriting an existing item for Spec Kit hygiene, specialize User Story,
FR-*, and SC-* from that issue's own acceptance (see
scripts.agents.issue_filing.rewrite_body_spec_kit). Keep the shared heading
checklist; never paste the generic stamp Deliver the stated acceptance onto
unrelated tickets. Trackers may keep a campaign-level story.
Exactly one primary type, exactly one lifecycle, at least one subsystem or module. Missing taxonomy fails closed with a named reason. Ready needs a proof plan; blocked needs at least one https dependency URL.
Detect the live CLI from the adopter environment. Do not assume GitHub. Command maps live in the adapters reference named from the contract. Live create/edit remains whatever CLI the adopter already runs; dry-run and fake runners prove the other maps.