Skip to content

Comments

Refactor doc spec guidance and remove step-level quality criteria#185

Merged
nhorton merged 2 commits intomainfrom
claude/update-define-step-docs-SVyo1
Jan 30, 2026
Merged

Refactor doc spec guidance and remove step-level quality criteria#185
nhorton merged 2 commits intomainfrom
claude/update-define-step-docs-SVyo1

Conversation

@nhorton
Copy link
Contributor

@nhorton nhorton commented Jan 30, 2026

Summary

This PR clarifies the distinction between doc spec quality criteria (which define output document requirements) and step-level quality criteria (which define process requirements). It removes redundant step-level quality criteria from the define step in the deepwork_jobs job, since those requirements are now covered by the job.yml doc spec.

Key Changes

  • Clarified doc spec quality criteria guidance: Added explicit documentation that doc spec quality criteria should focus on the output document itself, not the process of creating it. This prevents confusion and reduces duplication.

  • Removed step-level quality criteria from define step: Deleted 14 quality criteria from the define step in job.yml, as these are now properly covered by the job.yml doc spec. This follows the new guidance that step-level criteria should only be used for essential process requirements (e.g., "must use specific tool").

  • Removed step-level quality criteria from define.md: Deleted the "Quality Criteria" section at the end of the define step documentation, which was redundant with the doc spec validation.

  • Updated doc spec example reference: Changed references from the template example file (doc_spec.md.example) to the actual job.yml doc spec (.deepwork/doc_specs/job_spec.md) as the canonical example, making it more practical and real-world.

  • Removed example template file: Deleted doc_spec.md.example (AWS spending report example) since the job.yml doc spec now serves as the primary reference example.

  • Updated architecture documentation: Removed reference to the deleted example file from the directory structure documentation.

Implementation Details

The changes apply consistently across multiple locations:

  • .claude/skills/deepwork_jobs.define/SKILL.md
  • .deepwork/jobs/deepwork_jobs/job.yml
  • .deepwork/jobs/deepwork_jobs/steps/define.md
  • .gemini/skills/deepwork_jobs/define.toml
  • src/deepwork/standard_jobs/deepwork_jobs/job.yml
  • src/deepwork/standard_jobs/deepwork_jobs/steps/define.md
  • doc/architecture.md

This refactoring reduces cognitive load by establishing a clear separation of concerns: doc specs handle output quality validation, while step-level criteria are reserved for process-specific requirements.

https://claude.ai/code/session_01V4ubYEhRcUJmCbEntzrzMC

claude and others added 2 commits January 30, 2026 01:58
- Remove quality_criteria from define step in job.yml since output quality
  is covered by the doc_spec reference
- Add guidance that doc spec criteria should focus on output requirements,
  not process; step-level quality_criteria should be process-only and minimized
- Delete doc_spec.md.example files and update references to use
  .deepwork/doc_specs/job_spec.md as the canonical example
- Remove redundant Quality Criteria section from define.md instruction files

https://claude.ai/code/session_01V4ubYEhRcUJmCbEntzrzMC
@nhorton nhorton enabled auto-merge January 30, 2026 03:28
@nhorton nhorton added this pull request to the merge queue Jan 30, 2026
Merged via the queue into main with commit 3cfef10 Jan 30, 2026
4 checks passed
@nhorton nhorton deleted the claude/update-define-step-docs-SVyo1 branch January 30, 2026 03:34
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