菜单
After grill-me (or equivalent resolved decisions), produce a concise execution plan for the next agent session. No interviews, no issue tracker, no requirement expansion.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scaffold a new ds-* component (files, barrel export, validation). Use when the user asks to create, scaffold, or add a new component.
React patterns for design-system TSX including ds-* components, subcomponents, *.stories.tsx, and __tests__/*.browser.test.tsx. Use when editing hooks, useState, useEffect, ref prop, memoization, controlled state, or event handlers in @drivenets/design-system.
Write and update Storybook stories for design-system components. Use when editing `*.stories.tsx`, adding story variants, decorators, or removing Storybook play functions.
Check Ark UI primitives via MCP and integrate them in ds-* components without duplicating internal state. Use before building a custom component, wrapping Ark primitives, or when the user mentions Ark UI MCP.
Write and extend Vitest browser tests for design-system components. Use when adding or editing `*.browser.test.tsx`, writing behavioral coverage, or moving assertions out of Storybook.
Apply when preparing a PR, reviewing code changes, running git diff, or generating a changeset. Use when user says "review", "PR prep", "code review", or "changeset".
| name | to-plan |
| description | After grill-me (or equivalent resolved decisions), produce a concise execution plan for the next agent session. No interviews, no issue tracker, no requirement expansion. |
Package locked decisions from the conversation into a short execution plan. Do not plan for the user — only record what was already decided.
Grill-me (or equivalent) is finished: every branch resolved. If open questions remain, stop and tell the user to resume grilling.
One or two sentences.
Bullet list from grill-me — locked, no debate.
What was explicitly excluded.
Paths and packages (concrete).
Ordered checkboxes — implementation sequence only.
Which skills to read fully per step (e.g. component-scaffold, tdd, browser-tests).
Checkers from AGENTS.md#code-quality-checkers (and Other packages when applicable).
When done, the user or next agent can start implementation (typically tdd + design-system skills).
