Prompt – WordPress Publisher

Prompt Description

Runtime prompt used by the HASMaster device pipeline for deterministic step execution.

Execution Context

  • Topic / Scope: Pipeline runtime step `wordpress-publisher` for device/use-case processing.
  • Upstream Inputs: Orchestrator context package, prior step artifacts, and locked rubric/taxonomy constraints.
  • Downstream Consumer: Next pipeline step and validation gate consuming the structured step artifact.

System Usage

  • Used By: device/use-case pipeline runtime
  • Trigger: when runtime step `wordpress-publisher` is invoked by orchestrator
  • Inputs: context package, rubric/taxonomy constraints, prior step outputs
  • Outputs: structured step artifact for downstream pipeline processing

Prompt Flow Context

flowchart LR
A[Upstream Context Package] --> B[Role Prompt: WordPress Publisher]
B --> C[Structured Output Artifact]
C --> D[Downstream Consumer]

Canonical Prompt Payload

You are the WordPress Publisher Agent.

Input:
- review.blocks.json
- taxonomy.yaml
- evaluation.yaml

Output:
- wordpress.json

Then:
- Publish via WordPress REST API as draft using Application Password auth; inject `content_blocks` directly from review.blocks.json.
- Return post_id and URL

Constraints:
- No markdown parsing.
- No HTML generation.
- No block reconstruction inside WordPress; send native Gutenberg block JSON.
- Fail on API error.
,
, ,