# Vulcan Zone specialist agent — spec template (v1)

Fill this in with plain language. Think "department description in a procedure manual", not "software spec".
Our engineers turn it into the agent definition, its skill file and its playbook steps. Keep each section short
and concrete. Do not paste material that belongs to someone else (copyrighted manuals, another company's documents).

## 1. Name and one-line purpose
- Name: V-________ (e.g. V-Permits)
- In one sentence, for a contractor: "It ________ so that you ________."

## 2. Role and responsibilities (what it is accountable for)
List 4–8 responsibilities, each starting with a verb. Example style:
- Track permit applications, fees and inspection sign-offs for every job
- Prepare the submittal package the jurisdiction expects for ________

## 3. Inputs it needs
What must it know to start? Mark what usually comes from the contractor's company profile (trade, license, location…)
versus what it must ask for each time.

## 4. Outputs it produces (the real deliverables)
Documents, spreadsheets, logs, letters, decisions. For each: file type (Word / Excel / PDF), a short description, and a
template or example if you have one you are allowed to share.

## 5. The know-how (this is the valuable part)
Write it the way you would train a new hire:
- Step-by-step procedures (what first, what next, what to check before moving on)
- Checklists
- Rules of thumb, typical durations, quantities, prices, lead times (say for which region and year)
- Codes, standards and regulations it must follow, with section numbers
- Common mistakes and how to avoid them
- What must be reviewed by a licensed professional (PE, attorney, CPA, inspector)

## 6. Tools and data
- Web sources it should search (official sites first)
- Software it should connect to (and whether you can provide API access or documentation)
- Files it should read (drawings, spreadsheets, photos) and files it should write

## 7. Where the APM uses it (playbook)
For each outcome a contractor asks for where this specialist helps:
- Outcome: "________" (how the contractor would say it)
- Before this specialist runs: ________ (e.g. the estimate must exist)
- What this specialist does in that project, and what it hands to the next step
- Checks the APM should run on its work (numbers agree, nothing missing, deadlines stated…)

## 8. Quality and limits
- How to tell a good result from a bad one (3–5 checks)
- What it must never do or claim
- Who maintains the know-how (you? how often?)

## 9. About you
- Experience in this area, licenses, projects
- What you already have written down (procedures, templates, data)
- Franchisee? Contractor? Software partner?

Send this with the proposal form at https://vulcan-zone.ai/developers.html#propose, or email it to info@vulcan-zone.ai.