generate-tasks

Compile structured Rails implementation task plans from PRDs or feature descriptions.

22|6|Updated Mar 11, 2026

Search Tags:#planning #documentation #tasks #prd #generate #rails

Ready to run

npx skills add https://github.com/igmarin/rails-agent-skills --skill generate-tasks-igmarin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-tasks
Source: https://github.com/igmarin/rails-agent-skills/tree/main/generate-tasks
Command: npx skills add https://github.com/igmarin/rails-agent-skills --skill generate-tasks-igmarin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates a user's PRD or feature description into a structured, actionable task plan. It helps teams break high-level requirements into concrete, auditable steps that guide implementation, testing, and documentation.

Core Features & Use Cases

Generate phased plans or detailed implementation checklists from a PRD or feature description.
Include exact file paths, related files, and gating steps (tests, YARD, docs) to ensure traceability.
Produce outputs suitable for README updates, architecture diagrams, and PR self-reviews.

Quick Start

Provide a PRD or feature description and I will generate a phased task plan or a detailed implementation checklist with exact file paths.

Frequently Asked Questions about generate-tasks

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

FAQPage Schema

How do I convert a PRD into actionable tasks for a Rails implementation team?▼

Breaking down requirements involves translating a PRD into a detailed implementation checklist with exact file paths. It enforces HARD-GATE discipline by verifying the existence of tests, running them, and ensuring they fail for the correct reason before implementation.

What is a HARD-GATE discipline when planning Rails implementation tasks?▼

Yes, you can generate task plans for Rails monoliths, engines, and API surfaces. The structured plan adapts to these architectures by providing exact file paths, related files, and gating steps tailored to each specific Rails component.

How do I structure implementation tickets from a feature description?▼

A generated implementation plan includes exact file paths, related files, and gating steps for tests and documentation. It also produces outputs suitable for architecture diagrams and PR self-reviews to ensure comprehensive code quality and traceability.

Does this task planning approach work for Rails engines and API surfaces?▼

No specific dependencies are required to generate the task plan structure itself. You only need to provide a PRD or feature description to receive a phased plan with exact file paths and gating steps for your Rails implementation.