spec-driven-implementation Drive a spec-first workflow for substantial features in Warp. Overview Use this skill for significant features where a written spec will improve implementation quality, reduce ambiguity, or make review easier. Be pragmatic: not every change needs specs. Specs should usually live in: - - For example: - - should contain only ticket-named directories as direct children. Do not create engineer-named subdirectories or feature-slug directories there. If a relevant Linear issue does not already exist, create one before writing specs. Use the Linear MCP tools directly: - to…