What problem does it solve? Turning a written feature plan into working code often drifts: tasks get reordered, acceptance criteria get forgotten, and the plan silently diverges from what was built. This Skill enforces a disciplined implementation phase that re-resolves the plan and ticket from the environment, executes tasks in order, and verifies every acceptance criterion before reporting completion. ## Core Features & Use Cases - Plan and ticket resolution: Auto-resolves the newest plan artifact for a ticket (including refined _plan-v*.md revisions) and the governing ticket from explicit flags, session context, stored URLs, or plan frontmatter. - Ordered task execution with commits: Executes plan tasks in dependency order, commits each task separately via the create-commit skill, and raises material divergences to the user instead of rerouting silently. - Verification and audit gates: Runs a diff audit and the plan's own verification checks, refusing to claim a gate passed without seeing it pass, and rejects spike plans that are meant to be carried out rather than implemented. - Use Case: After planning a multi-task feature against a Jira ticket, invoke this Skill to implement each task as its own commit, run the plan's verification gates, and receive a closing summary plus next-step options such as branch review or PR creation. ## Quick Start Ask the agent to implement the latest plan for the current ticket using the implement-plan skill, optionally passing --plan or --ticket to override auto-resolution.
