Content Plan
Skill id: content-plan
Generated from JSON Schema — do not edit by hand. Run bun run cat-harness-tools/scripts/gen-schema-docs.ts.
Input schema for content planning — scope, team, timeline, governance.
Field Type Required Description projectNamestring yes scopestring no Description of the content scope. targetDatestring (date) no teamSizeinteger no min: 1 sprintDuration"1w" | "2w" | "3w" | "4w"no default: "2w"
Raw schema · ✎ Edit
Output
Output schema for content planning.
Field Type Required Description planobject yes stagingLinksany no The staging preview of the work this output asks a person to look at: one deep link per changed page, with the same page on main. Required whenever a preview exists; when it does not, say so in missing. Rule: cat-harness skills/sdlc/sdlc-core/staging-review.md §”The deep-link rule”.
planField Type Required Description projectNamestring yes sprintsarray yes teamarray yes
plan.sprints[]Field Type Required Description numberinteger no startDatestring (date) no endDatestring (date) no goalsarray no
plan.team[]Field Type Required Description actorIdstring no namestring no responsibilitiesarray no
Raw schema · ✎ Edit
folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.
deployed
b08c961 · 2026-10-23T23:11:09Z