wish
Skill1 starsChanged 23 days agoMITView on GitHub
Turn a request into a plan before anyone starts the work: a proposal, plan, or spec (方案 / 计划 / 提案 / 技术方案) for a feature, project, process change, campaign, event, or any task worth thinking through first. Use when someone asks for one or runs /wish. Writes for people by default: a single-page HTML doc rendered from JSON, with decisions up front, side notes for terms, and hidden-answer self-checks (docs/YY-MM-DD-{slug}.html + .json). Writes a self-contained Markdown plan instead when it is meant for an AI or agent to carry out (交给 AI / 给 AI 看 / 2ai). Reads the context first (the repo, or the files the user points to); asks at most 4 multiple-choice questions, only when the request is underspecified. Plans only; never does the work.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- kurofune/claudittheir own version, first seen Nov 8, 2026
- namastexlabs/automagik-genietheir own version, first seen Oct 8, 2026
- automagik-dev/genietheir own version, first seen Apr 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- kurofune/claudit★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- elderSkill
- wish2aiSkill
- wish2humanSkill
- web-animationSkill
- web-color-depthSkill
- web-interactionSkill
- web-layoutSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 73
Ask only when the answer changes the approach, the scope, or the finished look — content, never form.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Wish
A wish granted literally is a bug. Clarify first, then grant.
Rules only. The output is a file, not a chat essay. Plan only — never do the work itself here: no product code, nothing sent, nothing published. Paths below are relative to this skill's directory.
Input = the text after the command (Claude Code appends it as ARGUMENTS:). Empty → ask what to plan,
offering 3–5 candidates read from the context (README roadmap, TODO/FIXME, recent commits, the user's notes).
Works for any role: engineering, product, design, ops, marketing. In a code repo the plan is usually a build; elsewhere it may be a launch, a process, a campaign, an event.
Mode
| Mode | Reader | Output | Rules |
human (default) | People who review, decide, or need to understand; their attention is scarce | docs/YY-MM-DD-<slug>.json → .html | references/human.md |
ai | An agent (or person) who will carry it out cold, without this conversation | docs/YY-MM-DD-<slug>.md | references/ai.md |
/wish2human→human;/wish2ai→ai. No detection./wish→human, unless the plan is for an agent to carry out: "for AI / an agent / Codex / Cursor", "交给 AI", "给 AI 看", "让 AI / agent 照着做", "2ai", "markdown plan". Never ask which mode; name it in the report.- A follow-up keeps the mode of the file it edits.
Flow
- Read — the context. In a repo: README, manifests (
package.json,pyproject.toml,go.mod…), tree to depth 2, the modules the wish touches, existingdocs/. Otherwise: the files, links, and notes the user points to. Tools, vendors, or APIs the plan leans on: check current docs if a web tool exists. Skim, don't audit. Never ask what the material answers. - Gap check — mark every row of §Sufficiency
known/inferred/unknown. - Ask — only
unknownrows that change the approach, the scope, or the finished look (§Asking). Everything else becomes an assumption in the doc. Nothing to ask → write straight away. - Write — load the mode's rules file and follow it; save per §File.
- Gate — run the mode's gate; fix the doc until it passes.
- Report — path, ≤5-line summary, open decisions / questions, the mode used. Offer the next step; don't start it.
Follow-ups ("补充…", "also…", answers to open questions) → edit the same file (human: the .json,
then rebuild), bump the revision, add a changelog line. User approves → approved / Confirmed.
New file only for a different task.
Sufficiency
| # | Dimension | Unknown → ask when |
| 1 | Goal & audience — the problem, who it's for, why now | the audience or the motive is unclear (default: infer it from the wish and the context) |
| 2 | Scope — first version in, explicitly out | the wish fits more than one size |
| 3 | Finished look — what the result is: a screen, an API, a file, a page, an event, a process | more than one plausible form |
| 4 | Means — stack, tools, channels, people | the context doesn't settle it |
| 5 | Inputs & dependencies — data, systems, other teams, approvals | implied but unnamed |
| 6 | Done — acceptance criteria, success metric | not derivable from 1–3 |
| 7 | Constraints — deadline, budget, compliance, security, performance, accessibility | the domain makes it load-bearing |
Asking
- Ask only when the answer changes the approach, the scope, or the finished look — content, never form. Who reads it, how deep, what tone, which mode: defaults, corrected after the draft.
- ≤4 questions per round, ≤2 rounds; every question of a round in one message.
- Each question: 3–5 concrete options, the recommended one first, marked
(Recommended)with a one-line why. A free-text answer is always accepted. - Options are real alternatives grounded in the context ("reuse
src/api/client.ts" vs "a new SDK wrapper"; "the existing newsletter list" vs "a new segment"), never yes / no / other. - Native choice UI if the agent has one (Claude Code
AskUserQuestion: give 3–4 options; its automatic Other takes the free-text answer); otherwise numbered questions with options A–E in chat. - "You decide" / "你定" / "skip" → take every recommendation and record each as an assumption.
- Too big for one doc (several independent parts, weeks of work) → make "how to split" one of the questions; plan slice 1 in full, list the rest as later phases.
File
- Path:
<git root>/docs/YY-MM-DD-<slug>.<ext>; createdocs/if missing; outside a repo, use the working directory. - Date: today, local time, two-digit year — run
date +%y-%m-%dif unsure. Example:docs/26-09-23-export-orders-csv.html. - Slug: 2–5 words, lowercase ASCII kebab-case, English even when the doc isn't.
- Name taken: same task → update that file; different task → append
-2. - User named a path or file name → theirs wins.
- Language: the user's, headings included; code, paths, and identifiers stay verbatim.
Ban
- Doing the work while planning: writing product code, sending messages, buying, publishing
- Asking what the context already answers; yes/no questions; >4 questions per round; asking about form
- Filler — "ensure good performance", "follow best practices", "improve the user experience", "boost engagement": give a number or delete it
- Invented files, APIs, numbers, or names presented as real
- Pasting the whole doc into chat
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.