What is create-issues-from-text?

A work-breakdown helper that turns a complex assignment into separate, structured tracker issues. It preserves the original assignment and organizes the work into independently deliverable steps.

Use it to analyze scope, identify dependencies, create one issue per implementation step, assign the issues to the current user, and apply relevant labels.

It removes the effort of deciding how to split a large task and recording each piece consistently. It also keeps related work connected when an assignment spans several parts of an application.

create-issues-from-text — Skill for Claude Code and Codex by pekral

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add pekral/cursor-rules --skill create-issues-from-text

Clone the repo

git clone --depth 1 https://github.com/pekral/cursor-rules

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pekral/cursor-rules/create-issues-from-text/github.svg)](https://agentmods.dev/skills/pekral/cursor-rules/create-issues-from-text)

Your own site

<a href="https://agentmods.dev/skills/pekral/cursor-rules/create-issues-from-text"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/create-issues-from-text/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pekral/cursor-rules/create-issues-from-text"><img src="https://agentmods.dev/badge/skills/pekral/cursor-rules/create-issues-from-text.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 663 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00663
Opus 5.5	$0.00006	$0.00265
Sonnet 5.5	$0.00003	$0.00133
Haiku 4.5	$0.00002	$0.00066

Measured 1mo ago against content hash bbbc35b78ddb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-issues-from-text scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/create-issues-from-text/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Issues from Text

Purpose

Split a complex assignment into multiple clear, structured issues.

Constraints

Preserve original assignment (store in parent or first issue)
Do not implement code
Assign all issues to current user
Use CLI tools

Execution

1. Analyze Assignment

Understand scope and dependencies
Identify logical implementation steps

2. Propose Breakdown

List steps with short descriptions
Proceed directly to step 3; do not gate on a confirmation round when the breakdown is unambiguous

3. Create Issues

One issue per step
Ensure each is independently deliverable
Assign the most relevant existing label to each issue (per @rules/compound-engineering/general.mdc Assign the most relevant existing label when creating a tracker issue)

4. Output

Return list of created issues with URLs

Issue Structure

Use the template defined in templates/issue-structure.md.

EPIC parent & sub-issues

Use this when the assignment is a cross-cutting mix of requirements spanning multiple parts of the application (e.g. backend + frontend + mobile, or schema + API + UI). Instead of a flat list of peer issues, build a parent → children tree so the whole effort is trackable from one place.

Pick (or create) the parent. When the assignment already has a tracker item, that item becomes the EPIC parent. When the assignment is a described task with no tracker item, create the parent issue first, carrying the full original assignment in its body.
Label the parent EPIC. Apply the EPIC label to the parent. Create the label once if the repository does not have it yet (gh label create EPIC --description "Tracks a cross-cutting effort split into sub-issues" --color 5319e7), then ignore the "already exists" outcome on subsequent runs.
Create one sub-issue per application area. Each sub-issue is an independently deliverable assignment (same templates/issue-structure.md structure) scoped to a single area; do not bundle two areas into one sub-issue.
Link every sub-issue back to the parent (both directions).
- In each sub-issue body, reference the parent with Part of #<parent> so the relationship is visible from the child.
- In the parent body, keep a checkable task list of the children — - [ ] #<child> per sub-issue — under a ## Sub-issues heading, so the parent shows the full breakdown and progress.
Order. Fill each sub-issue's ## Dependencies so a resolving run can pick a dependency-aware order — dependencies before dependents.
Output. Return the EPIC-labelled parent URL plus the list of linked sub-issue URLs and the planned resolve order.

Read the full file on GitHub · 62 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

templates/issue-structure.md 285 B

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 62 lines · 15 tokens per session scan A bbbc35b78ddb

Subscribe to this mod's changes

create-issues-from-text is a skill published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 663 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code PHP Project management agent-skills ai cursor-rules laravel

parallel-feature-development

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…

wshobson/agents · 105 tokens

create-issues-from-text