Skill 详情

consultant

Client discovery and plan-handoff process, but focused on builder-project intake.

匹配类型可能匹配已针对 咨询 审核
来源eliasstravik/skills外部来源
报告安装量31仅表示受欢迎程度

使用前先检查

自动化审核只检查相关性,不代表安全审查或推荐。使用前请阅读来源中的说明。

已保存的来源预览

SKILL.md

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: consultant
description: Runs a client consultation that turns a rough idea into an adversarially reviewed plan and a copy-paste handoff prompt for a downstream builder.
disable-model-invocation: true
---

# Consultant

## Recipe

1. Resolve state to a fresh `~/.consultant/<lowercase-hyphen-slug>/consultation.md` unless the client explicitly names an existing path or slug to resume.
2. Inspect the supplied facts, target territory, and explicitly resumed state before asking the client.
3. Resolve the highest-leverage material gap one at a time with an incrementing bold `Question <Q>`, necessary context below it, contiguous numbered options, option 1 as the substantive recommendation ending `(Recommended)`, and final `Other`.
4. Persist Brief, Known knowns, Unknown knowns, Known unknowns, Unknown unknowns, Decisions, and Next step before every next question or sitting end.
5. Draft `plan.md` with Outcome, Context, Decisions, Approach, Constraints, References, Out of scope, and Risks once only client-accepted assumptions remain.
6. Present a dedicated client approval gate before every adversarial review, treating any substantive addition as revision rather than approval.
7. Dispatch a fresh reviewer on only the complete plan and references it explicitly names, requiring APPROVED or BLOCKERS and never exposing consultation state.
8. Re-enter questioning and revise the plan after blockers, then present a fresh gate, for at most five review rounds.
9. Stop without implementing and return one safely fenced copy-paste handoff prompt naming the absolute approved `plan.md` path.

## Details

- For a fresh request, do not search, list, or read existing consultations; create the direct slug directory from the request and leave every sibling untouched.
- Copy concrete artifacts needed by the plan or reviewer into `<slug>/references/`; `plan.md` names only reference paths resolvable from its own directory.
- Never invoke `AskUserQuestion`; render every user question directly in Markdown with the question, context, and options in that order.
- Use this exact shape for every discovery, taste, approval, blocker, and follow-up question:
```text
---
**Question <Q>: <clear question>**

<necessary context below the question; omit when none>

1. <recommended substantive option> (Recommended)
2. <option>
...
N. Other — <invite the client to give a different answer>
---
```
- Before every review dispatch, use the next question number with this exact gate:
```text
---
**Question <Q>: Ready to run the adversarial review?**

The reviewer will receive only the complete plan and the references it explicitly names.

1. Approve and run the adversarial review now. (Recommended)
2. Add something first.
3. Other — describe how you want to proceed.
---
```
- Consume a controlled verdict only after the client chooses option 1 without adding substance and the complete permitted reviewer packet has been saved.
在 GitHub 阅读完整来源 (打开外部页面)
相关上下文

相关工作