deepwork 0.3.0__tar.gz → 0.4.0__tar.gz

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

@@ -89,13 +89,55 @@
       "Bash(python3:*)",
       "Bash(pip:*)",
       "Bash(pip3:*)",
+      "Bash(pytest:*)",
+      "Bash(uv:*)",
       "Bash(node:*)",
       "Bash(npm:*)",
       "Bash(npx:*)",
-      "Edit(./**)"
+      "Edit(./**)",
+      "Read(./.deepwork/tmp/**)",
+      "Edit(./.deepwork/tmp/**)",
+      "Write(./.deepwork/tmp/**)",
+      "Skill(commit)",
+      "Skill(commit.review)",
+      "Skill(commit.test)",
+      "Skill(commit.lint)",
+      "Skill(commit.commit_and_push)",
+      "Skill(deepwork_jobs)",
+      "Skill(deepwork_jobs.define)",
+      "Skill(deepwork_jobs.review_job_spec)",
+      "Skill(deepwork_jobs.implement)",
+      "Skill(deepwork_jobs.learn)",
+      "Skill(add_platform)",
+      "Skill(add_platform.research)",
+      "Skill(add_platform.add_capabilities)",
+      "Skill(add_platform.implement)",
+      "Skill(add_platform.verify)",
+      "Skill(update)",
+      "Skill(update.job)",
+      "Skill(manual_tests)",
+      "Skill(manual_tests.run_not_fire_tests)",
+      "Skill(manual_tests.run_fire_tests)",
+      "Skill(deepwork_rules)",
+      "Skill(deepwork_rules.define)",
+      "Bash(deepwork rules clear_queue)",
+      "Bash(rm -rf .deepwork/tmp/rules/queue/*.json)",
+      "Skill(manual_tests.reset)",
+      "Skill(manual_tests.infinite_block_tests)"
     ]
   },
   "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "src/deepwork/hooks/check_version.sh"
+          }
+        ]
+      }
+    ],
     "UserPromptSubmit": [
       {
         "matcher": "",
@@ -113,7 +155,18 @@
         "hooks": [
           {
             "type": "command",
-            "command": "python -m deepwork.hooks.rules_check"
+            "command": "deepwork hook rules_check"
+          }
+        ]
+      }
+    ],
+    "SubagentStop": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "deepwork hook rules_check"
           }
         ]
       }

{deepwork-0.3.0 → deepwork-0.4.0}/.claude/skills/add_platform/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: add_platform
-description: "Add a new AI platform to DeepWork with adapter, templates, and tests"
+description: "Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools."
 ---
 
 # add_platform
 
-**Multi-step workflow**: Add a new AI platform to DeepWork with adapter, templates, and tests
+**Multi-step workflow**: Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
@@ -29,10 +29,10 @@ comprehensive test coverage for new functionality.
 
 ## 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)
+1. **research** - Captures CLI configuration and hooks system documentation for the new platform. Use when starting platform integration.
+2. **add_capabilities** - Updates job schema and adapters with any new hook events the platform supports. Use after research to extend DeepWork's hook system. (requires: research)
+3. **implement** - Creates platform adapter, templates, tests with 100% coverage, and README documentation. Use after adding hook capabilities. (requires: research, add_capabilities)
+4. **verify** - Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration. (requires: implement)
 
 ## Execution Instructions
 
@@ -64,6 +64,13 @@ If user intent is unclear, use AskUserQuestion to clarify:
 - Present available steps as numbered options
 - Let user select the starting point
 
+## Guardrails
+
+- Do NOT copy/paste step instructions directly; always use the Skill tool to invoke steps
+- Do NOT skip steps in the workflow unless the user explicitly requests it
+- Do NOT proceed to the next step if the current step's outputs are incomplete
+- Do NOT make assumptions about user intent; ask for clarification when ambiguous
+
 ## Context Files
 
 - Job definition: `.deepwork/jobs/add_platform/job.yml`

{deepwork-0.3.0 → deepwork-0.4.0}/.claude/skills/add_platform.add_capabilities/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add_platform.add_capabilities
-description: "Update job schema and adapters with any new hook events the platform supports"
+description: "Updates job schema and adapters with any new hook events the platform supports. Use after research to extend DeepWork's hook system."
 user-invocable: false
 hooks:
   Stop:
@@ -18,13 +18,28 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
+  SubagentStop:
+    - hooks:
+        - type: prompt
+          prompt: |
+            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>`.
+
 ---
 
 # add_platform.add_capabilities
 
 **Step 2/4** in **add_platform** workflow
 
-> Add a new AI platform to DeepWork with adapter, templates, and tests
+> Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 ## Prerequisites (Verify First)
 
@@ -33,7 +48,7 @@ Before proceeding, confirm these steps are complete:
 
 ## Instructions
 
-**Goal**: Update job schema and adapters with any new hook events the platform supports
+**Goal**: Updates job schema and adapters with any new hook events the platform supports. Use after research to extend DeepWork's hook system.
 
 # Add Hook Capabilities
 
@@ -208,7 +223,16 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## Outputs
 
 **Required outputs**:
-- `job_schema.py`- `adapters.py`
+- `job_schema.py`
+- `adapters.py`
+
+## Guardrails
+
+- Do NOT skip prerequisite verification if this step has dependencies
+- Do NOT produce partial outputs; complete all required outputs before finishing
+- Do NOT proceed without required inputs; ask the user if any are missing
+- Do NOT modify files outside the scope of this step's defined outputs
+
 ## Quality Validation
 
 Stop hooks will automatically validate your work. The loop continues until all criteria pass.

{deepwork-0.3.0 → deepwork-0.4.0}/.claude/skills/add_platform.implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add_platform.implement
-description: "Add platform adapter, templates, tests with 100% coverage, and README documentation"
+description: "Creates platform adapter, templates, tests with 100% coverage, and README documentation. Use after adding hook capabilities."
 user-invocable: false
 hooks:
   Stop:
@@ -22,13 +22,32 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
+  SubagentStop:
+    - hooks:
+        - type: command
+          command: ".deepwork/jobs/add_platform/hooks/run_tests.sh"
+        - type: prompt
+          prompt: |
+            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>`.
+
 ---
 
 # add_platform.implement
 
 **Step 3/4** in **add_platform** workflow
 
-> Add a new AI platform to DeepWork with adapter, templates, and tests
+> Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 ## Prerequisites (Verify First)
 
@@ -38,7 +57,7 @@ Before proceeding, confirm these steps are complete:
 
 ## Instructions
 
-**Goal**: Add platform adapter, templates, tests with 100% coverage, and README documentation
+**Goal**: Creates platform adapter, templates, tests with 100% coverage, and README documentation. Use after adding hook capabilities.
 
 # Implement Platform Support
 
@@ -306,7 +325,17 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## Outputs
 
 **Required outputs**:
-- `templates/` (directory)- `tests/` (directory)- `README.md`
+- `templates/` (directory)
+- `tests/` (directory)
+- `README.md`
+
+## Guardrails
+
+- Do NOT skip prerequisite verification if this step has dependencies
+- Do NOT produce partial outputs; complete all required outputs before finishing
+- Do NOT proceed without required inputs; ask the user if any are missing
+- Do NOT modify files outside the scope of this step's defined outputs
+
 ## Quality Validation
 
 Stop hooks will automatically validate your work. The loop continues until all criteria pass.

{deepwork-0.3.0 → deepwork-0.4.0}/.claude/skills/add_platform.research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add_platform.research
-description: "Capture CLI configuration and hooks system documentation for the new platform"
+description: "Captures CLI configuration and hooks system documentation for the new platform. Use when starting platform integration."
 user-invocable: false
 hooks:
   Stop:
@@ -19,18 +19,34 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
+  SubagentStop:
+    - hooks:
+        - type: prompt
+          prompt: |
+            Verify the research output meets ALL criteria:
+            1. Both files exist in doc/platforms/<platform>/: cli_configuration.md and hooks_system.md
+            2. Each file has a comment at the top with:
+               - Last updated date
+               - Source URL where the documentation was obtained
+            3. cli_configuration.md covers how the platform's CLI is configured
+            4. hooks_system.md covers hooks available for slash command definitions ONLY
+            5. No extraneous documentation (only these two specific topics)
+            6. Documentation is comprehensive enough to implement the platform
+
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
 ---
 
 # add_platform.research
 
 **Step 1/4** in **add_platform** workflow
 
-> Add a new AI platform to DeepWork with adapter, templates, and tests
+> Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 
 ## Instructions
 
-**Goal**: Capture CLI configuration and hooks system documentation for the new platform
+**Goal**: Captures CLI configuration and hooks system documentation for the new platform. Use when starting platform integration.
 
 # Research Platform Documentation
 
@@ -258,7 +274,16 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## Outputs
 
 **Required outputs**:
-- `cli_configuration.md`- `hooks_system.md`
+- `cli_configuration.md`
+- `hooks_system.md`
+
+## Guardrails
+
+- Do NOT skip prerequisite verification if this step has dependencies
+- Do NOT produce partial outputs; complete all required outputs before finishing
+- Do NOT proceed without required inputs; ask the user if any are missing
+- Do NOT modify files outside the scope of this step's defined outputs
+
 ## Quality Validation
 
 Stop hooks will automatically validate your work. The loop continues until all criteria pass.

{deepwork-0.3.0 → deepwork-0.4.0}/.claude/skills/add_platform.verify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: add_platform.verify
-description: "Set up platform directories and verify deepwork install works correctly"
+description: "Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration."
 user-invocable: false
 hooks:
   Stop:
@@ -17,13 +17,27 @@ hooks:
 
             If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
 
+  SubagentStop:
+    - hooks:
+        - type: prompt
+          prompt: |
+            Verify the installation meets ALL criteria:
+            1. Platform-specific directories/files are added to the deepwork repo as needed
+            2. Running `deepwork install --platform <platform>` completes without errors
+            3. Expected command files are created in the platform's command directory
+            4. Command file content matches the templates and job definitions
+            5. Established DeepWork jobs (deepwork_jobs, deepwork_rules) are installed correctly
+            6. The platform can be used alongside existing platforms without conflicts
+
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
 ---
 
 # add_platform.verify
 
 **Step 4/4** in **add_platform** workflow
 
-> Add a new AI platform to DeepWork with adapter, templates, and tests
+> Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 ## Prerequisites (Verify First)
 
@@ -32,7 +46,7 @@ Before proceeding, confirm these steps are complete:
 
 ## Instructions
 
-**Goal**: Set up platform directories and verify deepwork install works correctly
+**Goal**: Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration.
 
 # Verify Installation
 
@@ -182,7 +196,15 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 
 ## Outputs
 
-No specific file outputs required.
+**Required outputs**:
+- `verification_checklist.md`
+
+## Guardrails
+
+- Do NOT skip prerequisite verification if this step has dependencies
+- Do NOT produce partial outputs; complete all required outputs before finishing
+- Do NOT proceed without required inputs; ask the user if any are missing
+- Do NOT modify files outside the scope of this step's defined outputs
 
 ## Quality Validation
 
@@ -195,7 +217,7 @@ Stop hooks will automatically validate your work. The loop continues until all c
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 4/4 complete"
+2. Inform user: "Step 4/4 complete, outputs: verification_checklist.md"
 3. **Workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
 
 ---

deepwork-0.4.0/.claude/skills/commit/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: commit
+description: "Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks."
+---
+
+# commit
+
+**Multi-step workflow**: Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
+
+> **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
+
+A workflow for preparing and committing code changes with quality checks.
+
+This job starts with a code review to catch issues early, runs tests until
+they pass, formats and lints code with ruff, then reviews changed files
+before committing and pushing. The review and lint steps use sub-agents
+to reduce context usage.
+
+Steps:
+1. review - Code review for issues, DRY opportunities, naming, and test coverage (runs in sub-agent)
+2. test - Pull latest code and run tests until they pass
+3. lint - Format and lint code with ruff (runs in sub-agent)
+4. commit_and_push - Review changes and commit/push
+
+
+## Available Steps
+
+1. **review** - Reviews changed code for issues, DRY opportunities, naming clarity, and test coverage using a sub-agent. Use as the first step before testing.
+2. **test** - Pulls latest code and runs tests until all pass. Use after code review passes to verify changes work correctly. (requires: review)
+3. **lint** - Formats and lints code with ruff using a sub-agent. Use after tests pass to ensure code style compliance. (requires: test)
+4. **commit_and_push** - Verifies changed files, creates commit, and pushes to remote. Use after linting passes to finalize changes. (requires: lint)
+
+## Execution Instructions
+
+### Step 1: Analyze Intent
+
+Parse any text following `/commit` to determine user intent:
+- "review" or related terms → start at `commit.review`
+- "test" or related terms → start at `commit.test`
+- "lint" or related terms → start at `commit.lint`
+- "commit_and_push" or related terms → start at `commit.commit_and_push`
+
+### Step 2: Invoke Starting Step
+
+Use the Skill tool to invoke the identified starting step:
+```
+Skill tool: commit.review
+```
+
+### 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
+
+## Guardrails
+
+- Do NOT copy/paste step instructions directly; always use the Skill tool to invoke steps
+- Do NOT skip steps in the workflow unless the user explicitly requests it
+- Do NOT proceed to the next step if the current step's outputs are incomplete
+- Do NOT make assumptions about user intent; ask for clarification when ambiguous
+
+## Context Files
+
+- Job definition: `.deepwork/jobs/commit/job.yml`

deepwork-0.4.0/.claude/skills/commit.commit_and_push/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: commit.commit_and_push
+description: "Verifies changed files, creates commit, and pushes to remote. Use after linting passes to finalize changes."
+user-invocable: false
+hooks:
+  Stop:
+    - hooks:
+        - type: prompt
+          prompt: |
+            Verify the commit is ready:
+            1. Changed files list was reviewed by the agent
+            2. Files match what was modified during this session (or unexpected changes were investigated)
+            3. Commit was created with appropriate message
+            4. Changes were pushed to remote
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
+  SubagentStop:
+    - hooks:
+        - type: prompt
+          prompt: |
+            Verify the commit is ready:
+            1. Changed files list was reviewed by the agent
+            2. Files match what was modified during this session (or unexpected changes were investigated)
+            3. Commit was created with appropriate message
+            4. Changes were pushed to remote
+            If ALL criteria are met, include `<promise>✓ Quality Criteria Met</promise>`.
+
+---
+
+# commit.commit_and_push
+
+**Step 4/4** in **commit** workflow
+
+> Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
+
+## Prerequisites (Verify First)
+
+Before proceeding, confirm these steps are complete:
+- `/commit.lint`
+
+## Instructions
+
+**Goal**: Verifies changed files, creates commit, and pushes to remote. Use after linting passes to finalize changes.
+
+# Commit and Push
+
+## Objective
+
+Review the changed files to verify they match the agent's expectations, create a commit with an appropriate message, and push to the remote repository.
+
+## Task
+
+Check the list of changed files against what was modified during this session, ensure they match expectations, then commit and push the changes.
+
+### Process
+
+1. **Get the list of changed files**
+   ```bash
+   git status
+   ```
+   Also run `git diff --stat` to see a summary of changes.
+
+2. **Verify changes match expectations**
+
+   Compare the changed files against what you modified during this session:
+   - Do the modified files match what you edited?
+   - Are there any unexpected new files?
+   - Are there any unexpected deleted files?
+   - Do the line counts seem reasonable for the changes you made?
+
+   If changes match expectations, proceed to commit.
+
+   If there are unexpected changes:
+   - Investigate why (e.g., lint auto-fixes, generated files)
+   - If they're legitimate side effects of your work, include them
+   - If they're unrelated or shouldn't be committed, use `git restore` to discard them
+
+3. **Stage all appropriate changes**
+   ```bash
+   git add -A
+   ```
+   Or stage specific files if some were excluded.
+
+5. **View recent commit messages for style reference**
+   ```bash
+   git log --oneline -10
+   ```
+
+6. **Create the commit**
+
+   Generate an appropriate commit message based on:
+   - The changes made
+   - The style of recent commits
+   - Conventional commit format if the project uses it
+
+   ```bash
+   git commit -m "commit message here"
+   ```
+
+7. **Push to remote**
+   ```bash
+   git push
+   ```
+   If the branch has no upstream, use:
+   ```bash
+   git push -u origin HEAD
+   ```
+
+## Quality Criteria
+
+- Changed files list was reviewed by the agent
+- Files match what was modified during this session (or unexpected changes were investigated and handled)
+- Commit message follows project conventions
+- Commit was created successfully
+- Changes were pushed to remote
+- When all criteria are met, include `<promise>✓ Quality Criteria Met</promise>` in your response
+
+## Context
+
+This is the final step of the commit workflow. The agent verifies that the changed files match its own expectations from the work done during the session, then commits and pushes. This catches unexpected changes while avoiding unnecessary user interruptions.
+
+
+### Job Context
+
+A workflow for preparing and committing code changes with quality checks.
+
+This job starts with a code review to catch issues early, runs tests until
+they pass, formats and lints code with ruff, then reviews changed files
+before committing and pushing. The review and lint steps use sub-agents
+to reduce context usage.
+
+Steps:
+1. review - Code review for issues, DRY opportunities, naming, and test coverage (runs in sub-agent)
+2. test - Pull latest code and run tests until they pass
+3. lint - Format and lint code with ruff (runs in sub-agent)
+4. commit_and_push - Review changes and commit/push
+
+
+
+## Work Branch
+
+Use branch format: `deepwork/commit-[instance]-YYYYMMDD`
+
+- If on a matching work branch: continue using it
+- If on main/master: create new branch with `git checkout -b deepwork/commit-[instance]-$(date +%Y%m%d)`
+
+## Outputs
+
+**Required outputs**:
+- `changes_committed`
+
+## Guardrails
+
+- Do NOT skip prerequisite verification if this step has dependencies
+- Do NOT produce partial outputs; complete all required outputs before finishing
+- Do NOT proceed without required inputs; ask the user if any are missing
+- Do NOT modify files outside the scope of this step's defined outputs
+
+## Quality Validation
+
+Stop hooks will automatically validate your work. The loop continues until all criteria pass.
+
+
+
+**To complete**: Include `<promise>✓ Quality Criteria Met</promise>` in your final response only after verifying ALL criteria are satisfied.
+
+## On Completion
+
+1. Verify outputs are created
+2. Inform user: "Step 4/4 complete, outputs: changes_committed"
+3. **Workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
+
+---
+
+**Reference files**: `.deepwork/jobs/commit/job.yml`, `.deepwork/jobs/commit/steps/commit_and_push.md`