tk-implement

To execute a backlog issue end-to-end, you run a gated workflow that loads the issue, generates a plan, implements changes, runs typecheck/lint/build validations, and produces a QC report before closure. This enforces mandatory confirmation checkpoints to prevent premature coding and un-audited commits.

Ensuring issue compliance against acceptance criteria requires an evidence-driven closure workflow that evaluates test presence, checks lint/types/build compliance, and detects scope creep. The workflow blocks closure until a mandatory QC Report and explicit verdict are emitted, verifying all criteria are met.

Preventing scope creep during backlog implementation involves enforcing hard safety gates at the planning and pre-commit stages. The workflow requires a plan checkpoint approval before coding begins and evaluates acceptance criteria coverage against implementation evidence to detect unauthorized changes before closure.

Yes, the issue execution workflow enforces hard stops for Completed and Blocked statuses, halting execution when dependency unmet conditions are detected. This prevents proceeding with invalid issues and ensures the pipeline only executes actionable backlog items.

During the quality control phase, the workflow evaluates CI validations without re-running them by relying on evidence gathered during the implementation phase. This avoids redundant execution while ensuring lint, types, and build compliance are verified before the issue closure checkpoint.

Generating an auditable handoff summary requires completing the final close phase, which includes a pre-commit review checkpoint. The workflow emits a structured Implementation Evidence document and an explicit verdict, blocking closure until the handoff summary is successfully produced.