intake
/intake
Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape).
- Author
- vanducng ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 22
- Scripts
- 14
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 14 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: evals/01-bug-report/checks.sh, evals/01-bug-report/fixture/src/cart.js, evals/01-bug-report/fixture/tools/records.cjs, evals/02-question/checks.sh, evals/02-question/fixture/tools/records.cjs, evals/03-already-shaped/checks.sh, evals/03-already-shaped/fixture/src/cart.js, evals/03-already-shaped/fixture/tools/records.cjs, evals/04-stateful-retry/checks.sh, evals/04-stateful-retry/fixture/src/webho
What it does and when to use it
Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape).
Triggers from the description
Arguments
/intake <the ask, a ticket, or a bug report>
Original author description
Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape).
How it works
- Steps
- Rules
SKILL.md preview
--- name: intake description: "Turns an incoming ask into a work item before anyone builds: names its work type (bug fix, investigation, refactor, SOP and the rest; single source: `contract.cjs --list`), restates the intent, and writes the record's SPEC.md with that type's proof contract. Use when a new request, ticket, bug report or question arrives: 'take this', 'new task', 'triage this', 'what kind of work is this', 'start a record for', 'open a slice for'. Not for sharpening a record that already has its intent and contract (vd:shape)." license: MIT argument-hint: "<the ask, a ticket, or a bug report>" metadata: author: vanducng version: "0.2.1" --- # intake The first gate. It decides what kind of work this is and what will prove it done, before anyone designs or builds. It does not plan, design or code. `C=<this skill's directory>/scripts/contract.cjs` ## Steps 1. **Find the record.** - In an OpenRig rig, the record is the slice folder from `rig scope slice create`, created by the lead. - Elsewhere, the bench record the workbench skill resolves (`records.cjs resolve --id <id>`), where `<id>` is a short kebab name for the task. 2. **Already taken in?** Read the intents of the records beside it first. If one already covers this ask, use it, whatever its id. If its `SPEC.md` has an authored intent and a proof contract, change nothing: say it is shaped and stop. 3. **Classify:** pick one work type from `node "$C" --list`. - If two types fit, choose by what would prove the work done. - If the ask is too thin to tell, ask one question with your best guess, and write nothing. 4. **Write `SPEC.md`:** - frontmatter: `id`, `type` (the work type), and `intent` (the ask restated in one or two plain sentences); - `lenses: [statechart]` in the frontmatter only when the work has three or more states, or a rule about events over time (their order, a duplicate or late event, a retry). A pure calculation or a one-shot request gets no lens; - `## Mini-requirements`: numbered, observable outcomes taken from the ask, nothing invented; - `## Proof contract`: the lines from `node "$C" <type>`, made concrete for this ask (name the test, surface or number); - one more contract line: door type (one-way or two-way), blast radius, and the undo step. No `TODO` lines are left behind. 5. **Rig kind** (only in an OpenRig workspace): feature, bug fix or SOP maps to a rig template through the workspace skill's `rig-kind.cjs`. Name it. 6. **Hand off:** a queue row to the seat that owns the build: `--tags project:<org>.<project>`, `--mission <mission> --slice <slice>` when a slice exists; not the owner seat, hand the row's text to the lead. After every create, `rig queue show <id>`. 7. **Report:** the work type, the record path, the lens if you named one, and the open question if there is one. The next gate is `vd:shape`, which draws the lens's charts. ## Rules - The proof comes from the work type. A bug fix is proved by a check that fails on the old code and passes on the new. An investigation is proved by cited claims, each labelled measured, inferred or guess. - Restate the intent in your own words; never paste the ask. - One record per ask. Never create a second record for work that already has one.
Files in this package (22)
- SKILL.md 3 KB
- evals/common-checks.sh 1 KB
- evals/01-bug-report/checks.sh 1 KB
- evals/01-bug-report/prompt.md 1 KB
- evals/01-bug-report/fixture/src/cart.js 1 KB
- evals/01-bug-report/fixture/tools/records.cjs 1 KB
- evals/02-question/checks.sh 1 KB
- evals/02-question/prompt.md 1 KB
- evals/02-question/fixture/export.sql 1 KB
- evals/02-question/fixture/tools/records.cjs 1 KB
- evals/03-already-shaped/checks.sh 1 KB
- evals/03-already-shaped/prompt.md 1 KB
- evals/03-already-shaped/scenario.json 1 KB
- evals/03-already-shaped/fixture/.workbench/cart-coupon/SPEC.md 1 KB
- evals/03-already-shaped/fixture/src/cart.js 1 KB
- evals/03-already-shaped/fixture/tools/records.cjs 1 KB
- evals/04-stateful-retry/checks.sh 1 KB
- evals/04-stateful-retry/prompt.md 1 KB
- evals/04-stateful-retry/fixture/src/webhook.js 1 KB
- evals/04-stateful-retry/fixture/tools/records.cjs 1 KB
- scripts/contract.cjs 3 KB
- scripts/contract.test.cjs 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · vanducng/skills | 90 | MIT |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| alecs5am/ralphy | 100 | Apache-2.0 |
| lamngockhuong/aiteamkit | 100 | MIT |
| mathews-tom/armory | 100 | MIT |
| alecs5am/ralphy | 100 | Apache-2.0 |
| buriedsignals/splash | 100 | MIT |
| yuxqiu/loci | 90 | MIT |
| woditschka/agentic-coding-reference | 90 | MIT |
Database snapshot: 13.11.2026 · package version cfd69ee0bd14 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90shape
Shapes a work item's record before it is built: the intent in plain words, numbered mini-requirements anyone can check, and a checkbox proof contract, in the record's SPEC.md. A thin router: --grill walks an existing plan one question at a time; --options lays out two or three… - 85intent
Use when the user wants to think through what to build and why. Produces a conversational record of intent and context, not a requirements contract. Triggers include "help me shape this idea", "what should we build", or "capture the intent". - 96new-work-item
Creates and scopes a new work item in this repo's work/items/ folder. Use when asked to start, track, or plan a new piece of work, or when a request arrives in work/inbox/ that has no item yet. - 100echo-intent
Start or refine a work item's intent.md, the Plan-stage artifact. Use when beginning a new echo work item from a ticket and a short goal. - 100breakdown
Entry skill of the rastro flow. Turns an intent (a published design doc, an observed bug, a well-formed change request, or the walking skeleton that init writes) into work items through the tracker port. The result is a bug, a task, or a story with subtasks, each subtask… - 95new-track
Start a new feature or bug track. Collaborative intake process with structured questions, AI guidance, and progressive refinement before generating spec.md and plan.md. Use when the user asks to 'start a new track', 'create a feature track', 'add a bug fix track', or says 'I…