القائمة
Write a strategy doc before starting multi-step, multi-file, or unclear work. Use when asked to "plan out", "figure out the approach", or before any task needing more than one step.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.
Answer questions about how 'mi' works, write new tools, or modify the harness. Use for "how do you work", "write a tool", "add a tool", "create a tool", "extend yourself", "edit yourself", "what tools do you have", or any introspection/modification of the running agent.
Scan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows. Add missing facts, fix inaccurate ones, remove obsolete ones. Use when asked to discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match the code, or audit the fact sheet for accuracy.
Operate on @spec facts — implement them in code, then tag @implemented. Use when asked to implement facts, implement the spec, build from the fact sheet, make facts true, or work through unimplemented requirements.
Operate on @draft facts — collaboratively refine them into precise, actionable @spec facts. Resolve ambiguities, fill gaps, eliminate contradictions, and sharpen labels until every fact is ready to implement. Use when asked to refine facts, clarify the spec, review facts for quality, or "work on facts" with the user.
Manage .facts files — atomic, validatable truth statements about a project. Install, check, list, add, edit, remove, and lint facts via the CLI. ALWAYS read this skill when the user mentions facts in any capacity.
| name | plan |
| description | Write a strategy doc before starting multi-step, multi-file, or unclear work. Use when asked to "plan out", "figure out the approach", or before any task needing more than one step. |
Skip entirely for trivial one-step work (single edit, single command, single read).
Pick a short kebab-case <slug> for the task (e.g. auth-refactor, fix-retry-bug) and reuse the same slug for any execution-state list under /tmp/mi-<slug>/tasks.md so plan and tasks move together. If a plan already exists for the task, reuse the same slug rather than starting a new one (ls -d /tmp/mi-*/ 2>/dev/null to check).
Create the directory and write the plan file with one command:
mkdir -p /tmp/mi-<slug> && cat > /tmp/mi-<slug>/plan.md <<'EOF'
# Goal
...
# Approach
- ...
# Risks / Open Questions
- ...
EOF
Slug collisions: When multiple concurrent mi sessions may run simultaneously (e.g. parallel subagents each starting their own plan), append a timestamp or random suffix to avoid clobbering each other's files: auth-refactor-$(date +%s). Single-session sequential work does not need this.
Write /tmp/mi-<slug>/plan.md with three sections, nothing else:
# Goal
<one line: what "done" looks like>
# Approach
- <ordered bullets: the strategy, not every keystroke>
- <keep it to 3-6 bullets>
# Risks / Open Questions
- <unknowns, assumptions, things that could bite>
- <omit section if genuinely none>
This is strategy, not a task list. No checkboxes, no status fields — execution state belongs in /tmp/mi-<slug>/tasks.md, not here. To track step-by-step progress alongside this plan, call skill("tasks") and follow its body.
Re-read /tmp/mi-<slug>/plan.md before each major step. If reality diverges from the plan, revise the file before continuing — do not let it rot.
Revise (don't append) when direction changes. The doc should always reflect current intent, not history.