Releases: Unsupervisedcom/deepwork
Releases · Unsupervisedcom/deepwork
0.13.3
Added
/recordskill: "watch and learn" approach to creating DeepWork workflows — users do their work normally, then/deepwork learnturns it into a repeatable job/new_userskill: guided onboarding that introduces DeepWork, offers review rule setup for code projects, and offers to record a first workflow/deepwork learnnow routes to thenew_jobworkflow when invoked after/deepwork:record- Requirements specs PLUG-REQ-002 (record skill) and PLUG-REQ-003 (new user skill)
- Anonymous DeepSchemas for both new skills
Changed
- README install commands consolidated into a single
&&-joined command ending with/deepwork:new_user deepwork setupnow openshttps://www.deepwork.md/successin the default browser after completing configuration
Fixed
Removed
0.13.2
Added
deepwork setupCLI command that auto-configures Claude Code settings (marketplace, plugin, MCP permissions, auto-update) (#343)deepwork setupalso grants project-root-relativeRead/Write/Editpermissions for/.deepwork/**/*so the plugin can operate on.deepwork/in every project without per-prompt approval- Integration tests for quality gate review caching (JOBS-REQ-004.5.7)
- Requirements traceability coverage now at 100% (#346)
- Added section-level REQ ID annotations to 32 existing test files for traceability
- Wrote 218 new tests across 5 files for learning-agents requirements (LA-REQ-001, 003, 004, 005, 006, 010, 011)
- Added 6 anonymous DeepSchemas for judgment-based learning-agents skill requirements (LA-REQ-002, 007, 008, 009, 012)
- Added new PLUG-REQ-001.12 tests for session/agent identity injection hooks
- New
req-ids-in-commentsrequirement in the standard DeepSchema definition: requirement IDs must be placed in YAML comments, not requirement body text
Changed
- JOBS-REQ-004.5.7 strengthened to explicit MUST requirement for skipping already-passed reviews
Fixed
- DeepSchema PostToolUse hook (
deepschema_write) no longer reportsFile is not valid JSONfor YAML files whose name has no extension (e.g..deepreview). The hook now parses target files and the referenced JSON Schema as YAML, which is a superset of JSON, so both formats are accepted regardless of file extension. DW-REQ-011.7.3 updated to match. (Mirrors the fix shipped in #338 for the workflow quality gate.) review:blocks declared ontype: stringstep outputs are now actually executed. Previously they were silently dropped because the review pipeline only matched against file paths, leaving authors with misconfigured-but-silent quality gates. String output reviews now produce syntheticReviewTaskobjects with the string value carried on a newReviewTask.inline_contentfield and rendered into the instruction file as a "Content to Review" section. New requirements: JOBS-REQ-004.8, REVIEW-REQ-005.1.8, REVIEW-REQ-009.1.7. (#350)
Removed
0.13.1
0.13.0
Added
- Add DeepPlan — structured planning workflow that produces executable DeepWork job definitions (#331)
- New
deepplanstandard job withcreate_deep_planworkflow (5 steps: explore, design alternatives, synthesize, enrich, present) - New
register_session_jobandget_session_jobMCP tools for transient session-scoped job definitions - New
/deepplanskill for Claude Code plugin - Startup context hook auto-triggers DeepPlan when entering plan mode
- Session jobs are discoverable by
start_workflowand take priority over standard discovery
- New
/reviewskill now checks changelog accuracy and PR description during reviews (#331).deepreviewrules can now declare aprecomputed_info_for_reviewer_bash_commandthat runs before the review and injects stdout into the instruction file as precomputed context (#337)- Commands run in parallel across rules with a 60-second timeout and graceful error handling
- Applied to
requirements_traceabilityandpython_lintrules to eliminate redundant agent tool calls
- New
deepreviewstandard DeepSchema with semantic quality requirements for.deepreviewconfig files (#337) Makefilewithlinttarget that auto-fixes formatting/linting and runs type checking (#337)
Changed
Fixed
- Quality gate
validate_json_schemas()now usesyaml.safe_load(a JSON superset) instead ofjson.loads, so YAML output files are validated correctly