القائمة
Structured step-by-step deep analysis via the --deepthink flag, performed with Claude's native extended reasoning. Use for multi-step analysis or architecture decisions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
File a machine self-diagnostic report as a tagged GitHub issue. When a tool, daemon, hook, skill, or agent hangs, errors, returns garbage, or behaves wrong, open a `machine-report`-labeled issue on the machine plugin repo so every plugin user's reports funnel to the maintainer. Requires `gh` logged in. Write-side only — it logs, it does not fix. Trigger: "/report", "report a problem", "this tool is broken", "file a machine report", "log this hang/error/hiccup".
Consume the machine self-diagnostic backlog. Lists the open `machine-report` GitHub issues on the machine repo, ranks them by severity then age, fixes the single highest-priority one at its root cause, verifies green, then closes that issue. The act side of /report (which only writes). Machine-repo-only skill — not shipped to other installs. Trigger: "/resolve", "resolve a report", "triage the reports", "fix the top report", "work the reports backlog".
Second-AI review via the Codex CLI at the drill's single review point — the consolidated review of the finished diff, alongside the persona panel, before a landing is proposed. Advisory only: it returns notes and concerns for the driver and user to weigh, it never gates, blocks, merges, or edits. Skips cleanly when codex is not installed. Trigger via "/codex-review", "codex review", "second opinion from codex", or invoked by the drill skill.
The drill — the orchestrator's default driver mode. Runs grill-first: the drill and the user refine a request one question at a time until the user calls it a valid plan. From there the job runs autonomously — a plan subagent writes a markdown brief, a miner implements it on a git-fs branch inside the orchestrator's worktree, and the gate iterates until the build is green — with one consolidated advisory review (personas + codex) at the end. The drill surfaces only to land the work into main, plus on any blocker it cannot resolve. The live roster lives in the hub (claims + board), not on disk. Trigger via "/drill", "drill mode", "orchestrator mode", "background this", "spawn an agent for this", "drive this".
Promote crystallized brainstorm findings into board tickets. After a brainstorm (drill grill) settles one or more well-scoped features, this turns each into a card on the current cwd's board so the drill's plan step can iterate per ticket. The bridge between brainstorm and plan — it creates tickets, it does not plan or implement. Trigger: "/promote", "promote these", "promote to tickets", "make tickets", "turn findings into cards".
Run the single ongoing chat that resolves the open plan and implementation questions parallel agents raise. Plan/implement agents post questions to mesh and wait; the questioneer aggregates them into one prioritized queue, presents each to you for a decision, and writes the answer back so the waiting agent proceeds. It routes decisions — it does not plan, implement, or dispatch. Trigger: "/questioneer", "questioneer", "answer the questions", "resolve open questions", "what are the agents blocked on".
| name | workflow-thinking |
| description | Structured step-by-step deep analysis via the --deepthink flag, performed with Claude's native extended reasoning. Use for multi-step analysis or architecture decisions. |
| license | Apache-2.0 |
| compatibility | Designed for Claude Code |
| allowed-tools | Read, Grep, Glob |
| effort | high |
| user-invocable | false |
| metadata | {"version":"3.0.0","category":"workflow","status":"active","modularized":"false"} |
| progressive_disclosure | {"enabled":true,"level1_tokens":100,"level2_tokens":3000} |
| triggers | {"keywords":["deepthink","deep analysis","complex problem","architecture decision","technology selection","trade-off","breaking change"],"phases":["plan"],"agents":["manager-strategy","manager-spec"]} |
Structured, revisable step-by-step reasoning performed with Claude's native
extended reasoning. No external tool is required — --deepthink raises the rigor
and visibility of the reasoning, it does not call an MCP server.
| Mode | Trigger | Mechanism |
|---|---|---|
--deepthink | Explicit --deepthink flag | Native extended reasoning, written out as an explicit, numbered, revisable thought chain |
ultrathink | Keyword or auto-detection | Native extended reasoning at high effort |
Rules:
--deepthink → produce a visible, structured thought chain (numbered steps,
explicit revisions, explicit branches) before the conclusion.ultrathink → maximize native reasoning effort; structure is optional.ultrathink --deepthink means maximum effort AND a written,
structured chain.Produce a structured thought chain when --deepthink is present, or when the task
involves:
Write the reasoning as an explicit chain so the conclusion can be reviewed:
| Rationalization | Reality |
|---|---|
| "I can think through this in my head, it is simple" | Simple problems often hide second-order effects. A written chain forces you to enumerate them. |
| "The thinking steps are just internal, I do not need to record them" | Unrecorded reasoning cannot be reviewed. The chain is the evidence for the conclusion. |
| "I already know the answer, the framework is overhead" | Confirmation bias skips disconfirming evidence. The framework forces you to consider alternatives. |
| "Branching is overkill for this decision" | Decisions with more than one viable path benefit from explicit branch comparison, even briefly. |