From hw
Show current Hypo-Workflow progress when the user wants a concise status summary without mutating pipeline state.
npx claudepluginhub hypoxanthineovo/hypo-workflow --plugin hwThis skill uses the workspace's default tool permissions.
📌 输出语言规则：
Start Hypo-Workflow execution when the user wants to begin running milestones, continue automatically through the pipeline, or execute the first prompt.
Renders markdown progress bars for StatsClaw workflows, showing pipeline stages (Credentials, Plan, Specs, Build/Test, etc.), active tasks, and elapsed time after status.md updates.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
📌 输出语言规则： 读取 config.yaml → output.language
Use this skill to inspect pipeline progress only.
Status is strictly read-only. If state, logs, progress, or step pointers are inconsistent, report the inconsistency and the recommended repair command; do not repair files, do not advance the current step, and do not make Stop hooks pass as a side effect of showing status.
.pipeline/state.yaml is missing, report that no active pipeline exists~/.hypo-workflow/config.yaml if present..pipeline/config.yaml if present.--full, read .pipeline/state.yaml and .pipeline/PROGRESS.md directly and print 加载完整版 state.yaml / 加载完整版 PROGRESS.md with line counts when possible.--full is absent, prefer .pipeline/state.compact.yaml and .pipeline/PROGRESS.compact.md when they exist; otherwise fall back to .pipeline/state.yaml and .pipeline/PROGRESS.md.scripts/state-summary.sh for a quick summary when shell access is available; use compact files only as supplemental context because canonical state mutations still belong to state.yaml..pipeline/cycle.yaml existslast_heartbeat and watchdog state when present.pipeline/PROGRESS.md or .pipeline/PROGRESS.compact.md exists, use it as a human-facing summary source, but do not rewrite it during status inspection..pipeline/feature-queue.yaml contains Feature DAG dependencies, show a concise board summary with ready, blocked, and parallel candidates. Hide DAG concepts for ordinary single-feature queues..pipeline/derived-health.yaml when present and route stale derived views to /hw:sync --repair or /hw:docs repair as appropriate..pipeline/log.yaml sorted by timestamp newest-first, filtered to user-relevant lifecycle events, and redacted through the shared secret-safe evidence helper.PROJECT-SUMMARY.md exists, include its top summary line and Open Patches / Deferred counts./hw:status, prefer the shared Claude status surface shape: compact milestone table, current phase/next action, automation/profile basics, and recent events. Do not dump the full raw PROGRESS.md unless --full is requested.Status must expose one user-facing canonical phase and one next action. Derive these from .pipeline/cycle.yaml, .pipeline/state.yaml, acceptance state, and active continuation state. Important phases:
needs_revision -> next action resume_revisionfollow_up_planning -> next action start_follow_up_planpending_acceptance -> next action accept_or_rejectDo not make the user reconcile separate execution, acceptance, continuation, and lock axes on the first screen.
/hw:status --full: ignore compact files and load the complete .pipeline/state.yaml and .pipeline/PROGRESS.md./hw:status: use compact files when available, with full-file fallback when compact files are absent.state.yamlreferences/state-contract.md — state layoutreferences/progress-spec.md — progress summary layoutreferences/commands-spec.md — status command semanticsreferences/config-spec.md — config priority and fallback rulesSKILL.md — broader system reference if needed