lrh-implement

Automating git workflow validation requires a structured multi-phase process that links code changes back to work items. This skill executes planning, implementation, and validation phases to enforce traceability and ensure no code is merged without passing linting, formatting, and test suites.

Ensuring traceability for software development work items involves minting unique prompt IDs and creating execution records. This approach links every code change back to a specific work item or ad-hoc request, making the implementation process fully inspectable by team members.

Yes, GitHub CLI is required as an integration point. The structured task execution workflow depends on git, GitHub CLI, and local project validation scripts to manage the lifecycle of work items and ensure code quality throughout the implementation process.

Implementing a complex feature with automated quality gates requires invoking the skill with a specific work item ID. The workflow then enforces canonical validation by automatically executing linting, formatting, and test suites to guarantee code quality before merging.

A structured implementation workflow should be used when you need to execute complex features or chores and want to guarantee the work is planned, validated, and recorded. It applies to both lifecycle management of work items and ad-hoc tasks within the Logical Robotics Harness framework.