Agent Skills › codeaholicguy/ai-devkit › dev-design

dev-design

GitHub

用于在开发生命周期中审查功能设计，验证架构、需求覆盖度及权衡取舍。通过对比需求文档与设计文档，识别差距与开放问题，确保设计方案完整且合理后再进入实现阶段。

skills/dev-design/SKILL.md codeaholicguy/ai-devkit

Trigger Scenarios

用户希望验证架构设计需要审查设计文档解决设计权衡问题运行 dev-lifecycle 第3阶段

Install

npx skills add codeaholicguy/ai-devkit --skill dev-design -g -y

More Options

Use without installing

npx skills use codeaholicguy/ai-devkit@dev-design

指定 Agent (Claude Code)

npx skills add codeaholicguy/ai-devkit --skill dev-design -a claude-code -g -y

安装 repo 全部 skill

npx skills add codeaholicguy/ai-devkit --all -g -y

预览 repo 内 skill

npx skills add codeaholicguy/ai-devkit --list

SKILL.md

Frontmatter

{
    "name": "dev-design",
    "description": "AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3."
}

Dev Design

Run the design review phase for configured AI docs features. Before changing docs or code, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.

Phase Contract

Run npx ai-devkit@latest lint before phase work.
If working on a named feature, run npx ai-devkit@latest lint --feature <name>.
Read existing requirements and design docs before changes.
Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
Do not approve or transition past design while material open questions remain.
Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
If parent dev-lifecycle established usable task tracing, emit design phase, progress, blocker/open-question, and next-step events per task.

Review Design

Use for Phase 3.

Run npx ai-devkit@latest lint --feature <name> and review the design doc path it validates. If manual path resolution is unavoidable, first resolve .ai-devkit.json paths.docs, falling back to docs/ai.
Search memory for relevant architecture patterns or past decisions.
Cross-check against the latest matching requirements doc. Verify every goal, user story, and constraint has corresponding design coverage. Flag uncovered requirements.
Review completeness: architecture, components, technology choices, data models, API contracts, design trade-offs, and non-functional requirements.
Resolve every gap, misalignment, open question, hidden assumption, or unresolved trade-off between requirements and design.
Brainstorm alternatives for key architecture decisions and trade-offs before accepting the first approach.
Update the design doc with clarified decisions and chosen options.
Store reusable architecture decisions in memory.
If task tracing is available, record design coverage progress, next step, or blockers per task.
Summarize requirements coverage, completeness assessment, updates made, and remaining gaps.

Next: dev-implementation. If requirements gaps are found, return to dev-requirements. If design is fundamentally wrong, revise design and re-review.