القائمة
Use after implementation to analyze drift, update documentation, evolve evaluation, and close a completed epic.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/peel/fiddle --skill deliverيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Use when starting or resuming a full development lifecycle for a feature or explicit epic.
Use when you have a spec or requirements for a multi-step task, before touching code.
Use when working with the Fiddle portable skills library, choosing lifecycle skills, or adapting Fiddle instructions across Claude, Codex, and Pi harnesses.
| name | deliver |
| description | Use after implementation to analyze drift, update documentation, evolve evaluation, and close a completed epic. |
Invoke as fiddle:deliver --epic <id>.
Analyze design-versus-implementation drift, update documentation, evolve the evaluator, and close the epic.
--epic <id> is required. Read providers.phases.deliver, provider commands and flags, timeouts, product artifacts, spot-check, and aging settings from orchestrate configuration. When orchestrate invokes delivery, use its canonical main-worktree Beans path for every Beans command. Internal subagent models resolve through scripts/resolve-subagent-model.sh: models.roles.<role> overrides models.phases.<phase>, and default inherits the current session model; this is independent of provider CLI configuration.
Run beans show <epic-id> --json. If any child remains todo or in-progress, warn and ask whether to continue.
Follow drift analysis, documentation, and product artifacts. Each confirmation point there is required before moving on.
Follow evaluator evolution. Blind spot-checking precedes scorecard disclosure, and every calibration, threshold, aging, and close decision requiring confirmation remains attended.
Follow milestone handoff. Seed-aware epics must publish a valid handoff before closing; legacy epics skip this step.
After the user confirms evaluator evolution, run beans update <epic-id> --status completed. Delivery never runs repository-wide bean maintenance implicitly; when explicitly requested, beans archive remains a direct maintenance command.