epic-task-generation

Breaks epics into technical tasks and generates OpenProject work package scripts.

Updated Jan 31, 2023
One-click install
npx skills add https://github.com/Briian3306/Transporte --skill epic-task-generation-briian3306
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-task-generation
Source: https://github.com/Briian3306/Transporte/tree/main/ibarra-app/.agents/skills/epic-task-generation
Command: npx skills add https://github.com/Briian3306/Transporte --skill epic-task-generation-briian3306

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a large product epic into concrete, estimable technical tasks and then creating them in OpenProject is slow and error-prone. This Skill structures the breakdown into a reviewable Markdown plan and, only after explicit approval, generates a ready-to-run PowerShell upload script plus curl commands for OpenProject work package operations. ## Core Features & Use Cases - Two-stage epic breakdown: Stage 1 writes a task proposal (titles, descriptions, story points) to a new Markdown file and stops; Stage 2 generates upload_tasks.ps1 only after explicit user approval. - OpenProject API operations: Builds curls for creating, updating, and searching work packages, adding comments, managing watchers, assigning tasks to sprints, and uploading attachments. - Safety guardrails: Never executes write operations (POST/PATCH/DELETE); only read-only GETs may run when a .env token exists, and the token is never exposed in chat. - Use Case: A product owner pastes an epic's title, description, ID, and project; the Skill produces a story-pointed task list in Markdown, and after approval delivers a PowerShell script the developer runs locally to create all tasks in OpenProject. ## Quick Start Ask the agent to break down your epic into technical tasks by providing the epic title, description, work package ID, and project name.

Frequently Asked Questions about epic-task-generation

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

FAQPage Schema
How do I break down an epic into technical tasks?▼

Provide the epic title, description, work package ID, and project name. The Skill reviews the relevant repo modules, decomposes the epic into story-pointed tasks, and writes the proposal to a new Markdown file for your review before anything else happens.

How do I create OpenProject work packages from a task list?▼

After you explicitly approve the task proposal, the Skill generates an upload_tasks.ps1 PowerShell script with one curl block per task. A developer runs it locally; the agent never executes write operations itself.

Can the agent add a task to a sprint or comment on a work package?▼

It builds the correct curl commands for sprint assignment, comments, watchers, and attachments, but only read-only GET requests may be executed by the agent. All POST, PATCH, and DELETE commands are handed to the developer to run.

Where does the OpenProject API token come from?▼

The token lives in a .env file inside the skill folder as OPENPROJECT_AUTH, loaded by scripts at runtime. It is never hardcoded, printed, or pasted into chat, and if the file is missing the agent asks you to create it.

When should this Skill not be used?▼

Do not use it to implement the epic's actual product code; it only handles task breakdown and OpenProject operations. It also will not invent IDs, lockVersions, or project names you have not provided.