update pro-dev business case skill based on session feedback

This commit is contained in:
Connor Rhodes 2026-04-20 13:46:41 -05:00
parent dfd9af2422
commit 579d408ede

View file

@ -20,30 +20,35 @@ When Connor needs to justify a training, tool, book, course, or other profession
## Instructions
1. Ask for the following if not provided:
- Resource name or description
- Specific technical topics it covers
- Resource name or URL (visit the URL to get accurate details)
- Specific topics it covers
2. Write a single, direct paragraph using the template below.
2. Write a single, direct paragraph.
3. Do not ask follow-up questions or offer alternatives — just produce the paragraph.
## Output Location
Save the file to `~/notes/Inbox/agent/`. Use the format `YYMMDD-pro-dev-[short-name].md`.
4. Save the file to `~/notes/Inbox/agent/`. Use the format `YYMMDD-pro-dev-[short-name].md`.
## Rules
- Strictly factual: only state what the resource actually contains and what it will be used for
- No hyperbole or marketing language: avoid words like "comprehensive," "revolutionary," "invaluable," "highly cost-effective"
- Single paragraph, no headers, no bullet points
- Keep benefits general — audience is manager and HR, not a technical reviewer
- Focus on practical application: reference material, instructions, and documentation for designing, building, and testing proofs of concept
- Context: Connor is a Solutions Engineer at a physical security company working on hardware-software integration, edge computing, IoT development, and DC electronics
- **Single paragraph, no headers, no bullet points, no tables.** This is not a full document; it is one paragraph meant to paste into a form or email.
- **Direct and specific.** Say what the resource is, what it covers, and how it applies to Connor's work. Do not hand-wave with vague phrases like "provides reference material." Be concrete.
- **No "purchasing" framing.** Do not open with "Purchasing X..." or "Acquiring X..." Just state what the resource is and why it matters.
- **Do not include cost.** The submission form or receipt handles cost; do not mention the dollar amount in the paragraph.
- **Keep technical terms accessible.** The audience is manager and HR. Use general terms (e.g., "automation" instead of "custom perspectives" or "Apple Shortcuts"). Connor can use specific terms in conversation but the written justification should be broadly understood.
- **No hyperbole or marketing language.** Avoid words like "comprehensive," "revolutionary," "invaluable," "highly cost-effective."
- **Keep the closing simple.** One straightforward sentence connecting the resource to professional development. Do not overreach with long compound sentences about "enabling me to execute the X required for our Y initiatives."
- **Research the resource.** If Connor provides a URL, fetch the page to get accurate details about contents, format, and topics. Do not guess.
- **Context:** Connor is a Solutions Engineer at a physical security company. Relevant professional development themes include deal follow-up items, SE process work, calendar hygiene, Salesforce hygiene, pipeline management, and customer engagement coordination.
## Output Template
## Paragraph Structure
"Purchasing `[Resource Name]` provides reference material for `[specific technical topics]`. The [resource type] contains specific instructions and documentation for designing, building, and testing electrical proof of concepts. Acquiring this resource supports my professional development by expanding my technical capabilities, enabling me to execute the hardware prototyping required for our engineering initiatives."
Three sentences:
1. **What it is.** "[Resource Name] is a [format] covering [topics]."
2. **What you get from it.** "The course provides specific instructions for [applicable workflows/skills/techniques]."
3. **Why it matters.** "This course will support my professional development by [direct benefit to daily work]."
## Example Output
> Purchasing this bundle of technical books on ESP32, Raspberry Pi, and Arduino provides reference material for hardware-software integration, edge computing, and IoT development. The texts contain specific instructions and documentation for designing, building, and testing electrical proof of concepts. Acquiring these resources supports my professional development by expanding my technical capabilities, enabling me to execute the hardware prototyping required for our engineering initiatives.
> The OmniFocus 4 Field Guide is a self-paced video course covering advanced task management workflows, including organization techniques, automation, project templates, and structured review systems. The course provides specific instructions for building capture, processing, and review workflows that scale across simultaneous projects. This course will support my professional development by improving how I track deal follow-up items, SE process work, calendar hygiene, and Salesforce hygiene.