skills.rest
mattfletcher94
mattfletcher94COMMUNITY
Explore all skills by this author →
WebsiteGitHub

festina-rework

Return finalized tasks to In Progress with structured issue reports.

1|Updated Feb 26, 2026
Search Tags:#git#workflow#task-management#issue-report#festina-lente#rework#plan.xml
One-click install
npx skills add https://github.com/mattfletcher94/festinalente --skill festina-rework
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: festina-rework
Source: https://github.com/mattfletcher94/festinalente/tree/main/apps/festinalente/src/content/skills/festina-rework
Command: npx skills add https://github.com/mattfletcher94/festinalente --skill festina-rework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the rework workflow by returning finalized tasks to In Progress and attaching a structured issue report to guide remediation.

Core Features & Use Cases

  • Structured issue collection (type, severity, description, and reproduction steps) to ensure consistent remediation records.
  • Plan and iteration updates: adds an issue block to the plan.xml and advances the task through the Festina workflow.
  • PR handling and commit traceability: closes related PRs if needed and records a standardized commit message.

Quick Start

Provide a task ID to rework, and the system will start collecting issues and updating the plan automatically.

Frequently Asked Questions about festina-rework

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

FAQPage Schema
How do I reopen a finalized task for rework with a structured issue report?▼

To reopen a finalized task for rework, provide the task ID to trigger automated issue collection, returning the task to In Progress with a structured report capturing type, severity, description, and reproduction steps.

What is the best way to document QA findings and design gaps after task finalization?▼

Documenting QA findings after finalization involves adding a structured issue block to plan.xml, advancing the task through the Festina workflow, and ensuring consistent remediation records for design gaps.

How do I update plan.xml iterations when returning a task to In Progress?▼

Updating plan.xml iterations requires adding an issue block during the rework flow, which advances the task through the workflow and maintains traceable plan updates for issue capture.

Can I close related PRs automatically when starting a rework workflow?▼

Yes, the rework workflow handles PR traceability by closing related PRs if needed and recording a standardized commit message when returning a finalized task to In Progress.

What information do I need to provide to start collecting issues for task rework?▼

To start collecting issues for task rework, you need to provide a task ID, and the system will automatically begin collecting issue details and updating the plan.

Why does a finalized task need an issue report instead of just reopening it?▼

A finalized task needs an issue report to ensure consistent documentation and traceable plan updates, capturing the issue type, severity, and reproduction steps to guide remediation.

Related Skills

Explore More Software Engineering Skills→
Ting-s515Ting-s515

task-session

Generate cross-shell Claude Code startup commands for a task-list ID.

Community
Intermediate
mattfletcher94mattfletcher94
1

festina-create

Create product and engineering tasks via guided Q&A and commit them to Backlog.

Community
Advanced
1ambda1ambda
2

git-workflow

Automate Git commit messages, pull requests, and branch naming.

Community
Intermediate
pwnk77pwnk77
59

Progress Tracker

Track task completion and generate automated project status reports.

Community
Intermediate