Agent skill

To Issues

by serejaris in serejaris/personal-corp-os

Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.

MITAuto-check passedProduct & Project Management

Install To Issues

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/to-issues .claude/skills/to-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .claude/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/to-issues .agents/skills/to-issues && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .agents/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/to-issues .cursor/skills/to-issues && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .cursor/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/serejaris/personal-corp-os.git --path skills/to-issues

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/to-issues .gemini/skills/to-issues && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .gemini/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/to-issues .github/skills/to-issues && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .github/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add serejaris/personal-corp-os --skill to-issues -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install serejaris/personal-corp-os to-issues --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/to-issues .opencode/skills/to-issues && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "to-issues" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/to-issues into .opencode/skills/to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "to-issues", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: to-issues
GitHub stars: 229
Token cost: ~789 tokens
SKILL.md length: 438 words
Files: 3
Skills in repo: 36
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.

Works in 5 steps: Gather context → Explore the codebase (optional) → Draft vertical slices → …
Tasks that involve PRD writing
SKILL.md covers Process, What to build, Acceptance criteria and Depends on
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

To Issues is an agent skill from serejaris/personal-corp-os. Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `README.ru.md`).

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.

When your agent uses it

Tasks that involve PRD writing

Example prompts

“/to-issues”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Gather context
Explore the codebase (optional)
Draft vertical slices
Quiz the user
Write task files

What it can do on your machine

Read from SKILL.md and the folder at commit 95e36c3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

To Issues loads about 789 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~28
When it runs · the whole SKILL.md, loaded when a task matches: ~789

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 438 words, ~789 tokens.

Download SKILL.mdSave it as .claude/skills/to-issues/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: to-issues
description: Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.
disable-model-invocation: true

To Issues

Break a plan into independently-grabbable task files using vertical slices (tracer bullets).

Process

1. Gather context

Work from whatever is already in the conversation context. If PRD.md exists in the project folder root, read it in full. If the user points at another spec file, read that instead.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Task titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."

3. Draft vertical slices

Break the plan into tracer bullet tasks. Each task is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

<vertical-slice-rules>

Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
A completed slice is demoable or verifiable on its own
Any prefactoring should be done first

</vertical-slice-rules>

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

Title: short descriptive name
Depends on: which other tasks (if any) must complete first
User stories covered: which user stories this addresses (if the source material has them)

Ask the user:

Does the granularity feel right? (too coarse / too fine)
Are the dependency relationships correct?
Should any slices be merged or split further?

Iterate until the user approves the breakdown.

Show full SKILL.md (184 more words)Show less

5. Write task files

For each approved slice, create one markdown file under tasks/ in the project folder.

Filename: NN-slug.md where NN is 01, 02, … assigned in dependency order (blockers first, then dependents).
Slug: lowercase words separated by hyphens, derived from the task title.

Use the task file template below.

<task-template>

Title

Short descriptive title (same as the slice name).

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.

Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Acceptance criteria

Criterion 1
Criterion 2
Criterion 3

Depends on

tasks/NN-slug.md references for prerequisite tasks, one per line, or none if the task can start immediately.

</task-template>

When listing dependencies in Depends on, use paths relative to the project folder (e.g. tasks/01-roster-ingest.md). Do not modify PRD.md when writing tasks.

Files

SKILL.md and 2 other files in skills/to-issues of serejaris/personal-corp-os.

SKILL.md
README.md
README.ru.md

Open the folder on GitHubat commit 95e36c3

Compare with similar skills

To Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

To Issues compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
To Issues this skillserejaris/personal-corp-os	229	—	~789	Automated safety check: Pass	MIT	2 days ago
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Ralph Tui Create Beadssubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago
Trellis Brainstormanjiemo/SunnyBeach	178	7 repos	~4k	Automated safety check: Pass	Apache-2.0	28 days ago
Ralph Tui Create Beads Rustsubsy/ralph-tui	2.5k	1 repos	~2.8k	Automated safety check: Pass	MIT	1 mo ago
Ralph Tui Create JSONsubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
178 GitHub starsUsed in 7 repos~4k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
2.5k GitHub starsUsed in 1 repo~2.8k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Prd Generator
jamesrochabrun/skills
Generate comprehensive Product Requirements Documents (PRDs) for product managers.
216 GitHub starsUsed in 2 repos~3.8k tokens
Product & Project ManagementAuto-check passed

More from serejaris/personal-corp-os

All 36 skills in this repo

Weekly Planning
serejaris/personal-corp-os
A skill your agent uses when the user is transitioning from a completed retro into a weekly plan, choosing weekly outcomes, scheduling a full ISO week, or asking for "план на неделю", "weekly…
229 GitHub stars~2.4k tokensUpdated 2 days ago
Auto-check passed
Gh Issues
serejaris/personal-corp-os
A skill your agent uses when creating, searching, updating, or managing GitHub issues via CLI.
229 GitHub stars~1.8k tokensUpdated 2 days ago
Auto-check passed
Product Data Audit
serejaris/personal-corp-os
A skill your agent uses when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours.
229 GitHub stars~1.3k tokensUpdated 2 days ago
Auto-check passed
Tg Bot Ops
serejaris/personal-corp-os
A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.
229 GitHub stars~1.6k tokensUpdated 2 days ago
Auto-check: notes
Audit Agent Rules
serejaris/personal-corp-os
Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after…
229 GitHub stars~2.3k tokensUpdated 2 days ago
Auto-check passed
Make Landing
serejaris/personal-corp-os
Создаёт несколько вариантов дизайна 2D-поверхности (лендинг, герой, обложка, слайды): свой визуальный референс и автор на вариант, полный design.md с UTC/SHA-256 до кода, проверка в браузере…
229 GitHub stars~2.1k tokensUpdated 2 days ago
Auto-check passed

Questions about To Issues

What does To Issues do?

Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices. To Issues is an agent skill from serejaris/personal-corp-os. Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.

When should I use To Issues?

To Issues fits situations like: tasks that involve PRD writing.

How do I install To Issues in Claude Code?

Run `npx skills add serejaris/personal-corp-os --skill to-issues -a claude-code`. Or copy the skill folder (skills/to-issues in serejaris/personal-corp-os) into .claude/skills/to-issues in your project. Claude Code loads it when a task matches its description.

How do I install To Issues in Codex?

Run `npx skills add serejaris/personal-corp-os --skill to-issues -a codex`. Or copy the skill folder (skills/to-issues in serejaris/personal-corp-os) into .agents/skills/to-issues in your project. Codex loads it when a task matches its description.

Can I use To Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add serejaris/personal-corp-os --skill to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-issues, .gemini/skills/to-issues, .github/skills/to-issues and .opencode/skills/to-issues in your project.

What does To Issues need to run?

SKILL.md names no scripts, command-line tools or credentials: To Issues is instructions for the agent only.

Does To Issues access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is To Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does To Issues use?

To Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does To Issues use?

About 789 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to To Issues?

Skills that share tags, products or a category with To Issues: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Issues?

serejaris (a GitHub user) maintains it in serejaris/personal-corp-os, which has 229 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.

Source: serejaris/personal-corp-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install To Issues

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

To Issues

Process

1. Gather context

2. Explore the codebase (optional)

3. Draft vertical slices

4. Quiz the user

5. Write task files

Title

What to build

Acceptance criteria

Depends on

Files

Compare with similar skills

Similar skills

More from serejaris/personal-corp-os

Related

Questions about To Issues