implement

To turn Linear issues into committed code, this Skill orchestrates a gated 8-step implementation workflow that validates dependencies, governance artifacts, and acceptance criteria before executing a git commit.

A spec gate is a machine-enforced hook that stops implementation unless the required spec file exists, ensuring governance validation and required documentation are present before code changes begin.

You can enforce acceptance criteria validation by running a post-implementation protocol that verifies criteria with evidence, performs smoke testing, and logs security findings before marking the Linear issue Done.

This implementation workflow does not require manual code quality checks, as it automatically runs post-implement validation including architecture quick-checks and smoke testing to ensure code quality.

If the required specs are missing during issue implementation, the hard spec-file gate blocks the workflow entirely, preventing any code changes until the necessary governance artifacts are created.

Yes, you can use this workflow for backlog-driven software changes in Linear, as it specifically applies to scenarios where dependencies, context, and governance artifacts must be validated before committing.