igmarin/agnostic-planning-skills

generate-tasks

Use when breaking a feature or approved PRD into an implementation task list. Trigger words: task list, implementation plan, feature breakdown, generate tasks, TDD tasks, break down this PRD.

First seen Jun 19, 2026

Installation

$ npx skills add igmarin/agnostic-planning-skills --skill generate-tasks

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from igmarin/agnostic-planning-skills · top by installs.

npx skills add igmarin/agnostic-planning-skills

Browse all from igmarin/agnostic-planning-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
More metadata
version
1.0.0
user-invocable
true

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,630 B
  • docs SUMMARY.md 213 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 25 installs

SKILL.md

Generating a Task List from Requirements

HARD-GATE

DO NOT skip Task 0.0 (create the feature branch).
DO NOT combine TDD sub-tasks into a single task.
DO NOT generate tasks from an unapproved PRD.

Quick Reference

  • Task 0.0: create feature branch.
  • Output: /tasks/tasks-[feature-name].md.
  • Auto-detect test command, source dir, test dir, doc tool.
  • Validate test command before full generation.

Workflow

1. Project Detection

Detect conventions using config files (see [TESTCOMMANDS.md](./TESTCOMMANDS.md)). Identify source and test directories.

2. Validation

Run detected test command; if it fails, confirm with user.

3. Requirements Analysis

Break down the feature/PRD:

  • Identify user-visible behaviors.
  • Choose a smallest slice (first-slice heuristics) for TDD.
  • Group behaviors into parent task groups.

4. Generate Task List

Create /tasks/tasks-[feature-name].md using the template in [TASKTEMPLATES.md](./TASKTEMPLATES.md). Each parent group follows TDD quadruplet (write failing test, confirm fail, implement, confirm pass).

5. Final Validation

Review tasks for coverage, correctness, and file paths.

Integration

Skill When
create-prd Feeds requirements
estimate-tasks After tasks generated