executing-plans
チェックポイント付き実装計画の実行
또한 다음에서 사용할 수 있습니다: CodingCossack,davila7,Doyajin174,DYAI2025,Cycleaddict,ZhanlinCui,obra,sickn33,DMJGilbert
大規模な実装計画を構造化せずに実行すると、エラーが発生する可能性があります。このスキルは、計画を検証済みバッチに分割し、人間によるレビューチェックポイントを設けます。
스킬 ZIP 다운로드
Claude에서 업로드
설정 → 기능 → 스킬 → 스킬 업로드로 이동
토글을 켜고 사용 시작
테스트해 보기
"executing-plans" 사용 중입니다. ユーザー認証計画をバッチで実行
예상 결과:
- Loaded plan from auth-plan.md
- Reviewed plan - no concerns identified
- Created TodoWrite with 12 tasks
- Executed batch 1 (tasks 1-3): Implemented user model, created auth routes, added password hashing
- All verifications passed
- Ready for feedback before continuing to batch 2
"executing-plans" 사용 중입니다. データベース移行計画の処理
예상 결과:
- Loaded migration-plan.md
- Identified concern: backup strategy not specified
- Asked for clarification before proceeding
- Partner confirmed backup approach
- Created TodoWrite with migration tasks
- Proceeding with first batch after confirmation
"executing-plans" 사용 중입니다. チームコードレビュー後の続行
예상 결과:
- Team reviewed batch 1 implementation
- Feedback incorporated: 2 small changes made
- Executed batch 2 (tasks 4-6): Added API endpoints, configured rate limiting
- Tests passing for all new code
- Ready for review before batch 3
보안 감사
안전Pure prompt-based skill containing only markdown guidance documentation. No executable code, no file system access, no network calls, and no external command execution. All 8 static findings are false positives triggered by natural language in metadata fields describing standard development practices.
위험 요인
🌐 네트워크 접근 (1)
품질 점수
만들 수 있는 것
機能ロードマップの実行
コードレビューチェックポイントを組み込んだアーキテクチャ計画に従って機能を実装
マイルストーン提供の追跡
品質管理のための検証チェックポイント付きで大規模な成果物をバッチに分割
複雑なリリースの調整
各変更バッチ間でチームレビューを行いながら段階的なロールアウトを実行
이 프롬프트를 사용해 보세요
I'm using the executing-plans skill. Read the plan file at [path] and review it critically. Raise any concerns before proceeding. If no concerns, create TodoWrite and execute the first batch of 3 tasks.
I'm using the executing-plans skill. Based on the feedback provided, execute the next batch of 3 tasks from the plan. Follow each step exactly and run verifications.
I'm using the executing-plans skill. I've hit a blocker: [describe blocker]. Stop execution and ask for clarification rather than guessing the solution.
I'm using the executing-plans skill. All tasks are complete and verified. Now I'm using the finishing-a-development-branch skill to complete this work properly.
모범 사례
- 潜在的な問題を早期に発見するため、開始前に必ず計画を批判的にレビュー
- レビュアーが実装品質を評価できるよう、検証出力を明確に報告
- 推測するのではなく、ブロッカーに遭遇したら停止して説明を求める
피하기
- 進捗を速めるために検証をスキップ
- 指示が不明確な場合に解決策を推測
- 人間のフィードバックを待たずにバッチを超えて続行