Add meta-command architecture for job entry points

Each job now generates a single user-facing meta-command (e.g., /deepwork_jobs)
that interprets user intent and routes to appropriate hidden step commands.

Key changes:
- Add `exposed` field to job.yml steps (default: false = hidden)
- Step commands are hidden by default (underscore prefix: _job.step.md)
- Steps with `exposed: true` remain visible (e.g., deepwork_jobs.learn.md)
- New meta-command templates for Claude and Gemini
- Generator creates meta-command first, then step commands

User experience:
- Before: /deepwork_jobs.define
- After: /deepwork_jobs define a new job

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: nhorton

…ommands/add_platform.add_capabilities.md …mmands/_add_platform.add_capabilities.md.claude/commands/add_platform.add_capabilities.md renamed to .claude/commands/_add_platform.add_capabilities.md .claude/commands/add_platform.add_capabilities.md renamed to .claude/commands/_add_platform.add_capabilities.md

@@ -0,0 +1,72 @@
+---
+description: Add a new AI platform to DeepWork with adapter, templates, and tests
+---
+
+# add_platform
+
+You are executing the **add_platform** job. Add a new AI platform to DeepWork with adapter, templates, and tests
+
+A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
+
+This job guides you through four phases:
+1. **Research**: Capture the platform's CLI configuration and hooks system documentation
+2. **Add Capabilities**: Update the job schema and adapters with any new hook events
+3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
+4. **Verify**: Ensure installation works correctly and produces expected files
+
+The workflow ensures consistency across all supported platforms and maintains
+comprehensive test coverage for new functionality.
+
+**Important Notes**:
+- Only hooks available on slash command definitions should be captured
+- Each existing adapter must be updated when new hooks are added (typically with null values)
+- Tests must achieve 100% coverage for any new functionality
+- Installation verification confirms the platform integrates correctly with existing jobs
+
+
+## Available Steps
+
+This job has 4 step(s):
+
+### research
+**Research Platform Documentation**: Capture CLI configuration and hooks system documentation for the new platform
+- Command: `_add_platform.research`
+### add_capabilities
+**Add Hook Capabilities**: Update job schema and adapters with any new hook events the platform supports
+- Command: `_add_platform.add_capabilities`
+- Requires: research
+### implement
+**Implement Platform Support**: Add platform adapter, templates, tests with 100% coverage, and README documentation
+- Command: `_add_platform.implement`
+- Requires: research, add_capabilities
+### verify
+**Verify Installation**: Set up platform directories and verify deepwork install works correctly
+- Command: `_add_platform.verify`
+- Requires: implement
+
+## Instructions
+
+Determine what the user wants to do and route to the appropriate step.
+
+1. **Analyze user intent** from the text that follows `/add_platform`
+
+2. **Match intent to a step**:
+   - research: Capture CLI configuration and hooks system documentation for the new platform
+   - add_capabilities: Update job schema and adapters with any new hook events the platform supports
+   - implement: Add platform adapter, templates, tests with 100% coverage, and README documentation
+   - verify: Set up platform directories and verify deepwork install works correctly
+
+3. **Invoke the matched step** using the Skill tool:
+   ```
+   Skill: <step_command_name>
+   ```
+
+4. **If intent is ambiguous**, ask the user which step they want:
+   - Present the available steps as numbered options
+   - Use AskUserQuestion to let them choose
+
+**Critical**: You MUST invoke the step using the Skill tool. Do not copy/paste the step's instructions. The Skill tool invocation ensures the step's quality validation hooks fire.
+
+## Context Files
+
+- Job definition: `.deepwork/jobs/add_platform/job.yml`

…laude/commands/add_platform.implement.md …aude/commands/_add_platform.implement.md.claude/commands/add_platform.implement.md renamed to .claude/commands/_add_platform.implement.md .claude/commands/add_platform.implement.md renamed to .claude/commands/_add_platform.implement.md

@@ -0,0 +1,60 @@
+---
+description: DeepWork job management commands
+---
+
+# deepwork_jobs
+
+You are executing the **deepwork_jobs** job. DeepWork job management commands
+
+Core commands for managing DeepWork jobs. These commands help you define new multi-step
+workflows and learn from running them.
+
+The `define` command guides you through an interactive process to create a new job by
+asking structured questions about your workflow, understanding each step's inputs and outputs,
+and generating all necessary files.
+
+The `learn` command reflects on conversations where DeepWork jobs were run, identifies
+confusion or inefficiencies, and improves job instructions. It also captures bespoke
+learnings specific to the current run into AGENTS.md files in the working folder.
+
+
+## Available Steps
+
+This job has 3 step(s):
+
+### define
+**Define Job Specification**: Create the job.yml specification file by understanding workflow requirements
+- Command: `_deepwork_jobs.define`
+### implement
+**Implement Job Steps**: Generate instruction files for each step based on the job.yml specification
+- Command: `_deepwork_jobs.implement`
+- Requires: define
+### learn
+**Learn from Job Execution**: Reflect on conversation to improve job instructions and capture learnings
+- Command: `deepwork_jobs.learn`
+
+## Instructions
+
+Determine what the user wants to do and route to the appropriate step.
+
+1. **Analyze user intent** from the text that follows `/deepwork_jobs`
+
+2. **Match intent to a step**:
+   - define: Create the job.yml specification file by understanding workflow requirements
+   - implement: Generate instruction files for each step based on the job.yml specification
+   - learn: Reflect on conversation to improve job instructions and capture learnings
+
+3. **Invoke the matched step** using the Skill tool:
+   ```
+   Skill: <step_command_name>
+   ```
+
+4. **If intent is ambiguous**, ask the user which step they want:
+   - Present the available steps as numbered options
+   - Use AskUserQuestion to let them choose
+
+**Critical**: You MUST invoke the step using the Skill tool. Do not copy/paste the step's instructions. The Skill tool invocation ensures the step's quality validation hooks fire.
+
+## Context Files
+
+- Job definition: `.deepwork/jobs/deepwork_jobs/job.yml`