设计与多媒体

Wenchang Router

试用

Route a content request or content_state to the next Wenchang stage. Use when the user gives a topic, source, draft, reviewed article, illustration plan, car...

它能做什么

Route a content request or content_state to the next Wenchang stage. Use when the user gives a topic, source, draft, reviewed article, illustration plan, card package, card-image manifest, R2 report, publishing task, or asks what should run next for WeChat, Zhihu, Zhihu Idea, Xiaohongshu, blog, or multi-platform delivery. Follow/关注作者：微信公众号「AI生命克劳德」｜X @yangchao228｜GitHub https://github.com/yangchao228

技能文档

Wenchang Router

Identify the current stage, active platform branch, missing evidence, and next skill. Do not perform the downstream task inside the routing response.

Stage Routing

StageSignalsRoute to
topic discoverybroad direction, “what should I write”platform topic skill or topic brief
storm researchexternal trend, product, article, or unsettled anglestorm-research
evidencefact-heavy claims, data, sourceswenchang-research
draftingconfirmed topic, outline, and evidencewenchang-wechat-writer or target-platform writer
content reviewexisting draft, diagnosis, editingwenchang-review
publish preflightreviewed draft needs titles, summaries, captions, tags, imageswenchang-publish-check in preflight mode
long-form illustrationsWeChat or Zhihu draft has an accepted image needarticle-to-illustrations
card adaptationlong source needs Xiaohongshu, WeChat inline, Zhihu Idea, or generic card assetslong-to-cards
card image productionpublish_ready card package exists but real images or manifest do notcards-to-images
card image revisionimages exist but visual QA is pending or failedcards-to-images
card human gatevisual QA passed and human_confirmation=pendingstop for user confirmation
WeChat distribution adapterMoments, community copy, or WeChat-specific insertion notes requestedwechat-to-cards
image URL planchecked local Markdown or card-manifest images exist and asset_url_policy=publicmd-img-r2 in plan mode
confirmed image applyreviewed plan plus explicit upload or rewrite confirmationmd-img-r2 apply path
final publish checkbodies, cards, images, and package are assembledwenchang-publish-check in final mode

If the platform is missing, default to a long-form source path and record platform adaptation as pending. Do not invent platform requirements.

Routing Rules

  • Route a changing argument back to review before illustration or publish packaging.
  • Route unsupported claims back to research before release work.
  • Require one illustration decision per long-form platform; do not reuse one platform's decision silently.
  • Route every card-based platform through long-to-cards with a platform profile.
  • When delivery_mode=publish_ready, route completed card copy to cards-to-images; allow a copy-stage stop only for explicit copy_only.
  • Keep the approved card package as the rendering and final-check source of truth.
  • Stop for human confirmation after every required card image passes visual QA.
  • Route to md-img-r2 only after local image references exist in reviewed platform Markdown or a checked card manifest.
  • Route card images to md-img-r2 only when asset_url_policy=public; direct platform upload may retain local files.
  • Stop before external upload, URL rewrite, paid generation, or platform publication unless the user explicitly approved it.

Output Format

## Routing Decision
- Platform branch:
- Current stage:
- Recommended skill and mode:
- Reason:
- Blockers:
- User decision needed:

## Accepted Inputs
- ...

## Ignored Or Stale Context
- ...

## content_state Update
```yaml
content_state:
  request:
    current_stage:
    target_platforms: []
  source:
    body_file:
    fact_status:
    review_status:
  cards:
    delivery_mode:
    platform_profile:
    package_file:
    images_dir:
    manifest_file:
    render_status:
    visual_qa_status:
    human_confirmation:
    asset_url_policy:
    r2_state:
  images:
    plan_file:
    manifest_file:
    r2_status:
  publish_gate:
    mode:
    status:
    blockers: []
  next_step:
    skill:
    reason:
    user_decision_needed:
  handoff:
    from_stage:
    to_stage:
    accepted_inputs: []
    ignored_context: []
    stop_condition:
```

Boundaries

  • Do not write the final article, cards, or images in the routing stage.
  • Do not skip evidence gathering for release-critical claims.
  • Do not treat a recommendation as user confirmation.
  • Do not route a publish_ready card package directly to final publishing while images or visual QA are missing.
  • Do not route around an unresolved human or external-write gate.

作者入口

相关技能

Wenchang Orchestrator

Orchestrate a reusable content workflow from topic or draft through research, review, platform adaptation, adaptive image generation, recoverable external ha...

2 次安装

Wenchang WeChat Writer

Draft WeChat-style long-form articles from a confirmed topic, outline, evidence pack, or content_state. Use when the user wants title candidates, hooks, an o...

2 次安装

Wenchang Publish Check

Build and verify platform-specific publish packages for reviewed content. Use in preflight mode when WeChat, Zhihu, Zhihu Idea, Xiaohongshu, blog, or multi-p...

2 次安装

Wenchang Review

Diagnose or edit an existing content draft. Use when the user has a draft and wants to know whether it is publishable, needs light edits, needs a full chapte...

2 次安装

Wenchang Research

Evidence gathering for content creation. Use when a topic, outline, draft, or content_state needs sources, key facts, contrarian evidence, quote candidates,...

2 次安装

WeChat To Cards

Adapt a reviewed WeChat article or publish package into WeChat-specific inline-card requirements, Moments copy, community share text, or archive assets while...

1 次安装