Menú
Use when you need to validate workflow state schema or error handling.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
| name | team-shinchan:verify-workflow |
| description | Use when you need to validate workflow state schema or error handling. |
| user-invocable | false |
When this skill is invoked, execute immediately. Do not explain.
| Validator | Command | What it checks |
|---|---|---|
| workflow-state-schema | cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/workflow-state-schema.js | WORKFLOW_STATE.yaml template + stage/transition gates, plus the big-project layer (project-state.schema.json parses, bigproject PROJECT.yaml template present) |
| error-handling | cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/error-handling.js | Error handling patterns are properly defined |
| part-numbering | cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/part-numbering.js | Multi-part agent files have correct numbering |
| quick-fix-path | cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/quick-fix-path.js | Quick-fix (lite mode) workflow path is valid |
docs/workflow-guide.md, hooks/)cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/workflow-state-schema.js
Success criteria:
schemas/project-state.schema.json parses and
skills/bigproject/SKILL.md contains a PROJECT.yaml templateschemas/workflow-state.schema.json declares current.completion_prompted as an OPTIONAL
boolean (main-076 FR-6 / HR-8: absent ⇒ false; NOT in required)On failure:
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/error-handling.js
Success criteria:
On failure:
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/part-numbering.js
Success criteria:
On failure:
cd "${CLAUDE_PLUGIN_ROOT}" && node tests/validate/quick-fix-path.js
Success criteria:
On failure:
The executing stage is driven by src/dag-executor.js over a task DAG. Each PLAN.md task MUST
carry the six DAG fields (id, depends_on, touches, verify, estimate, scope) and the
plan SHOULD declare integration_test metadata. The executor enforces a per-task verify gate and
a strict ALL-PASS completion gate before the executing → done transition.
cd "${CLAUDE_PLUGIN_ROOT}" && node --test tests/dag-executor.test.js
Success criteria:
src/dag-executor.js exposes parsePlan, topoSort, buildConflictGraph,
connectedComponents, evaluateVerify, recoveryStep, evaluateCompletionGate,
runIntegration, executePlanOn failure:
docs/dag-executor.md)Use when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need persistent looping until a task is fully complete.
Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.
Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.
Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.