Use when an architect in the solution-design stage must produce or review a 业务流程图 that explains roles, steps, and handoff order without collapsing into system architecture, technical architecture, or detailed-design flow logic.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add xiaohei-info/oh-my-multica --skill software-design-lifecycle-solution-design-biz-flow-diagramming --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Software Design Lifecycle Solution Design Biz Flow Diagramming?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/xiaohei-info-software-design-lifecycle-solution-design-biz-flow)More formats (shields.io, HTML) on the badges page.
---
name: software-design-lifecycle-solution-design-biz-flow-diagramming
description: "Use when an architect in the solution-design stage must produce or review a 业务流程图 that explains roles, steps, and handoff order without collapsing into system architecture, technical architecture, or detailed-design flow logic."
version: 1.1.0
author: Hermes Agent
license: MIT
metadata:
hermes:
tags: [architect, lifecycle, solution-design, business-flow, diagramming]
related_skills: [arch-lifecycle-solution-design-methodology, arch-lifecycle-solution-design-biz-arch-diagramming]
---
# Solution Design Business Flow Diagramming
## Overview
This skill owns **解决方案设计阶段的业务流程图 artifact**.
## Canonical Solution-Design Slice (Preserved)
| 业务流程有哪些？ _业务问题与需求拆解，不同的角色与对应的需求问题_ | 给出业务流程图 |
## What This Artifact Must Answer
- which roles participate
- what steps happen in which order
- what the business handoffs are
## Verification Checklist
- [ ] Roles are explicit
- [ ] Steps and order are explicit
- [ ] Handoffs are explicit
- [ ] Artifact stays at business-flow level
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
