Menu
Guidelines for creating and refining Product Vision and Strategy.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | skill-product-analysis |
| description | Guidelines for creating and refining Product Vision and Strategy. |
| tier | 2 |
| version | 1.1 |
To define what we are building and why, before writing code. This skill powers the Product Analyst (p02) role.
You MUST use the provided Python script to scaffold the Vision document.
DO NOT write the PRODUCT_VISION.md header/structure manually.
Run the following command (Headless mode):
python3 [skill_path]/scripts/init_product.py --name "Product Name" --problem "Problem description" --audience "Users" --metrics "KPI1, KPI2"
Note:
[skill_path]is the path to this skill (e.g..agent/skills/skill-product-analysis).
Before drafting the Vision, you MUST score the idea to determine viability.
Run the scoring script with your estimated values (1-10, where 10 is Best/Easiest):
# Example: High problem intensity (9), but weak moat (3)
python3 [skill_path]/scripts/score_product.py --problem_intensity 9 --moat_durability 3 --market_size 8
PRODUCT_VISION.md.PRODUCT_VISION.md)See assets/vision_template.md for the authoritative structure.
All sections are mandatory.
When breaking down the vision into the Backlog:
When defining the product features, you MUST position it for the Early Majority.
Every feature implementation plan must start with:
Use the Official Template for the full structure.
examples/01_strong_go_devboost.mdexamples/02_consider_talentflow.mdexamples/03_nogo_quickbites.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.