deepwork 0.1.1__tar.gz → 0.3.0__tar.gz

{deepwork-0.1.1 → deepwork-0.3.0}/.claude/settings.json

@@ -1,6 +1,11 @@
 {
   "permissions": {
     "allow": [
+      "WebFetch(domain:code.claude.com)",
+      "WebFetch(domain:www.anthropic.com)",
+      "WebFetch(domain:anthropic.com)",
+      "WebFetch(domain:platform.claude.com)",
+      "WebFetch(domain:docs.anthropic.com)",
       "Bash(ls:*)",
       "Bash(grep:*)",
       "Bash(find:*)",
@@ -97,7 +102,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": ".deepwork/jobs/deepwork_policy/hooks/user_prompt_submit.sh"
+            "command": ".deepwork/jobs/deepwork_rules/hooks/user_prompt_submit.sh"
           }
         ]
       }
@@ -108,7 +113,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": ".deepwork/jobs/deepwork_policy/hooks/policy_stop_hook.sh"
+            "command": "python -m deepwork.hooks.rules_check"
           }
         ]
       }

deepwork-0.3.0/.claude/skills/add_platform/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: add_platform
+description: "Add a new AI platform to DeepWork with adapter, templates, and tests"
+---
+
+# add_platform
+
+**Multi-step workflow**: Add a new AI platform to DeepWork with adapter, templates, and tests
+
+> **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
+
+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
+
+1. **research** - Capture CLI configuration and hooks system documentation for the new platform
+2. **add_capabilities** - Update job schema and adapters with any new hook events the platform supports (requires: research)
+3. **implement** - Add platform adapter, templates, tests with 100% coverage, and README documentation (requires: research, add_capabilities)
+4. **verify** - Set up platform directories and verify deepwork install works correctly (requires: implement)
+
+## Execution Instructions
+
+### Step 1: Analyze Intent
+
+Parse any text following `/add_platform` to determine user intent:
+- "research" or related terms → start at `add_platform.research`
+- "add_capabilities" or related terms → start at `add_platform.add_capabilities`
+- "implement" or related terms → start at `add_platform.implement`
+- "verify" or related terms → start at `add_platform.verify`
+
+### Step 2: Invoke Starting Step
+
+Use the Skill tool to invoke the identified starting step:
+```
+Skill tool: add_platform.research
+```
+
+### Step 3: Continue Workflow Automatically
+
+After each step completes:
+1. Check if there's a next step in the sequence
+2. Invoke the next step using the Skill tool
+3. Repeat until workflow is complete or user intervenes
+
+### Handling Ambiguous Intent
+
+If user intent is unclear, use AskUserQuestion to clarify:
+- Present available steps as numbered options
+- Let user select the starting point
+
+## Context Files
+
+- Job definition: `.deepwork/jobs/add_platform/job.yml`

deepwork-0.1.1/.claude/commands/add_platform.add_capabilities.md → deepwork-0.3.0/.claude/skills/add_platform.add_capabilities/SKILL.md

@@ -1,14 +1,12 @@
 ---
-description: Update job schema and adapters with any new hook events the platform supports
+name: add_platform.add_capabilities
+description: "Update job schema and adapters with any new hook events the platform supports"
+user-invocable: false
 hooks:
   Stop:
     - hooks:
         - type: prompt
           prompt: |
-            You must evaluate whether Claude has met all the below quality criteria for the request.
-
-            ## Quality Criteria
-
             Verify the capability additions meet ALL criteria:
             1. Any new hooks from the platform (for slash commands only) are added to src/deepwork/schemas/job_schema.py
             2. All existing adapters in src/deepwork/adapters.py are updated with the new hook fields
@@ -20,54 +18,23 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
-
-            ## Instructions
-
-            Review the conversation and determine if ALL quality criteria above have been satisfied.
-            Look for evidence that each criterion has been addressed.
-
-            If the agent has included `<promise>✓ Quality Criteria Met</promise>` in their response AND
-            all criteria appear to be met, respond with: {"ok": true}
-
-            If criteria are NOT met AND the promise tag is missing, respond with:
-            {"ok": false, "reason": "Continue working. [specific feedback on what's wrong]"}
 ---
 
 # add_platform.add_capabilities
 
-**Step 2 of 4** in the **add_platform** workflow
-
-**Summary**: Add a new AI platform to DeepWork with adapter, templates, and tests
+**Step 2/4** in **add_platform** workflow
 
-## Job Overview
+> 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
+## Prerequisites (Verify First)
 
-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
-
-
-## Prerequisites
-
-This step requires completion of the following step(s):
+Before proceeding, confirm these steps are complete:
 - `/add_platform.research`
 
-Please ensure these steps have been completed before proceeding.
-
 ## Instructions
 
+**Goal**: Update job schema and adapters with any new hook events the platform supports
+
 # Add Hook Capabilities
 
 ## Objective
@@ -205,86 +172,57 @@ For reference, here are common hook patterns across platforms:
 When you find a new hook type, consider whether it maps to an existing pattern or is genuinely new functionality.
 
 
-## Inputs
+### Job Context
 
+A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-### Required Files
-
-This step requires the following files from previous steps:
-- `hooks_system.md` (from step `research`)
-
-Make sure to read and use these files as context for this step.
-
-## Work Branch Management
-
-All work for this job should be done on a dedicated work branch:
-
-1. **Check current branch**:
-   - If already on a work branch for this job (format: `deepwork/add_platform-[instance]-[date]`), continue using it
-   - If on main/master, create a new work branch
-
-2. **Create work branch** (if needed):
-   ```bash
-   git checkout -b deepwork/add_platform-[instance]-$(date +%Y%m%d)
-   ```
-   Replace `[instance]` with a descriptive identifier (e.g., `acme`, `q1-launch`, etc.)
+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
 
-## Output Requirements
+The workflow ensures consistency across all supported platforms and maintains
+comprehensive test coverage for new functionality.
 
-Create the following output(s):
-- `job_schema.py`- `adapters.py`
-Ensure all outputs are:
-- Well-formatted and complete
-- Ready for review or use by subsequent steps
+**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
 
-## Quality Validation Loop
 
-This step uses an iterative quality validation loop. After completing your work, stop hook(s) will evaluate whether the outputs meet quality criteria. If criteria are not met, you will be prompted to continue refining.
+## Required Inputs
 
-### Quality Criteria
-Verify the capability additions meet ALL criteria:
-1. Any new hooks from the platform (for slash commands only) are added to src/deepwork/schemas/job_schema.py
-2. All existing adapters in src/deepwork/adapters.py are updated with the new hook fields
-   (set to None/null if the platform doesn't support that hook)
-3. Only hooks available on slash command definitions are added (not general CLI hooks)
-4. job_schema.py remains valid Python with no syntax errors
-5. adapters.py remains consistent - all adapters have the same hook fields
-6. If no new hooks are needed, document why in a comment
 
-If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+**Files from Previous Steps** - Read these first:
+- `hooks_system.md` (from `research`)
 
+## Work Branch
 
-### Completion Promise
+Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 
-To signal that all quality criteria have been met, include this tag in your final response:
+- If on a matching work branch: continue using it
+- If on main/master: create new branch with `git checkout -b deepwork/add_platform-[instance]-$(date +%Y%m%d)`
 
-```
-<promise>✓ Quality Criteria Met</promise>
-```
+## Outputs
 
-**Important**: Only include this promise tag when you have verified that ALL quality criteria above are satisfied. The validation loop will continue until this promise is detected.
+**Required outputs**:
+- `job_schema.py`- `adapters.py`
+## Quality Validation
 
-## Completion
+Stop hooks will automatically validate your work. The loop continues until all criteria pass.
 
-After completing this step:
 
-1. **Verify outputs**: Confirm all required files have been created
 
-2. **Inform the user**:
-   - Step 2 of 4 is complete
-   - Outputs created: job_schema.py, adapters.py
-   - Ready to proceed to next step: `/add_platform.implement`
+**To complete**: Include `<promise>✓ Quality Criteria Met</promise>` in your final response only after verifying ALL criteria are satisfied.
 
-## Next Step
+## On Completion
 
-To continue the workflow, run:
-```
-/add_platform.implement
-```
+1. Verify outputs are created
+2. Inform user: "Step 2/4 complete, outputs: job_schema.py, adapters.py"
+3. **Continue workflow**: Use Skill tool to invoke `/add_platform.implement`
 
 ---
 
-## Context Files
-
-- Job definition: `.deepwork/jobs/add_platform/job.yml`
-- Step instructions: `.deepwork/jobs/add_platform/steps/add_capabilities.md`
+**Reference files**: `.deepwork/jobs/add_platform/job.yml`, `.deepwork/jobs/add_platform/steps/add_capabilities.md`

deepwork-0.1.1/.claude/commands/add_platform.implement.md → deepwork-0.3.0/.claude/skills/add_platform.implement/SKILL.md

@@ -1,5 +1,7 @@
 ---
-description: Add platform adapter, templates, tests with 100% coverage, and README documentation
+name: add_platform.implement
+description: "Add platform adapter, templates, tests with 100% coverage, and README documentation"
+user-invocable: false
 hooks:
   Stop:
     - hooks:
@@ -7,10 +9,6 @@ hooks:
           command: ".deepwork/jobs/add_platform/hooks/run_tests.sh"
         - type: prompt
           prompt: |
-            You must evaluate whether Claude has met all the below quality criteria for the request.
-
-            ## Quality Criteria
-
             Verify the implementation meets ALL criteria:
             1. Platform adapter class is added to src/deepwork/adapters.py
             2. Templates exist in src/deepwork/templates/<platform>/ with appropriate command structure
@@ -24,55 +22,24 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
-
-            ## Instructions
-
-            Review the conversation and determine if ALL quality criteria above have been satisfied.
-            Look for evidence that each criterion has been addressed.
-
-            If the agent has included `<promise>✓ Quality Criteria Met</promise>` in their response AND
-            all criteria appear to be met, respond with: {"ok": true}
-
-            If criteria are NOT met AND the promise tag is missing, respond with:
-            {"ok": false, "reason": "Continue working. [specific feedback on what's wrong]"}
 ---
 
 # add_platform.implement
 
-**Step 3 of 4** in the **add_platform** workflow
-
-**Summary**: Add a new AI platform to DeepWork with adapter, templates, and tests
-
-## Job Overview
-
-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
+**Step 3/4** in **add_platform** workflow
 
+> Add a new AI platform to DeepWork with adapter, templates, and tests
 
-## Prerequisites
+## Prerequisites (Verify First)
 
-This step requires completion of the following step(s):
+Before proceeding, confirm these steps are complete:
 - `/add_platform.research`
 - `/add_platform.add_capabilities`
 
-Please ensure these steps have been completed before proceeding.
-
 ## Instructions
 
+**Goal**: Add platform adapter, templates, tests with 100% coverage, and README documentation
+
 # Implement Platform Support
 
 ## Objective
@@ -301,93 +268,60 @@ The templates use Jinja2 and should produce files that match exactly what the pl
 - Template syntax errors often show up at runtime - test early
 
 
-## Inputs
-
+### Job Context
 
-### Required Files
-
-This step requires the following files from previous steps:
-- `job_schema.py` (from step `add_capabilities`)
-- `adapters.py` (from step `add_capabilities`)
-- `cli_configuration.md` (from step `research`)
-
-Make sure to read and use these files as context for this step.
-
-## Work Branch Management
-
-All work for this job should be done on a dedicated work branch:
-
-1. **Check current branch**:
-   - If already on a work branch for this job (format: `deepwork/add_platform-[instance]-[date]`), continue using it
-   - If on main/master, create a new work branch
-
-2. **Create work branch** (if needed):
-   ```bash
-   git checkout -b deepwork/add_platform-[instance]-$(date +%Y%m%d)
-   ```
-   Replace `[instance]` with a descriptive identifier (e.g., `acme`, `q1-launch`, etc.)
+A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-## Output Requirements
+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
 
-Create the following output(s):
-- `templates/` (directory)- `tests/` (directory)- `README.md`
-Ensure all outputs are:
-- Well-formatted and complete
-- Ready for review or use by subsequent steps
+The workflow ensures consistency across all supported platforms and maintains
+comprehensive test coverage for new functionality.
 
-## Quality Validation Loop
+**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
 
-This step uses an iterative quality validation loop. After completing your work, stop hook(s) will evaluate whether the outputs meet quality criteria. If criteria are not met, you will be prompted to continue refining.
 
-**Validation Script**: `.deepwork/jobs/add_platform/hooks/run_tests.sh`
+## Required Inputs
 
-The validation script will be executed automatically when you attempt to complete this step.
-### Quality Criteria (2)
-Verify the implementation meets ALL criteria:
-1. Platform adapter class is added to src/deepwork/adapters.py
-2. Templates exist in src/deepwork/templates/<platform>/ with appropriate command structure
-3. Tests exist for all new functionality
-4. Test coverage is 100% for new code (run: uv run pytest --cov)
-5. All tests pass
-6. README.md is updated with:
-   - New platform listed in supported platforms
-   - Installation instructions for the platform
-   - Any platform-specific notes
 
-If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+**Files from Previous Steps** - Read these first:
+- `job_schema.py` (from `add_capabilities`)
+- `adapters.py` (from `add_capabilities`)
+- `cli_configuration.md` (from `research`)
 
+## Work Branch
 
-### Completion Promise
+Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 
-To signal that all quality criteria have been met, include this tag in your final response:
+- If on a matching work branch: continue using it
+- If on main/master: create new branch with `git checkout -b deepwork/add_platform-[instance]-$(date +%Y%m%d)`
 
-```
-<promise>✓ Quality Criteria Met</promise>
-```
+## Outputs
 
-**Important**: Only include this promise tag when you have verified that ALL quality criteria above are satisfied. The validation loop will continue until this promise is detected.
+**Required outputs**:
+- `templates/` (directory)- `tests/` (directory)- `README.md`
+## Quality Validation
 
-## Completion
+Stop hooks will automatically validate your work. The loop continues until all criteria pass.
 
-After completing this step:
 
-1. **Verify outputs**: Confirm all required files have been created
+**Validation script**: `.deepwork/jobs/add_platform/hooks/run_tests.sh` (runs automatically)
 
-2. **Inform the user**:
-   - Step 3 of 4 is complete
-   - Outputs created: templates/, tests/, README.md
-   - Ready to proceed to next step: `/add_platform.verify`
+**To complete**: Include `<promise>✓ Quality Criteria Met</promise>` in your final response only after verifying ALL criteria are satisfied.
 
-## Next Step
+## On Completion
 
-To continue the workflow, run:
-```
-/add_platform.verify
-```
+1. Verify outputs are created
+2. Inform user: "Step 3/4 complete, outputs: templates/, tests/, README.md"
+3. **Continue workflow**: Use Skill tool to invoke `/add_platform.verify`
 
 ---
 
-## Context Files
-
-- Job definition: `.deepwork/jobs/add_platform/job.yml`
-- Step instructions: `.deepwork/jobs/add_platform/steps/implement.md`
+**Reference files**: `.deepwork/jobs/add_platform/job.yml`, `.deepwork/jobs/add_platform/steps/implement.md`