dev-implementlisted

# dev-implement ## Overview Execute implementation plans using test-driven development with subagent-driven development. Each task in the plan gets a fresh subagent. Every task passes through a two-stage review gate: spec compliance first, then code quality. Nothing ships without both gates green. This is the core engine. It takes a plan and turns it into working, tested, reviewed code. ## Announcement When this skill activates, announce: > I'm using enggenie:dev-implement to execute this plan. --- ## Entry Condition This skill requires one of: 1. An approved plan produced by enggenie:dev-plan 2. A Jira ticket reference (e.g., "Pick up PROJ-1234", "Implement PROJ-1234") 3. A direct user request to implement specific tasks ### Jira Ticket Entry When the user references a Jira ticket, read the ticket first using MCP tools. The ticket contains handoff context from PM and/or Architect: 1. Read the ticket description - look for "For Dev" section with spec path and constraints 2. Read the "Implementation Plan" comment (if dev-plan added one) - get the plan file path 3. Open the linked spec and plan files. Do not work from the Jira description alone - it is a summary, not the full context. 4. If anything is unclear or missing, ask the user for clarification before starting. Do not guess. If Jira MCP is not available, ask: "I can't read PROJ-1234 directly. Can you share the plan file path or paste the relevant details?" **If no plan or Jira ticket is found:** > No pla