cabloy-spec-execution

Provide an explicit WBS task ID such as WBS-HUA-20-01. The Skill reads the linked PRD, SRS, ATP, dependencies, and progress records, presents an execution dossier for confirmation, then routes the work to the appropriate backend, frontend, or contract-loop specialist.

Only a finite, explicitly approved phase with named WBS tasks and a defined closure boundary is accepted. Open-ended requests like "implement the whole suite" are rejected, and you must select a bounded task or approve a finite task list first.

A task becomes verified only after all applicable WBS checks and ATP procedures pass with durable, redacted evidence containing revision, environment, exact procedure, and observed result. A successful build, scaffold, or passing typecheck alone is not sufficient proof.

Execution stops before any implementation. The unresolved authority conflict or failed gate is routed back to cabloy-spec-generation for correction, and the task remains blocked rather than being worked around.

No. Operations such as npm run init, database resets, deployments, provider or webhook calls, working-tree cleanup, and commits are prohibited unless a separate explicit workflow and confirmation authorizes them.

Contract changes follow the forward loop: establish backend contract truth, inspect the OpenAPI output, then regenerate Zova consumers. Hand-editing generated consumer files is refused; stale consumers are diagnosed through the contract-loop skill.