ticket-status

Automated KB ticket status checks validate ticket docs, tests, and roadmap data to determine CI/CD readiness. The skill runs deterministic scripts against required files like 1-definition.md, 2-plan.md, and 3-spec.md to verify progression and gate commits.

Phase-level ticket readiness validation aggregates the statuses of individual tickets within a phase to identify blockers and surface missing steps. It checks required documentation and tests to provide next-step guidance for planning across the knowledge-base workflow.

To validate missing steps in KB ticket docs, the status check skill runs deterministic scripts that verify the presence and formatting of required files including 1-definition.md, 2-plan.md, 3-spec.md, and 5-final.md, surfacing any incomplete documentation.

Yes, you can detect blockers across a project phase by running phase-level aggregation checks. The validation process reviews ticket docs and optional tests.json files to identify incomplete tickets and generate next-step guidance for the entire phase.

Yes, existing ticket docs are required to check phase readiness. The validation scripts require 1-definition.md, 2-plan.md, and 3-spec.md to determine statuses, while an optional tests.json and 5-final.md formatting provide additional readiness context.

The best way to gate CI/CD pipelines is by running deterministic validation checks against ticket docs, tests, and roadmap data before commits. This ensures phase readiness by detecting missing steps and blockers, preventing unverified tickets from progressing.