implement-plan

Generate a file-level implementation plan and AC-to-test map from a Jira issue and linked artefacts.

Updated May 16, 2026
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill implement-plan-cedricfarinazzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-execution/skills/implement-plan
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill implement-plan-cedricfarinazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This sub-skill translates a Jira issue and its linked artefacts into a concrete, actionable implementation plan with an acceptance-criteria-to-test map.

Core Features & Use Cases

  • Generate a file-level plan mapping tasks, order, and ownership across data, service, API, frontend, and tests.
  • Create an AC→test map aligning acceptance criteria with test cases, including edge cases.
  • Read the Jira ticket, ADR, PRD, Specs UI, and linked QA bugs to ensure plan accuracy and traceability.
  • Post the plan as a phase marker on the Jira issue so progress is resumeable by the orchestrator.

Quick Start

Provide a concrete implementation plan for the active ticket by reading the Jira issue, ADR, PRD, Specs UI, and linked QA bugs, and post the plan using the designated phase marker.

Frequently Asked Questions about implement-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan from a Jira ticket and linked artefacts?

To generate an implementation plan from a Jira ticket, this skill reads the issue alongside linked ADRs, PRDs, Specs UI, and QA bugs to produce a file-level plan and post a resumeable phase marker on the issue.

How do I map Jira acceptance criteria to test cases?

Mapping Jira acceptance criteria to test cases is done by aligning the ticket's ACs with specific test cases and edge cases, creating a structured AC-to-test map for the implementation plan.

What is the best way to plan file-level implementation tasks across frontend and service layers?

Planning file-level implementation tasks across frontend and service layers involves mapping the execution order and ownership across data, service, API, and frontend components based on linked Jira artefacts.

Can I use ADRs and PRDs to ensure implementation plan traceability?

Yes, you can use ADRs and PRDs to ensure implementation plan traceability by reading these linked artefacts alongside the Jira issue to surface design decisions and align the file-level plan accurately.

Does the implementation plan automatically update the Jira issue for progress tracking?

Yes, the implementation plan updates the Jira issue by posting the generated plan as a designated phase marker, allowing the orchestrator to resume progress tracking directly within the ticket.