Menú
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Runs the Daneel GitHub admin CLI for labels, milestones, project board sync, issues, pull requests, releases, and review threads against the GitHub REST and GraphQL APIs. Use when the user or workflow needs GitHub repository or project maintenance, creating or updating PRs and issues (including bodies from files), syncing labels or milestones, posting verification comments, or any task matching the commands in this skill's reference.
Updates project tracking whenever a task transitions lifecycle state (started, blocked, ready-for-merge, done). Receives task context from the calling workflow, resolves the associated work item if one exists, then updates its status and posts a comment. Exits gracefully when no work item is found. Depends on the github-admin skill for GitHub operations.
Use proactively at the end of each implementation slice when project workflow requires it, or when a user asks to refactor, simplify, clean up, or restructure code while preserving behavior. Do not wait for an explicit user request if the workflow already mandates a post-implementation pass (features and bug fixes). Applies Martin Fowler style refactoring discipline and points to one reference file per refactoring from the official catalog.
Use when executing implementation plans with independent tasks in the current session; requires a refactoring skill pass at the end of each implementation slice (features and bug fixes) before the next review gate
Use when implementing any feature or bugfix, before writing implementation code
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs or MRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
| name | executing-plans |
| description | Use when you have a written implementation plan to execute in a separate session with review checkpoints |
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Note: Tell your human partner that this workflow works much better with access to subagents. If subagents are available, use subagent-driven-development instead of this skill.
Before touching any code, check whether skills/project-management/SKILL.md exists.
If it does, collect whatever task context is available from the plan and the current workspace.
Spawn a subagent with the available context and instruct it to read and follow skills/project-management/SKILL.md with event started:
Event: started
Task: <task-id-or-name-from-plan>
Branch: <current-branch-name>
The subagent is responsible for finding any associated work item and updating its status. Omit fields that are not yet known — the skill handles missing context gracefully. If the skill file is absent, skip this step entirely.
For each task:
refactoring skill on all files you changed for this task (features and bug fixes), then rerun the plan's fast checks. Do this proactively—do not wait for the user to say "refactor." Ad-hoc tidying while coding does not count.After all tasks complete and verified:
finishing-a-development-branchAfter the PR is opened, check whether skills/project-management/SKILL.md exists.
If it does, collect whatever context is available from the completed work.
Compose a brief implementation summary covering what changed, how it was tested, and any known limitations or follow-up items.
Spawn a subagent with the available context and instruct it to read and follow skills/project-management/SKILL.md with event ready-for-merge:
Event: ready-for-merge
Task: <task-id-or-name-from-plan>
Branch: <branch-name>
PR: <pr-number-if-known>
Summary: <IMPLEMENTATION_SUMMARY>
The subagent is responsible for finding any associated work item, updating its status, and posting the summary. Omit fields that are not yet known — the skill handles missing context gracefully. If the skill file is absent, skip this step entirely.
STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
Required workflow skills and practices:
using-git-worktrees - REQUIRED: Set up an isolated workspace before startingwriting-plans - Creates the plan this skill executesfinishing-a-development-branch - Complete development after all tasksproject-management - Optional: invoked at start (Step 2) and completion (Step 5) with task context