impl-plan-executor

Automate Jira implementation plan execution by reading IMPL_<STORYKEY>.md files and translating them into a deterministic sequence of development steps. The process enforces preflight checks, feature branching, step-level coding, commits, PR creation, and Jira synchronization.

Quality gates in automated plan execution are validation checkpoints that enforce AI readiness, test case mapping, and risk controls. They ensure each step meets guardrails before proceeding and provide explicit rollback or feature-flag guidance when requirements are not satisfied.

You can execute implementation plans in range mode to process specific segments of a Story. This allows targeted development of individual work-breakdown steps while still enforcing preflight checks, commits, PR creation, and Jira synchronization for that segment.

When risk requirements remain unresolved during plan execution, the process provides explicit escalation points. It also generates rollback or feature-flag guidance to ensure guardrails are maintained and the codebase remains stable.

Automated plan execution enforces a Git branching strategy and handles pull request creation natively. It creates feature branches, commits code step-by-step, and synchronizes the final pull request with Jira.

You need an IMPL_<STORYKEY>.md file defining the work-breakdown steps and a connected Jira Story. The execution process relies on these inputs to enforce preflight checks, validate TC mappings, and apply risk controls.