硬件详细设计:原理图指导、BOM约束、PCB布局规则、信号完整性要求、电源完整性设计。Hardware detailed design — schematic guidance, BOM constraints, PCB layout rules, signal integrity requirements, and power delivery network (PDN) design. Use when the user says 硬件详细设计, 原理图设计, PCB布局, BOM, hardware detailed design, schematic design, PCB layout, or when hardware…
A checklist-based review of a release package, including its binary, release notes, version manifest, and test reports. It checks that the files agree with one another and can be traced back to requirements.
A method for turning mixed source documents—such as a product brief, chip datasheet, industry standard, or customer specification—into one structured system requirements document. It classifies requirements, assigns ownership, and keeps links to their sources.
需求文档审查:基于检查清单对需求文档进行完整性和可追溯性审查。每个发现都引用检查项ID。Requirements document checklist review — focused review of a requirements document against company review checklists. Every finding cites a checklist item ID. Use when the user says 需求审查, 需求评审, requirements review, or when a requirements document is ready for formal peer…
软件/固件架构设计:RTOS线程模型、内存预算、IPC设计、模块间数据流。Firmware/software architecture design — RTOS thread/ISR model, memory budget allocation, IPC design, and inter-module data flows. Use when the user says 软件架构, 固件架构, RTOS设计, firmware architecture, software architecture, memory budget, or when system architecture is confirmed and…
软件详细设计:函数签名、数据结构、状态机、错误处理、线程安全模式。Firmware module detailed design — function signatures, data structures, state machines, error handling logic, and thread-safe design patterns for each firmware module. Use when the user says 软件详细设计, 函数设计, 状态机设计, software detailed design, function specification, or when software…
规格文档编写:生成软件概要设计(SOD)、软硬件接口规格(HW-SW IF Spec)、测试方案(Test Plan)。Specification authoring — produces Software Outline Design (SOD), Hardware-Software Interface Specification, and Test Plan from architecture and requirements. Use when the user says 规格编写, 概要设计, 接口规格, 测试方案, SOD, HW-SW IF Spec, spec authoring, or when…
A review process for test plans that checks both whether the plan follows its checklist and whether its test cases cover the stated requirements. P0 means the highest-priority requirements or risks.
A review of a test report against the test plan that governs it. It checks whether the reported results, conclusions, test conditions, and pass/fail decisions are correct, complete, and traceable.
A map of links between source requirements, system requirements, design elements, and test cases. It checks whether those links are complete and identifies requirements, designs, or tests that are disconnected.
SE技能发现和管道引导器:自动检测当前阶段并引导用户完成Define→Design→Document→Verify→Validate全流程。SE skill discovery and pipeline conductor — automatically detects the current SE phase and guides the user through the full Define-Design-Document-Verify-Validate workflow chain. Use when the user says 我不知道用什么技能, 该用哪个技能, which skill should I use…