execute-plan
Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-12
- Stars
- ★ 28
- Forks
- 3
01 前言 Front Matter
- name
- execute-plan
- description
- Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
03 SKILL.md 正文
Execute Plan
Execute structured task plans with automatic status tracking and progress updates.
Commitment to Completion
When a plan is provided, all tasks in the plan must be completed. Before starting execution, recite:
"I will execute this plan to completion. All the 20 tasks will be addressed and marked as DONE."
Execution Steps
STEP 1: Recite the commitment to complete all tasks in the plan.
STEP 2: Read the entire plan file to identify pending tasks based on task_status.
STEP 3: Announce the next pending task and update its status to IN_PROGRESS in the plan file.
STEP 4: Execute all actions required to complete the task and mark the task status to DONE in the plan file.
STEP 5: Repeat from Step 3 until all tasks are marked as DONE.
STEP 6: Re-read the plan file to verify all tasks are completed before announcing completion.
Task Status Format
Use these status indicators in the plan file:
[ ]: PENDING
[~]: IN_PROGRESS
[x]: DONE
[!]: FAILED
Example Usage
- User provides: "Execute plan at plans/2025-11-23-refactor-auth-v1.md"
- Recite commitment: "I will execute this plan to completion..."
- Read the plan file
- Find first
[ ](PENDING) task - Update to
[~](IN_PROGRESS) - Execute the task
- Update to
[x](DONE) - Move to next PENDING task
- Repeat until all tasks appear DONE
- Re-read plan file to verify completion
- Announce completion
04 同仓库更多 Skills
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
test-skill
A test skill with resources
minimal-skill
A minimal skill with no resources
write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").
test-reasoning
Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify reasoning config fields, or check that ReasoningConfig maps correctly to provider-specific JSON (OpenRouter, Anthropic, GitHub Copilot, Codex).