implement

Implement phased feature plans with Linear issue context and approval gates.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lutzcc1/claude-skills --skill implement-lutzcc1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/lutzcc1/claude-skills/tree/main/project/implement
Command: npx skills add https://github.com/lutzcc1/claude-skills --skill implement-lutzcc1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the enforcement of a disciplined, phase-by-phase feature implementation workflow driven by an explicit implementation plan and its linked Linear issue. It reads the plan, fetches context, asks clarifying questions when needed, and coordinates disciplined progress with explicit user approvals between each phase.

Core Features & Use Cases

  • Phase-based execution: Implement features one phase at a time, pausing for approval between phases.
  • Plan & context integration: Locate and parse PROD-*-IMPLEMENTATION-PLAN.md files and fetch the associated Linear issue for full context.
  • Verification & governance: Validate the current git branch, generate per-phase diffs, and present summaries to the user for decision making.
  • Question handling: Identify unresolved questions and ambiguities, and prompt for clarifications before starting work.

Quick Start

Use the implement skill with a plan or issue identifier, for example: /implement PROD-808 to begin the phased workflow. It will locate the appropriate implementation plan, fetch the Linear issue, and request your approval before each phase.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate phased feature implementation from an implementation plan?

Phased feature implementation is automated by parsing a PROD-*-IMPLEMENTATION-PLAN.md file, fetching the linked Linear issue context, and executing each phase with diffs while pausing for explicit user approval before proceeding to the next phase.

What is the best way to enforce stakeholder approvals between software delivery phases?

Enforcing stakeholder approvals between software delivery phases is handled by generating phase-based todos, implementing each phase with diff output, and pausing the workflow to present summaries for explicit user decision making before moving forward.

Does the implement workflow require a specific git branch to start?

Yes, the implement workflow requires validating the current git branch before starting. It checks the branch state to ensure traceability from the implementation plan to the actual code changes across all phases.

Can I use a Linear issue identifier to start a phased implementation workflow?

Yes, you can use a Linear issue identifier like PROD-808 to start the workflow. The system will locate the associated implementation plan file, fetch the Linear issue context, and request approval before each phase begins.

How do unresolved questions and ambiguities get handled during phased implementation?

Unresolved questions and ambiguities are handled by identifying them after parsing the implementation plan and fetching Linear context, then prompting the user for clarifications before starting any implementation work.

What limitations exist when using a named implementation plan for multi-phase delivery?

A limitation is that the workflow requires a PROD-*-IMPLEMENTATION-PLAN.md file or a specifically named plan to exist. Without this explicit plan file and the linked Linear issue, the phased implementation cannot be parsed or executed.