Quickly answer "where are we now, where are we stuck, and what's next".
Read first:
${CLAUDE_PLUGIN_ROOT}/core/workflow/README.md${CLAUDE_PLUGIN_ROOT}/core/workflow/protocols/status.md
Read sources
Prefer calling the shared runner:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/cx-workflow-status.sh \
--runner cc
开发文档/CX工作流/配置.json开发文档/CX工作流/状态.json开发文档/CX工作流/功能/{功能标题}/状态.json开发文档/CX工作流/修复/*/修复记录.md(if needed)
Display focus
1. Current feature
- Chinese title
- Stable
slug - Current status:
drafting / planned / executing / blocked / completed / summarized - Completion progress:
completed / total
2. Current task
Prefer displaying the in_progress task; if there is none, display the next executable task.
3. Blocking information
When a feature or task enters blocked , the structured reason must be displayed:
reason_typemessage
For example:
{
"reason_type": "verification_failed",
"message": "测试仍未通过,需要继续修复"
}
4. Next-step suggestions
- In progress: suggest
/cx:cx-exec - Completed and awaiting wrap-up: suggest
/cx:cx-summary - No active feature: suggest
/cx:cx-prdor/cx:cx-fix
Explain principles
- Status should come from JSON first, not model memory
- GitHub information is only supplementary and does not override local status
- Output should be short, structured, and actionable
- If the shared core shows the feature is held by
codex, the owner and handoff suggestion must be clearly displayed