fix: address review findings from first review pass

- Remove unnecessary `gh repo edit` command from new_user skill
- Add new_user/ and record/ to skill directory listings in CLAUDE.md
  and doc/architecture.md
- Fix incorrect requirement ID mapping in record DeepSchema
  (workflow-name-prompt was mistagged as PLUG-REQ-002.1.1)
- Add PLUG-REQ-002.7 requirement for learn-after-record redirect
- Update CHANGELOG.md with unreleased changes

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: nhorton

CHANGELOG.md

@@ -9,8 +9,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- `/record` skill: "watch and learn" approach to creating DeepWork workflows — users do their work normally, then `/deepwork learn` turns it into a repeatable job
+- `/new_user` skill: guided onboarding that introduces DeepWork, offers review rule setup for code projects, and offers to record a first workflow
+- `/deepwork learn` now routes to the `new_job` workflow 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`
+
 ### Fixed
 
 ### Removed

doc/architecture.md

@@ -113,6 +113,8 @@ deepwork/                       # DeepWork tool repository
 │   │   │   ├── deepreviews/SKILL.md
 │   │   │   ├── deepwork/SKILL.md
 │   │   │   ├── deepschema/SKILL.md
+│   │   │   ├── new_user/SKILL.md
+│   │   │   ├── record/SKILL.md
 │   │   │   └── review/SKILL.md
 │   │   ├── hooks/              # hooks.json, post_commit_reminder.sh, post_compact.sh, startup_context.sh, deepschema_write.sh
 │   │   └── .mcp.json           # MCP server config

plugins/claude/skills/new_user/SKILL.md

@@ -21,7 +21,7 @@ If `gh` is available, use `AskUserQuestion` to say something like:
 If they agree, run:
 
 ```bash
-gh repo edit Unsupervisedcom/deepwork --visibility public 2>/dev/null; gh api -X PUT /user/starred/Unsupervisedcom/deepwork
+gh api -X PUT /user/starred/Unsupervisedcom/deepwork
 ```
 
 If `gh` is not installed, skip this entirely — do not mention it.

plugins/claude/skills/record/.deepschema.SKILL.md.yml

@@ -10,7 +10,7 @@ requirements:
     If the user agrees to star the repo, the skill MUST run
     `gh api -X PUT /user/starred/Unsupervisedcom/deepwork`.
 
-  # PLUG-REQ-002.1.1
+  # PLUG-REQ-002.3.1 (workflow name collection is part of the handoff flow)
   workflow-name-prompt: >
     The skill MUST ask the user for a workflow name before proceeding.
 

specs/deepwork/cli_plugins/PLUG-REQ-002-record-skill.md

@@ -44,3 +44,9 @@ This skill targets new users who know *what* they want to automate but haven't y
 2. If `gh` is available, the skill MUST use `AskUserQuestion` to offer to star the DeepWork repo on GitHub so the user gets update notifications.
 3. If the user agrees, the skill MUST run `gh api -X PUT /user/starred/Unsupervisedcom/deepwork`.
 4. If `gh` is not installed, the skill MUST skip this step entirely without mentioning it.
+
+### PLUG-REQ-002.7: Learn After Record Redirect
+
+1. When `/deepwork learn` is invoked in a conversation where `/deepwork:record` was used, the `/deepwork` skill MUST start the `new_job` workflow (`job_name: "deepwork_jobs"`, `workflow_name: "new_job"`) instead of the `learn` workflow.
+2. The `learn` step in the `deepwork_jobs` standard job MUST check for a prior `/deepwork:record` invocation and redirect to `new_job` if found.
+3. The conversation history from the recording session MUST be used as the primary input for defining the new job's steps, inputs, and outputs.