dev-workflow
Dev-workflow structures your development process across five stages—requirements understanding, design, implementation, code review, and bug fixing. It automatically detects which stage you're in via keywords and guides you through the appropriate steps, saving outputs to your docs folder.
Dev-workflow guides you through a five-stage development lifecycle from requirements to bug fixes.
AI-generated summary based on this skill's SKILL.md
Install
xstongxue/best-skills/dev-workflow · repository language: JavaScript
git clone https://github.com/xstongxue/best-skills
cp -r best-skills/skills/dev-workflow ~/.claude/skills/dev-workflowFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How should I design this system architecture with dev-workflow?
Dev-workflow guides you through technical design documentation by helping you structure your system architecture decisions. When you describe what you're building, dev-workflow identifies that you're in the design phase and walks you through defining components, data flows, and integration points. It generates a technical design document saved to your docs folder, ensuring your architecture is documented before implementation begins.
Can you review my code with dev-workflow?
Dev-workflow includes a dedicated code review stage that detects when you're ready for peer feedback. Share your code and dev-workflow guides you through a structured review checklist covering quality, performance, security, and maintainability. It identifies potential issues before merge and documents findings in your docs folder, helping maintain code standards across your team.
Help me understand the requirements with dev-workflow?
Dev-workflow starts by analyzing your requirements through its first stage. It helps you clarify what needs to be built by asking clarifying questions, documenting acceptance criteria, and identifying dependencies. Dev-workflow generates a requirements document template in your docs folder, ensuring all stakeholders have a shared understanding before design and coding begin.
What should I do when my app is crashing?
Dev-workflow detects runtime errors and guides you through systematic debugging. When your app crashes, dev-workflow helps you isolate the error, trace its source, and document the fix. It walks you through diagnosis steps and generates a bug report in your docs folder, ensuring the issue is properly resolved and documented for future reference.
What are the development workflow steps dev-workflow covers?
Dev-workflow structures your entire development lifecycle across five stages: requirements understanding, technical design, implementation, code review, and bug fixing. It automatically detects which stage you're in based on your keywords and questions, then guides you through appropriate steps with templates and checklists. All outputs save to your docs folder for team reference.
How does dev-workflow detect which development stage I'm in?
Dev-workflow analyzes your input keywords and context to identify your current stage—whether you're gathering requirements, designing architecture, implementing features, reviewing code, or debugging errors. This automatic detection ensures you receive stage-specific guidance and templates. The skill then generates relevant documentation in your docs folder tailored to that phase.
SKILL.md
rendered from the published skill — quoted content, verbatim
开发流程五步法
需求理解 → 方案设计 → 代码实现 → 代码审查 → Bug 修复
使用时机
- 用户描述新功能/项目想法，需要需求分析
- 用户提到「方案设计」「架构设计」「怎么实现」
- 用户提到「代码实现」「开始写代码」「帮我实现」
- 用户提到「代码审查」「Review」「检查代码」「看看有没有问题」
- 用户提到「bug」「报错」「崩溃」「异常」「不工作」「出错了」「测试失败」
Step 1：识别当前步骤
根据用户需求选择对应 reference 文件执行：
| 步骤 | 文件 | 触发关键词 |
|---|---|---|
| 需求理解 | requirement.md | 需求分析、理解需求、整理需求、帮我梳理 |
| 方案设计 | design.md | 方案设计、技术设计、架构设计、怎么实现 |
| 代码实现 | implementation.md | 代码实现、开始写代码、帮我实现、写一下 |
| 代码审查 | review.md | 代码审查、Review、检查代码、看看有没有问题 |
| Bug 修复 | bug-fix.md | bug、报错、崩溃、异常、不工作、出错了、测试失败 |
Step 2：收集输入
- 需求理解：从用户描述或对话中提取功能想法、约束条件
- 方案设计：确认已有需求文档，或简要收集关键信息
- 代码实现：确认已有技术方案，或根据需求快速拟定实现思路
- 代码审查：明确审查范围（哪些文件/模块）
- **Bug
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 15 files
skills/dev-workflow/SKILL.md
skills/dev-workflow/reference/bug-fix.md
skills/dev-workflow/reference/design.md
skills/dev-workflow/reference/implementation.md
skills/dev-workflow/reference/requirement.md
skills/dev-workflow/reference/review-kit/guides/architecture-review-guide.md
skills/dev-workflow/reference/review-kit/guides/c.md
skills/dev-workflow/reference/review-kit/guides/common-bugs-checklist.md
skills/dev-workflow/reference/review-kit/guides/cpp.md
skills/dev-workflow/reference/review-kit/guides/css-less-sass.md
skills/dev-workflow/reference/review-kit/guides/go.md
skills/dev-workflow/reference/review-kit/guides/java.md
skills/dev-workflow/reference/review-kit/guides/performance-review-guide.md
skills/dev-workflow/reference/review-kit/guides/python.md
skills/dev-workflow/reference/review-kit/guides/qt.md