Convert Jira story acceptance criteria into production code with contract-based tests.
npx skills add https://github.com/flightctl/ai-workflows --skill implement-flightctl
Please help me install this Agent Skill. Skill: implement Source: https://github.com/flightctl/ai-workflows/tree/main/implement Command: npx skills add https://github.com/flightctl/ai-workflows --skill implement-flightctl
This Skill helps you convert a Jira story into working production code with contract-based tests, aligned with the project’s CI expectations, without skipping the review and validation steps that keep changes safe.
Run the implementation workflow for your Jira story by invoking the ingest phase with your issue key, for example: "Use the implement skill to ingest EDM-1234".
High-intent search queries and answers about installing and using this skill.
Converting Jira stories into tested code involves ingesting acceptance criteria, creating a plan, and executing a test-first TDD workflow with incremental commits and CI-aligned validation. Contract tests are written before the implementation to satisfy behavioral requirements.
Contract-based testing in TDD implementation means writing tests first that define expected behavior before coding. The implementation is written to satisfy these behavioral contracts, ensuring code coverage and CI validation meet the project's discovered quality thresholds.
Yes, TDD implementation works with GitHub pull requests by running the full validation suite and preparing a draft PR. It handles iterative PR review responses while maintaining strict safety around publishing and Jira modifications.
Yes, implementation planning requires Jira story read-only ingestion to pull story details and load available PRD or design context. This discovers project-specific validation commands like tests, lint, and build thresholds.
The best way to automate code coverage analysis from Jira stories is to run the project's discovered full validation suite after TDD coding. This analyzes coverage to surface behavioral gaps before publishing a draft GitHub PR.
TDD coding does not auto-advance between phases to enforce strict review and validation steps that keep changes safe. This requires manual approval before moving from planning to coding, validation, and PR publishing.
k3sdtwCreate Task, Bug, and Story issues in Jira from templates.
pradeepmouliIdentify test coverage gaps in pull requests for behavioral resilience.
YoshikemoloGenerate Git branch names and validate commit messages against Jira issues.
agentglassEnforce the Test-Driven Development cycle across Rust, Python, and TypeScript projects.
