plan-solution
Skill9 starsChanged 4 months agoMITView on GitHub
据已解析的题目(design/problem.yaml)定技术方案并推导系统需求。当用户要"定方案""选主控/视觉路线""出需求表""根据题目决定怎么做"时使用。产出 design/solution.md(技术方案 + 签字需求表 + 子系统清单),需用户签字确认后才进选材。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- xSolutions365/skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- xSolutions365/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- boardSkill
- elec-designSkill
- firmware-scaffoldSkill
- interconnectSkill
- power-designSkill
- read-problemSkill
- select-partsSkill
- setup-envSkill
- test-checklistSkill
- vision-scaffoldSkill
The file
Files
plan-solution —— 方案 + 需求(流水线 ②)
lane: lead(推理重,建议 Claude) · needs: 无 · 门: 人工签字需求表
把题目变成"怎么做 + 要满足哪些硬指标"。借鉴金奖经验,别凭空设计。
前置
读 design/problem.yaml(没有就先跑 /read-problem)。重点看 restrictions.camera_allowed —— 决定视觉路线。
步骤
- 查金奖经验/技术栈(Read,不复制):
kb/10-典型赛题实战Playbook与Checklist.md—— "典型赛题技术栈组合"表,找与本题category最近的一行作起点。kb/09-开源资源与备赛经验.md—— 金奖做法/避坑。kb/06-PID及衍生控制算法.md、kb/08-软件架构与调试工程化.md—— 控制结构。
- 定方案(逐子系统):
- 主控:默认 MSPM0G3507(KB03),需更强算力/FPU 再议 STM32G431。
- 视觉:
camera_allowed=true→ K230 做识别/巡线;=false→ 纯灰度/电磁,显著标注本届不上 K230。 - 传感:循迹(灰度阵列/电磁/K230)、定位(编码器/IMU/TOF)按题目功能选。
- 执行:电机+驱动(默认 TB6612+编码电机)、舵机(如需转向/云台)。
- 控制结构:嵌套 PID(外环位置/航向 ← 视觉/IMU/灰度;内环速度 ← 编码器)+ FSM 跑流程。
- 推导需求(硬数字,给后续选材/供电/接线用):
- 电源轨与电压、每轨最坏电流(电机用堵转)、逻辑电平。
- 接口清单与数量:要几路 PWM/UART/I2C/SPI/ADC/QEI(对照 MCU 能力表
contracts/mcu/)。 - 每个外设及其接口、对端连接器。
- 写
design/solution.md(模板见下)。 - 人工门:把"签字需求表"摊给用户逐项确认;用户没确认的硬指标不要默认,标 TODO。确认后更新
STATUS.md→ ③/④,并提示可并行:lead 跑/setup-env,随后/select-parts。
design/solution.md 模板
# 方案与需求 —— <题目名>
来源: design/problem.yaml | 类别: <category> | 摄像头: <允许/禁止>
## 技术方案
- 主控: MSPM0G3507(理由…)
- 视觉: K230 / 无(依据 camera_allowed)
- 传感: … 执行: … 控制结构: 嵌套PID + FSM
- 参考金奖技术栈: KB10 <哪一行>
## 子系统清单
| 子系统 | 方案 | 接口 | 备注 |
## 签字需求表(★用户逐项确认)
| # | 需求 | 指标 | 确认 |
|---|------|------|------|
| 电源 | 轨/电压/最坏电流 | … | ☐ |
| 接口数量 | PWMx? UARTx? I2C? ADCx? QEIx? | … | ☐ |
| 每外设接口+电平 | … | … | ☐ |
| 连接器 | … | … | ☐ |
## 待确认/风险(不擅自默认)
- …(源自 problem.yaml.ambiguities)注意
- 需求表是后面
select-parts/power-design/interconnect的输入契约,数字要硬。 camera_allowed=false时整条视觉链改纯灰度/电磁,务必在方案顶部红字提示。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

