بنقرة واحدة
executing-plans
Use when you have a written implementation plan to execute, with review checkpoints between tasks
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when you have a written implementation plan to execute, with review checkpoints between tasks
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | executing-plans |
| description | Use when you have a written implementation plan to execute, with review checkpoints between tasks |
Load plan, review critically, execute tasks in batches, report for review between batches.
Core principle: Batch execution with checkpoints. Review after every batch.
For each task:
After each task (or batch):
Stage 1 — Spec Compliance:
Stage 2 — Code Quality:
When batch complete:
After all tasks verified:
finishing-work skill to handle merge/PR/cleanupStop executing immediately when:
Ask for clarification rather than guessing.
For independent tasks, dispatch subagents: