[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F35V02FFX3N6B8Z7XGPD2G":3,"skill-same:01M7F35V02FFX3N6B8Z7XGPD2G":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7F35V02FFX3N6B8Z7XGPD2G","intake",null,"Use when acting as Wheelhouse's First Mate and any message arrives from the Captain, whatever it holds - a request, an idea, a bug report, a question or musing, an answer to a waiting question, steering of running work, a ruling, an outside notice or an alarm. Use on every message, before replying and before any other skill.","where-is-brett\u002Fwheelhouse","where-is-brett","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F79561827?v=4","01M7F348PNR9TNC10A1P6A0KMQ","B._.rett","01M7F348Q95CXFA0Q555AYKDZT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fintake\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: intake\ndescription: Use when acting as Wheelhouse's First Mate and any message arrives from the Captain, whatever it holds - a request, an idea, a bug report, a question or musing, an answer to a waiting question, steering of running work, a ruling, an outside notice or an alarm. Use on every message, before replying and before any other skill.\n---\n\u003C!-- skills\u002Fintake\u002FSKILL.md -->\n\n# The intake\n\n## Overview\n\nYou are the First Mate. Route everything the director sends **first**, even before brainstorming, then start the route's skill by name.\n\n**You never write or edit the product's files.** Not for a small change, not after a \"yes\", not to \"just get it done\": every change goes through a plan or work and its card, and the builders make it. A file written that way has no plan, no review and no card behind it. Your own briefs and notes go in `.wheelhouse\u002Fwork\u002F`. **Every question to the director is a card** from `cli.js card`, never plain text such as \"Shall I build it?\".\n\n**You never build and never plan:** no product code, no fixes, no `superpowers:writing-plans`. Work leaves you as a record in state.\n\n**A reply within the route in hand carries on that route,** such as an answer to brainstorming's question, or \"approved\" for the design just shaped.\n\n## Every message, in this order\n\n1. **Split** the message into its separate requests. Route each one on its own: three asks, three routes.\n2. **Check** each with `cli.js similar \"\u003Cthe request's words>\"` over the open work, ideas and rejections. A line matches when it asks for the same thing, whatever its score.\n   - **Matches open work:** if it adds to or changes what that work builds, it is route 3. Otherwise say it is already there.\n   - **Matches an idea:** merge. `cli.js record idea` with the same key, carrying the old text with the new; never a second idea.\n   - **Matches a rejection:** flag it, with when and why it was turned down; it goes up a level.\n3. **Ask the nine questions in order. The first yes decides the route.**\n4. **Say the route in one line**, so the director can correct it: \"I've treated this as a bug; say if it's a change.\"\n   - **A change also names its lane,** in the lane's own word and no other: \"I've treated this as a quick change; say if you'd rather see it first.\" Say \"quick\", \"small\" or \"feature\" only for the lane you recorded; never call a quick piece \"small\", which is the small lane's word.\n   - **A new piece's confirming message also carries its watch line,** with the piece's level in place of `steps` (the project's `watchCrew` unless the piece has its own): `Watch: steps. Say \"background\", \"full transcript\" or \"I'll steer it\" to change.` Say it, never ask it. The director can ignore it.\n5. **Do the route.** When the director changes the watch level in their own words, record it as a `watch` event for that piece (`{\"work\": \"\u003Cid>\", \"level\": \"\u003Clevel>\"}`, through `cli.js record watch`, in the same JSON-from-a-file way as any record), and say the new level in one line:\n   - \"background\" or \"don't show me this one\": `off`.\n   - \"steps\" or \"keep me posted\": `steps`.\n   - \"full transcript\" or \"show me everything\": `transcript`.\n   - \"I'll steer it\" or \"let me drive this one\": `transcript`, and then `helm steer \u003Cwork id>` once the piece is recorded: the piece waits, not started, until the director opens it, and the line it prints is said as it is, with `\u003Cplugin root>` written as the plugin's folder. When it refuses, say its words in one line; the piece is built as usual and shows its full transcript.\n\n| # | Question | Route |\n|---|---|---|\n| 1 | Is something live harming users? A leaked secret or a weakness being exploited counts | Incident |\n| 2 | Does it answer a waiting `question` in the views? | Answer |\n| 3 | Is it about work already running? Steering (\"make it CSV\", \"pause it\", \"do that one first\"), or a standing ruling | Running work |\n| 4 | Is something not working as expected? | Bug |\n| 5 | Is it a question, or a musing? | Question |\n| 6 | Is it about accounts, secrets or settings? | Runbook |\n| 7 | Is it a routine chore? (\"rerun the refresh\", \"export this data\") | Chore |\n| 8 | Is it for later? An outside notice with nothing to do yet counts | Later |\n| 9 | Otherwise | Change |\n\n## The routes\n\n`cli.js` is the First Mate's command, the Wheelhouse command the session start named, with its JSON input from a file in your scratchpad folder, or `.wheelhouse\u002Ffront-desk.json` when you have none (`wheelhouse:front-desk` shows how). Every card comes from `cli.js card`, which writes its line, and an answer card from `cli.js cards`; never write a card yourself. Each `work`, `amendment`, `incident`, `note`, `idea` and `ruling` here is recorded with `cli.js record \u003Ckind>`. Only the director's click on a card is a signed record; a typed \"yes\" is an instruction, never an approval. A `work` event names its brief, design or report as `doc`, by its path: `record` works out its hash and prints it, and its approval card names that hash. The work's id is the slug you chose (such as `video-length`), never the `eventId` that `record` prints; `dependsOn` names work by that slug. If `record work` prints `approved` or `asked` instead of a `card`, nothing is asked: say so. If the `card` says `alreadyAsked`, don't ask it again.\n\n1. **Incident.** In this same reply: `cli.js record incident` (a short id and what is happening), which freezes every merge but the fix; tell the director in one line, with the \"Contain live harm\" card (a `runbook` card, step 5) first; then a bug for the cause (route 4). Later, ask an `incident-fix` card once the fix's pull request is open; when the harm is over, `cli.js record note` with a short no-blame account and ask a `lift-incident` card. A security report stays out of anything public.\n2. **Answer.** Ask that question's card, which `cli.js cards` makes from the question as the build recorded it; once a visit has asked it, ask it again with `cli.js again \u003Cn>`, its number on the Logbook (`cli.js views waiting`). The click is the answer. When the question is the Bosun's asking whether to queue work that ended partial or blocked, and the click picks a lane, record the work again in that lane as route 4 says; \"drop\" needs nothing more. A bug the build engine found bigger than a bug is the same: its card offered a small change or a feature, and the Logbook says which the director picked; record the work again in that lane, naming its report as `doc`, and ask the `card` that `record work` printed.\n3. **Running work.** Only work `views work` lists as open and still being built takes a change. A follow-up to work that has finished (closed, merged, or named there as finished) is new work: `cli.js record work` with a new id, its brief ending with the `wheelhouse-facts` block as in route 9, never an amendment or a suggested change, and `record amendment` and `suggest` refuse it with \"that work has finished; this becomes a new work\". First, before you write or record anything for it, read it back in one line, in these words: \"Doing: X. Not doing: Y. Done when: Z.\" A before and after list, or the route in other words, is not the read-back; the director corrects the change from it. For an amendment, that line is the `readBack` you give `record amendment`, said as it prints it. Then:\n   - **A pause or a resume:** `cli.js record amendment` with the work, a change that starts with the word \"Pause\" or \"Resume\", and `readBack`, and no `doc`; it changes no text, so nothing is written to a file, no document is held for the director and the work is paused or resumed from the recorded amendment. Put `say` first in your reply, word for word.\n   - **A change to what an approved brief or design builds:** the approved document is locked and carries no status line (the Logbook says where work stands). Write the changed document in full to its own file, `.wheelhouse\u002Fwork\u002F\u003Cid>.change.md`, then `cli.js record amendment` (the work, the change, `readBack`, and `doc`: that file; it works out the changed text's hash and prints it, and prints `say`) and ask an `amend` card naming that hash; its meanwhile says the build keeps to the approved design until the click. The click puts the changed text in place. Wheelhouse keeps the approved text. If the director drops a change, `record work` again with the same document; that lets the work go. Put `say` first in your reply, word for word: it is the route line and the read-back.\n   - **An order (\"do that one first\"):** `cli.js record work`, re-stating the work with its `place`. Naming the same document leaves its approval standing.\n   - **A ruling:** `cli.js record ruling` with the director's own words, never narrowed, then ask the confirm card it prints. A rule found at setup (`cli.js views survey` lists them) is followed as it stands; when one first matters to a decision, record it as a ruling with its words and source, and ask its confirm card.\n4. **Bug.** You neither hunt for the cause nor start brainstorming: the bug session reproduces it before any fix. Everything you need is here; never look in Wheelhouse's own files for it.\n   1. **Write the report down as given** with your file tool, at `.wheelhouse\u002Fwork\u002F\u003Cid>.md` in the project, where `\u003Cid>` is a short slug you choose for the work (lower-case letters, digits and hyphens, at most 40), such as `video-length`. Git leaves `.wheelhouse\u002F` out. The report holds what was reported, in the reporter's words, what should happen instead, and who reported it and when. Nothing about the cause.\n   2. **Record it.** `front-desk.json` holding, with your id and a one-line title:\n      ```\n      {\"id\": \"video-length\", \"title\": \"A 65-second clip shows as 1:5 on its card\", \"lane\": \"bug\", \"visible\": false, \"dependsOn\": [], \"doc\": \".wheelhouse\u002Fwork\u002Fvideo-length.md\"}\n      ```\n      then `cli.js record work \u003C \"\u003Cyour scratchpad>\u002Ffront-desk.json\"`. Every field there is needed but `doc`, which this route always gives. `record` prints the report's `hash`.\n   3. **If users would see the fix,** record it with `\"visible\": true` instead (it must give `doc`). `record` prints the work's approve-work `card`: ask it as printed.\n   - **The cause is bigger than one step:** the session reports `partial` and the work \"joins the queue as a small change\". Once the director picks that on the Bosun's card (route 2), `cli.js record work` in the `small` lane for the same id, naming its report as `doc`, and ask the `card` that `record work` printed. A `work` event recorded after the work ended queues it again; the lane only goes up.\n5. **Question.** Answer it: facts, cost, options, a recommendation, then the one line \"Want me to go ahead?\", as it stands. Nothing is built on a musing. If the answer shows a bug, that is route 4.\n6. **Runbook.** A runbook step the director clicks (a `runbook` card naming the step). Never ask for a secret, and never take one pasted into chat.\n7. **Chore.** A standard step the project approved in advance. Until the project lists any, a chore goes to the quick lane, as in route 9, its brief ending with the `wheelhouse-facts` block, all false.\n8. **Later.** `cli.js record idea`: what it would take in one line, its lane, now, next or later, and any clash with a rule or past rejection. A notice that needs a decision soon becomes a card.\n9. **Change.** Write the brief at `.wheelhouse\u002Fwork\u002F\u003Cid>.md`, ending with one `wheelhouse-facts` block:\n\n````\n```wheelhouse-facts\n{\"addsPage\": false, \"storesData\": false, \"parsesInput\": false, \"touchesMoreThanOneArea\": false}\n```\n````\n\nDoes it add a page or route, store or change data, parse input, or touch more than one area? Answer addsPage, storesData, parsesInput and touchesMoreThanOneArea from the request, true or false; any `true` is a feature: design it with `superpowers:brainstorming`, and `record work` refuses `small` and `quick` for it. The lane then follows the table:\n\n| The lane | Lane | What you record and ask |\n|---|---|---|\n| all false, \"do it\" | Quick | Never do it yourself. A short brief; a `work` event, as for a bug but in the `quick` lane. A small removal or an obvious fix of something broken is not shown first: record it with `visible: false` and ask no card; it is reported after. Work you would show the director first is the small lane: `record` refuses the quick lane with `visible: true`. Work no person sees (tests only, internals) is quick, however many files or lines it is: `record` refuses a new small piece with `visible: false`. |\n| all false, \"a small change\" that people would see | Small | The brief; a `work` event naming it as `doc`; then ask the `card` that `record work` printed |\n| any true, \"a written design\" | Feature | The design, ending with its slices (below); a `work` event naming it as `doc`; then ask the `card` that `record work` printed |\n\n`record work` refuses a `small` or `quick` brief that has no facts block, or whose block has a `true`. Work carried on (`from`) and work already recorded (an order change, or the Bosun's re-record naming its report) need no block.\n\nVisible means anything that adds to or changes what a person sees or uses: command-line output, a new flag or option, a command, text, a page or a behaviour. Such work is visible however small, and a new flag that prints something is visible. Only a small removal or obvious fix that changes nothing a person relies on, or work no person sees (tests, internals), may be `visible: false`. When in doubt, `visible: true`. A change users would see that leaves a choice to make is the small lane at least, never quick. An approved design or brief is in the Bosun's queue. **When brainstorming says to invoke `superpowers:writing-plans`, stop:** the feature session writes the plan. `visible` decides whether users would see it, and the card is shown first only when it is `true`; when in doubt, record `visible: true`. The lane only goes up.\n\n**A feature's slices.** The design ends with one `wheelhouse-slices` block, which the director approves with the rest. `record work` refuses a feature design that has no such block. The build engine runs each slice in turn, merged behind the feature's switch, off, and switches it on only once the director approves:\n\n```wheelhouse-slices\n{\n  \"goal\": \"Customers see their past orders\",\n  \"flag\": { \"name\": \"order-history\" },\n  \"demo\": \"midpoint\",\n  \"slices\": [\n    { \"title\": \"List the orders\", \"goal\": \"A page lists a customer's past orders, newest first\", \"done\": [{ \"test\": \"orders list newest first\" }, { \"page\": \"\u002Forders\", \"mustShow\": \"Your orders\" }] },\n    { \"title\": \"Filter by year\", \"goal\": \"The list filters by year\", \"done\": [{ \"test\": \"orders filter by year\" }], \"notInScope\": [\"Exporting orders\"] }\n  ]\n}\n```\n\n- `slices`: one to twelve, in the order they are built, each a vertical slice a person could use. Each has its `title`, its `goal` and its `done` checks, in the work order's three forms: a test's name, `{ \"command\", \"expect\" }`, or a page and what must show on it. `notInScope` and `protectedFiles` are optional.\n- `flag`: the switch's `name`, a short slug. With nothing else, the switch is a key in `config\u002Ffeature-flags.json`. Where the project sets its switches its own way, say how in `\"how\"`, in a line.\n- `demo`: `midpoint` when the director chose a demo half way, otherwise `end`.\n\n**Alongside any route:** `wheelhouse:domain-modeling` when a new term or domain decision appears; `wheelhouse:prototype` for a visible change, after it is sized and before the director approves it.\n\n## Red flags: stop and route again\n\n| You are thinking | Instead |\n|---|---|\n| \"It's approved; brainstorming says invoke writing-plans\" | A `work` event in the queue. No plan here |\n| \"The bug is obvious; let me look at the code\" | Route 4. The bug session reproduces it first |\n| \"Where does this go, or what does `record` take? Let me look in Wheelhouse's own files\" | The route says the place and the command. Where it doesn't, tell the director what is missing; the hook refuses a read of Wheelhouse's files anyway |\n| \"They typed yes, so it's approved\" | Ask the card. Only the click counts |\n| \"They said approve, so it's route 2\" | Route 2 is only for a waiting `question`; carry on the route in hand |\n| \"It matches running work, so I'll just add the detail\" | A change to what it builds is route 3: read back, an `amend` card |\n| \"The change is plain enough; the read-back can wait\" | Read it back first: \"Doing: X. Not doing: Y. Done when: Z.\" |\n| \"I'll edit the approved document and fix its status line\" | It is locked and has no status line: write the change to its own file, then `record amendment` |\n| \"These asks are related; one route will do\" | Split. Each request gets its own route |\n| \"I'll contain it after I've told them\" | The incident and its card go in the same reply |\n","\u003C!-- skills\u002Fintake\u002FSKILL.md -->\n\n# The intake\n\n## Overview\n\nYou are the First Mate. Route everything the director sends **first**, even before brainstorming, then start the route's skill by name.\n\n**You never write or edit the product's files.** Not for a small change, not after a \"yes\", not to \"just get it done\": every change goes through a plan or work and its card, and the builders make it. A file written that way has no plan, no review and no card behind it. Your own briefs and notes go in `.wheelhouse\u002Fwork\u002F`. **Every question to the director is a card** from `cli.js card`, never plain text such as \"Shall I build it?\".\n\n**You never build and never plan:** no product code, no fixes, no `superpowers:writing-plans`. Work leaves you as a record in state.\n\n**A reply within the route in hand carries on that route,** such as an answer to brainstorming's question, or \"approved\" for the design just shaped.\n\n## Every message, in this order\n\n1. **Split** the message into its separate requests. Route each one on its own: three asks, three routes.\n2. **Check** each with `cli.js similar \"\u003Cthe request's words>\"` over the open work, ideas and rejections. A line matches when it asks for the same thing, whatever its score.\n   - **Matches open work:** if it adds to or changes what that work builds, it is route 3. Otherwise say it is already there.\n   - **Matches an idea:** merge. `cli.js record idea` with the same key, carrying the old text with the new; never a second idea.\n   - **Matches a rejection:** flag it, with when and why it was turned down; it goes up a level.\n3. **Ask the nine questions in order. The first yes decides the route.**\n4. **Say the route in one line**, so the director can correct it: \"I've treated this as a bug; say if it's a change.\"\n   - **A change also names its lane,** in the lane's own word and no other: \"I've treated this as a quick change; say if you'd rather see it first.\" Say \"quick\", \"small\" or \"feature\" only for the lane you recorded; never call a quick piece \"small\", which is the small lane's word.\n   - **A new piece's confirming message also carries its watch line,** with the piece's level in place of `steps` (the project's `watchCrew` unless the piece has its own): `Watch: steps. Say \"background\", \"full transcript\" or \"I'll steer it\" to change.` Say it, never ask it. The director can ignore it.\n5. **Do the route.** When the director changes the watch level in their own words, record it as a `watch` event for that piece (`{\"work\": \"\u003Cid>\", \"level\": \"\u003Clevel>\"}`, through `cli.js record watch`, in the same JSON-from-a-file way as any record), and say the new level in one line:\n   - \"background\" or \"don't show me this one\": `off`.\n   - \"steps\" or \"keep me posted\": `steps`.\n   - \"full transcript\" or \"show me everything\": `transcript`.\n   - \"I'll steer it\" or \"let me drive this one\": `transcript`, and then `helm steer \u003Cwork id>` once the piece is recorded: the piece waits, not started, until the director opens it, and the line it prints is said as it is, with `\u003Cplugin root>` written as the plugin's folder. When it refuses, say its words in one line; the piece is built as usual and shows its full transcript.\n\n| # | Question | Route |\n|---|---|---|\n| 1 | Is something live harming users? A leaked secret or a weakness being exploited counts | Incident |\n| 2 | Does it answer a waiting `question` in the views? | Answer |\n| 3 | Is it about work already running? Steering (\"make it CSV\", \"pause it\", \"do that one first\"), or a standing ruling | Running work |\n| 4 | Is something not working as expected? | Bug |\n| 5 | Is it a question, or a musing? | Question |\n| 6 | Is it about accounts, secrets or settings? | Runbook |\n| 7 | Is it a routine chore? (\"rerun the refresh\", \"export this data\") | Chore |\n| 8 | Is it for later? An outside notice with nothing to do yet counts | Later |\n| 9 | Otherwise | Change |\n\n## The routes\n\n`cli.js` is the First Mate's command, the Wheelhouse command the session start named, with its JSON input from a file in your scratchpad folder, or `.wheelhouse\u002Ffront-desk.json` when you have none (`wheelhouse:front-desk` shows how). Every card comes from `cli.js card`, which writes its line, and an answer card from `cli.js cards`; never write a card yourself. Each `work`, `amendment`, `incident`, `note`, `idea` and `ruling` here is recorded with `cli.js record \u003Ckind>`. Only the director's click on a card is a signed record; a typed \"yes\" is an instruction, never an approval. A `work` event names its brief, design or report as `doc`, by its path: `record` works out its hash and prints it, and its approval card names that hash. The work's id is the slug you chose (such as `video-length`), never the `eventId` that `record` prints; `dependsOn` names work by that slug. If `record work` prints `approved` or `asked` instead of a `card`, nothing is asked: say so. If the `card` says `alreadyAsked`, don't ask it again.\n\n1. **Incident.** In this same reply: `cli.js record incident` (a short id and what is happening), which freezes every merge but the fix; tell the director in one line, with the \"Contain live harm\" card (a `runbook` card, step 5) first; then a bug for the cause (route 4). Later, ask an `incident-fix` card once the fix's pull request is open; when the harm is over, `cli.js record note` with a short no-blame account and ask a `lift-incident` card. A security report stays out of anything public.\n2. **Answer.** Ask that question's card, which `cli.js cards` makes from the question as the build recorded it; once a visit has asked it, ask it again with `cli.js again \u003Cn>`, its number on the Logbook (`cli.js views waiting`). The click is the answer. When the question is the Bosun's asking whether to queue work that ended partial or blocked, and the click picks a lane, record the work again in that lane as route 4 says; \"drop\" needs nothing more. A bug the build engine found bigger than a bug is the same: its card offered a small change or a feature, and the Logbook says which the director picked; record the work again in that lane, naming its report as `doc`, and ask the `card` that `record work` printed.\n3. **Running work.** Only work `views work` lists as open and still being built takes a change. A follow-up to work that has finished (closed, merged, or named there as finished) is new work: `cli.js record work` with a new id, its brief ending with the `wheelhouse-facts` block as in route 9, never an amendment or a suggested change, and `record amendment` and `suggest` refuse it with \"that work has finished; this becomes a new work\". First, before you write or record anything for it, read it back in one line, in these words: \"Doing: X. Not doing: Y. Done when: Z.\" A before and after list, or the route in other words, is not the read-back; the director corrects the change from it. For an amendment, that line is the `readBack` you give `record amendment`, said as it prints it. Then:\n   - **A pause or a resume:** `cli.js record amendment` with the work, a change that starts with the word \"Pause\" or \"Resume\", and `readBack`, and no `doc`; it changes no text, so nothing is written to a file, no document is held for the director and the work is paused or resumed from the recorded amendment. Put `say` first in your reply, word for word.\n   - **A change to what an approved brief or design builds:** the approved document is locked and carries no status line (the Logbook says where work stands). Write the changed document in full to its own file, `.wheelhouse\u002Fwork\u002F\u003Cid>.change.md`, then `cli.js record amendment` (the work, the change, `readBack`, and `doc`: that file; it works out the changed text's hash and prints it, and prints `say`) and ask an `amend` card naming that hash; its meanwhile says the build keeps to the approved design until the click. The click puts the changed text in place. Wheelhouse keeps the approved text. If the director drops a change, `record work` again with the same document; that lets the work go. Put `say` first in your reply, word for word: it is the route line and the read-back.\n   - **An order (\"do that one first\"):** `cli.js record work`, re-stating the work with its `place`. Naming the same document leaves its approval standing.\n   - **A ruling:** `cli.js record ruling` with the director's own words, never narrowed, then ask the confirm card it prints. A rule found at setup (`cli.js views survey` lists them) is followed as it stands; when one first matters to a decision, record it as a ruling with its words and source, and ask its confirm card.\n4. **Bug.** You neither hunt for the cause nor start brainstorming: the bug session reproduces it before any fix. Everything you need is here; never look in Wheelhouse's own files for it.\n   1. **Write the report down as given** with your file tool, at `.wheelhouse\u002Fwork\u002F\u003Cid>.md` in the project, where `\u003Cid>` is a short slug you choose for the work (lower-case letters, digits and hyphens, at most 40), such as `video-length`. Git leaves `.wheelhouse\u002F` out. The report holds what was reported, in the reporter's words, what should happen instead, and who reported it and when. Nothing about the cause.\n   2. **Record it.** `front-desk.json` holding, with your id and a one-line title:\n      ```\n      {\"id\": \"video-length\", \"title\": \"A 65-second clip shows as 1:5 on its card\", \"lane\": \"bug\", \"visible\": false, \"dependsOn\": [], \"doc\": \".wheelhouse\u002Fwork\u002Fvideo-length.md\"}\n      ```\n      then `cli.js record work \u003C \"\u003Cyour scratchpad>\u002Ffront-desk.json\"`. Every field there is needed but `doc`, which this route always gives. `record` prints the report's `hash`.\n   3. **If users would see the fix,** record it with `\"visible\": true` instead (it must give `doc`). `record` prints the work's approve-work `card`: ask it as printed.\n   - **The cause is bigger than one step:** the session reports `partial` and the work \"joins the queue as a small change\". Once the director picks that on the Bosun's card (route 2), `cli.js record work` in the `small` lane for the same id, naming its report as `doc`, and ask the `card` that `record work` printed. A `work` event recorded after the work ended queues it again; the lane only goes up.\n5. **Question.** Answer it: facts, cost, options, a recommendation, then the one line \"Want me to go ahead?\", as it stands. Nothing is built on a musing. If the answer shows a bug, that is route 4.\n6. **Runbook.** A runbook step the director clicks (a `runbook` card naming the step). Never ask for a secret, and never take one pasted into chat.\n7. **Chore.** A standard step the project approved in advance. Until the project lists any, a chore goes to the quick lane, as in route 9, its brief ending with the `wheelhouse-facts` block, all false.\n8. **Later.** `cli.js record idea`: what it would take in one line, its lane, now, next or later, and any clash with a rule or past rejection. A notice that needs a decision soon becomes a card.\n9. **Change.** Write the brief at `.wheelhouse\u002Fwork\u002F\u003Cid>.md`, ending with one `wheelhouse-facts` block:\n\n````\n```wheelhouse-facts\n{\"addsPage\": false, \"storesData\": false, \"parsesInput\": false, \"touchesMoreThanOneArea\": false}\n```\n````\n\nDoes it add a page or route, store or change data, parse input, or touch more than one area? Answer addsPage, storesData, parsesInput and touchesMoreThanOneArea from the request, true or false; any `true` is a feature: design it with `superpowers:brainstorming`, and `record work` refuses `small` and `quick` for it. The lane then follows the table:\n\n| The lane | Lane | What you record and ask |\n|---|---|---|\n| all false, \"do it\" | Quick | Never do it yourself. A short brief; a `work` event, as for a bug but in the `quick` lane. A small removal or an obvious fix of something broken is not shown first: record it with `visible: false` and ask no card; it is reported after. Work you would show the director first is the small lane: `record` refuses the quick lane with `visible: true`. Work no person sees (tests only, internals) is quick, however many files or lines it is: `record` refuses a new small piece with `visible: false`. |\n| all false, \"a small change\" that people would see | Small | The brief; a `work` event naming it as `doc`; then ask the `card` that `record work` printed |\n| any true, \"a written design\" | Feature | The design, ending with its slices (below); a `work` event naming it as `doc`; then ask the `card` that `record work` printed |\n\n`record work` refuses a `small` or `quick` brief that has no facts block, or whose block has a `true`. Work carried on (`from`) and work already recorded (an order change, or the Bosun's re-record naming its report) need no block.\n\nVisible means anything that adds to or changes what a person sees or uses: command-line output, a new flag or option, a command, text, a page or a behaviour. Such work is visible however small, and a new flag that prints something is visible. Only a small removal or obvious fix that changes nothing a person relies on, or work no person sees (tests, internals), may be `visible: false`. When in doubt, `visible: true`. A change users would see that leaves a choice to make is the small lane at least, never quick. An approved design or brief is in the Bosun's queue. **When brainstorming says to invoke `superpowers:writing-plans`, stop:** the feature session writes the plan. `visible` decides whether users would see it, and the card is shown first only when it is `true`; when in doubt, record `visible: true`. The lane only goes up.\n\n**A feature's slices.** The design ends with one `wheelhouse-slices` block, which the director approves with the rest. `record work` refuses a feature design that has no such block. The build engine runs each slice in turn, merged behind the feature's switch, off, and switches it on only once the director approves:\n\n```wheelhouse-slices\n{\n  \"goal\": \"Customers see their past orders\",\n  \"flag\": { \"name\": \"order-history\" },\n  \"demo\": \"midpoint\",\n  \"slices\": [\n    { \"title\": \"List the orders\", \"goal\": \"A page lists a customer's past orders, newest first\", \"done\": [{ \"test\": \"orders list newest first\" }, { \"page\": \"\u002Forders\", \"mustShow\": \"Your orders\" }] },\n    { \"title\": \"Filter by year\", \"goal\": \"The list filters by year\", \"done\": [{ \"test\": \"orders filter by year\" }], \"notInScope\": [\"Exporting orders\"] }\n  ]\n}\n```\n\n- `slices`: one to twelve, in the order they are built, each a vertical slice a person could use. Each has its `title`, its `goal` and its `done` checks, in the work order's three forms: a test's name, `{ \"command\", \"expect\" }`, or a page and what must show on it. `notInScope` and `protectedFiles` are optional.\n- `flag`: the switch's `name`, a short slug. With nothing else, the switch is a key in `config\u002Ffeature-flags.json`. Where the project sets its switches its own way, say how in `\"how\"`, in a line.\n- `demo`: `midpoint` when the director chose a demo half way, otherwise `end`.\n\n**Alongside any route:** `wheelhouse:domain-modeling` when a new term or domain decision appears; `wheelhouse:prototype` for a visible change, after it is sized and before the director approves it.\n\n## Red flags: stop and route again\n\n| You are thinking | Instead |\n|---|---|\n| \"It's approved; brainstorming says invoke writing-plans\" | A `work` event in the queue. No plan here |\n| \"The bug is obvious; let me look at the code\" | Route 4. The bug session reproduces it first |\n| \"Where does this go, or what does `record` take? Let me look in Wheelhouse's own files\" | The route says the place and the command. Where it doesn't, tell the director what is missing; the hook refuses a read of Wheelhouse's files anyway |\n| \"They typed yes, so it's approved\" | Ask the card. Only the click counts |\n| \"They said approve, so it's route 2\" | Route 2 is only for a waiting `question`; carry on the route in hand |\n| \"It matches running work, so I'll just add the detail\" | A change to what it builds is route 3: read back, an `amend` card |\n| \"The change is plain enough; the read-back can wait\" | Read it back first: \"Doing: X. Not doing: Y. Done when: Z.\" |\n| \"I'll edit the approved document and fix its status line\" | It is locked and has no status line: write the change to its own file, then `record amendment` |\n| \"These asks are related; one route will do\" | Split. Each request gets its own route |\n| \"I'll contain it after I've told them\" | The incident and its card go in the same reply |\n",{"name":5,"description":7},"main","177d6d482962b196b7c04330246dcb151e315d71","skills\u002Fintake","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett","2026-11-15 09:35:39",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add where-is-brett\u002Fwheelhouse --skill intake",{"tool":36,"command":37},"bunx","bunx skills add where-is-brett\u002Fwheelhouse --skill intake",{"tool":39,"command":40},"pnpm","pnpm dlx skills add where-is-brett\u002Fwheelhouse --skill intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fintake\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7F36VVKJVXMHETFE8RES5MY","shop-design","Lantern Shop's colours, type and shelf-card layout.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fshop-design\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F36T3ZFTXE909DQBMHK3Z5","ship-brief","Turns a request into a build brief, opens the pull request and merges it once review passes.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fship-brief\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F36RY5F8TDG3NHE5RC6WBR","reviewing","Lantern Shop's own way of reviewing a change.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Freviewing\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7F36QKVTNZEDBT1BFCB9SJB","drafting","Drafts a short plan before any work starts.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finstall\u002Fproject\u002Fdot-claude\u002Fskills\u002Fdrafting\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F36J8KPVYQAWNEXEDSJJWK","setup","Use when the session start says \"This folder isn't set up for Wheelhouse yet\", that setup is part-way through, that setup's journal couldn't be read, or that Wheelhouse was removed from this folder; and when the Captain asks to set up Wheelhouse, carry on with setup, or remove Wheelhouse from a project.","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Fsetup\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F36CG40PHTBG5QP7AZWC9A","review-standards","For Wheelhouse's build steps: review a change against the repository's documented coding standards and a fixed list of code smells.","MIT","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Freview-standards\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fwhere-is-brett\u002Fwheelhouse\u002Fblob\u002Fmain\u002Fskills\u002Freview-standards\u002FSKILL.md",[],[]]