菜单
Guidelines for creating Solution Blueprints (UX Flows, ROI, Risk Registers) for BRD preparation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | skill-product-solution-blueprint |
| description | Guidelines for creating Solution Blueprints (UX Flows, ROI, Risk Registers) for BRD preparation. |
| tier | 2 |
| version | 1 |
To translate abstract "Vision" into concrete "Requirements" without writing code. This skill powers the Solution Architect (p04) agent.
Constraint: Do NOT use Mermaid graphs for detailed logical flows. Use text lists.
Use the Official Template for the full structure.
### Flow 1: [User Story Name]
- **Size:** M (60h) | **LLM Friendly:** 0.8
1. User [Action] on [Page/Component].
- *System:* [Validates/Checks/Loads].
- *Error Path:* If [Condition], show [Error Message].
2. User sees [Result].
[!IMPORTANT] FORBIDDEN ACTION: You are strictly forbidden from calculating ROI/NPV manually. You MUST first list all User Stories with sizes + friendliness, then run the script.
docs/product/ (e.g., docs/product/stories.json):
{
"stories": [
{ "name": "Login", "size": "S", "llm_friendly": 0.9 },
{ "name": "Complex Dashboard", "size": "L", "llm_friendly": 0.3 }
]
}
# Usage: python3 [skill_path]/scripts/calculate_roi.py --file docs/product/stories.json --users <SOM> --price <PRICE>
python3 [skill_path]/scripts/calculate_roi.py --file docs/product/stories.json --users 5000 --price 29.99
Track top 5 risks using this structure:
| Risk ID | Risk Description | Impact (1-5) | Likelihood (1-5) | Mitigation Strategy |
|---|---|---|---|---|
| R01 | API Limit Hit | 5 | 3 | Use Rotating Proxies |
The output must be ready for handoff_to_technical.py.
examples/01_simple_flexarb.mdexamples/02_advanced_loyaltyhub.mdUse when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
Use when performing Verification-Driven Development with adversarial approach. Actively challenge assumptions and find weak spots.
Use when performing VDD adversarial review with an opt-in sarcastic, provocative delivery style — a stylistic skin over vdd-adversarial mechanics (exhaustive reporting + objective bar).
Performance critic in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.