dev-jira-ticket

To turn a Jira ticket into ready code, provide a markdown export or URL so the tool can extract acceptance criteria, scan project docs, implement changes, verify coverage, and prepare Jira-referenced commits.

The best way to implement Jira requirements using project workflow manifests is to run an analysis-only mode first, generate a mini-plan, and then execute changes that validate coverage against the ticket's acceptance criteria.

Yes, you can use a direct Jira URL to generate an implementation plan and code changes. The workflow parses the ticket identity and type, scans relevant scopes, and produces an end-to-end implementation outcome.

Jira ticket automation supports auto-committing code changes after verification by using a controlled auto-commit mode, ensuring commits are properly referenced to the original ticket and acceptance criteria are validated.

To validate that code changes satisfy Jira acceptance criteria before committing, the workflow scans relevant project docs, implements changes, and checks coverage against the extracted requirements during the verification phase.

You should use the analysis-only mode for Jira ticket implementation when you need to review the extracted ticket identity, requirements analysis, and mini-plan before executing any actual code changes or commits.