igmarin/generate-tasks
generate-tasks/SKILL.md
Use when breaking down a feature or generating an implementation task list from a PRD. Output MUST follow this exact structure: (1) Task 0.0: Create feature branch with git checkout command, (2) Relevant Files section listing all files with concrete paths, (3) At least 3 TDD task groups with four sub-tasks each: X.Xa Write spec, X.Xb Run spec and verify it FAILS, X.Xc Implement, X.Xd Run spec and verify it PASSES, (4) YARD documentation task, (5) Documentation update task for README/diagrams, (6) Code review gate, (7) Save as tasks-[name].md in /tasks/ folder. Trigger words: task list, implementation plan, feature breakdown, todo list, project tasks, work plan, break down this PRD, generate tasks, feature branch, TDD, write spec, run spec fail, run spec pass.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills generate-tasksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 3:11 AM59.4s3 files scanned
SKILL.md
- name:
- generate-tasks
- license:
- MIT
- description:
- >
- Output MUST follow this exact structure:
- (1) Task 0.0: Create feature branch with git
- (3) At least 3 TDD task groups with four sub-tasks each:
- X.Xa Write spec, X.Xb Run spec
- gate, (7) Save as tasks-[name].md in /tasks/ folder. Trigger words:
- task list,
Generating a Task List from Requirements
Output Requirements (MUST Follow)
Task 0.0 is ALWAYS "Create feature branch" unless user explicitly says otherwise.
Each sub-task MUST be a single, clear action completable in 2-5 minutes.
Sub-tasks MUST include exact file paths, not vague references.
OUTPUT MODE:
If the user asks for strategy, sequencing, phases, or approach, produce a phased plan first.
If the user asks for implementation tasks, checklist, or exact steps, produce the detailed mode.
Every generated task list MUST contain the following elements:
- Task 0.0 — "Create feature branch" with checkout command (e.g.,
git checkout -b feature/name) - Relevant Files section — All files to create/modify with concrete paths, listed before Tasks
- TDD quadruplets — At least 3 implementation groups with four sub-tasks each:
X.XaWrite spec atspec/...X.XbRun spec — verify it failsX.XcImplement atapp/...X.XdRun spec — verify it passes
- YARD parent task — Add YARD docs to new/changed public API; name each file (skill: yard-documentation)
- Documentation update task — Update README, diagrams (Mermaid, ADRs), domain docs; list concrete paths
- Code review gate — Self-review via rails-code-review; fix blockers before opening PR
- Save location —
tasks-[feature-name].mdin/tasks/folder
See TASK_TEMPLATES.md for full templates.
Extended Resources (Load When Needed)
Load these files only when their specific guidance is required:
- HEURISTICS.md — Use when deciding the first spec to write for a given change type (endpoint, service, job, engine, bug fix)
- TASK_TEMPLATES.md — Use when you need the full template structure for phased plans or detailed checklists
Process
- Analyze: Extract Functional Requirements and Goals from the PRD, or use the feature description. Identify scope and main work areas.
- Detect work type: Rails monolith, engine, API-only, background job, or external integration — affects spec paths and follow-up skills.
- Relevant Files: List files to create or modify including tests, docs, and diagrams. Infer test command (
bundle exec rspecornpm test). - Save: Save as
tasks-[feature-name].mdin/tasks/. Use the same[feature-name]as the PRD if one was provided. - Verify: Re-read the saved file and confirm all of the following:
- Task
0.0creates the feature branch Relevant Filessection is present- At least 3 implementation task groups use the full TDD sequence: write spec -> run fail -> implement -> run pass
- YARD, documentation, and code-review parent tasks appear after implementation work
- Task
Rails-First Slice Heuristics
See HEURISTICS.md for the full change-type → first-slice mapping table.
Pitfalls
| Problem | Correct approach | |---------|------------------| | Dependencies out of order | A task must never reference something created in a later task | | No README/diagram/doc paths when integrators need updates | List concrete doc paths in Relevant Files |
Integration
| Skill | When to chain | |-------|---------------| | create-prd | Generate PRD first, then derive tasks from it | | rails-tdd-slices | When planning the best first failing spec for a Rails change | | ticket-planning | When the same initiative also needs ticket drafts | | rails-bug-triage | When the request starts from a bug report |
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026