Task workflow skills
Refine, Plan, Act, Consolidate
The Task workflow skills are a set of utilities that support any developer through a standard development task, from fetching the ticket to handing the finished code over to review.
They are based on the RPAC pattern: Refine, Plan, Act, Consolidate. Misunderstandings surface in a reviewable document before any code is written, and a failed attempt costs a retry from the last file, not the whole task.
Each phase runs in a fresh session and hands over a file, not chat history, so the context stays sharp.
fetch-ticket
Every task starts with a ticket. This skill downloads it from Jira, GitHub, Azure DevOps or similar into a self-contained TICKET.md, attachments and linked tickets included. No tracker? Write the file by hand and the workflow stays the same.
refine-ticket
Defines the WHAT. The agent checks the ticket against the actual codebase and interviews you, one question at a time, each with a recommended answer. No silent assumptions: you decide. The result is a validated REQUIREMENTS.md.
create-implementation-plan
Defines the HOW. The agent studies the code, settles the technical decisions with you and writes a self-contained PLAN.md that a fresh session can execute step by step.
Execute the plan
The Act phase needs no skill at all. Open a fresh session and ask the agent to execute the plan: everything it needs is in PLAN.md. Ask it to run your project's checks too, so it verifies its own work.
fresh-eyes-review
First step of Consolidate: before handing over, let a sub-agent with a clean context review the changeset. It catches what the session that wrote the code misses.
handover
Closes the task. Give it a ticket id, or nothing at all, and it finds the task's planning files, gathers the decisions made along the way, from the ticket to the session itself, matches the plan against the actual diff and writes a HANDOVER.md: a paste-ready PR description with the decisions worth knowing, where to look and what's still open, so reviewers never reconstruct intent from the diff.
Extra workflow skills
Not part of the main flow, but handy when the task calls for them.
create-manual-test-instructions
Turns the requirements into a concise MANUAL-TEST.md a non-author can follow: what changed, how to get there, before vs after, and what to verify.
review-ticket
A triage glance before anyone picks a ticket up: compares it against the codebase and reports whether it's ready, plus the questions worth asking whoever owns the requirements. Each question survived an adversarial hunt for its answer across code, tracker, designs and docs, so you're never asked what the sources could have answered. Verdict and briefing land in a TICKET-REVIEW.md next to the ticket.
check-ticket-implementation
Answers one question: how much of this ticket is already built? It splits the ticket into individual requirements and judges each one against the code, so the verdict lands per requirement instead of on the ticket as a whole: done, partially done, not done, or not verifiable from the code, each with a short note and the file:line where it was checked.
The report goes into a TICKET-STATUS.md, headed by the tally and the requirements that need attention. Useful when you pick up a branch someone else started, or before you call a ticket finished. It writes that one file and nothing else: your code and the ticket stay untouched.