implement-plan

Coordinate Jira-driven implementation by traversing Taskwarrior task trees and applying design specs.

4|1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill implement-plan-gtheys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/gtheys/pi-my-rifle-ext/tree/main/skills/implement-plan
Command: npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill implement-plan-gtheys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the execution of Jira-approved implementation specs by driving work from Taskwarrior, aligning design notes with actionable phases and subtasks.

Core Features & Use Cases

  • Plan-driven execution: builds a structured, phase-by-phase workflow from a Jira spec and its related task tree.
  • Resume & verification: supports resuming mid-flight, enforces phase/subtask verification gates, and records progress back to the spec.
  • Spec-driven coordination: reads the approved spec file, navigates to the correct workspace, and advances tasks in order.

Quick Start

Provide a Jira ID (e.g., DP-121) and I will locate the spec, generate the execution plan, and drive phase-by-phase work through Taskwarrior until completion.

Frequently Asked Questions about implement-plan

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

FAQPage Schema
How do I execute Jira implementation specs phase by phase using Taskwarrior?

Executing Jira implementation specs phase by phase requires a Jira ID to resolve the approved spec and traverse a Taskwarrior task tree. This applies design notes to actionable phases and subtasks, enforcing verification gates and recording progress back to the spec.

Can I resume Taskwarrior phase execution if my Jira implementation work is interrupted?

Yes, you can resume Taskwarrior phase execution after an interruption. The process supports resuming mid-flight by navigating the task tree, identifying the current phase, and continuing subtask progression while enforcing verification gates until the Jira spec is complete.

What do I need to start driving approved design specs from a Jira ID?

To start driving approved design specs, you need a valid Jira ID and a corresponding approved spec file in your notes. The workflow resolves the Jira ID, reads the spec, navigates the workspace, and generates the execution plan for Taskwarrior.

How does spec-driven execution handle subtask progression and verification gates?

Spec-driven execution handles subtask progression by traversing the Taskwarrior task tree and applying design specs in order. It enforces verification gates between phases, advancing tasks only when previous subtasks are verified, and records the completion state back to the spec.

Does this approach work without a Jira ID to coordinate the implementation plan?

No, this approach demands a Jira ID as input to coordinate implementation work. The Jira ID is strictly required to locate the related approved spec file, resolve the design notes, and generate the structured phase-by-phase execution plan in Taskwarrior.