Ve manual writer

Skill onyx679/automotive-ve-ai-skills-kit/skills/ve-manual-writer

AI Skill templates and workflow scoring tools for automotive value engineering and VAVE productivity scenarios

Install

npx -y skills add onyx679/automotive-ve-ai-skills-kit --skill ve-manual-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Convert value-engineering workflow notes, SOP drafts, meeting decisions, templates, or best-practice examples into concise operating manuals, checklists, FAQs, and training materials for value engineering teams.

SKILL.md

1.6 KB, as published. Nobody here has run it

VE Manual Writer

Use this skill to turn process knowledge into documents that colleagues can actually use.

Inputs

Raw process notes.
Existing SOP fragments.
Meeting decisions.
Screenshots or descriptions of tool workflows.
Templates and example reports.
Feedback from users.

Workflow

Identify the target reader: new joiner, cost analyst, VAVE engineer, project manager, procurement collaborator, or manager.
Define the task boundary: when to use the process and when not to use it.
Convert the process into steps with inputs, actions, outputs, owner, and checks.
Add common mistakes and exception handling.
Add a concise example using redacted or synthetic data.
Add a version record and feedback channel.

Output

# <Manual Title>

## Purpose

## When To Use

## Required Inputs

## Procedure

| Step | Action | Owner | Output | Quality Check |
|---|---|---|---|---|

## Exceptions

| Situation | What To Do | Escalation |
|---|---|---|

## Example

## FAQ

## Version Record

| Version | Date | Change | Owner |
|---|---|---|---|

Style Rules

Use short steps and active verbs.
Prefer tables for repeated process information.
Put business rules in checklists.
Avoid long background explanations in operating manuals.
Clearly mark confidential or internal-only sections.