Conversation
…rovement 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 appropriate working folder. Key features: - Analyzes conversation for DeepWork job executions - Classifies learnings as generalizable (→ instructions) or bespoke (→ AGENTS.md) - Uses file references in AGENTS.md to keep things in sync - Creates learning_summary.md documenting all changes Changes: - Removed refine step from deepwork_jobs - Added learn step with comprehensive instructions - Updated job version to 0.2.0 - Regenerated all command files
…ction Updates to the learn command: - Simplified working folder identification (use conversation history, fall back to git diff) - Added quality criteria for instruction conciseness (no redundancy/verbosity) - Added Step 4b for extracting shared/lengthy content into referenced files - Instructions can now reference shared files in steps/shared/ directory This helps keep job instructions maintainable and DRY.
Contributor
|
All contributors have signed the CLA. ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 15, 2026
* Fix CLA signatures file format
Replace Markdown with JSON array - CLA Assistant action
expects JSON format for storing signatures.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fix CLA signatures JSON structure
CLA Assistant expects { "signedContributors": [] } format,
not a plain array.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Remove manually created signatures file
Per CLA Assistant docs: "You do not need to create this file manually.
Our workflow will create the signature file if it does not already exist.
Manually creating this file will cause the workflow to fail."
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Creating file for storing CLA Signatures
* @nhorton has signed the CLA in #27
* @tylerwillis has signed the CLA in #31
* Add automated CI test for Claude Code integration
Add a deterministic 'fruits' test job and comprehensive CI tests to validate
that deepwork-generated commands work correctly with Claude Code.
Changes:
- Add fruits job fixture (identify + classify steps) for CI testing
- Add integration tests for fruits workflow (8 tests)
- Add e2e tests for Claude Code execution (3 tests, skipped without API key)
- Add GitHub Actions workflow for automated testing:
- validate-generation: Always runs, tests command generation
- claude-code-e2e: Runs with ANTHROPIC_API_KEY, tests actual execution
The fruits job is designed to be deterministic:
- Input: comma-separated list of items (e.g., "apple, car, banana")
- Step 1: Identify which items are fruits
- Step 2: Classify fruits by category (citrus, tropical, etc.)
* Fix CI workflow: use deepwork install with --path, add concurrency rules
- Add concurrency rules to ensure only one instance runs per PR
- Fix test to use 'deepwork install --platform claude --path test_project'
- Create .claude directory before install for platform detection
- Run commands from repo root with --path flag instead of cd'ing
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
nhorton
added a commit
that referenced
this pull request
Jan 15, 2026
* Fix CLA signatures file format
Replace Markdown with JSON array - CLA Assistant action
expects JSON format for storing signatures.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fix CLA signatures JSON structure
CLA Assistant expects { "signedContributors": [] } format,
not a plain array.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Remove manually created signatures file
Per CLA Assistant docs: "You do not need to create this file manually.
Our workflow will create the signature file if it does not already exist.
Manually creating this file will cause the workflow to fail."
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Creating file for storing CLA Signatures
* @nhorton has signed the CLA in #27
* @tylerwillis has signed the CLA in #31
* Add automated CI test for Claude Code integration
Add a deterministic 'fruits' test job and comprehensive CI tests to validate
that deepwork-generated commands work correctly with Claude Code.
Changes:
- Add fruits job fixture (identify + classify steps) for CI testing
- Add integration tests for fruits workflow (8 tests)
- Add e2e tests for Claude Code execution (3 tests, skipped without API key)
- Add GitHub Actions workflow for automated testing:
- validate-generation: Always runs, tests command generation
- claude-code-e2e: Runs with ANTHROPIC_API_KEY, tests actual execution
The fruits job is designed to be deterministic:
- Input: comma-separated list of items (e.g., "apple, car, banana")
- Step 1: Identify which items are fruits
- Step 2: Classify fruits by category (citrus, tropical, etc.)
* Fix CI workflow: use deepwork install with --path, add concurrency rules
- Add concurrency rules to ensure only one instance runs per PR
- Fix test to use 'deepwork install --platform claude --path test_project'
- Create .claude directory before install for platform detection
- Run commands from repo root with --path flag instead of cd'ing
* Add full e2e test: define -> implement -> execute workflow
Update the claude-code-e2e job to test the COMPLETE DeepWork workflow:
1. /deepwork_jobs.define - Create a new job from scratch
2. /deepwork_jobs.implement - Generate step instruction files
3. /fruits.identify - Execute the generated identify command
4. /fruits.classify - Execute the generated classify command
This tests the actual user experience rather than just validating
pre-existing fixtures. The test provides deterministic instructions
for creating a 'fruits' job with identify and classify steps.
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
nhorton
added a commit
that referenced
this pull request
Jan 15, 2026
* Fix CLA signatures file format
Replace Markdown with JSON array - CLA Assistant action
expects JSON format for storing signatures.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fix CLA signatures JSON structure
CLA Assistant expects { "signedContributors": [] } format,
not a plain array.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Remove manually created signatures file
Per CLA Assistant docs: "You do not need to create this file manually.
Our workflow will create the signature file if it does not already exist.
Manually creating this file will cause the workflow to fail."
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Creating file for storing CLA Signatures
* @nhorton has signed the CLA in #27
* @tylerwillis has signed the CLA in #31
* Fix CI workflow to run on all PRs
Remove the `branches: ["*"]` filter from the pull_request trigger.
The glob pattern `*` doesn't match `/`, so PRs targeting branches
with slashes (like feature/...) were not triggering the workflow.
By removing the filter, the workflow now runs on all PRs regardless
of target branch, while still not running on post-merge to main
(since there's no push trigger).
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
nhorton
added a commit
that referenced
this pull request
Jan 15, 2026
* Fix CLA signatures file format
Replace Markdown with JSON array - CLA Assistant action
expects JSON format for storing signatures.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Fix CLA signatures JSON structure
CLA Assistant expects { "signedContributors": [] } format,
not a plain array.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Remove manually created signatures file
Per CLA Assistant docs: "You do not need to create this file manually.
Our workflow will create the signature file if it does not already exist.
Manually creating this file will cause the workflow to fail."
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Creating file for storing CLA Signatures
* @nhorton has signed the CLA in #27
* @tylerwillis has signed the CLA in #31
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.