content-loop

name	content-loop
description	Orchestrate only the net-new Career Hub content pipeline: topic discovery, optional VOC research, factual research, structure, draft, edit, and review. Use only when creating a brand-new content asset from scratch.
metadata	{"family":"orchestrators","owner":"engineering + content","last_reviewed":"2026-04-30T00:00:00.000Z","version":"1.0.0"}

Content Loop

This is the orchestrator for new content only.

Entrypoints

• Ad-hoc content-loop: artifact-only. Produce the editorial artifacts and implementation handoff; do not write repo files.
• Scheduled vital-loop Stage 4: operator workflow that may write or stage content data after Stage 3 routing. Do not treat Stage 4 as the default ad-hoc content-loop behavior.

Boundary

• Use this skill only for brand-new Career Hub content generation.
• Do not use it for refreshes, audits, CRO, AI visibility reviews, SEO diagnostics, or code implementation.
• If the work turns into a repo implementation task, hand off to the code family.

Required Sequence

1. content-scout
2. optional worker-research
3. content-researcher
4. content-strategist
5. content-writer
6. copy-editor
7. content-review

Inputs

Start with one of:

• a topic
• a keyword
• a target persona
• a business priority for a new article

Expected Outputs

The loop should end with these artifacts:

• Opportunity Brief
• optional VOC Notes
• Research Dossier
• Content Plan
• draft article data object
• edited draft
• final review scorecard
• structured implementation handoff requirements when the asset needs route, metadata, schema, internal-link, UI, or mobile verification work

Implementation Handoff

Mobile-first is a non-negotiable criterion across every content asset that lives in a public route, but new-content skills do not own rendered-route verification.

• If the draft needs route, metadata, UI, schema, or internal-link work, stop this loop and hand off to code skills.
• If the approved draft is data-only, the handoff still must list pnpm audit:responsive as a required code-family verification before shipping.

Return this block with the final accepted draft:

implementation_handoff:
  requires_code_family: true
  target_destination: "<feature-owned data or route path>"
  required_code_skills:
    - data-placement
    - verification-checklist
  route_requirements:
    - metadata
    - schema
    - internal_links
  verification_required:
    - pnpm audit:responsive

Do not run route implementation or browser verification from this loop.

Common Editorial Data Homes

• guides: nextjs-app/src/features/guides/data/guides/articles/data.ts
• financial tips: nextjs-app/src/features/financial-tips/data/financial-tips/data.ts
• persona hubs: nextjs-app/src/features/career-hub/personas/data/persona-hubs/*

These are common homes, not the full routing table. Template-driven destinations outside these homes must follow the content-strategist destination recommendation and, for implementation, the code-family data-placement or Stage 3 routing decision.

Handoff Rule

When the draft is approved and needs implementation in routes, metadata, UI, schema, or internal linking, stop this loop and switch to code skills. The handoff must carry forward the mobile responsiveness requirement; the implementing code skill is responsible for running pnpm audit:responsive before declaring the work complete.