Restructure skills to distinguish workflows from standalone skills

.claude/skills/add_platform.add_capabilities/SKILL.md

@@ -4,7 +4,9 @@ description: "Updates job schema and adapters with any new hook events the platf
 
 # add_platform.add_capabilities
 
-**Step 2/4** in **add_platform** workflow
+**Step 2/4** in **integrate** workflow
+
+> Full workflow to integrate a new AI platform into DeepWork
 
 > Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
@@ -158,7 +160,7 @@ When you find a new hook type, consider whether it maps to an existing pattern o
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
+The **integrate** workflow guides you through four phases:
 1. **Research**: Capture the platform's CLI configuration and hooks system documentation
 2. **Add Capabilities**: Update the job schema and adapters with any new hook events
 3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
@@ -203,7 +205,7 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 2/4 complete, outputs: job_schema.py, adapters.py"
+2. Inform user: "integrate step 2/4 complete, outputs: job_schema.py, adapters.py"
 3. **Continue workflow**: Use Skill tool to invoke `/add_platform.implement`
 
 ---

.claude/skills/add_platform.implement/SKILL.md

@@ -8,7 +8,9 @@ description: "Creates platform adapter, templates, tests with 100% coverage, and
 
 # add_platform.implement
 
-**Step 3/4** in **add_platform** workflow
+**Step 3/4** in **integrate** workflow
+
+> Full workflow to integrate a new AI platform into DeepWork
 
 > Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
@@ -254,7 +256,7 @@ The templates use Jinja2 and should produce files that match exactly what the pl
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
+The **integrate** workflow guides you through four phases:
 1. **Research**: Capture the platform's CLI configuration and hooks system documentation
 2. **Add Capabilities**: Update the job schema and adapters with any new hook events
 3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
@@ -303,7 +305,7 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 3/4 complete, outputs: templates/, tests/, README.md"
+2. Inform user: "integrate step 3/4 complete, outputs: templates/, tests/, README.md"
 3. **Continue workflow**: Use Skill tool to invoke `/add_platform.verify`
 
 ---

.claude/skills/add_platform.research/SKILL.md

@@ -4,7 +4,9 @@ description: "Captures CLI configuration and hooks system documentation for the
 
 # add_platform.research
 
-**Step 1/4** in **add_platform** workflow
+**Step 1/4** in **integrate** workflow
+
+> Full workflow to integrate a new AI platform into DeepWork
 
 > Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
@@ -207,7 +209,7 @@ Take time to be thorough - incomplete documentation will slow down subsequent st
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
+The **integrate** workflow guides you through four phases:
 1. **Research**: Capture the platform's CLI configuration and hooks system documentation
 2. **Add Capabilities**: Update the job schema and adapters with any new hook events
 3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
@@ -252,7 +254,7 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 1/4 complete, outputs: cli_configuration.md, hooks_system.md"
+2. Inform user: "integrate step 1/4 complete, outputs: cli_configuration.md, hooks_system.md"
 3. **Continue workflow**: Use Skill tool to invoke `/add_platform.add_capabilities`
 
 ---

.claude/skills/add_platform.verify/SKILL.md

@@ -4,7 +4,9 @@ description: "Sets up platform directories and verifies deepwork install works c
 
 # add_platform.verify
 
-**Step 4/4** in **add_platform** workflow
+**Step 4/4** in **integrate** workflow
+
+> Full workflow to integrate a new AI platform into DeepWork
 
 > Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
@@ -134,7 +136,7 @@ Take time to verify each aspect - finding issues now is much better than having
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
+The **integrate** workflow guides you through four phases:
 1. **Research**: Capture the platform's CLI configuration and hooks system documentation
 2. **Add Capabilities**: Update the job schema and adapters with any new hook events
 3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
@@ -178,8 +180,8 @@ Use branch format: `deepwork/add_platform-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 4/4 complete, outputs: verification_checklist.md"
-3. **Workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
+2. Inform user: "integrate step 4/4 complete, outputs: verification_checklist.md"
+3. **integrate workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
 
 ---
 

.claude/skills/add_platform/SKILL.md

@@ -5,13 +5,13 @@ description: "Adds a new AI platform to DeepWork with adapter, templates, and te
 
 # add_platform
 
-**Multi-step workflow**: Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
+Adds a new AI platform to DeepWork with adapter, templates, and tests. Use when integrating Cursor, Windsurf, or other AI coding tools.
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
+The **integrate** workflow guides you through four phases:
 1. **Research**: Capture the platform's CLI configuration and hooks system documentation
 2. **Add Capabilities**: Update the job schema and adapters with any new hook events
 3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
@@ -27,22 +27,27 @@ comprehensive test coverage for new functionality.
 - Installation verification confirms the platform integrates correctly with existing jobs
 
 
-## Available Steps
+## Workflows
 
+### integrate
+
+Full workflow to integrate a new AI platform into DeepWork
+
+**Steps in order**:
 1. **research** - Captures CLI configuration and hooks system documentation for the new platform. Use when starting platform integration.
-2. **add_capabilities** - Updates job schema and adapters with any new hook events the platform supports. Use after research to extend DeepWork's hook system. (requires: research)
-3. **implement** - Creates platform adapter, templates, tests with 100% coverage, and README documentation. Use after adding hook capabilities. (requires: research, add_capabilities)
-4. **verify** - Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration. (requires: implement)
+2. **add_capabilities** - Updates job schema and adapters with any new hook events the platform supports. Use after research to extend DeepWork's hook system.
+3. **implement** - Creates platform adapter, templates, tests with 100% coverage, and README documentation. Use after adding hook capabilities.
+4. **verify** - Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration.
+
+**Start workflow**: `/add_platform.research`
+
 
 ## Execution Instructions
 
 ### Step 1: Analyze Intent
 
 Parse any text following `/add_platform` to determine user intent:
-- "research" or related terms → start at `add_platform.research`
-- "add_capabilities" or related terms → start at `add_platform.add_capabilities`
-- "implement" or related terms → start at `add_platform.implement`
-- "verify" or related terms → start at `add_platform.verify`
+- "integrate" or related terms → start integrate workflow at `add_platform.research`
 
 ### Step 2: Invoke Starting Step
 
@@ -54,20 +59,22 @@ Skill tool: add_platform.research
 ### Step 3: Continue Workflow Automatically
 
 After each step completes:
-1. Check if there's a next step in the sequence
+1. Check if there's a next step in the workflow sequence
 2. Invoke the next step using the Skill tool
 3. Repeat until workflow is complete or user intervenes
 
+**Note**: Standalone skills do not auto-continue to other steps.
+
 ### Handling Ambiguous Intent
 
 If user intent is unclear, use AskUserQuestion to clarify:
-- Present available steps as numbered options
+- Present available workflows and standalone skills as options
 - Let user select the starting point
 
 ## Guardrails
 
 - Do NOT copy/paste step instructions directly; always use the Skill tool to invoke steps
-- Do NOT skip steps in the workflow unless the user explicitly requests it
+- Do NOT skip steps in a workflow unless the user explicitly requests it
 - Do NOT proceed to the next step if the current step's outputs are incomplete
 - Do NOT make assumptions about user intent; ask for clarification when ambiguous
 

.claude/skills/commit.commit_and_push/SKILL.md

@@ -4,7 +4,9 @@ description: "Verifies changed files, creates commit, and pushes to remote. Use
 
 # commit.commit_and_push
 
-**Step 4/4** in **commit** workflow
+**Step 4/4** in **full** workflow
+
+> Full commit workflow: review, test, lint, and commit
 
 > Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
 
@@ -115,7 +117,7 @@ This is the final step of the commit workflow. The agent verifies that the chang
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job starts with a code review to catch issues early, runs tests until
+The **full** workflow starts with a code review to catch issues early, runs tests until
 they pass, formats and lints code with ruff, then reviews changed files
 before committing and pushing. The review and lint steps use sub-agents
 to reduce context usage.
@@ -150,8 +152,8 @@ Use branch format: `deepwork/commit-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 4/4 complete, outputs: changes_committed"
-3. **Workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
+2. Inform user: "full step 4/4 complete, outputs: changes_committed"
+3. **full workflow complete**: All steps finished. Consider creating a PR to merge the work branch.
 
 ---
 

.claude/skills/commit.lint/SKILL.md

@@ -4,7 +4,9 @@ description: "Formats and lints code with ruff using a sub-agent. Use after test
 
 # commit.lint
 
-**Step 3/4** in **commit** workflow
+**Step 3/4** in **full** workflow
+
+> Full commit workflow: review, test, lint, and commit
 
 > Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
 
@@ -95,7 +97,7 @@ This step ensures code quality and consistency before committing. It runs after
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job starts with a code review to catch issues early, runs tests until
+The **full** workflow starts with a code review to catch issues early, runs tests until
 they pass, formats and lints code with ruff, then reviews changed files
 before committing and pushing. The review and lint steps use sub-agents
 to reduce context usage.
@@ -130,7 +132,7 @@ Use branch format: `deepwork/commit-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 3/4 complete, outputs: code_formatted"
+2. Inform user: "full step 3/4 complete, outputs: code_formatted"
 3. **Continue workflow**: Use Skill tool to invoke `/commit.commit_and_push`
 
 ---

.claude/skills/commit.review/SKILL.md

@@ -4,7 +4,9 @@ description: "Reviews changed code for issues, DRY opportunities, naming clarity
 
 # commit.review
 
-**Step 1/4** in **commit** workflow
+**Step 1/4** in **full** workflow
+
+> Full commit workflow: review, test, lint, and commit
 
 > Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
 
@@ -124,7 +126,7 @@ This is the first step of the commit workflow. Code review happens before tests
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job starts with a code review to catch issues early, runs tests until
+The **full** workflow starts with a code review to catch issues early, runs tests until
 they pass, formats and lints code with ruff, then reviews changed files
 before committing and pushing. The review and lint steps use sub-agents
 to reduce context usage.
@@ -159,7 +161,7 @@ Use branch format: `deepwork/commit-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 1/4 complete, outputs: code_reviewed"
+2. Inform user: "full step 1/4 complete, outputs: code_reviewed"
 3. **Continue workflow**: Use Skill tool to invoke `/commit.test`
 
 ---

.claude/skills/commit.test/SKILL.md

@@ -4,7 +4,9 @@ description: "Pulls latest code and runs tests until all pass. Use after code re
 
 # commit.test
 
-**Step 2/4** in **commit** workflow
+**Step 2/4** in **full** workflow
+
+> Full commit workflow: review, test, lint, and commit
 
 > Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
 
@@ -76,7 +78,7 @@ This step runs after code review. Tests must pass before proceeding to lint and
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job starts with a code review to catch issues early, runs tests until
+The **full** workflow starts with a code review to catch issues early, runs tests until
 they pass, formats and lints code with ruff, then reviews changed files
 before committing and pushing. The review and lint steps use sub-agents
 to reduce context usage.
@@ -116,7 +118,7 @@ Use branch format: `deepwork/commit-[instance]-YYYYMMDD`
 ## On Completion
 
 1. Verify outputs are created
-2. Inform user: "Step 2/4 complete, outputs: tests_passing"
+2. Inform user: "full step 2/4 complete, outputs: tests_passing"
 3. **Continue workflow**: Use Skill tool to invoke `/commit.lint`
 
 ---

.claude/skills/commit/SKILL.md

@@ -5,13 +5,13 @@ description: "Reviews code, runs tests, lints, and commits changes. Use when rea
 
 # commit
 
-**Multi-step workflow**: Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
+Reviews code, runs tests, lints, and commits changes. Use when ready to commit work with quality checks.
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job starts with a code review to catch issues early, runs tests until
+The **full** workflow starts with a code review to catch issues early, runs tests until
 they pass, formats and lints code with ruff, then reviews changed files
 before committing and pushing. The review and lint steps use sub-agents
 to reduce context usage.
@@ -23,22 +23,27 @@ Steps:
 4. commit_and_push - Review changes and commit/push
 
 
-## Available Steps
+## Workflows
 
+### full
+
+Full commit workflow: review, test, lint, and commit
+
+**Steps in order**:
 1. **review** - Reviews changed code for issues, DRY opportunities, naming clarity, and test coverage using a sub-agent. Use as the first step before testing.
-2. **test** - Pulls latest code and runs tests until all pass. Use after code review passes to verify changes work correctly. (requires: review)
-3. **lint** - Formats and lints code with ruff using a sub-agent. Use after tests pass to ensure code style compliance. (requires: test)
-4. **commit_and_push** - Verifies changed files, creates commit, and pushes to remote. Use after linting passes to finalize changes. (requires: lint)
+2. **test** - Pulls latest code and runs tests until all pass. Use after code review passes to verify changes work correctly.
+3. **lint** - Formats and lints code with ruff using a sub-agent. Use after tests pass to ensure code style compliance.
+4. **commit_and_push** - Verifies changed files, creates commit, and pushes to remote. Use after linting passes to finalize changes.
+
+**Start workflow**: `/commit.review`
+
 
 ## Execution Instructions
 
 ### Step 1: Analyze Intent
 
 Parse any text following `/commit` to determine user intent:
-- "review" or related terms → start at `commit.review`
-- "test" or related terms → start at `commit.test`
-- "lint" or related terms → start at `commit.lint`
-- "commit_and_push" or related terms → start at `commit.commit_and_push`
+- "full" or related terms → start full workflow at `commit.review`
 
 ### Step 2: Invoke Starting Step
 
@@ -50,20 +55,22 @@ Skill tool: commit.review
 ### Step 3: Continue Workflow Automatically
 
 After each step completes:
-1. Check if there's a next step in the sequence
+1. Check if there's a next step in the workflow sequence
 2. Invoke the next step using the Skill tool
 3. Repeat until workflow is complete or user intervenes
 
+**Note**: Standalone skills do not auto-continue to other steps.
+
 ### Handling Ambiguous Intent
 
 If user intent is unclear, use AskUserQuestion to clarify:
-- Present available steps as numbered options
+- Present available workflows and standalone skills as options
 - Let user select the starting point
 
 ## Guardrails
 
 - Do NOT copy/paste step instructions directly; always use the Skill tool to invoke steps
-- Do NOT skip steps in the workflow unless the user explicitly requests it
+- Do NOT skip steps in a workflow unless the user explicitly requests it
 - Do NOT proceed to the next step if the current step's outputs are incomplete
 - Do NOT make assumptions about user intent; ask for clarification when ambiguous