Support for policies

.claude/commands/AGENTS.md

@@ -0,0 +1,5 @@
+# Auto-Generated Commands
+
+All command files in this directory are auto-generated by `deepwork-sync` and should not be manually edited. Changes will be overwritten on the next sync.
+
+If you need to modify a command, update the source configuration and re-run the sync process.

.claude/commands/deepwork_jobs.define.md

@@ -329,7 +329,6 @@ After creating the file:
 - Description provides rich context for future refinement
 - Specification is valid YAML and follows the schema
 - Ready for implementation step
-- Output artifacts have quality criteria defined
 
 
 ## Inputs
@@ -364,18 +363,24 @@ Create the following output(s) in the work directory:
 - `deepwork/deepwork_jobs/job.yml`
 Ensure all outputs are:
 - Well-formatted and complete
+- Committed to the work branch
 - Ready for review or use by subsequent steps
 
 ## Completion
 
 After completing this step:
 
-1. **Verify outputs**: Confirm all required files have been created
+1. **Commit your work**:
+   ```bash
+   git add deepwork/deepwork_jobs/
+   git commit -m "deepwork_jobs: Complete define step"
+   ```
+
+2. **Verify outputs**: Confirm all required files have been created
 
-2. **Inform the user**:
-   - Step 1 of 2 is complete
+3. **Inform the user**:
+   - Step 1 of 3 is complete
    - Outputs created: job.yml
-   - They should review the job.yml file before proceeding
    - Ready to proceed to next step: `/deepwork_jobs.implement`
 
 ## Next Step

.claude/commands/deepwork_jobs.implement.md

@@ -380,8 +380,8 @@ Before marking this step complete, ensure:
 - [ ] Registry updated with new job
 - [ ] `deepwork sync` executed successfully
 - [ ] Commands generated in platform directory
-- [ ] Reload the slash commmands so the user can use them immediately if the current CLI requires it
 - [ ] User informed of next steps (reload commands)
+- [ ] implementation_summary.md created
 
 ## Quality Criteria
 
@@ -430,19 +430,25 @@ Create the following output(s) in the work directory:
 - `deepwork/deepwork_jobs/implementation_summary.md`
 Ensure all outputs are:
 - Well-formatted and complete
+- Committed to the work branch
 - Ready for review or use by subsequent steps
 
 ## Completion
 
 After completing this step:
 
-1. **Verify outputs**: Confirm all required files have been created
+1. **Commit your work**:
+   ```bash
+   git add deepwork/deepwork_jobs/
+   git commit -m "deepwork_jobs: Complete implement step"
+   ```
+
+2. **Verify outputs**: Confirm all required files have been created
 
-2. **Inform the user**:
-   - All steps are complete
-   - They should review the generated files before proceeding
-   - Suggest that before they try the job, they should commit the changes so far.
-   - Remind them what the first command for their new job will be to run it
+3. **Inform the user**:
+   - Step 2 of 3 is complete
+   - Outputs created: implementation_summary.md
+   - Ready to proceed to next step: `/deepwork_jobs.refine`
 
 ## Next Step
 

.claude/commands/deepwork_jobs.refine.md

@@ -4,7 +4,7 @@ description: Modify an existing job definition
 
 # deepwork_jobs.refine
 
-**Step 3 of 3** in the **deepwork_jobs** workflow
+**Standalone command** in the **deepwork_jobs** job - can be run anytime
 
 **Summary**: DeepWork job management commands
 
@@ -439,31 +439,38 @@ All work for this job should be done on a dedicated work branch:
 
 ## Output Requirements
 
-**No separate output file is created**. All changes are made directly to:
-- `.deepwork/jobs/[job_name]/job.yml` (updated with new version and changelog entry)
-- `.deepwork/jobs/[job_name]/steps/[step_id].md` (if step instructions are modified)
-- Any new step instruction files created
+Create the following output(s) in the work directory:
+- `deepwork/deepwork_jobs/job.yml`
+Ensure all outputs are:
+- Well-formatted and complete
+- Committed to the work branch
+- Ready for review or use by subsequent steps
 
 ## Completion
 
 After completing this step:
 
-1. **Verify outputs**: Confirm all required files have been created
+1. **Commit your work**:
+   ```bash
+   git add deepwork/deepwork_jobs/
+   git commit -m "deepwork_jobs: Complete refine step"
+   ```
+
+2. **Verify outputs**: Confirm all required files have been created
 
-2. **Inform the user**:
-   - Step 3 of 3 is complete
-   - Changes made to job.yml with updated version and changelog
-   - They should review the updated job.yml file before proceeding
-   - This is the final step - the job is complete!
+3. **Inform the user**:
+   - The refine command is complete
+   - Outputs created: job.yml
+   - This command can be run again anytime to make further changes
 
-## Workflow Complete
+## Command Complete
 
-This is the final step in the deepwork_jobs workflow. All outputs should now be complete and ready for review.
+This is a standalone command that can be run anytime. The outputs are ready for use.
 
 Consider:
-- Reviewing all work products in `deepwork/deepwork_jobs/`
-- Creating a pull request to merge the work branch
-- Documenting any insights or learnings
+- Reviewing the outputs in `deepwork/deepwork_jobs/`
+- Running `deepwork sync` if job definitions were changed
+- Re-running this command later if further changes are needed
 
 ---