refactor-plan
Judge whether a system is fragile or just fast-moving, and write a ticket-ready refactor plan for one root problem, with measured evidence and a stable fingerprint. Use after system history (or a bug trace) points at a systemic problem worth fixing at the root.
来源信息
- 仓库
- BuilderIO/agent-native
- 最近来源活动
- 2026年10月14日 17:53
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 7,366
- 分支
- 669
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
6 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- refactor-plan
- description
- Judge whether a system is fragile or just fast-moving, and write a ticket-ready refactor plan for one root problem, with measured evidence and a stable fingerprint. Use after system history (or a bug trace) points at a systemic problem worth fixing at the root.
- scope
- dev
- metadata
- {"internal":true}
# Refactor plan
## Judge first
`references/rubric.md` separates fragile from fast-moving from coupled, and
sets confidence. The counts from system-history are leads. A plan needs
a named repeated mechanism, taken from diffs you read.
## Scaffold
```bash
pnpm exec tsx .agents/skills/refactor-plan/scripts/new-plan.ts --run <id> \
--slug <kebab> --title "<imperative line>" --systems a,b \
--area <Framework|Slides|Design|Clips|Content|Dispatch|General> [--force]
```
It reads the run's `analysis.json`. Every system must be one analyze
scored. When the run has a `bug.json`, the plan becomes a bug plan:
- it adds a Trigger section, and quotes the report when it has no link;
- its paths are the focus files only;
- its frontmatter gets `trigger: bug` and the report as `source`.
Plans go to `<plansDir>/<run>/<slug>.md` (see `config.json`).
## Fill it
Replace every `TODO(agent)` marker, `summary`, and `confidence`, following
`references/plan-guide.md`. Keep slugs stable across runs. The
fingerprint comes from the systems and the slug, and Jira dedup keys on it.
A plan is finished when `jira-refactor-findings`' `jira-upsert.ts` accepts
it.
在 GitHub 查看