Fix schema validation errors in spec_driven_development library job

[Copilot]

The spec_driven_development job from library uses schema features not supported by DeepWork v0.5.0, causing deepwork sync to fail with 5 validation errors.

Changes

Step property compatibility

• Replace hidden: true with exposed: false (v0.5.0 uses exposed not hidden)

Output schema fixes

• Change directory: outputs to simple strings (src/, tests/)
• Remove description fields from output objects (schema only accepts {file} or {file, doc_spec})

Input schema fix

• Change plan step's architecture input from invalid {file, description} to valid {name, description} user parameter

Dependency resolution

• Add explicit transitive dependencies where steps reference files via from_step:
  • plan: add constitution dependency
  • tasks: add clarify dependency
  • implement: add plan and clarify dependencies

DeepWork requires every from_step reference to be explicitly listed in the step's dependencies array - transitive dependencies are not inferred.

Documentation

Added schema compatibility notes to:

• library/jobs/spec_driven_development/readme.md - documents the 5 fixes applied
• AGENTS.md - general guidelines for importing external jobs

Original prompt

See about addressing the following We hit 5 schema validation errors when importing the upstream spec_driven_development job from the Unsupervisedcom/deepwork library. Each caused deepwork sync to fail:

1. hidden: true on steps — Not a valid step property. DeepWork uses exposed: boolean (default false) instead.
2. directory: in outputs — Only file and doc_spec are valid output properties. Changed directory: src/ to file: src/.
3. description: on output objects — Output objects only accept {file} or {file, doc_spec}. Removed description from two implement step outputs.
4. {file, description} input without from_step — Inputs must be either {name, description} (user parameter) or {file, from_step} (file reference). The plan step had {file:
   "[docs_folder]/architecture.md", description: "..."} which doesn't match either schema.
5. Implicit transitive dependencies — DeepWork requires every from_step reference to be explicitly listed in the step's dependencies array. The upstream job assumed transitive
   resolution (e.g., implement depending on tasks which depends on plan which depends on clarify), but DeepWork doesn't infer this. We had to add clarify and constitution to multiple
   steps' dependency lists.

The root cause is that the upstream library's job.yml uses a superset of the DeepWork v0.5.0 schema — likely targeting a newer or internal version of the validator. All fixes are
documented in readme.md:45-53 and AGENTS.md:38-45.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.