VE Scenario Miner
Use this skill to turn messy value-engineering notes into structured AI-Skill opportunities.
Inputs
Accept any of:
- Interview notes from value engineering colleagues.
- Meeting minutes from cost review, VAVE review, supplier discussion, or project review.
- Existing SOPs, templates, checklists, or weekly reports.
- Shadowing notes from observing daily work.
If inputs include confidential cost, supplier, drawing, or project data, remind the user to use approved enterprise tooling and redact sensitive details before external processing.
Workflow
- Identify the business role involved: cost analysis, VAVE, procurement collaboration, project management, documentation, or other.
- Extract repeated tasks and record frequency signals: daily, weekly, monthly, per project, per supplier, or ad hoc.
- For each task, capture input, action steps, decisions, output, downstream user, tools used, and common rework reasons.
- Mark standardization potential:
- High: clear inputs, repeated format, low business judgment.
- Medium: repeated structure with human review.
- Low: mostly expert judgment, negotiation, or sensitive decision-making.
- Convert high and medium candidates into Skill cards.
- Flag risks: missing data, confidentiality, engineering judgment, supplier sensitivity, unclear ownership, or quality/safety review.
Output
Return:
# VE Scenario Mining Output
## Scenario Map
| Scenario | Role | Frequency | Current Pain | Input | Output | Standardization Potential |
|---|---|---:|---|---|---|---|
## Skill Candidate Cards
### 1. <Skill candidate name>
- Trigger:
- Users:
- Required inputs:
- Steps the Skill can automate:
- Steps requiring human review:
- Output format:
- Success metric:
- Risks and boundaries:
## Questions For Business Validation
1.
2.
3.
Quality Checks
- Do not invent processes not present in the source notes.
- Keep uncertain items under "Questions For Business Validation".
- Separate facts, assumptions, and recommended next steps.
- Prefer small Skills that solve one frequent task over broad assistant concepts.
1---2name: ve-scenario-miner3description: Extract value-engineering business scenarios, high-frequency tasks, reusable methods, and Skill candidates from interview notes, meeting notes, SOPs, or shadowing records. Use when analyzing value engineering, VAVE, cost analysis, BOM review, supplier collaboration, or process documentation materials.4---56# VE Scenario Miner78Use this skill to turn messy value-engineering notes into structured AI-Skill opportunities.910## Inputs1112Accept any of:1314- Interview notes from value engineering colleagues.15- Meeting minutes from cost review, VAVE review, supplier discussion, or project review.16- Existing SOPs, templates, checklists, or weekly reports.17- Shadowing notes from observing daily work.1819If inputs include confidential cost, supplier, drawing, or project data, remind the user to use approved enterprise tooling and redact sensitive details before external processing.2021## Workflow22231. Identify the business role involved: cost analysis, VAVE, procurement collaboration, project management, documentation, or other.242. Extract repeated tasks and record frequency signals: daily, weekly, monthly, per project, per supplier, or ad hoc.253. For each task, capture input, action steps, decisions, output, downstream user, tools used, and common rework reasons.264. Mark standardization potential:27 - High: clear inputs, repeated format, low business judgment.28 - Medium: repeated structure with human review.29 - Low: mostly expert judgment, negotiation, or sensitive decision-making.305. Convert high and medium candidates into Skill cards.316. Flag risks: missing data, confidentiality, engineering judgment, supplier sensitivity, unclear ownership, or quality/safety review.3233## Output3435Return:3637```markdown38# VE Scenario Mining Output3940## Scenario Map4142| Scenario | Role | Frequency | Current Pain | Input | Output | Standardization Potential |43|---|---|---:|---|---|---|---|4445## Skill Candidate Cards4647### 1. <Skill candidate name>4849- Trigger:50- Users:51- Required inputs:52- Steps the Skill can automate:53- Steps requiring human review:54- Output format:55- Success metric:56- Risks and boundaries:5758## Questions For Business Validation59601.612.623.63```6465## Quality Checks6667- Do not invent processes not present in the source notes.68- Keep uncertain items under "Questions For Business Validation".69- Separate facts, assumptions, and recommended next steps.70- Prefer small Skills that solve one frequent task over broad assistant concepts.
wenhaoone