[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-todos":3,"mdc--b700w-key":32,"related-repo-jetbrains-todos":799,"related-org-jetbrains-todos":808},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":28,"sourceUrl":30,"mdContent":31},"todos","manage shared live task lists","This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo_* tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose the plan FIRST (todo_write before you ask questions or start work), work tasks strictly in order with one step in_progress, keep statuses current, re-read the list (source of truth) to catch the user's edits, respect removals, and never delete done items.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"jetbrains","JetBrains","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fjetbrains.png",[12,16,19],{"name":13,"slug":14,"type":15},"Productivity","productivity","tag",{"name":17,"slug":18,"type":15},"Collaboration","collaboration",{"name":20,"slug":21,"type":15},"Task Management","task-management",7,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fthinkrail","2026-07-30T05:26:24.64275",null,0,[],{"repoUrl":23,"stars":22,"forks":26,"topics":29,"description":25},[],"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fthinkrail\u002Ftree\u002FHEAD\u002Fpackages\u002Fpi-todos\u002Fskills\u002Ftodos","---\nname: todos\ndescription: \"This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo_* tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose the plan FIRST (todo_write before you ask questions or start work), work tasks strictly in order with one step in_progress, keep statuses current, re-read the list (source of truth) to catch the user's edits, respect removals, and never delete done items.\"\n---\n\n# Chat TODO plan\n\n## What it is\n\n- A plan **scoped to this chat** — your tasks for the conversation. Shown to the user in the Todo\n  panel; lives with the session (not committed to the repo).\n- **Group = task, item = step.** One user ask = one group; its title is the *outcome* (\"Fix login\n  redirect\"), not the process. The steps inside are the items — each has a **title**, a **status**\n  (`pending` → `in_progress` → `done`), and an optional **note** (put the done-criterion there, e.g.\n  \"login e2e green\"). A task's own status is never stored — it derives from its steps.\n- **Loose items are the user's lane — and they sit at the END of the plan.** They hold what the\n  **user** adds from the UI; you work them, but never group, rewrite, or drop them. `todo_list` renders\n  them **last**, after every group, on purpose: a request the user adds mid-task queues *after* your\n  current work. So **finish (or resume) the task you're on before you pick up a loose item** — don't\n  jump to a freshly-added user item and abandon a step you had in progress. You don't author loose\n  items (the tools require a `group` or an `after` anchor); a tiny ask is a small group (1–2 steps is\n  fine), or no list at all.\n- It is **shared and live**: you maintain it, and the **user edits it while you work** — adding tasks,\n  removing ones they've dropped. The stored list is the **source of truth**; what you remember is only\n  a snapshot. **Re-read it (`todo_list`)** to stay in sync, don't trust your memory of it.\n- It is **the user's status window** — how they follow what's happening at a glance, without reading\n  the chat. Short, concrete step titles; statuses always current.\n\n## Granularity\n\n| Size of the ask | Shape in the plan |\n| --- | --- |\n| Trivial (an answer, one edit) | no list at all |\n| 1–7 steps | one group (a small ask = a 1–2-step group, that's fine) |\n| more than ~10 steps | those aren't steps, they're tasks — split into several groups |\n\nSteps are **verifiable** and ≈ commit-sized: \"easy to check off as you go\", not \"phase 1\".\n\n## Working with it\n\n1. **Propose the plan first — it's the point of the list.** The moment you understand a request that\n   takes more than a couple of steps, your first action is **`todo_write`** with your proposed plan —\n   one group per task, steps inside — **before** you ask clarifying questions and **before** you start\n   the work. Then refine it in place as you learn more. (A one-shot answer needs no list.)\n2. **Work tasks strictly in order, one step at a time:**\n   - Flip a step to `in_progress` when you start it, `done` when you finish. Starting a new step\n     auto-returns any other `in_progress` step to `pending` — so finish (mark `done`) before moving on,\n     or the previous step visibly falls back to open.\n   - Don't start the next group while the current one has open steps. The one exception: a genuinely\n     **blocked** task — record why in the step's `note`, tell the user, and move on to the next group.\n   - **Before each next step, `todo_list` again.** The user may have edited mid-work: note anything\n     new (it's appended in the user's lane at the **end** — take it up *after* the step you're on, don't\n     preempt in-progress work), and if an item you planned is gone, they dropped it — **skip it, don't\n     re-add it**.\n   - The tool results help you: after a `done` they name the task's next step; when nothing is\n     `in_progress` they remind you to flip the step you're on. Act on those nudges.\n3. **A new ask mid-session = a new group appended** (`todo_add` with `group:`, one per step — or lay\n   out the new task's steps with several `todo_add` calls). Never mix a new ask's steps into the\n   current group. **A step you discover mid-task** slots in with `todo_add after: \u003Ccurrent step id>` (anchor to one of *your* steps — anchoring to one of the user's own items is rejected, since your items never live in their lane) —\n   don't rebuild the plan with `todo_write` for that.\n4. **Reconcile before you finish.** At the end of a turn, `todo_list` once more. If open steps remain\n   (including items the user just added), either do them or clearly say what's left and why — don't go\n   idle silently leaving fresh items untouched.\n\n## Invariants\n\n- **Done stays.** Completing a step = `todo_update` → `done`. **Never delete a done item** — it's the\n  user's history. `todo_remove` is only for when the user explicitly asks to drop something.\n- **Edit surgically.** After the first plan, use `todo_update` \u002F `todo_add` (they touch one item).\n  **Never `todo_write` to tweak** an existing list — it replaces everything; `todo_write` is only for\n  laying out a fresh plan.\n- **Respect the user's edits.** The list is shared; treat their additions as new requests and their\n  removals as cancellations. Loose items are theirs — do them, but don't rewrite or drop them when you\n  re-plan. (`todo_write` preserves user items and done items for you, but don't lean on that — reach\n  for `todo_add`\u002F`todo_update` to edit, and keep `todo_write` for a genuinely fresh plan.)\n\n## Tools\n\n- `todo_list` — read the current plan (the source of truth; re-read to catch the user's edits).\n- `todo_add` — add one step (into a `group`, or `after` an existing step; leaves the rest untouched).\n- `todo_update` — progress one step (`in_progress` on start, `done` when finished; done stays).\n- `todo_remove` — delete one item (only when the user asks).\n- `todo_write` — lay out a fresh plan (groups only — one per task; replaces your open items; use once,\n  at the start).\n",{"data":33,"body":34},{"name":4,"description":6},{"type":35,"children":36},"root",[37,46,53,246,252,319,332,338,581,587,712,718],{"type":38,"tag":39,"props":40,"children":42},"element","h1",{"id":41},"chat-todo-plan",[43],{"type":44,"value":45},"text","Chat TODO plan",{"type":38,"tag":47,"props":48,"children":50},"h2",{"id":49},"what-it-is",[51],{"type":44,"value":52},"What it is",{"type":38,"tag":54,"props":55,"children":56},"ul",{},[57,71,134,195,235],{"type":38,"tag":58,"props":59,"children":60},"li",{},[61,63,69],{"type":44,"value":62},"A plan ",{"type":38,"tag":64,"props":65,"children":66},"strong",{},[67],{"type":44,"value":68},"scoped to this chat",{"type":44,"value":70}," — your tasks for the conversation. Shown to the user in the Todo\npanel; lives with the session (not committed to the repo).",{"type":38,"tag":58,"props":72,"children":73},{},[74,79,81,87,89,94,96,101,103,110,112,118,119,125,127,132],{"type":38,"tag":64,"props":75,"children":76},{},[77],{"type":44,"value":78},"Group = task, item = step.",{"type":44,"value":80}," One user ask = one group; its title is the ",{"type":38,"tag":82,"props":83,"children":84},"em",{},[85],{"type":44,"value":86},"outcome",{"type":44,"value":88}," (\"Fix login\nredirect\"), not the process. The steps inside are the items — each has a ",{"type":38,"tag":64,"props":90,"children":91},{},[92],{"type":44,"value":93},"title",{"type":44,"value":95},", a ",{"type":38,"tag":64,"props":97,"children":98},{},[99],{"type":44,"value":100},"status",{"type":44,"value":102},"\n(",{"type":38,"tag":104,"props":105,"children":107},"code",{"className":106},[],[108],{"type":44,"value":109},"pending",{"type":44,"value":111}," → ",{"type":38,"tag":104,"props":113,"children":115},{"className":114},[],[116],{"type":44,"value":117},"in_progress",{"type":44,"value":111},{"type":38,"tag":104,"props":120,"children":122},{"className":121},[],[123],{"type":44,"value":124},"done",{"type":44,"value":126},"), and an optional ",{"type":38,"tag":64,"props":128,"children":129},{},[130],{"type":44,"value":131},"note",{"type":44,"value":133}," (put the done-criterion there, e.g.\n\"login e2e green\"). A task's own status is never stored — it derives from its steps.",{"type":38,"tag":58,"props":135,"children":136},{},[137,142,144,149,151,157,159,164,166,171,173,178,180,186,188,193],{"type":38,"tag":64,"props":138,"children":139},{},[140],{"type":44,"value":141},"Loose items are the user's lane — and they sit at the END of the plan.",{"type":44,"value":143}," They hold what the\n",{"type":38,"tag":64,"props":145,"children":146},{},[147],{"type":44,"value":148},"user",{"type":44,"value":150}," adds from the UI; you work them, but never group, rewrite, or drop them. ",{"type":38,"tag":104,"props":152,"children":154},{"className":153},[],[155],{"type":44,"value":156},"todo_list",{"type":44,"value":158}," renders\nthem ",{"type":38,"tag":64,"props":160,"children":161},{},[162],{"type":44,"value":163},"last",{"type":44,"value":165},", after every group, on purpose: a request the user adds mid-task queues ",{"type":38,"tag":82,"props":167,"children":168},{},[169],{"type":44,"value":170},"after",{"type":44,"value":172}," your\ncurrent work. So ",{"type":38,"tag":64,"props":174,"children":175},{},[176],{"type":44,"value":177},"finish (or resume) the task you're on before you pick up a loose item",{"type":44,"value":179}," — don't\njump to a freshly-added user item and abandon a step you had in progress. You don't author loose\nitems (the tools require a ",{"type":38,"tag":104,"props":181,"children":183},{"className":182},[],[184],{"type":44,"value":185},"group",{"type":44,"value":187}," or an ",{"type":38,"tag":104,"props":189,"children":191},{"className":190},[],[192],{"type":44,"value":170},{"type":44,"value":194}," anchor); a tiny ask is a small group (1–2 steps is\nfine), or no list at all.",{"type":38,"tag":58,"props":196,"children":197},{},[198,200,205,207,212,214,219,221,233],{"type":44,"value":199},"It is ",{"type":38,"tag":64,"props":201,"children":202},{},[203],{"type":44,"value":204},"shared and live",{"type":44,"value":206},": you maintain it, and the ",{"type":38,"tag":64,"props":208,"children":209},{},[210],{"type":44,"value":211},"user edits it while you work",{"type":44,"value":213}," — adding tasks,\nremoving ones they've dropped. The stored list is the ",{"type":38,"tag":64,"props":215,"children":216},{},[217],{"type":44,"value":218},"source of truth",{"type":44,"value":220},"; what you remember is only\na snapshot. ",{"type":38,"tag":64,"props":222,"children":223},{},[224,226,231],{"type":44,"value":225},"Re-read it (",{"type":38,"tag":104,"props":227,"children":229},{"className":228},[],[230],{"type":44,"value":156},{"type":44,"value":232},")",{"type":44,"value":234}," to stay in sync, don't trust your memory of it.",{"type":38,"tag":58,"props":236,"children":237},{},[238,239,244],{"type":44,"value":199},{"type":38,"tag":64,"props":240,"children":241},{},[242],{"type":44,"value":243},"the user's status window",{"type":44,"value":245}," — how they follow what's happening at a glance, without reading\nthe chat. Short, concrete step titles; statuses always current.",{"type":38,"tag":47,"props":247,"children":249},{"id":248},"granularity",[250],{"type":44,"value":251},"Granularity",{"type":38,"tag":253,"props":254,"children":255},"table",{},[256,275],{"type":38,"tag":257,"props":258,"children":259},"thead",{},[260],{"type":38,"tag":261,"props":262,"children":263},"tr",{},[264,270],{"type":38,"tag":265,"props":266,"children":267},"th",{},[268],{"type":44,"value":269},"Size of the ask",{"type":38,"tag":265,"props":271,"children":272},{},[273],{"type":44,"value":274},"Shape in the plan",{"type":38,"tag":276,"props":277,"children":278},"tbody",{},[279,293,306],{"type":38,"tag":261,"props":280,"children":281},{},[282,288],{"type":38,"tag":283,"props":284,"children":285},"td",{},[286],{"type":44,"value":287},"Trivial (an answer, one edit)",{"type":38,"tag":283,"props":289,"children":290},{},[291],{"type":44,"value":292},"no list at all",{"type":38,"tag":261,"props":294,"children":295},{},[296,301],{"type":38,"tag":283,"props":297,"children":298},{},[299],{"type":44,"value":300},"1–7 steps",{"type":38,"tag":283,"props":302,"children":303},{},[304],{"type":44,"value":305},"one group (a small ask = a 1–2-step group, that's fine)",{"type":38,"tag":261,"props":307,"children":308},{},[309,314],{"type":38,"tag":283,"props":310,"children":311},{},[312],{"type":44,"value":313},"more than ~10 steps",{"type":38,"tag":283,"props":315,"children":316},{},[317],{"type":44,"value":318},"those aren't steps, they're tasks — split into several groups",{"type":38,"tag":320,"props":321,"children":322},"p",{},[323,325,330],{"type":44,"value":324},"Steps are ",{"type":38,"tag":64,"props":326,"children":327},{},[328],{"type":44,"value":329},"verifiable",{"type":44,"value":331}," and ≈ commit-sized: \"easy to check off as you go\", not \"phase 1\".",{"type":38,"tag":47,"props":333,"children":335},{"id":334},"working-with-it",[336],{"type":44,"value":337},"Working with it",{"type":38,"tag":339,"props":340,"children":341},"ol",{},[342,376,502,564],{"type":38,"tag":58,"props":343,"children":344},{},[345,350,352,361,363,368,370,374],{"type":38,"tag":64,"props":346,"children":347},{},[348],{"type":44,"value":349},"Propose the plan first — it's the point of the list.",{"type":44,"value":351}," The moment you understand a request that\ntakes more than a couple of steps, your first action is ",{"type":38,"tag":64,"props":353,"children":354},{},[355],{"type":38,"tag":104,"props":356,"children":358},{"className":357},[],[359],{"type":44,"value":360},"todo_write",{"type":44,"value":362}," with your proposed plan —\none group per task, steps inside — ",{"type":38,"tag":64,"props":364,"children":365},{},[366],{"type":44,"value":367},"before",{"type":44,"value":369}," you ask clarifying questions and ",{"type":38,"tag":64,"props":371,"children":372},{},[373],{"type":44,"value":367},{"type":44,"value":375}," you start\nthe work. Then refine it in place as you learn more. (A one-shot answer needs no list.)",{"type":38,"tag":58,"props":377,"children":378},{},[379,384],{"type":38,"tag":64,"props":380,"children":381},{},[382],{"type":44,"value":383},"Work tasks strictly in order, one step at a time:",{"type":38,"tag":54,"props":385,"children":386},{},[387,427,446,483],{"type":38,"tag":58,"props":388,"children":389},{},[390,392,397,399,404,406,411,413,418,420,425],{"type":44,"value":391},"Flip a step to ",{"type":38,"tag":104,"props":393,"children":395},{"className":394},[],[396],{"type":44,"value":117},{"type":44,"value":398}," when you start it, ",{"type":38,"tag":104,"props":400,"children":402},{"className":401},[],[403],{"type":44,"value":124},{"type":44,"value":405}," when you finish. Starting a new step\nauto-returns any other ",{"type":38,"tag":104,"props":407,"children":409},{"className":408},[],[410],{"type":44,"value":117},{"type":44,"value":412}," step to ",{"type":38,"tag":104,"props":414,"children":416},{"className":415},[],[417],{"type":44,"value":109},{"type":44,"value":419}," — so finish (mark ",{"type":38,"tag":104,"props":421,"children":423},{"className":422},[],[424],{"type":44,"value":124},{"type":44,"value":426},") before moving on,\nor the previous step visibly falls back to open.",{"type":38,"tag":58,"props":428,"children":429},{},[430,432,437,439,444],{"type":44,"value":431},"Don't start the next group while the current one has open steps. The one exception: a genuinely\n",{"type":38,"tag":64,"props":433,"children":434},{},[435],{"type":44,"value":436},"blocked",{"type":44,"value":438}," task — record why in the step's ",{"type":38,"tag":104,"props":440,"children":442},{"className":441},[],[443],{"type":44,"value":131},{"type":44,"value":445},", tell the user, and move on to the next group.",{"type":38,"tag":58,"props":447,"children":448},{},[449,461,463,468,470,474,476,481],{"type":38,"tag":64,"props":450,"children":451},{},[452,454,459],{"type":44,"value":453},"Before each next step, ",{"type":38,"tag":104,"props":455,"children":457},{"className":456},[],[458],{"type":44,"value":156},{"type":44,"value":460}," again.",{"type":44,"value":462}," The user may have edited mid-work: note anything\nnew (it's appended in the user's lane at the ",{"type":38,"tag":64,"props":464,"children":465},{},[466],{"type":44,"value":467},"end",{"type":44,"value":469}," — take it up ",{"type":38,"tag":82,"props":471,"children":472},{},[473],{"type":44,"value":170},{"type":44,"value":475}," the step you're on, don't\npreempt in-progress work), and if an item you planned is gone, they dropped it — ",{"type":38,"tag":64,"props":477,"children":478},{},[479],{"type":44,"value":480},"skip it, don't\nre-add it",{"type":44,"value":482},".",{"type":38,"tag":58,"props":484,"children":485},{},[486,488,493,495,500],{"type":44,"value":487},"The tool results help you: after a ",{"type":38,"tag":104,"props":489,"children":491},{"className":490},[],[492],{"type":44,"value":124},{"type":44,"value":494}," they name the task's next step; when nothing is\n",{"type":38,"tag":104,"props":496,"children":498},{"className":497},[],[499],{"type":44,"value":117},{"type":44,"value":501}," they remind you to flip the step you're on. Act on those nudges.",{"type":38,"tag":58,"props":503,"children":504},{},[505,510,512,518,520,526,528,533,535,540,542,548,550,555,557,562],{"type":38,"tag":64,"props":506,"children":507},{},[508],{"type":44,"value":509},"A new ask mid-session = a new group appended",{"type":44,"value":511}," (",{"type":38,"tag":104,"props":513,"children":515},{"className":514},[],[516],{"type":44,"value":517},"todo_add",{"type":44,"value":519}," with ",{"type":38,"tag":104,"props":521,"children":523},{"className":522},[],[524],{"type":44,"value":525},"group:",{"type":44,"value":527},", one per step — or lay\nout the new task's steps with several ",{"type":38,"tag":104,"props":529,"children":531},{"className":530},[],[532],{"type":44,"value":517},{"type":44,"value":534}," calls). Never mix a new ask's steps into the\ncurrent group. ",{"type":38,"tag":64,"props":536,"children":537},{},[538],{"type":44,"value":539},"A step you discover mid-task",{"type":44,"value":541}," slots in with ",{"type":38,"tag":104,"props":543,"children":545},{"className":544},[],[546],{"type":44,"value":547},"todo_add after: \u003Ccurrent step id>",{"type":44,"value":549}," (anchor to one of ",{"type":38,"tag":82,"props":551,"children":552},{},[553],{"type":44,"value":554},"your",{"type":44,"value":556}," steps — anchoring to one of the user's own items is rejected, since your items never live in their lane) —\ndon't rebuild the plan with ",{"type":38,"tag":104,"props":558,"children":560},{"className":559},[],[561],{"type":44,"value":360},{"type":44,"value":563}," for that.",{"type":38,"tag":58,"props":565,"children":566},{},[567,572,574,579],{"type":38,"tag":64,"props":568,"children":569},{},[570],{"type":44,"value":571},"Reconcile before you finish.",{"type":44,"value":573}," At the end of a turn, ",{"type":38,"tag":104,"props":575,"children":577},{"className":576},[],[578],{"type":44,"value":156},{"type":44,"value":580}," once more. If open steps remain\n(including items the user just added), either do them or clearly say what's left and why — don't go\nidle silently leaving fresh items untouched.",{"type":38,"tag":47,"props":582,"children":584},{"id":583},"invariants",[585],{"type":44,"value":586},"Invariants",{"type":38,"tag":54,"props":588,"children":589},{},[590,629,674],{"type":38,"tag":58,"props":591,"children":592},{},[593,598,600,606,607,612,614,619,621,627],{"type":38,"tag":64,"props":594,"children":595},{},[596],{"type":44,"value":597},"Done stays.",{"type":44,"value":599}," Completing a step = ",{"type":38,"tag":104,"props":601,"children":603},{"className":602},[],[604],{"type":44,"value":605},"todo_update",{"type":44,"value":111},{"type":38,"tag":104,"props":608,"children":610},{"className":609},[],[611],{"type":44,"value":124},{"type":44,"value":613},". ",{"type":38,"tag":64,"props":615,"children":616},{},[617],{"type":44,"value":618},"Never delete a done item",{"type":44,"value":620}," — it's the\nuser's history. ",{"type":38,"tag":104,"props":622,"children":624},{"className":623},[],[625],{"type":44,"value":626},"todo_remove",{"type":44,"value":628}," is only for when the user explicitly asks to drop something.",{"type":38,"tag":58,"props":630,"children":631},{},[632,637,639,644,646,651,653,665,667,672],{"type":38,"tag":64,"props":633,"children":634},{},[635],{"type":44,"value":636},"Edit surgically.",{"type":44,"value":638}," After the first plan, use ",{"type":38,"tag":104,"props":640,"children":642},{"className":641},[],[643],{"type":44,"value":605},{"type":44,"value":645}," \u002F ",{"type":38,"tag":104,"props":647,"children":649},{"className":648},[],[650],{"type":44,"value":517},{"type":44,"value":652}," (they touch one item).\n",{"type":38,"tag":64,"props":654,"children":655},{},[656,658,663],{"type":44,"value":657},"Never ",{"type":38,"tag":104,"props":659,"children":661},{"className":660},[],[662],{"type":44,"value":360},{"type":44,"value":664}," to tweak",{"type":44,"value":666}," an existing list — it replaces everything; ",{"type":38,"tag":104,"props":668,"children":670},{"className":669},[],[671],{"type":44,"value":360},{"type":44,"value":673}," is only for\nlaying out a fresh plan.",{"type":38,"tag":58,"props":675,"children":676},{},[677,682,684,689,691,696,698,703,705,710],{"type":38,"tag":64,"props":678,"children":679},{},[680],{"type":44,"value":681},"Respect the user's edits.",{"type":44,"value":683}," The list is shared; treat their additions as new requests and their\nremovals as cancellations. Loose items are theirs — do them, but don't rewrite or drop them when you\nre-plan. (",{"type":38,"tag":104,"props":685,"children":687},{"className":686},[],[688],{"type":44,"value":360},{"type":44,"value":690}," preserves user items and done items for you, but don't lean on that — reach\nfor ",{"type":38,"tag":104,"props":692,"children":694},{"className":693},[],[695],{"type":44,"value":517},{"type":44,"value":697},"\u002F",{"type":38,"tag":104,"props":699,"children":701},{"className":700},[],[702],{"type":44,"value":605},{"type":44,"value":704}," to edit, and keep ",{"type":38,"tag":104,"props":706,"children":708},{"className":707},[],[709],{"type":44,"value":360},{"type":44,"value":711}," for a genuinely fresh plan.)",{"type":38,"tag":47,"props":713,"children":715},{"id":714},"tools",[716],{"type":44,"value":717},"Tools",{"type":38,"tag":54,"props":719,"children":720},{},[721,731,755,779,789],{"type":38,"tag":58,"props":722,"children":723},{},[724,729],{"type":38,"tag":104,"props":725,"children":727},{"className":726},[],[728],{"type":44,"value":156},{"type":44,"value":730}," — read the current plan (the source of truth; re-read to catch the user's edits).",{"type":38,"tag":58,"props":732,"children":733},{},[734,739,741,746,748,753],{"type":38,"tag":104,"props":735,"children":737},{"className":736},[],[738],{"type":44,"value":517},{"type":44,"value":740}," — add one step (into a ",{"type":38,"tag":104,"props":742,"children":744},{"className":743},[],[745],{"type":44,"value":185},{"type":44,"value":747},", or ",{"type":38,"tag":104,"props":749,"children":751},{"className":750},[],[752],{"type":44,"value":170},{"type":44,"value":754}," an existing step; leaves the rest untouched).",{"type":38,"tag":58,"props":756,"children":757},{},[758,763,765,770,772,777],{"type":38,"tag":104,"props":759,"children":761},{"className":760},[],[762],{"type":44,"value":605},{"type":44,"value":764}," — progress one step (",{"type":38,"tag":104,"props":766,"children":768},{"className":767},[],[769],{"type":44,"value":117},{"type":44,"value":771}," on start, ",{"type":38,"tag":104,"props":773,"children":775},{"className":774},[],[776],{"type":44,"value":124},{"type":44,"value":778}," when finished; done stays).",{"type":38,"tag":58,"props":780,"children":781},{},[782,787],{"type":38,"tag":104,"props":783,"children":785},{"className":784},[],[786],{"type":44,"value":626},{"type":44,"value":788}," — delete one item (only when the user asks).",{"type":38,"tag":58,"props":790,"children":791},{},[792,797],{"type":38,"tag":104,"props":793,"children":795},{"className":794},[],[796],{"type":44,"value":360},{"type":44,"value":798}," — lay out a fresh plan (groups only — one per task; replaces your open items; use once,\nat the start).",{"items":800,"total":807},[801],{"slug":4,"name":4,"fn":5,"description":6,"org":802,"tags":803,"stars":22,"repoUrl":23,"updatedAt":24},{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[804,805,806],{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},1,{"items":809,"total":940},[810,828,837,846,857,867,880,889,898,908,917,930],{"slug":811,"name":811,"fn":812,"description":813,"org":814,"tags":815,"stars":825,"repoUrl":826,"updatedAt":827},"mps-aspect-accessories","configure JetBrains MPS module dependencies","Wire MPS module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language\u002Fdependency versions. Use when adding\u002Fremoving module dependencies, importing languages or devkits into a model, declaring runtime solutions, or shipping accessory content visible to consumers without explicit import.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[816,819,822],{"name":817,"slug":818,"type":15},"Architecture","architecture",{"name":820,"slug":821,"type":15},"Configuration","configuration",{"name":823,"slug":824,"type":15},"Engineering","engineering",1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":829,"name":829,"fn":830,"description":831,"org":832,"tags":833,"stars":825,"repoUrl":826,"updatedAt":836},"mps-aspect-actions","define and edit MPS node factories","Use when defining or editing MPS node factories (the \"actions\" aspect) — `NodeFactories` roots, per-concept `NodeFactory` setup functions that initialize a freshly created node and optionally copy data from a replaced `sampleNode`, plus the actions aspect's `CopyPasteHandlers` and `PasteWrappers` roots. Reach for this skill when a substitution, side transform, completion replacement, or `add new initialized(...)` should preserve fields from the node it is replacing, or when defaults set in a constructor are not enough.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[834,835],{"name":817,"slug":818,"type":15},{"name":823,"slug":824,"type":15},"2026-07-17T06:04:48.066901",{"slug":838,"name":838,"fn":839,"description":840,"org":841,"tags":842,"stars":825,"repoUrl":826,"updatedAt":845},"mps-aspect-behavior","define and edit MPS concept behavior","Use when defining or editing MPS `ConceptBehavior` — per-concept methods (non-virtual \u002F virtual \u002F abstract \u002F static \u002F virtual static), constructors, virtual dispatch (MRO), super and interface-default calls (`super\u003CInterface>.method`), overriding methods from `lang.core.behavior` interfaces such as `ScopeProvider.getScope` \u002F `INamedConcept.getName` \u002F `BaseConcept.getPresentation`, calling sibling methods (`LocalBehaviorMethodCall`) and behavior methods from other aspects via `node.method(...)`. Reach for this skill whenever the task involves authoring or modifying `\u003Clang>\u002FlanguageModels\u002Fbehavior.mps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[843,844],{"name":817,"slug":818,"type":15},{"name":823,"slug":824,"type":15},"2026-07-13T06:45:21.757084",{"slug":847,"name":847,"fn":848,"description":849,"org":850,"tags":851,"stars":825,"repoUrl":826,"updatedAt":856},"mps-aspect-constraints","define JetBrains MPS language constraints","Use when defining or editing MPS language constraints — property validators \u002F setters \u002F getters, referent search scopes (imperative or inherited via `ScopeProvider.getScope`), `referentSetHandler` side effects, default-scope blocks, `canBeChild` \u002F `canBeParent` \u002F `canBeAncestor` \u002F `canBeRoot` placement rules, `defaultConcreteConcept` for abstract concepts, `set \u003Cread-only>` and `{name}` aliasing, and scope helpers (`SimpleRoleScope`, `ListScope`, `CompositeScope`, `HidingByNameScope`). Reach for this skill whenever the task involves authoring or modifying `\u003Clang>\u002FlanguageModels\u002Fconstraints.mps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[852,853],{"name":817,"slug":818,"type":15},{"name":854,"slug":855,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":858,"name":858,"fn":859,"description":860,"org":861,"tags":862,"stars":825,"repoUrl":826,"updatedAt":866},"mps-aspect-dataflow","define and debug MPS dataflow builders","Use when defining or debugging MPS dataflow builders for a concept — control\u002Fdata flow declarations that drive reachability analysis and variable-use checking. Covers DataFlowBuilderDeclaration, BuilderBlock, emit instructions (code for, jump, ifjump, label, read, write, ret, mayBeUnreachable), positions (AfterPosition, BeforePosition, LabelPosition), the jetbrains.mps.lang.dataFlow language, the NodeParameter implicit, BL+smodel usage inside builder bodies, and IBuilderMode for advanced analyses such as nullable\u002Fnon-null tracking.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[863],{"name":864,"slug":865,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":868,"name":868,"fn":869,"description":870,"org":871,"tags":872,"stars":825,"repoUrl":826,"updatedAt":879},"mps-aspect-editor","define MPS editor layouts","Use when creating or changing MPS editor definitions — the overall workflow from scaffolding a `ConceptEditorDeclaration` through componentizing reusable `EditorComponentDeclaration`s, refining cell models and cell layouts, applying style sheets and indent-layout style items, wiring smart references, leveraging inheritance via super-concepts and interfaces, inspecting (`print_node_json`, `show_node_representation`) and validating (`check_root_node_problems`). Covers `jetbrains.mps.lang.editor` cell models (`CellModel_RefNode`\u002F`CellModel_RefNodeList`\u002F`CellModel_RefCell`\u002F`CellModel_Property`\u002F`CellModel_Constant`), layout choices, and JSON blueprints for common editor shapes. For the non-layout side (action maps, keymaps, transformation\u002Fsubstitute menus) use `mps-aspect-editor-menus-and-keymaps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[873,876],{"name":874,"slug":875,"type":15},"Design","design",{"name":877,"slug":878,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":881,"name":881,"fn":882,"description":883,"org":884,"tags":885,"stars":825,"repoUrl":826,"updatedAt":888},"mps-aspect-editor-menus-and-keymaps","author MPS editor menus and keymaps","Use when authoring the **non-layout** parts of the MPS editor aspect — what happens when the user types, presses a key, triggers completion, pastes, or invokes a context action. Covers action maps (`CellActionMapDeclaration`), cell keymaps (`CellKeyMapDeclaration`), transformation menus (`TransformationMenu_Default` \u002F `_Named` \u002F `_Contribution`), substitute menus (`SubstituteMenu_Default` \u002F `SubstituteMenu` \u002F contributions), side transforms (LEFT\u002FRIGHT), legacy cell menus, paste wrappers and copy-paste handlers (in the actions language), completion styling, reference presentation, two-step deletion, and the editor selection API. Trigger terms: `actionMap`, `keyMap`, `delete_action_id`, `transformationMenu`, `substituteMenu`, `Ctrl+Space`, `Ctrl+Alt+B`, side transform, paste wrapper, completion styling, `PasteWrappers`, `CopyPasteHandlers`. For the **layout** side (cells, layouts, style sheets) use `mps-aspect-editor` instead.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[886,887],{"name":823,"slug":824,"type":15},{"name":877,"slug":878,"type":15},"2026-07-23T05:41:49.666535",{"slug":890,"name":890,"fn":891,"description":892,"org":893,"tags":894,"stars":825,"repoUrl":826,"updatedAt":897},"mps-aspect-generation-plan","modify MPS generation plans","Use when defining or modifying an MPS generation plan — explicit ordering of generators, checkpoints for cross-model reference resolution, forks for parallel branches, IncludePlan composition, conditional PlanContribution activation, ParameterEquals\u002FConceptListSelector fork selectors, and InitModelAttributes for targetFacet routing. Apply when working with @genplan models, the jetbrains.mps.lang.generator.plan language, attaching plans via DevKits or the Custom generation facet, or debugging cross-model mapping label resolution.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[895,896],{"name":817,"slug":818,"type":15},{"name":823,"slug":824,"type":15},"2026-07-13T06:44:59.507855",{"slug":899,"name":899,"fn":900,"description":901,"org":902,"tags":903,"stars":825,"repoUrl":826,"updatedAt":907},"mps-aspect-generator","define JetBrains MPS generator rules","Use when defining or modifying MPS generators — author a generator module, add or edit root\u002Freduction\u002Fweaving\u002Fpattern mapping rules, attach template macros ($COPY_SRC, $LOOP, $IF, $PROPERTY, $REF, $SWITCH, $MAP_SRC, $WEAVE, $INSERT, $LABEL, $TRACE, $VAR), wire mapping labels, build template switches, write pre\u002Fpost mapping scripts, navigate `genContext`, or debug \"rule didn't fire\", missing references, empty output, infinite reduction loops, and generated-Java compile failures.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[904,905,906],{"name":817,"slug":818,"type":15},{"name":854,"slug":855,"type":15},{"name":823,"slug":824,"type":15},"2026-07-17T06:06:58.042999",{"slug":909,"name":909,"fn":910,"description":911,"org":912,"tags":913,"stars":825,"repoUrl":826,"updatedAt":916},"mps-aspect-intentions","define and edit MPS intentions","Use when defining or editing MPS intentions (the Alt+Enter context-action aspect) — adding `IntentionDeclaration` roots, parameterized or surround-with variants, description\u002FisApplicable\u002Fexecute blocks, child-filter functions, factory-initialized AST splicing, or debugging why an intention is not offered. Lives in the language's `intentions` model and uses `jetbrains.mps.lang.intentions`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[914,915],{"name":817,"slug":818,"type":15},{"name":823,"slug":824,"type":15},"2026-07-23T05:41:48.692899",{"slug":918,"name":918,"fn":919,"description":920,"org":921,"tags":922,"stars":825,"repoUrl":826,"updatedAt":929},"mps-aspect-migrations","author and debug MPS migration scripts","Use when authoring or debugging MPS migration scripts that upgrade user models after a language definition changes — covers jetbrains.mps.lang.migration (MigrationScript class-based, PureMigrationScript declarative, MoveConcept\u002FMoveContainmentLink\u002FMoveReferenceLink\u002FMoveProperty, ordering via OrderDependency, data exchange via putData\u002FgetData, RefactoringLog, ConceptMigrationReference) and jetbrains.mps.lang.script Enhancement Scripts (MigrationScript with MigrationScriptPart_Instance, ExtractInterfaceMigration, FactoryMigrationScriptPart, CommentMigrationScriptPart) — when a model needs version-gated upgrade, concept rename or removal, link or property rename, instance-level transformation, or composition of migration steps.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[923,926],{"name":924,"slug":925,"type":15},"Debugging","debugging",{"name":927,"slug":928,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":931,"name":931,"fn":932,"description":933,"org":934,"tags":935,"stars":825,"repoUrl":826,"updatedAt":939},"mps-aspect-structure-concepts","define concepts in MPS structure aspect","Define concepts, interface concepts, enumerations, and constrained data types in an MPS language's `structure` aspect. Covers smart-reference detection, alias rules, cardinality, INamedConcept usage, bulk creation, and the full `mps_mcp_alter_structure` \u002F `mps_mcp_query_structure` reference. Use when authoring or modifying a language's structure model.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[936],{"name":937,"slug":938,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]