feat(library): add marketing job with competitive content analysis workflow

Add a new library job for marketing workflows, starting with
competitive_content_analysis — a 5-step workflow that researches
competitors' content strategies in parallel and produces a prioritized
gap analysis with actionable recommendations.

Includes research_one_competitor sub-workflow for per-competitor
deep dives launched via parallel agents.

Also documents the "signal intent, not mechanism" pattern for library
job output conventions in the library README — library jobs defer to
the user's notes directory AGENTS.md for note creation mechanics
rather than embedding zk commands or specific paths.

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

Author: ncrmro

library/jobs/README.md

@@ -17,6 +17,7 @@ This walks you through configuring `DEEPWORK_ADDITIONAL_JOBS_FOLDERS` so the Dee
 | Job | Description |
 |-----|-------------|
 | [Engineer](./engineer) | Domain-agnostic engineering execution from product issue through PR merge and product sync, with TDD discipline |
+| [Marketing](./marketing) | Competitive content analysis across channels with parallel per-competitor research |
 | [Research](./research) | Multi-workflow research suite — deep investigation, quick summaries, material ingestion, and reproduction planning |
 | [Platform Engineer](./platform_engineer) | Incident response, observability, CI/CD, releases, security, cost management, and infrastructure |
 | [Repo](./repo) | Audit and configure repositories — labels, branch protection, milestones, and boards |
@@ -61,6 +62,25 @@ The job library provides:
 - **Templates**: Copy and adapt jobs for your own use cases
 - **Learning**: Understand the job definition format through real examples
 
+## Output conventions for library jobs
+
+Library jobs that produce durable outputs (reports, research, decisions) should defer to the user's environment for note creation mechanics rather than embedding specific tools or paths.
+
+**Pattern**: Signal the intent, not the mechanism.
+
+- **Do**: "The final report and supporting research are durable notes. If the user has a notes directory, follow its AGENTS.md conventions."
+- **Don't**: Embed `zk new reports/ --title ...` commands, specific frontmatter schemas, or directory paths in the job's `common_job_info`.
+
+**Why**: Users have different note-taking setups (zk, Obsidian, plain markdown, no notes repo). The user's notes directory AGENTS.md and their platform conventions (if any) are the source of truth for how to create notes. Library jobs that embed one system's mechanics become non-portable.
+
+**How it works in practice**:
+
+1. The job's `discover_context` step checks `NOTES_DIR` or `ZK_NOTEBOOK_DIR` and reads the AGENTS.md there.
+2. The agent's platform conventions (e.g., `process.notes`, `tool.zk-notes`) provide the mechanics for note creation.
+3. If no notes directory exists, the job falls back to `.deepwork/tmp/` with plain markdown.
+
+This separation means the same library job works for a Keystone user with a zk notebook, an Obsidian user, or someone with no notes system at all.
+
 ## Structure
 
 Each job in this library follows the same structure as the `.deepwork/jobs` subfolders in your local project:

library/jobs/marketing/AGENTS.md

@@ -0,0 +1,57 @@
+# Project context for marketing
+
+This is a **library job** -- reusable marketing workflows that any project can adopt.
+
+## Purpose
+
+Marketing workflows for competitive content analysis, content strategy, and campaign
+execution. The first workflow (`competitive_content_analysis`) analyzes competitors'
+content strategies across channels and produces actionable recommendations.
+
+## Location
+
+This job lives in `library/jobs/marketing/`. It is NOT auto-installed -- users adopt it
+via `DEEPWORK_ADDITIONAL_JOBS_FOLDERS`, the `shared_jobs` workflow, or by copying it
+into their project's `.deepwork/jobs/` directory.
+
+## Workflows
+
+| Workflow                       | Steps                                                                                    | Purpose                                                  |
+|--------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| `competitive_content_analysis` | discover_context, research_all_competitors, analyze_patterns, gap_analysis, final_report | Full competitive content analysis with parallel research |
+| `research_one_competitor`      | gather_content, analyze_content                                                          | Deep-dive on a single competitor (sub-workflow)          |
+
+## Planned workflows (not yet implemented)
+
+- `campaign_planning` -- strategy through execution
+- `content_calendar` -- content calendar across channels
+- `seo_audit` -- technical and content SEO audit
+- `social_media_strategy` -- platform-specific playbooks
+- `email_marketing` -- campaigns and automations
+- `launch_comms` -- launch communications coordination
+- `analytics_attribution` -- performance and attribution models
+
+## Shared patterns
+
+These steps are designed for reuse across sibling workflows:
+
+- **discover_context**: Project/brand context discovery with output directory inference
+- **Competitor identification**: Building and validating competitor lists
+
+## Output conventions
+
+Workflow outputs are durable notes. If the user has a notes directory
+(`NOTES_DIR` or `ZK_NOTEBOOK_DIR`), follow its AGENTS.md conventions for note
+creation and placement. The final report is a report-type note; supporting
+per-competitor research goes as literature notes linked via wikilinks. Fall back
+to `.deepwork/tmp/` only if no notes directory exists.
+
+This job does not embed note creation mechanics (zk commands, frontmatter
+format, tag conventions) because those vary by user setup. The user's notes
+repo AGENTS.md and the agent's platform conventions are the source of truth for
+how to create notes. See `process.notes` and `tool.zk-notes` for the canonical
+rules if available in the agent's instruction context.
+
+## Quality review learnings
+
+(No learnings recorded yet.)

library/jobs/marketing/CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md