Skip to main content

compose-execute

Use when you have a written implementation plan to execute in a separate session with review checkpoints

소스 정보

저장소
XiaomiMiMo/MiMo-Code
최근 소스 활동
2026년 9월 30일 08:41
감지된 SKILL.md 언어
영어
스타
13,623
포크
1,428

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
compose:execute
description
Use when you have a written implementation plan to execute in a separate session with review checkpoints
# Executing Plans ## Overview Load plan, review critically, execute all tasks, report when complete. **Announce at start:** "I'm using the compose:execute skill to implement this plan." **Note:** Compose works much better with access to subagents. If subagents are available, use compose:subagent instead of this skill for significantly higher quality. ## The Process ### Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create a task per plan task with the `task` tool and proceed ### Step 2: Execute Tasks For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed ### Step 3: Complete Development After all tasks complete and verified: - Use compose:report to write the final report (summarizes what was built in human-readable form) - Report skill will transition to compose:merge on completion ## When to Stop and Ask for Help **STOP executing immediately when:** - Hit a blocker (missing dependency, test fails, instruction unclear) - Plan has critical gaps preventing starting - You don't understand an instruction - Verification fails repeatedly **Use `compose:ask` to present the blocker and options rather than describing it in free text.** If no user is available, resolve the blocker with your best judgment and continue. ## When to Revisit Earlier Steps **Return to Review (Step 1) when:** - Partner updates the plan based on your feedback - Fundamental approach needs rethinking **Don't force through blockers** - stop and ask. ## Remember - Review plan critically first - Follow plan steps exactly - Don't skip verifications - Reference skills when plan says to - Stop when blocked, don't guess - Never start implementation on main/master branch without explicit user consent ## Integration **Required workflow skills:** - **compose:worktree** - Ensures isolated workspace (creates one or verifies existing) - **compose:plan** - Creates the plan this skill executes - **compose:report** - Write final report after all tasks complete - **compose:merge** - Complete development (invoked by report skill)
GitHub에서 보기