What problem does it solve? Teams often jump from a design or issue straight into code, losing traceability between requirements and implementation. This Skill turns a design into a structured specification, ordered build cards with acceptance criteria, and a prompt a fresh executor session can pick up cold. ## Core Features & Use Cases - Requirement-Traced Specs: Converts a design into a specification where every requirement is traceable through the plan. - Dependency-Ordered Build Cards: Produces small, sequenced build cards so work can be executed and reviewed incrementally. - Cold-Executor Prompt: Generates a self-contained prompt so a new agent session can execute the plan without prior context. - Use Case: After agreeing on a design for a new health endpoint, run the plan workflow to produce the spec and build cards, then hand the executor prompt to a fresh Copilot session to implement them. ## Quick Start Ask your Copilot agent to run /li-plan with a short description of the change, such as planning a health endpoint with a focused acceptance test.