Skip to content

Conversation

@nhorton
Copy link
Contributor

@nhorton nhorton commented Feb 1, 2026

Summary

  • Migrated jobs system to workflows within experts
  • Jobs are now defined as workflows inside expert directories
  • Removed standalone deepwork_jobs expert - merged into experts expert
  • Added review_pr workflow for expert-driven PR reviews
  • Updated schema from job.yml to workflow.yml
  • Updated all tests and documentation

Test plan

  • All 630 tests pass
  • deepwork install creates correct skills
  • /experts.new_workflow works for creating new workflows
  • /experts.review_pr works for PR review

🤖 Generated with Claude Code

nhorton and others added 13 commits January 30, 2026 15:56
Add specification for the experts system - auto-improving collections of
domain knowledge that get exposed as Claude agents.

- Add doc/experts_requirements.md with full specification:
  - Directory structure (.deepwork/experts/[name]/)
  - File formats (expert.yml, topics/*.md, learnings/*.md)
  - CLI commands (deepwork topics, deepwork learnings)
  - Sync behavior (generates agents in .claude/agents/)

- Add initial "experts" standard expert in src/deepwork/standard/experts/:
  - Meta-expert for the experts system itself
  - Topics on design patterns and discovery descriptions

- Update doc/architecture.md:
  - Add src/deepwork/standard/ directory to structure diagram
  - Add "Experts (Planned)" section

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Remove "(Planned)" from section heading and update status to reflect
that the experts system implementation is now complete.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Add `agent: deepwork-jobs` to all 4 steps in deepwork_jobs job.yml
- Remove misleading "Prerequisites" documentation from step files
- Create new step_delegation.md topic explaining how to use expert delegation
- Update job_yml_schema.md with "Agent Delegation" section
- Key insight: "This is how you make a step 'run via' an expert"

The deepwork_jobs steps now properly delegate to the deepwork-jobs expert,
giving them access to job schema knowledge, best practices, and learnings.

Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Add new review_pr job with 3 steps: check_relevance, deep_review, improve_and_rereview
- Use inline bash completion $(gh pr diff) for efficient token usage in expert prompts
- Experts focus only on their domain expertise for specialized feedback
- Iterative improvement cycles until all experts approve or 3 max iterations
- Add learnings: domain focus in expert prompts, efficiency improvements
- Code cleanup: remove redundant try/except and unused context variables
- Include PR review output files from workflow execution

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Jobs are now workflows inside experts. Each expert is a complete package:
expertise + topics + learnings + workflows.

Changes:
- deepwork_jobs expert merged into experts expert (new_workflow, learn, review_pr)
- deepwork_rules job became deepwork-rules expert with define workflow
- Schema renamed: job_schema.py → workflow_schema.py
- Templates renamed: skill-job-*.jinja → skill-workflow-*.jinja
- Added path traversal protection for script/prompt_file paths
- Fixed potential IndexError in hooks_syncer

BREAKING: Skill naming changed to use expert name:
- /deepwork-jobs.define → /experts.define
- /review_pr.* → /experts.review_pr, /experts.deep_review, etc.
- /deepwork-rules.define (unchanged structure, new expert)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants